<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.9 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc docmapping="yes"?>

<rfc ipr="trust200902" docName="draft-eggert-irtf-rfc2014bis-05" category="info" obsoletes="2014">

  <front>
    <title abbrev="IRTF Research Group Guidelines">IRTF Research Group Guidelines and Procedures</title>

    <author initials="L." surname="Eggert" fullname="Lars Eggert">
      <organization>NetApp</organization>
      <address>
        <email>lars@netapp.com</email>
        <uri>https://eggert.org/</uri>
      </address>
    </author>

    <date year="2018" month="November" day="23"/>

    <area>IRTF</area>
    <workgroup>Internet Research Task Force (IRTF)</workgroup>
    

    <abstract>


<t>The Internet Research Task Force (IRTF) has responsibility for organizing groups
to investigate research topics related to the Internet protocols, applications,
and technology. IRTF activities are organized into Research Groups. This
document describes the guidelines and procedures for formation and operation of
IRTF Research Groups. It describes the relationship between IRTF participants,
Research Groups, the Internet Research Steering Group (IRSG) and the Internet
Architecture Board (IAB). The basic duties of IRTF participants, including the
IRTF Chair, Research Group Chairs and IRSG members are defined.</t>

<t>This document obsoletes RFC2014.</t>



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>This document defines guidelines and procedures for Internet Research Task Force
(IRTF) Research Groups. It obsoletes <xref target="RFC2014"/>, which originally documented
them. The IRTF focuses on longer term research issues related to the Internet,
while its parallel organization, the Internet Engineering Task Force (IETF),
focuses on shorter term issues of engineering and standards making.</t>

<t>The IRTF is composed of a number of focused, long-term, small Research Groups.
These groups work on topics related to Internet protocols, applications,
architecture and technology. Research Groups are expected to have the stable,
long-term membership needed to promote the development of research collaboration
and teamwork in exploring research issues. Participation is by individual
contributors, rather than by representatives of organizations.</t>

<t>The IRTF is managed by the IRTF Chair in consultation with the Internet Research
Steering Group (IRSG). The IRSG membership includes the IRTF Chair, the chairs
of the various Research Groups and possibly other individuals
(“members-at-large”) from the research community.</t>

<t>The IRTF Chair is appointed by the Internet Architecture Board (IAB)
<xref target="RFC2850"/><xref target="IAB"/>, the Research Group chairs are appointed as part of the
formation of Research Groups (as detailed below) and the IRSG members-at-large
are chosen by the IRTF Chair in consultation with the rest of the IRSG and on
approval by the IAB.</t>

<t>In addition to managing the Research Groups, the IRSG MAY from time to time hold
topical workshops focusing on research areas of importance to the evolution of
the Internet, or more general workshops to, for example, discuss research
priorities from an Internet perspective.</t>

<t>This document defines procedures and guidelines for the formation and operation
of Research Groups in the IRTF. The duties of the IRTF Chair, the Research Group
Chairs and IRSG members are also described; the first is also described in more
detail in <xref target="RFC7827"/>.  Except for members-at-large of the IRSG, there is no
general participation in the IRTF, only participation in a specific Research
Group. However, since around 2010, the IRTF has begun to hold “open meetings”
during IETF meetings <xref target="IRTFOPEN"/>, and a mailing list was created for discussion
of IRTF-wide topics <xref target="IRTF-DISCUSS"/>, both allowing the community to engage with
the IRTF.</t>

<t><xref target="RFC4440"/> provides additional important background information that the
readers of this document should familiarize themselves with. <xref target="RFC7418"/>
provides an introduction to the IRTF for IETF participants, focusing on the
differences between the two organizations.</t>

<t>The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
“SHOULD NOT”, “RECOMMENDED”,  “MAY”, and “OPTIONAL” in this document are to be
interpreted as described in <xref target="RFC2119"/>.</t>

<section anchor="irtf-approach" title="IRTF Approach">

<t>The reader is encouraged to study The Internet Standards Process <xref target="RFC2026"/> to
gain a complete understanding of the philosophy, procedures and guidelines of
the IETF and its approach to standards making.</t>

<t>The IRTF does not set standards, and thus has somewhat different and
complementary philosophy and procedures. In particular, an IRTF Research Group
is expected to be long-lived, producing a sequence of “products” over time. The
products of a Research Group (often abbreviated as “RG”) are research results
that may be disseminated by publication in scholarly journals and conferences,
as white papers for the community, as Informational RFCs, and so on. In
addition, it is expected that any concrete technologies developed in a Research
Group will be brought to the IETF as input to IETF Working Group(s) or in the
form of birds-of-a-feather (BoF) sessions for possible standardization. However,
Research Group input carries no more weight than other community input, and goes
through the same standards setting process as any other proposal.</t>

<t>IRTF Research Groups are formed to encourage research in areas of importance to
the evolution of the Internet. Clearly, anyone may conduct such research,
whether or not they are members of a Research Group. The expectation is that by
sponsoring Research Groups, the IRTF can foster cross-organizational
collaboration, help to create “critical mass” in important research areas, and
add to the visibility and impact of the work.</t>

<t>IRTF Research Groups may have open or closed memberships. Limited membership may
be advantageous to the formation of the long term working relationships that are
critical to successful collaborative research. However, limited membership MUST
be used with care and sensitivity to avoid unnecessary fragmentation of the work
of the research community. Allowing limited membership is in stark contrast to
IETF Working Groups, which are always open; this contrast reflects the different
goals and environments of the two organizations – research vs. standards
setting.</t>

<t>To ameliorate the effects of closed membership, all Research Groups are REQUIRED
to regularly report progress to the community, and are encouraged to hold
occasional open meetings (most likely co-located with IETF meetings). In
addition, the IRTF may host open plenaries at regular IETF meetings during which
research results of interest to the community are presented. Finally, multiple
Research Groups working in the same general area may be formed, if appropriate.</t>

<t>Even more than the IETF, the work of the IRSG is expected to be marked by
informality. The goal is to encourage and foster valuable research, not to add
burdensome bureaucracy to the endeavor.</t>

</section>
<section anchor="irtf-and-intellectual-property-rights" title="IRTF and Intellectual Property Rights">

<t>The IRTF follows the IETF Intellectual Property Rights (IPR) disclosure rules,
as described in Section 3.2 of <xref target="RFC5743"/>. This is a summary of these rules as
they relate to IRTF research group discussions, mailing lists and Internet
Drafts:</t>

<t><list style="symbols">
  <t>If a participant includes their own or their employer’s IPR in a contribution
to an IRTF research group, then they must file an IPR disclosure with the
IETF.</t>
  <t>If a participant recognizes their own or their employer’s IPR in someone
else’s contribution and they are participating in the discussions in the
research group relating to that contribution, then they must file an IPR
disclosure with the IETF. Even if they are not participating in the
discussion, the IRTF still requests that they file an IPR disclosure with the
IETF.</t>
  <t>Finally, the IRTF requests that a participant file an IPR disclosure with the
IETF if they recognize IPR owned by others in any IRTF contribution.</t>
</list></t>

<t>Participants may file an IPR disclosure here:
http://www.ietf.org/ipr/file-disclosure</t>

<t>See <xref target="RFC8179"/> for definitions of “IPR” and “contribution” and for the
detailed rules (substituting “IRTF” for “IETF”).</t>

</section>
</section>
<section anchor="research-group-formation" title="Research Group Formation">

<t>Research Groups are the activity centers in the IRTF. A Research Group is
typically created to address a research area related to Internet protocols,
applications, architecture or technology area. Research Groups have the stable,
long-term membership needed to promote the development of research collaboration
and teamwork in exploring research issues. Participation is by individual
contributors, rather than by representatives of organizations.</t>

<t>A Research Group may be established at the initiative of an individual or group
of individuals. Anyone interested in creating an IRTF Research Group MUST submit
a charter for the proposed group to the IRTF Chair along with a list of proposed
founding members. The charter SHALL be reviewed by the IRSG and then forwarded
to the IAB for approval. If approved, the charter is placed on the IRTF Web
site.</t>

<t>This process allows the IRTF Chair considerable freedom in how to decide to
charter new work, and different approaches have been tried. One approach seems
to have worked well recently, and is therefore briefly described here as an
example: Under this approach, the IRTF Chair permits the proponents of new
Research Groups to start a mailing list under the irtf.org domain, schedule
meetings during IETF weeks and elsewhere for their new group, and otherwise act
as if they were already formally chartered. These RGs are referred to as
“Proposed RGs” in the IETF Datatracker, on the meeting agenda, etc. and while
they often create a wiki page for themselves, their charter is not posted on the
IRTF web site, in order to distinguish them from officially chartered RGs. After
roughly a year, the IRTF Chair reviews the progress, activity levels and general
operation of the Proposed RG, and decides to formally charter or abandon the
effort.</t>

<section anchor="criteria-for-formation" title="Criteria for Formation">

<t>In determining whether it is appropriate to create a Research Group, the IRTF
Chair, the IRSG and the IAB SHALL consider several issues:</t>

<t><list style="symbols">
  <t>Is the research area that the Research Group plans to address clear and
relevant for the Internet community?</t>
  <t>Will the formation of the Research Group foster work that would not be done
otherwise? For instance, membership drawn from more than a single institution,
more than a single country, and so on, is to be encouraged.</t>
  <t>Do the Research Group’s activities overlap with those of another Research
Group? If so, it may still be appropriate to create the Research Group, but
this question must be considered carefully since subdividing efforts often
dilutes the available technical expertise.</t>
  <t>Is there sufficient interest and expertise in the Research Group’s topic with
at least several people willing to expend the effort that is likely to produce
significant results over time? Research Groups require considerable effort,
including management of the Research Group process, editing of Research Group
documents, and contribution to the document text.</t>
</list></t>

<t>The Internet Architecture Board (IAB) SHALL also review the charter of the
proposed Research Group to determine the relationship of the proposed work to
the overall architecture of the Internet Protocol Suite.</t>

</section>
<section anchor="charter" title="Charter">

<t>A charter is a contract between a Research Group and the IRTF to conduct
research in the designated area. Charters MAY be renegotiated periodically to
reflect changes to the current status, organization or goals of the Research
Group.</t>

<t>The formation of a Research Group requires a charter, which is initially
negotiated between a prospective Research Group Chair and the IRTF Chair. When
the prospective Chair and the IRTF Chair are satisfied with the charter form and
content, it becomes the basis for forming a Research Group.</t>

<t>A IRTF Research Group charter consists of five sections:</t>

<t><list style="numbers">
  <t>Research Group Name  <vspace blankLines='1'/>
A Research Group name SHOULD be reasonably descriptive or identifiable.
Additionally, the group SHALL define a short acronym (consisting of printable
US-ASCII characters) to reference the group in the IRTF directories, mailing
lists, and general documents. The name and acronym MUST NOT conflict with any
past or existing IETF or IRTF names and acronyms. It is helpful if the
acronym ends with “RG”, to help distinguish Research Groups from IETF Working
Groups.</t>
  <t>Chair(s)  <vspace blankLines='1'/>
The Research Group may have a small number of Chair(s) to perform the
administrative functions of the group. The email address(es) of the Chair(s)
SHALL be included.</t>
  <t>Mailing list(s)  <vspace blankLines='1'/>
Each Research Group SHALL have an address (possibly a Chair’s) for members of
the Internet community to send queries regarding the Research Group. For
instance, for requests to join the group.  <vspace blankLines='1'/>
A Research Group, whether limited-membership or open, SHALL have an Internet
mailing list open to all interested parties. This list is used for an open
discussion of the issues and announcements of results as they become
available. Included SHOULD be the address to which an interested party sends
a subscription request for the interest list and the procedures to follow
when subscribing, and the location of the interest mailing list archive. It
is RECOMMENDED that this mailing list be hosted under the irtf.org domain, so
its archive will remain available in the future.  <vspace blankLines='1'/>
It is expected that a limited-membership Research Group MAY also have a
mailing list limited to the regular meeting participants on which substantial
part of the work of a Research Group is likely to be conducted via e-mail.</t>
  <t>Membership Policy  <vspace blankLines='1'/>
The Charter MUST define the membership policy (whether open or limited), and
the procedure to apply for membership in the group. While limited membership
is permitted, it is in no way encouraged or required.</t>
  <t>Description of Research Group  <vspace blankLines='1'/>
The focus and intent of the group SHALL be set forth briefly. By reading this
section alone, an individual should be able to decide whether this group is
relevant to their own work. The first paragraph SHOULD give a brief summary
of the research area, basis, goal(s) and approach(es) planned for the
Research Group. This paragraph will frequently be used as an overview of the
Research Group’s effort.  <vspace blankLines='1'/>
To facilitate evaluation of the intended work and to provide on-going
guidance to the Research Group, the charter SHALL describe the proposed
research and SHALL discuss objectives and expected impact with respect to the
Internet Architecture.</t>
</list></t>

</section>
</section>
<section anchor="research-group-operation" title="Research Group Operation">

<t>Research Groups are autonomous and each determines most of the details of its
own operation with respect to session participation, reaching closure, norms of
behavior, etc. Since the products are research results, not Internet standards,
consensus of the group is not required. Rather, the measure of success is the
quality and impact of the research results.</t>

<t>A number of procedural questions and issues will arise over time, and it is the
function of the Research Group Chairs to manage the group process, keeping in
mind that the overall purpose of the group is to make progress towards realizing
the Research Group’s goals and objectives.</t>

<t>There are few hard and fast rules on organizing or conducting Research Group
activities, but a set of guidelines and practices have evolved over time that
have proven successful. These are listed here, with actual choices typically
determined by the Research Group members and a Chair.</t>

<section anchor="mtgplan" title="Meeting Planning">

<t>For coordinated, structured Research Group interactions, a Chair MUST publish to
the group mailing list a draft agenda well in advance of the actual meeting. The
agenda needs to contain at least:</t>

<t><list style="symbols">
  <t>The items for discussion;</t>
  <t>The estimated time necessary per item; and</t>
  <t>A clear indication of what documents the participants will need to read before
the meeting in order to be well prepared.</t>
</list></t>

<t>A Research Group will conduct much of its business via its electronic mail
distribution list(s). It is also likely to meet periodically to accomplish those
things that are better achieved in more interactive meetings, such as
brainstorming, heated altercations, etc. Meetings MAY be scheduled as telephone
conference, video teleconference, or face-to-face (physical) meetings.</t>

<t>It is REQUIRED that all Research Group meetings be recorded in written minutes,
to keep informed members who were not present and the community at large and to
document the proceedings for present and future members. These minutes SHOULD
include the agenda for the meeting, an account of the high points of the
discussion, and a list of attendees. Unless the Research Group chair decides
otherwise, the minutes SHOULD be sent to the interest list and made available
through other channels, e.g., the IETF proceedings web pages.</t>

</section>
<section anchor="meeting-venue" title="Meeting Venue">

<t>Each Research Group SHALL determine the balance of email and face-to-face
meetings that is appropriate for making progress on its goals.</t>

<t>Electronic mail permits the easiest and most affordable participation;
face-to-face meetings often permit better focus, more productive debate and
enhanced working relationships.</t>

<t>Face-to-face meetings are encouraged to be held co-located with the regular IETF
meetings to minimize travel, since IRTF members are often also active in the
IETF, and to encourage the cross-fertilization that occurs during hallway and
after-hours interactions. Furthermore, as described above, even
limited-membership Research Groups are encouraged to hold occasional open
meetings; an IETF meeting would serve as an ideal venue for such an event.</t>

<t>Face-to-face meetings that are collocated with academic conferences or workshops
have also worked well for some Research Groups, particularly those with
substantial academic participation. Such groups are still encouraged to
occasionally collocate a meeting with an IETF meeting, in order to facilitate
the cross-fertilization between research and engineering that the IRTF is
chartered to stimulate.</t>

</section>
<section anchor="meeting-management" title="Meeting Management">

<t>The challenge of managing Research Group meetings is to balance the need for
consideration of the various issues, opinions and approaches against the need to
allow forward progress. The Research Group, as a whole, has the final
responsibility for striking this balance.</t>

</section>
</section>
<section anchor="research-group-termination" title="Research Group Termination">

<t>If, at some point, it becomes evident that a Research Group is not making
progress in the research areas defined in its charter, or fails to regularly
report the results of its research to the community, the IRTF Chair can either:</t>

<t><list style="numbers">
  <t>Require that the group recharter to refocus on a different set of problems,</t>
  <t>Request that the group choose new Chair(s), or</t>
  <t>Disband the group.</t>
</list></t>

<t>The IRTF Chair is encouraged to make this decision after consulting with the RG.
However, if the RG disagrees with the chair’s decision, it MAY appeal to the
IAB.</t>

</section>
<section anchor="staff-roles" title="Staff Roles">

<t>Research Groups require considerable care and feeding. In addition to general
participation, successful Research Groups benefit from the efforts of
participants filling specific functional roles.</t>

<section anchor="irtf-chair" title="IRTF Chair">

<t>The IRTF Chair is responsible for ensuring that Research Groups produce
coherent, coordinated, architecturally consistent and timely output as a
contribution to the overall evolution of the Internet architecture. In addition
to the detailed tasks related to Research Groups outlined below, the IRTF Chair
MAY also from time to time arrange for topical workshops attended by the IRSG
and perhaps other experts in the field.</t>

<t><list style="hanging">
  <t hangText='Planning'><vspace blankLines='1'/>
  The IRTF Chair monitors the range of activities. This may include encouraging
the formation of Research Groups directly, rather than waiting for proposals
from IRTF participants.</t>
  <t hangText='Coordination of Research Groups'><vspace blankLines='1'/>
  The IRTF Chair coordinates the work done by the various Research Groups.</t>
  <t hangText='Reporting'><vspace blankLines='1'/>
  The IRTF Chair reports on IRTF progress to the to the IAB and the wider
Internet community.</t>
  <t hangText='Progress tracking'><vspace blankLines='1'/>
  The IRTF Chair tracks and manages the progress of the various Research Groups
with the aid of a regular status report on documents and accomplishments from
the Research Group Chairs. The resulting reports are made available to the
community at large at regular intervals. The IRTF Chair MAY use the IETF
Datatracker to manage the status of Internet Drafts authored by the various
Research Groups <xref target="RFC6322"/>.</t>
</list></t>

</section>
<section anchor="irsg-member" title="IRSG Member">

<t>Members of the IRSG are responsible for advising the IRTF Chair on the
chartering of new Research Groups and other matters relating to the smooth
operation of the IRTF. They are also responsible for helping review documents
that are being published on the IRTF Stream <xref target="RFC5743"/>. In addition, most IRSG
members are also Research Group chairs.</t>

</section>
<section anchor="research-group-chair" title="Research Group Chair">

<t>A Research Group Chair is concerned with making forward progress in the areas
under investigation, and has wide discretion in the conduct of Research Group
business. A Chair MUST ensure that a number of tasks are performed, either
directly or by others assigned to the tasks. This encompasses at the very least
the following:</t>

<t><list style="hanging">
  <t hangText='Ensuring the Research Group process and content management'><vspace blankLines='1'/>
  A Chair has ultimate responsibility for ensuring that a Research Group
achieves forward progress. For some Research Groups, this can be accomplished by
having a Chair perform all management-related activities. In other Research
Groups – particularly those with large or divisive participation – it is
helpful to allocate process and/or secretarial functions to other participants,
after approval from the IRTF Chair. Process management pertains strictly to the
style of Research Group interaction and not to its content. Research Group
Chairs remain responsible for all actions a Secretary performs on their behalf.</t>
  <t hangText='Moderate the Research Group email list'><vspace blankLines='1'/>
  A Chair SHOULD attempt to ensure that the discussions on a list are relevant
and do not devolve to “flame” attacks or rat-hole into technical trivia. A Chair
SHOULD make sure that discussions on the list are summarized and that the
outcome is well documented (to avoid repetition).</t>
  <t hangText='Organize, prepare and chair face-to-face and on-line formal meetings'><vspace blankLines='1'/>
  A Chair SHOULD plan and announce meetings well in advance. (See <xref target="mtgplan"/>
for procedures.)</t>
  <t hangText='Communicate results of meetings'><vspace blankLines='1'/>
  A Chair and/or Secretary MUST ensure that minutes of a meeting are taken and
published to the participants.</t>
  <t hangText='Distribute the work'><vspace blankLines='1'/>
  It is expected that all Research Group participants will actively contribute
to the work of the group. Research Group membership is expected to be a
long-term commitment by a set of motivated members of the research community. Of
course, at any given time, more of the work is likely to be done by a few
participants with particular interests, set of skills and ideas. It is the task
of the Chair to motivate enough experts to allow for a fair distribution of the
workload.</t>
  <t hangText='Document development'><vspace blankLines='1'/>
  Research Groups produce documents and documents need authors. However,
authorship of papers related to the work of a Research Group is one of the
primary reasons that researchers become members, so finding motivated authors
should not be a problem.

It is up to the Research Group to decide the authorship of papers resulting
from Research Group activities. In particular, authorship by the entire group
is not required.
The Research Group Chair MAY use the IETF Datatracker to manage the status of
Internet Drafts authored by the group <xref target="RFC6322"/>.</t>
  <t hangText='Document publication'><vspace blankLines='1'/>
  The IRTF Chair, RG Chair and/or Secretary SHALL work with the IESG, IANA and
the RFC Editor to ensure documents to be published as RFCs conform with RFC
publication requirements, such as the conflict review defined in <xref target="RFC5742"/>
and to coordinate any editorial changes suggested by the RFC Editor.</t>
</list></t>

<t>The publication process has been changing over the years and is expected to
continue to change on occasion. In addition, the IRTF Chair has freedom to
decide how IRTF documents are reviewed and approved before being sent onward for
publication. For at least the last ten years, the detailed publication process
has been documented on a wiki page <xref target="IRTF-RFCs"/>.</t>

</section>
<section anchor="research-group-editorsecretary" title="Research Group Editor/Secretary">

<t>Taking minutes and editing jointly-authored Research Group documents often is
performed by a specifically-designated participant or set of participants
appointed by an RG Chair and approval from the IRTF Chair.</t>

</section>
</section>
<section anchor="research-group-documents" title="Research Group Documents">

<section anchor="meeting-documents" title="Meeting Documents">

<t>All relevant documents for a meeting (including the final agenda) SHOULD be
published and be made available as Internet Drafts at least two weeks before a
meeting starts. If a meeting is collocated with an IETF meeting, the agenda and
document submission deadlines communicated for that IETF meeting take
precedence.</t>

<t>It is strongly RECOMMENDED that a Research Group Chair make sure that all
meeting materials are made available via the IETF Datatracker’s proceedings
system, which also handles “interim” meetings not collocated with IETF meetings.
All relevant documents (including the final agenda and the minutes of the
meeting) SHOULD be placed there. This has the advantage that all participants
can retrieve all files and thus make sure they have all relevant documents.</t>

</section>
<section anchor="request-for-comments-rfc" title="Request For Comments (RFC)">

<t>The work of an IRTF Research Group usually results in publication of research
papers and other documents, as well as Informational or Experimental Request For
Comments (RFCs). The RFC series is the archival publication record for the
Internet community. Since 2009, IRTF RFCs have been published on a separate IRTF
Document Stream <xref target="RFC5743"/>. A document can be written by individuals in a
Research Group, by the group as a whole with a designated Editor, or by others
not involved with the IRTF. The designated author(s) need not include the group
Chair(s). Initial publication as an Internet Draft is preferred, if only to
facilitate review, before asking for RFC publication.</t>

<t>NOTE: The RFC series is a publication mechanism only and publication does not
determine the status of a document. Status is determined through separate,
explicit status labels. In other words, the reader is reminded that all Internet
Standards are published as RFCs, but NOT all RFCs specify standards.</t>

<t>The RFC’s authors are expected to work with the RFC Editor to meet all
formatting, review and other requirements that the RFC Editor, IAB or IESG may
impose. <xref target="RFC5743"/> describes the approach that Research Groups follow when
they want to publish RFCs on the IRTF Stream. In summary, after the group has
decided that a given document is ready, a Chair initiates an IRSG Review. After
approval by the IRSG, the IESG reviews the document for conflicts with the
Internet Standards Process as described in <xref target="RFC5742"/>. After the IESG review
concludes, the document undergoes final publication preparation at the RFC
Editor.</t>

</section>
</section>
<section anchor="iana-considerations" title="IANA Considerations">

<t>This document has no IANA considerations.</t>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>Security issues are not discussed in this memo.</t>

</section>
<section anchor="acknowledgments" title="Acknowledgments">

<t>This document is based on the October 1996 RFC “IRTF Research Group Guidelines
and Procedures” by A. Weinrib <xref target="RFC2014"/>, which in turn was based on the March
1994 RFC “IETF Working Group Guidelines and Procedures” by E. Huizer and D.
Crocker <xref target="RFC1603"/>.</t>

<t>Lars Eggert has received funding from the European Union’s Horizon 2020 research
and innovation program 2014-2018 under grant agreement No. 644866 (“SSICLOPS”).
This document reflects only the authors’ views and the European Commission is
not responsible for any use that may be made of the information it contains.</t>

</section>


  </middle>

  <back>

    <references title='Normative References'>





<reference  anchor="RFC2014" target='https://www.rfc-editor.org/info/rfc2014'>
<front>
<title>IRTF Research Group Guidelines and Procedures</title>
<author initials='A.' surname='Weinrib' fullname='A. Weinrib'><organization /></author>
<author initials='J.' surname='Postel' fullname='J. Postel'><organization /></author>
<date year='1996' month='October' />
<abstract><t>This document describes the guidelines and procedures for formation and operation of IRTF Research Groups.  It describes the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB).  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='8'/>
<seriesInfo name='RFC' value='2014'/>
<seriesInfo name='DOI' value='10.17487/RFC2014'/>
</reference>



<reference  anchor="RFC2119" target='https://www.rfc-editor.org/info/rfc2119'>
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1997' month='March' />
<abstract><t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='14'/>
<seriesInfo name='RFC' value='2119'/>
<seriesInfo name='DOI' value='10.17487/RFC2119'/>
</reference>



<reference  anchor="RFC2026" target='https://www.rfc-editor.org/info/rfc2026'>
<front>
<title>The Internet Standards Process -- Revision 3</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<date year='1996' month='October' />
<abstract><t>This memo documents the process used by the Internet community for the standardization of protocols and procedures.  It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='9'/>
<seriesInfo name='RFC' value='2026'/>
<seriesInfo name='DOI' value='10.17487/RFC2026'/>
</reference>



<reference  anchor="RFC8179" target='https://www.rfc-editor.org/info/rfc8179'>
<front>
<title>Intellectual Property Rights in IETF Technology</title>
<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
<author initials='J.' surname='Contreras' fullname='J. Contreras'><organization /></author>
<date year='2017' month='May' />
<abstract><t>The IETF policies about Intellectual Property Rights (IPR), such as patent rights, relative to technologies developed in the IETF are designed to ensure that IETF working groups and participants have as much information as possible about any IPR constraints on a technical proposal as early as possible in the development process.  The policies are intended to benefit the Internet community and the public at large, while respecting the legitimate rights of IPR holders.  This document sets out the IETF policies concerning IPR related to technology worked on within the IETF.  It also describes the objectives that the policies are designed to meet. This document updates RFC 2026 and, with RFC 5378, replaces Section 10 of RFC 2026.  This document also obsoletes RFCs 3979 and 4879.</t></abstract>
</front>
<seriesInfo name='BCP' value='79'/>
<seriesInfo name='RFC' value='8179'/>
<seriesInfo name='DOI' value='10.17487/RFC8179'/>
</reference>



<reference  anchor="RFC5742" target='https://www.rfc-editor.org/info/rfc5742'>
<front>
<title>IESG Procedures for Handling of Independent and IRTF Stream Submissions</title>
<author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'><organization /></author>
<author initials='R.' surname='Housley' fullname='R. Housley'><organization /></author>
<date year='2009' month='December' />
<abstract><t>This document describes the procedures used by the IESG for handling documents submitted for RFC publication from the Independent Submission and IRTF streams. </t><t>This document updates procedures described in RFC 2026 and RFC 3710.   This memo documents an Internet Best Current Practice.</t></abstract>
</front>
<seriesInfo name='BCP' value='92'/>
<seriesInfo name='RFC' value='5742'/>
<seriesInfo name='DOI' value='10.17487/RFC5742'/>
</reference>




    </references>

    <references title='Informative References'>

<reference anchor="IRTF-RFCs" target="http://trac.tools.ietf.org/group/irtf/trac/wiki/IRTF-RFCs">
  <front>
    <title>IRTF RFC Process</title>
    <author >
      <organization>IRTF</organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="IRTFOPEN" target="https://datatracker.ietf.org/group/irtfopen/about/">
  <front>
    <title>IRTF Open Meeting</title>
    <author >
      <organization>IRTF</organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="IRTF-DISCUSS" target="https://www.irtf.org/mailman/listinfo/irtf-discuss">
  <front>
    <title>IRTF General and New-Work Discussion List</title>
    <author >
      <organization>IRTF</organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>
<reference anchor="IAB" target="https://www.iab.org/about/description/">
  <front>
    <title>Internet Architecture Board Description</title>
    <author >
      <organization>IAB</organization>
    </author>
    <date year="n.d."/>
  </front>
</reference>




<reference  anchor="RFC2850" target='https://www.rfc-editor.org/info/rfc2850'>
<front>
<title>Charter of the Internet Architecture Board (IAB)</title>
<author><organization>Internet Architecture Board</organization></author>
<author initials='B.' surname='Carpenter' fullname='B. Carpenter' role='editor'><organization /></author>
<date year='2000' month='May' />
<abstract><t>This memo documents the composition, selection, roles, and organization of the Internet Architecture Board.  It replaces RFC 1601.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
</front>
<seriesInfo name='BCP' value='39'/>
<seriesInfo name='RFC' value='2850'/>
<seriesInfo name='DOI' value='10.17487/RFC2850'/>
</reference>



<reference  anchor="RFC7827" target='https://www.rfc-editor.org/info/rfc7827'>
<front>
<title>The Role of the IRTF Chair</title>
<author initials='L.' surname='Eggert' fullname='L. Eggert'><organization /></author>
<date year='2016' month='March' />
<abstract><t>This document briefly describes the role of the Chair of the Internet Research Task Force (IRTF), discusses its duties, and outlines the skill set a candidate for the role should ideally have.</t></abstract>
</front>
<seriesInfo name='RFC' value='7827'/>
<seriesInfo name='DOI' value='10.17487/RFC7827'/>
</reference>



<reference  anchor="RFC4440" target='https://www.rfc-editor.org/info/rfc4440'>
<front>
<title>IAB Thoughts on the Role of the Internet Research Task Force (IRTF)</title>
<author initials='S.' surname='Floyd' fullname='S. Floyd' role='editor'><organization /></author>
<author initials='V.' surname='Paxson' fullname='V. Paxson' role='editor'><organization /></author>
<author initials='A.' surname='Falk' fullname='A. Falk' role='editor'><organization /></author>
<author><organization>IAB</organization></author>
<date year='2006' month='March' />
<abstract><t>This document is an Internet Architecture Board (IAB) report on the role of the Internet Research Task Force (IRTF), both on its own and in relationship to the IETF.  This document evolved from a discussion within the IAB as part of a process of appointing a new chair of the IRTF.  This memo provides information for the Internet community.</t></abstract>
</front>
<seriesInfo name='RFC' value='4440'/>
<seriesInfo name='DOI' value='10.17487/RFC4440'/>
</reference>



<reference  anchor="RFC7418" target='https://www.rfc-editor.org/info/rfc7418'>
<front>
<title>An IRTF Primer for IETF Participants</title>
<author initials='S.' surname='Dawkins' fullname='S. Dawkins' role='editor'><organization /></author>
<date year='2014' month='December' />
<abstract><t>This document provides a high-level description of things for Internet Engineering Task Force (IETF) participants to consider when bringing proposals for new research groups (RGs) into the Internet Research Task Force (IRTF).  This document emphasizes differences in expectations between the two organizations.</t></abstract>
</front>
<seriesInfo name='RFC' value='7418'/>
<seriesInfo name='DOI' value='10.17487/RFC7418'/>
</reference>



<reference  anchor="RFC5743" target='https://www.rfc-editor.org/info/rfc5743'>
<front>
<title>Definition of an Internet Research Task Force (IRTF) Document Stream</title>
<author initials='A.' surname='Falk' fullname='A. Falk'><organization /></author>
<date year='2009' month='December' />
<abstract><t>This memo defines the publication stream for RFCs from the Internet Research Task Force.  Most documents undergoing this process will come from IRTF Research Groups, and it is expected that they will be published as Informational or Experimental RFCs by the RFC Editor.   This document is not an Internet Standards Track specification; it is published for informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='5743'/>
<seriesInfo name='DOI' value='10.17487/RFC5743'/>
</reference>



<reference  anchor="RFC6322" target='https://www.rfc-editor.org/info/rfc6322'>
<front>
<title>Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams</title>
<author initials='P.' surname='Hoffman' fullname='P. Hoffman'><organization /></author>
<date year='2011' month='July' />
<abstract><t>This document describes extending the IETF Datatracker to capture and display the progression of Internet-Drafts that are intended to be published as RFCs by the IAB, IRTF, or Independent Submissions Editor.  The states and annotations that are to be added to the Datatracker will be applied to Internet-Drafts as soon as any of these streams identify the Internet-Draft as a potential eventual RFC, and will continue through the lifetime of the Internet-Draft. The goal of adding this information to the Datatracker is to give the whole Internet community more information about the status of these Internet-Drafts and the streams from which they originate. This document is not an Internet Standards Track specification; it is published for informational purposes.</t></abstract>
</front>
<seriesInfo name='RFC' value='6322'/>
<seriesInfo name='DOI' value='10.17487/RFC6322'/>
</reference>



<reference  anchor="RFC1603" target='https://www.rfc-editor.org/info/rfc1603'>
<front>
<title>IETF Working Group Guidelines and Procedures</title>
<author initials='E.' surname='Huizer' fullname='E. Huizer'><organization /></author>
<author initials='D.' surname='Crocker' fullname='D. Crocker'><organization /></author>
<date year='1994' month='March' />
<abstract><t>This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG).  This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.</t></abstract>
</front>
<seriesInfo name='RFC' value='1603'/>
<seriesInfo name='DOI' value='10.17487/RFC1603'/>
</reference>




    </references>


<section anchor="changes-from-rfc2014" title="Changes from RFC2014">

<texttable>
      <ttcol align='left'>Rev</ttcol>
      <ttcol align='left'>Changes</ttcol>
      <c>-05</c>
      <c>More feedback from Niels ten Oever. Fixed typos. RFC5793 -&gt; RFC8179. Converted to kramdown-rfc2629.</c>
      <c>-04</c>
      <c>Addressed feedback from Mat Ford, Niels ten Oever and Martin Thomson.</c>
      <c>-03</c>
      <c>Changed the stream to IRTF and status to Informational, per discussion with the IAB at the Cambridge, MA retreat. Added funding acknowledgment.</c>
      <c>-02</c>
      <c>Added text about and reference to <xref target="RFC7418"/>. Add pointer to IRTF RFC process wiki. More wordsmithing.</c>
      <c>-01</c>
      <c>Use <xref target="RFC2119"/> terms instead of local definitions. Fix idnits (missing IANA section, say that we obsolete <xref target="RFC2014"/>, etc.) Update obsoleted references. Update acknowledgments. Remove text about the Internet Monthly Report (IMR). Remove text that says that a RG should have 4-5 members, and that proposed charters should include the names of such “charter members”. Add suggestion that RG acronyms end in “RG”. Change recommendation that RGs have 1-2 chairs to instead say “a small number”, to allow cases where more than two chairs are useful. Update text on IRTF RFC Stream publication <xref target="RFC5742"/><xref target="RFC5743"/>. Add text on IRTF IPR policies. Add pointers and text to <xref target="RFC4440"/> and <xref target="RFC6322"/>.</c>
      <c>-00</c>
      <c>Document contains the entire, unmodified contents of <xref target="RFC2014"/>, except for (1) boilerplate and layout changes that are due to the conversion to xml2rfc and (2) changed author information. It is being submitted so that it will be easier to view diffs of the content changes that will be introduced in subsequent versions.</c>
</texttable>

</section>


  </back>

<!-- ##markdown-source:
H4sIADH391sAA+V9W5MbR7Lee/2K9uyDZhwAeBGllaiw5REvEiPEizmkFScc
DkcBXcD0si84XY2BsFr+d+eXmXXpRg+lE+fR+7AaAt1VWVl5+fJSheVyaYZq
qN3T4tX7Dy+L9847229ui5/77rAvfj5Upaur1vnCtmXxru82rjz0zhu7Xvfu
7s/eMmW3aW1Do5e93Q5Lt9u5flhW/bBd9tvN44ePnqwrv3z4jdnYwe26/vS0
qNptZ0y1758WQ3/ww+OHD79/+NjY3lmZznRr39VucP5pgRHMses/7TAzfd8O
rm/dkEj6YP2n4mXXb1xxibevjPEDLeb/2rpribATUbmvnhb/e+g2i8J3/dC7
rae/To38QUto7H5ftbv/Y4w9DLdd/9QU9L+qJQJ+XRUveFH8kaz1V9v7/NOu
3z0t3rjher/nf7vGVvXToqbH/gfRSoOvNl3DXx16IuV2GPb+6YMHwq0Vvf6A
GEJs6Rs7VHdOpsdilu9fPvPyT/xvtJMvn8l+eR+/z6kP/2PimK1xFNvv3CBk
EBVDbzeroetqv6rcsGVymNsPsI389YNj9al6EAkykb637168mSfv7d61xWvn
BuLrf4I+sKm0gwUVn1w/R2FHMz2w6+4wPEiELZ+/unn28eZmnrifXet6W7PM
v3HH5W8kYMXzym8O3lddW/xa+eE/SfTxeFyBOiYW8tDY9kFN42Kfme5lKRMq
0dc/ndMahP2aBL0a3GYg1Sx+6mxfFs+d3/TVfiBy/wKl1z99mVC7ZjqFi2Ua
mjhqlstlYdceOzAY8+HW/RUlLG6tL8iO7LvWV+uqroZTQfINcmxb/ZOEouAd
9GboSNHuHDFmRyYC78iQQ7evNhijpo9L+mcx5FPv+44UmoR2UZB+1RXZF6LX
Lwz2lFh123Z1tzutZMOJ9OquGirYOWKhUkHDVi0NPDZvflV8uK3YtB0a1w6F
8GNN74KC3dhk7qPJ5PWpDpMM4UsSzV7+1W3NjCWlqV5Nx+cFYym31b5Yu+Ho
SJH43b3th2pT7W070DonIy3G7Inf3gzO9WC3mG7anZufr5i4/HkzI2GXJDVX
4IUr1tZXm6I8MAO77Qw5xMhNfSgxEY0ra312a6t+MXUe/KnwDrQUjWvWrpd9
Kd2WGFuuIGaVL+IORIcAqweXsFK5bKqyrJ0xf8NK+q48bFghJq/LsP5Ptu5L
Um1Uque2LxH3xx//Ren7/HlRHG8rerDrq13V2ro+RXpcaYhHjbCWObWlbzxY
2xbktMgpkAT3TdKFyvuDu1cXFoamql1RDR6bQnO5Oog4i9JENl60RJFKxUhx
X9ASFyYjxpM5GQI1SgRtv8sGACPZ35LI+KKxn+jDlZoJLI32gXzfvvNEN71q
i/aA/cbfMlG54DUvMQd55YbIP2MzhvNOLUYBOADqzi3EX7AOuZxPTcVkWhZJ
9/uenpbhb+2dY1bSgte1W5hIeJBi6CxxppTniYqmG+SV0t25utuLOG/T1hKR
NZldMRNqvGzDS6xazF53zOeJLKyKd0H92L4Qm9cneqMkM1cebG02HSlEtT4M
XU9MoOFvsY+3tsVzvdtjvHZguMF7msuLn2wguS67oyXRm0P4mNUYJNJE/lAP
QsaxGm7nDZGZNURBB5IdAAfFlqg9zE0J/r1h+2GIZPzrzvZVd/DnWwf97sib
r0nxOl58Yo43lxc63dIOyxoe8eKq2NJ2qQmOm9M0h5Z8V84QXbmHZHUV1Dky
5gv+mq2p+eOPH2Ehvvvm4efPf/xBH8FQ4NWJkdyokYSQxlksqzeLD2xscjX0
wXT9l/RwSdCT7AKRR5J3zIx+xu64fuBvmpb0tP2P7DOxKhAk47LbI0Hek/Df
EcQKY13/RDx8RW6xLCsegvSD5UpdxnQFizTk6+t/072pGsfGD/+97WqyozAB
NAv0hYzV3otRwZg0RdxHxBYs5RVZop6s1cYFI+ruuvoQXPTIqpJKFE1HXNkp
WkyTDN2CXYb73TZ7MgSFQrk4o9mTWPYCOJh00rtknIjvMCqkemeeLriqzDeB
o5nnwryg8x6kYWaEgXYv7KcoXPLkcxo2ft18yWGTLnURv5Q/CGH09MD6MfoS
VICdRsQS/xRt+Pt3j//++fOqKF78vnH7gRc4lc5cxJhImptmaDsTNmc/Nodp
xbSPLdmAs+9tgU2otgRsoo3iBa+KX7ojWWviBgkSSYqlT2nx5NcfLhLDAHDX
bndgSYYwFheIRIh0jnn8haHtgyDCrcZPac0hboLqg6m2QHiAJxEeFEcad0Py
Co0HK8oYlhhFXssjCUPwfjJeCHcw5prMHfGeVD6oVjRjIJWcNxlz1mATpcKo
ZXry5AlZJkgfWUrInmorMTiozkBocMPheFsWMWiFQt/agQ0TEV9CQHjPcuEm
5TkQn7a2ofWS4f4nu8bGuxpOCBStgkw8efTd588m0YEtSwAvIiABT73weAxI
c0MAqspquyWxoQ31EVZjjOHYzTq/T+4EjSdQc/H6482Hi4X8t3jzlv9+/+J/
fnz1/sVz/H3zy/Wvv8Y/whM3v7z9+Ct9b/Sv9Oazt69fv3jznF+mUa//7UIk
4eLtuw+v3r65/vVCBDjnHbSNVr12Bs6gJ/+tLmGkYIpAHz36njSKMPLf/iY8
uoY5tiThvDTZICgQsaM79OzcaXA/HMpTMYrwbiK001xDBLmPvyVBGUgBLSsT
QB5QcEFiQZuP15j5ord7Aqid7/a3p8UXTFuwwNhMfAVAa5Vyoe9+nFl2DvaA
hIyojg8u1OkRQoC++q5xR4hpEIYB3xuhHWy2/SmjdRIlENpvVcgOZJUWbNTP
gzoDvmaoce0E4NZk70tePkkxQ2ei9d8PkEiw6UK+GPxF0d0Bq5GTY2ttwheC
nydI4bLbDiTJkq6rrArFxfufCdBAZqIPpD/IfVO8jfU39gS6yLZ411B4oiBm
f1gHrAxp8oQHaKFkPf9BUkJGQHaMkEDQJALUHoEO7fvewq9F9xRtzgL0vEp2
gkwJckiyM+QguhZ8NcHSUCTJziNxEPTa9oRpN5D6BNnhwxRXi/jbiSknm0LR
BC10Tf/a3Q7RbrCEwTHuD/whf4AsUASol/4KAEAcCWMtsH9dkVAtu+3SLrdO
MPXlTx0FhhQwwUTL+hV4uiiHalqSZ5lE70rIxvZ9xWIswOPoKiYaqF0wbLLk
/IYwcUeiT9vKS5TwxDYuUxbSCPgekWTSYOuZnzIifUjk2hrobCZBwTKE1Yss
R3uRxSPtPfDKTOHVCCOvime1g2xhDaeudSyTtMcQ9cIfRGJ5CsS3jokl3kLF
6e8TExagyIxiCNARKYohEsvS+mQ4LSVx1T2wkzixIa5vO4/4d9PTji5zL8ER
Vha5LYpbV+/BIvHdxcUG8A/YtLHes0FPHnQMTHkXoQBBPO+qmDNjM9js7Sai
bKDQ+zYLLOQglZEIcWtTc+CdYisyYr9WTTWMPsR7hrTElndEHe0uIiqlZRRl
4APYMkkIHFVf8oyV8pjWZSIDYLkPG4je9lDnAe9dEqMMdNXn9MHxgkCkCyT2
2FiN3yle8RUn9xjd2LuuKskHtQ7zwZxvSVwbCXXTIkB6CCFnor3iOsCnGWIq
BtSkXhSic5RtPWyIObchPiSBBCof7cnzzvwgvj2+3Ltt7WDgOVEQXJPZdcHi
uvau6rsWy4io/Qy3FMtlWssdbXS0AEYtAPwlsaghdwv+S2LC0XTqXM6kZVHM
ZGN4NQH+IH3bEwoWN9E7SDhsyq6HpVEZyn0BAC/SKiPgwbFct9lYLw5iBKSL
y4a0kHbik6thIZZ1t2GHxYIwQtdXE1cSdZkVA6PwyOTsW8uW1g6B+glMV+zO
22emPpRNHeyY88PZGnl5ml5x5ap4Kdm/RdHQqxVNPc3cRj3SoIWtdwhrYCCC
txYzTA5yK6iIYkziA23qizsnsZW4iuDhFlHURxH6OTxpSJQZAIQiVM1KAAMK
GWTLmdt+bKJaRgrxD8iFJWMtFrpD6GDWh74k/STUVdCfzh42vd2cYuhNSJH0
tc+BKkeZxLgaCnGguQl2Eq4gtr6HL/QZ4tt2UFKfHPqX3isuX717f8XBFAk5
0jL9oVb8MkLQN04ijK9Xj8E1CUe++fuTrxGicqyOyJYMWtPAughjvQ5HrtWw
c5KcJCMLkBoFiDOYWUhHFiIP/nxcPyfln6Om6p8a81+LV/BwWYAzypFV5BmP
bO/lH47gbHdy/VcEvN69LxSfaz5QCkbYoHaOOBaaVlxscyD53iK1jGdppIx9
IQNEY4H5q1kie7fpdii0/EUyISkEBWhMV3v3lR9RHfJXqmEpnk+qkzE2ILdi
ynzxVvBhnfiqfI4vrZ6Gmlm/rL5gFay2iT5owRyNOopQmVkoPwCq9ggI/OBj
MH36j/A/mpo46ni88eb8tYHjouJe8gu0kRIyMIpkbgNTCnDKGEp0vcvCcjZl
90yMpM5To0VprkqGWm+17x/gpWV62pgb5zQW/e7R3ynclWQJ0meVuEPEVDTF
hYTWOVEXasF6SQyENKmo8KU/rGkzhgNv2gVWdMHPXoAdF1dsraZR2MuAksyZ
defAnfZDS5DkweAY+klW7no6YkWW5MTJTTg9zQeJWWXXascg8k+qIGZUBSlG
VRCwIRZBeLDzSsj/T5WPs61Q9+t47ZW/RYjNylmwrAmQRQjSZmSArWxwDIOF
WHqgrZZwJwAIcTu8w1JPm2254dQTSSahUWNRHuC6XAi2JYijkcTE5dkxyd9b
Ru2s2lbSjERVeIui24Nka3QvxfWHSSSptYaLv6vcMa8Dab6fbSbRciSwieJm
F1L+TGAoBazYP/A/gGKGbAraw31tNygRJqUofnNrQ9g+Jslj/Jr5/bRE1Ceq
kkAT0Mi2J1HsGnD2tjuCIaXbSNbUhElbd2RwJKA0ywhpxsmp2K85U0hwkcDc
29aljJR3ruH+BX4MQwGUOjbjUPJa8S4HnjT2FghtTQNtUQyOoIOT2RyTG60n
PC0+IokmUUKYbjFdMMGbptKggbeyDeEBrezMDEn6rB+m6eaDzkQCqd0qBTHO
VuSbPPGgJJtopqiY/cLRuU8anZCvPvIqttG3g7mKJ7g8AQYcK89mEJgreJUj
L75GRvIksSbbO9kicPwDo6v3P3vNZtEm9WoJvbl4FwSfHriIFhXkPU9NQ4sg
VbqOgjAsBUaLwg2bFZPH9XNBbpJO0yDeFmh8Iq+5i2vTbPVC15lJMHv8jhVa
U868WUe3LiDFaJEgo8Dc7uD3QMqBzAmPKlWibrslwzZmAZZGRoPI6g2neOhL
W5yc7c8kQhQ0SgTHYIvkeGoYYk26Snhh8gYVfi1jqOoF6w3Lz3R7YOLsmh7S
5VIkSdEf/CPg/DMK/x1FKMy4zD++alGYhOy2EmFJakeyfllck+VSprmdtHCT
la1yc8TGRwxXsAukrnccUokbEVQdWm5yTxqg19QEk4Vqfe6CN0hgce4GIJO4
y6hKTXJ0wjEw/BEz/gaUN5tXmcym8RW7Q6boyLUTCBkSt4KSo1r9CA6jYZGT
b4vcKZe9JdDN4pVCRIvS1g49I61iHQKjNODMExT0kT89ZfnahQaE6zyMZwD6
vJtZCsH4rP0Kue3a7gPMJFkT1ynZyJi+LeTdH+EzfMdJYbhhQclrd4+gnE++
oMATrXxsShkLg+UM7dcuygbJOxJK2wOkW4p+5GvZZ0NGRbC92AYG8PVh0PYE
e0fWlH0OgyhOeCG8Joji3SoJWY8hWb0dR2+aPWD7GR4PBuyMf1zrk5JdAexB
gueHKNB715HT4Fy3xjUYURVBaBcRIhZoFkUgWnnYQIp8RbieKNPMpGQ4Qgni
xzMsiJii6t3Y4co0EKHUCCZtIwH3zWmUOHQyxEjYSLVoUkspYgVMKwajiFCR
RiySDe73YTXpUbyvF0PNAxepxXCOIIk2WURkNSGdEYVYMac2JGvbC1Wv8LJo
sWTEO960eoLBx8lxmGFG7sXNQQAQW1QhDQg1czsa2iNDHMqaZ0Wi1PlBvgLq
Imn2lNgK8bODLEgRieMAndJzDwZDwNbtukHqTCS1VVdqiEKr0zQmiGt3LmX/
Dj3jKrJNw8EvRnibUTKnOScSoqV42cuRrTxbnMojc0LIDWlXztQCoROBJiM8
8Yl2KLRizPYpjjnHH62K3wjuGt3f+PZ9jzNs8US931YhZ5nLGVeWpAhJm98O
bOrWFGs3amDQe5l6S6VuOCl1QCLmgoYwB2uqF2y4BbFeklxwgo+mwV7xxjaO
e5LPAiF0vxdazGZhsL5r7Tqi2b1EQiSWJa2ETApMw4qHin0EIT0hkYrooDS9
wOWg35C8Rd+1p6a4VLrVMpC1bzn6xIAfb5bXN89eveI1kuyTjF4VnIvW0mQ2
SRZok+kmbE6RYeVS6g3jcfZtkWOjZHgkHOLFc/payQvdAFwPpeB60PiqPWHA
PSw0twjpChiVolUBZGAwn48mraS00SgjoUwiABkjhfnIokuTBFd3F5w3R80p
h5JTW81uPy9MYMDQVGker0RGL/0Vb/iHcxMdK0pWWzNT+2Z4lZ2J61mQA8kl
0B1axlkitod2E3MycV+0QodNCJDq0qHqKs9Eymi8GIJq1hNo4+tV8ToLZMIa
XiAymyxCXpdltBG+Xcb+QCuTfUWTZ81HaEdAv/wsmON4Cj6WMAVXEnq3Q6F3
tpltBXSGsRJAwzwpOdcV/+hUSneq0TP6t4hgWatSywzmobeenP5istiYS6bx
RnEfF0IAZus6T0VwgtBpC7w8Sf/luhvH8i2/iNFSFjPsmDYIs1S3LcHGjYsV
q4ArrJe4Tywcy0oAUKjdyO5mNoYhlm4YUavltHZK8ok3gw/CIDe/jgcYApMj
Lo/Ii9cW7HXWk8KBDjIMGOyIzIaOtybeLeIbXITKFx/GHXGZnfwdlsY7QKzM
un9CpMEdttlLa8e1Kld+MTjveECwVOaQXoce+tRmqFTFansAzhC5ejXXYDEn
U9McFGEAhksiXGciFWql6vdDYS1E3Xl7FiJk2UvOttJH5KTFbPajSvesxx/h
WIHxgDM09R3Fm24JqmipT8hCpMW868hGn6KdU2QjVlwdkOQI4ht7fqO4jN0H
WlTXdV4tNPYbSxAr1X5fn3JbIl3Nue37jVv2z8vLKiaS3Bm43Ddoybkl+Sdz
nJVO1YhUPVvEb1b5qaAZMB3Wzq1xkppizDEyy8nYopMKqP42JK1WxU8nbh4T
M1exvimW4BSjW0ySoNrxh4CNQ6SYhws8ZenfhYx3kQXSIkVaM+KmB6Gdu0tx
zGHX2/1tMBW7in0UExqKcxhuWuMHrF0Iplow8oQDY4ulaTZ2QQj1W5dKBDTQ
eXdJ5TMyWPm2bGyQ+CtCswLn9Rjzc4TRbefHoxgvZk+wSWSD7AYdIIhqHRdZ
p8amLUNgwSapC02bpFrLXaeuHs11ebfzXB5lnOcNeclRACMbE1jYluFZ7Xru
1v8QFOxjPMvaqI0rjFlwFgzBgRDCZmguQputrryNzc2z1RV7GLq2azqVaQcE
EIMzsq1dalGXWo8U8AdvuBwZU2BTOrWna9w6vIACEL2kAVqKQsW7bxgurB2Z
xqrrNbV4UwUgGlv45lrypGQe2ZGaFxEToL/lMAZOIdkYVb94z0WOhRow6zWk
1K4bTUCbfz/Ye3qKphRxRJGQXrBtpNAhhaLmQzw+C7/tkcGIeQNNfQ9h8oAB
70kFaJN5OBSQw/eYJfjk3F4KqYZ2tkyJuhBS7w/9XhNKI2bxqJ9c3pdy5M44
2sqaDyOa2bRLasBJEi4hKaQO+W5S6VtkFLieyK08XEPkwDYedOz64KHOG85M
So1xqoqbQnlfzg6r4clNKEqgr+4OHiDwm7lh+DuusLRZz1XIooNkeGotOiw0
YJGGic1tx8PHqqOJOhQrPtPgIJwE4C52iY4lVaEHf4t3MKT444+/NcMOZvWz
MS+ZIR3QsmUPR4HCgbX/LM3CqMpuQtlSQ2r22dyriuy5pFV2Gq7k4EsOpWu6
XyozwEbocttEKdHlK0qRjlt9A/VMr/mSgWGVpt44eQxvRGar8ZM2/R/Cl9CU
Roqy2KDUkrbnfLdrfmAAQU9fay4ZnjPBSulUDlGo2JEcQ7HagUYJfC38LGpM
phhVO/Kyw9oJG/a9o6EYNZxF+TxsaMRs0Igp1pLE00McPaMsfOCQ7qHgtNow
4w0i0Zib06AsxLUMHBNqA3HTBBJtBXdiS02EFJk2lstOoaUQiRt4Kthfd5eO
lCQxuYvLxgl/0G69WfcWgZdkT9CoKQmumt6JFXG2169DnUuzXaEAxm58oNXu
b5F3T/3PiwIet+Pv8k+RrLEbtxy6Jf5LoebtyWOdV5E8tHAOEhBIJ52u8qzf
LvWkccplg73klR97AETiQNUiG71AJRImUg9lJFRJgtRJoY1LVFL/joFM1rg2
FHLYRgBFOgAd8a0rmRDucc6GkeBiVD0ma6N0KUIzGrqLzol+hZhMV8jgETJw
SJD0ttrdFnwALvhAk7fPiOUJBW07MCxC+PqxrdnQnxstPloXylomVlDUeY5o
FhAcsehM7NjYMisBxCZsbda+BYrEGVS32q0WqTaZ8xLlQdQX/cRy/i/XHpwx
96czxunnta2DUdOMCnukJIOpiBtKAXkJhUMVPlORnCR6KwZ1gmgyHCv7qPxM
NrEK1QyGWxZgtmTMP0JPP5iRXkSapOoqQwYt5yhlIQqu+An6Xbo11wTJcrr2
Fosu5zuRieaXs5Od958i4nZ1edZcmoex2LmMiR1khaI3nGHqyevW4bSY9Jtm
Z+T0gAbsn5oo7QSTHk1F76m7kpWSG863KAvVIVXO+9ZtNoc+FuJvyVwgJOT+
cVSIlxRvcWtRcpur4uWhhzyCkYvxiSG7JqRA4klwwfxp/D/HOD73NmncjUz6
gRNQWVut1jA9BUPa8YBMMb12B2FnIRSb3TJJw707GB0CeojyDbMbUsiGRDQ7
owJrHI9uCkLizcgbNnhqtKmeHQdI533go7heyXW4LG+RZh3JOuH/Q+g6FN5J
9XLEwazrmZubdTno0gg8k6TyiJHjXoIUKpr7ZCdUPEZBXH6MP2JpPfNtUv8B
d45UzaG2sRIVjNTrWOGTQs0GAknDsh2Kp3vv82daRVbLhckZzNBemFhbzEOG
cNZbog7yshQNxFAk69qxO/b3aURiM/cMhR6laONWMylvVhELn4mDvbeSsCy2
aK1EvWx6oQkQz6eQDwmLmY1iP7C5Dl0Q2wX8Lcscu7dR3cfdcQUlpObO019w
5GKvTbTXml+aHHrWKzX4/AlZ61ghY4iCUDhv4DfawK/jxF73IZ1snunpnxS8
cG7GVbA4obwk9eIoYqEPNyQepGzDOSnkkbJWLA2FaInkSRqCOChZvNeM7mQ8
il+gnGg8CqUDrJILBc8rvw54JyTYP4ypPjsMyRGjnMEkrMCJADax4SB81E3G
GD+vTDzAUmmE+zOCAkubo4dbQ7YFlYY4KO87Z1b3eyeHZdg38Hl5EqKbgXxp
8Z6E0Z9nP2ZL8fFozFYwBh9bzI/dh+afSV4jO6MznWdNb2yJznhDQuqIMKOQ
ZKs9CPFodQj7aWU91pD3+jPj5zYiqlktTgEpkGSlpsSFRoZNd8tSsxgHl1md
XW0sFxUjBKbQDFdEHAacwIPqm7kWg5BiuPc826ieP2J56IeMfcaD9Z9G15ZM
V0TE1BJ24+KGqYKZmIc/vxTB9j1q74Ksz+5GUHw8auDkxlsCXrcWEzNulX6U
aFC2FUEjnBB/euf35Ib/28Wji88mRPbmaTHZwIYwInpvxYpY9QYpz6G5U1QW
Q0wQNC9kYr54tYWUcFFHznt7j1ZaSCQ2kTON3kj9c3pbES3mWRCR+UnOV5Vk
yqfiBNqwAjPvuYlkBa2FUZ3lldhbtntC5eTkVNZKG+wXDv/35rwiiU77+DYa
H2cn5G+8xi5w3uNuwamrnbIlmjFb6XU+AR5Ld0c4AUbrSYkLKXOH0F4+w8bM
JN00Dyh+WTyQ4HphE5/5HIVcwV7ORbHpbBfj4Tvuvp7wA7p08C7GZibrG51k
I3WFuIQhMF8O6Oi9a0mvlHtn5loOE3379ePH2el8XHDCkNuY1+k4a1DPkDAe
2UNb4oSolpqzxWgfpvpVbZuAQzwD8qEll9Y3cH/P+FQMLbbp6IHz/tB4h8gp
3f8xJQ9dCbJrXPOIgmCyPA5HmofQTp93fd8MhFuaycGrzJwuJMJk23V2Fclc
rB98zpykzaS/ohfCeXNss4YWGh5PIWSwkoy2jBRs0312MUkBHMnXdiB70bv8
kpKQajuv14WEG46HZJlPdocugMOUphe/woejpB0D7k+QmAlGE7gvndqxHv1e
qWTLI6h9hk1u9vSEHJNkuXb9SRKgaqX1lOzTqXN4kRz2fU1/sZkPjjh1CpLF
CmsFy6D/jV4LOEXeY1QwRclGk4R+BvS/vDfak3O5OCriMpMlZyNR2uHuq9h+
L71bdZ3RvwxuPfd3r8Lx/XF3G5/YvSe+VBvGiWUo+90kkYJXubhiQsOQ9HJI
9Jjx+AHW6iByZJQIDaReHHpBrwAY3SsoIDfe3xQhX94BF+4CyTo8ARkQdnFA
xJKmltkPp9qdC3eeo2BZ0GOjHKSIWEw708JNRNrjcGYVUYTStVmc4+Q1n8JG
ebUytHUo09VbMguvO44x5xqHNY2GTF8mk5oXhNFs9oPkbZIyMsrLjiByNKN9
IC5WthlxlR0vuJQ6Dga62Na2cRcYm100avt2WCIMlVsqU38xcfiustEqGKWK
I5ZEzYQSEBdpkQo534Bps0qaIeSJCBTmj/Mi6crC4jKeridvTAYMjMZhuLd6
l+YiFBVEs5ldo2Sf3Ay2BLLVowQxFXDOYZSKRp1EKW0wqeOsiks5ChgKTJ+N
YsBwbcsV4B7Dg42akhDYzsyvKpPE58zkhhwxw594pATfEv+ZaJM8mxrWCfp8
HgolLmJJImG2L+e8HnBeA5K0osQ2Om4IOvLT39p5Ml/E05sNJifDbXbQDxCr
GljZ16dUp2w6mtxmTSxnReXsXoW3WwOkj3S73uqCxo1WK8ac6s2bf6aNPgFv
W1RezYQRZDSTMY25etSBhFD/iXildeuSnFioTAXHF+6DUKDcxZXR7nNWP8RF
ammPYnWQRuHyX4oZtVCBJdSdRez0PN3vFg9D0o7fE8pOsHP6F2ezBG367DIZ
/UQ7z/UinslloV9qpgJXY797xefapbdXM61hJzGspKjCXqMPDbkx6fePkqAE
GW3/0UMrNiRyuMlFmJ9OK8412MuRvVtX3LNCjQ9oNHZT0673sQse3dyUxlPM
joblXnXEFGctFqD4PFd4TxBR/IUgwhR/GkZIXmsSNERJyu5qOgvzFkg+3WPP
pHrE4pCdYce1eq+u31yz+eLtePmseFEikM+8XFaMZn1Mds7y1bzsuhkV8dD0
icmvlFJu6mkOLc8GDCwt1CFmSFlLOeNNgQCt32ixJAXjbEMc01lxE4McPfCH
3U66Q0PnQlyOpv5yugJckiv9cPwPw3D8dKf9lzhvF3peciPJyaIK1QuQdSvZ
jjaWRCaRyyRew3zhpCrqrSLvOLCqV5pFK9Bnp29jtvvOhYq/BlRcq+xaRrvI
omdrFNAbjw4xGOA/aLW8tsU4RzXDHhPZk6EChjjpkKTeRghRiCHuRGVkFx5E
gaTtkMgq+FUuTeiBILRFE5ZcRtWYDJZYJFU2wsMx9lEvpZlI5P6W2fmW/CYE
hsiSac5cihnd70pwJNepLwPkufT/8xgG5xWU7NNrbt/V7se0MHEyAWdcju7Z
lrKEltOvUtU6AyCgdX2WNeEr2SbWJ8rGsdPDvSpcNlT05ASxl4Pcqb/En5fh
puWqrOgPA5NuhMSJdumyI5dcSrvTJoG10IJJxI0KiYBa5KscQTwn9RZxJx4V
6h3hhbM26zO/p8nKMWYmKYmLRdwJozKbdkILzJy5/8rn1X3jT2SEmngNlDRP
tyV6xC4YoVTNRUK28DhTVo6uJVrdJyRfEIuYOMxwKzy9jplJTTiDj6DQaRYg
1L/i1WAJlo50BTEz6XOPkJu/xX0dPt2+mPPZhSMls2uJVkOqPDBbQO+yTDIs
V2K/I56Zvy/h4A+c7Q9gnxxJbtKyeyiMoomUE8tPHGq4cXaFIVH1AnCw4qvF
6pxcMyLX6x3XcEBejooo5pS+fZzfHLlINPjExuOZNK92leJXUxbxl0DyqwpG
aTXAdHQpD3peOsKH2TTbdTpKqUmQ0GQ0umJDrnuZpDcXY9iSiqjh2onM+IoP
WIySUQbSX7Xa15igSbq0ODucyO4ArduMiOXN1F60S9kC6UCTQ4AjRkv7wdgI
cuN9uGKA63h8dTC55qwbW/zwIhpHH9KCvMW5yzXmzdsPL57ObL8dkdKgEtpW
vpHpuCCTfR1uNjXjjp+UjrZx11YoFw5cIi+y7s3QlhREYWFwuwrpbjiUSVhg
7eo8U8U33y40jgu3xfa4K7TMQ9N4vCjdE8v5xykulN5WHJbjgBYCK475lNqd
FZjRl18FLHx+Bf8Yt45BKvcUwoKLoornUUCZtDsHoSltk0ZacLWF7xTGZdf2
ZCr++YLVSFcmP9qRbqmdq1BKopQPE8klE0c94BB6WJkh50lw3g89zLDQ6nPS
MDLNChnjGR4JpqMO85bZ8pQ6Z/XCGrlRmesL75k/4YKJs2vbw33bwo38gok4
y1b6mxm/p0J3Ml3nVwjP31osEF8pmc4JnC0Xni3Gs3PGHTegqtMbA1cReNb3
uM8mxgH42RDEPM/ybhM/vZIdLrDt5MlRX4rXCr3bHHokpafDxC/CwTjtwNTE
nKxdjn+5ppPBrjef2u5ICHynqHBMC7eY+FQxebsZOmT/H33//bcswxd/8ntd
dvQrXxfY5+tV8RuFD7Qbsz9gAhoPfcv3ko/mfs3ek2Z+ojOf3X95/8+L8cQv
VsUvh+qfTgD185V5Rt8jZBZFe/Ttw685iMh+bkt/VmjjcJcyctkMeSIEf3HA
rX8k2h/RGERm5BcKC/9J9D5++Phh8vhy8qklQQ/xza4nX4h1L+n/vtNzd/Qh
mgTQwMHMf9Otim+fPPnu22+Ly4ubm1fPfn377gYXgo33KN7mKc4jZS++KkR7
AiCL1AIwKAquxA+e5bYpypUMQ7q8mRFpPBCUSubVEPrVWUD5d3JwZTvE65nG
x5Iuka025l/0iPkXTEHxr/BI+HD58Bv68HXHpx1ciYHk7TcVLpMBNniLLBQu
uvwdluhExnJVsD5//3Wx/O+F3tC2gn7Qg2rIPxHHy+7Y8s/Effv4+xXP9YTm
upbjnq6cTPjaMrwixzyZmhn6Gmi0JV/bNR6+F6N9HZdTqstkzBNuZbTy0zWD
XHY7wncL7tHPjrgmPIJSvNiSZ7ZZ91W5c4vi9TWjX2fJBRP9mWzakUILXY9l
laDK/T4U/KtbTE12er0b3YTPo0qjmKSU4k/AhdwFYvCV7BP77qbi5nmZ8BFN
+NG70fXwfIev5yPJODpAgoS4o86v0OM9LaqyRVHmkkUUB9lhCPXU36Lw9iRS
eXTxl5AmdgS99VfFx30J+BSeyRaLdm35cswsiBEZRpRHEpuGvOfmNck57kOS
Dovi8tXr91fjl5g0j4t3QxT4cziUyIj5yfKblMuMpZB4cccm3H+h7+QoU87w
yzGr2+IidLPpaBeyZZqIiv27NH048Y8D/bCuOM2/Ujll/I/oobT5OwrvHy0f
h1+GQaVMdw47cDE+ni+3A0iSemNRwZX7ubI7Yo9d/iMzZFv4nJDuA7Mu9KRA
yjRayJ1r7rQnUURZjkfARY98mJZTsZkkqy3kjQoCrz9BgS/GqU8I8kMS5BjC
BCuX5W8XZLqbrqz4rg0tI3q5x3UkkemXRi4fXRXrjoLVfl9rXzmh4RNELd5j
EtoWykPsyNmwLfPaIfZ7Uz8mO8YvXz6+0jdDnJJb51B00IQdX+gHZfB6GWk1
xDvruamelV1SotV2G2sroXA+IjG8GH4pQwAGGpXlWGqhFMMt/D8XMNGsGHQA
AA==

-->

</rfc>

