rfc2014.txt

中、英文RFC文档大全打包下载完全版 .

   -    The estimated time necessary per item; and

   -    A clear indication of what documents the participants will
        need to read before the meeting in order to be well
        prepared.

   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.

   It is strongly encouraged 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 group
   and made available through the IRTF Web and ftp sites.






Weinrib & Postel         Best Current Practice                  [Page 7]

RFC 2014             IRTF Research Group Guidelines         October 1996


3.2. Meeting venue

   Each Research Group will determine the balance of email and face-to-
   face meetings that is appropriate for making progress on its goals.

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

   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.

3.3. Meeting management

   The challenge to 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.

4.  RESEARCH GROUP TERMINATION

   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, in consultation with Group, either:

      1.   Require that the group recharter to refocus on a different
      set of problems,

      2.   Request that the group choose new Chair(s), or

      3.   Disband the group.

   If the Research Group disagrees with the IRTF Chair's choice, it may
   appeal to the IAB.

5.  STAFF ROLES

   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.




Weinrib & Postel         Best Current Practice                  [Page 8]

RFC 2014             IRTF Research Group Guidelines         October 1996


5.1. IRTF Chair

   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.

   Planning

      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.

   Coordination of Research Groups

      The IRTF Chair coordinates the work done by the various Research
      Groups.

   Reporting

      The IRTF Chair reports on IRTF progress to the to the IAB and the
      wider Internet community (including via the IMR).

   Progress tracking

      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.

5.2.  IRSG Member

   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.  In addition, most IRSG members are
   also Research Group chairs.











Weinrib & Postel         Best Current Practice                  [Page 9]

RFC 2014             IRTF Research Group Guidelines         October 1996


5.3. Research Group Chair

   The 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.  The 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:

   Ensuring the Research Group process and content management

      The Chair has ultimate responsibility for ensuring that a Research
      Group achieves forward progress.  For some  Research Groups, this
      can be accomplished by having the 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.  Process management pertains strictly to the style
      of Research Group interaction and not to its content.  The
      secretarial function encompasses preparation of minutes, and
      possibly editing of group-authored  documents.

   Moderate the Research Group email list

      The Chair should attempt to ensure that the discussions on this
      list are relevant and that not devolve to "flame" attacks or rat-
      hole into technical trivia.  The Chair should make sure that
      discussions on the list are summarized and that the outcome is
      well documented (to avoid repetition).

   Organize, prepare and chair face-to-face and on-line formal meetings

      The Chair should plan and announce meetings well in advance.  (See
      section on Meeting Planning for procedures.)

   Communicate results of meetings

      The Chair and/or Secretary must ensure that minutes of a meeting
      are taken.













Weinrib & Postel         Best Current Practice                 [Page 10]

RFC 2014             IRTF Research Group Guidelines         October 1996


   Distribute the work

      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.

   Document development

      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.

   Document publication

      The Chair and/or Secretary will work with the RFC Editor to ensure
      documents to be published as RFCs conform with RFC publication
      requirements and to coordinate any editorial changes suggested by
      the RFC Editor.

5.4. Research Group Editor/Secretary

   Taking minutes and editing jointly-authored Research Group documents
   often is performed by a specifically-designated participant or set of
   participants.

6.  RESEARCH GROUP DOCUMENTS

6.1. Meeting documents

   All relevant documents for a meeting (including the final agenda)
   should be published to the group mailing list and available at least
   two weeks before a meeting starts.









Weinrib & Postel         Best Current Practice                 [Page 11]

RFC 2014             IRTF Research Group Guidelines         October 1996


   It is strongly suggested that the Research Group Chair make sure that
   an anonymous FTP directory or Web site be available for the upcoming
   meeting.  All relevant documents (including the final agenda and the
   minutes of the last meeting) should be placed in this directory.
   This has the advantage that all participants can retrieve all files
   in this directory and thus make sure they have all relevant
   documents. Also, it will be helpful to provide electronic mail-based
   retrieval for those documents.

6.2. Request For Comments (RFC)

   The work of an IRTF Research Group usually results in publication of
   research papers and other documents, as well as documents as part of
   the Informational or Experimental Request For Comments (RFCs) series
   [1].  This series is the archival publication record for the Internet
   community.  A document can be written by an individual in a Research
   Group, by a 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).

   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.

   The RFC's authors are expected to work with the RFC Editor to meet
   all formatting, review and other requirements that the Editor may
   impose. Usually, in case of a submission intended as an Informational
   or Experimental RFC minimal review is necessary, although publication
   in the Experimental track generally requires IESG review.  However,
   in all cases initial publication as an Internet Draft is preferred.

   If the Research Group or the RFC Editor thinks that an extensive
   review is appropriate, the IRTF Chair may be asked to conduct one.
   This review may either be done by the IRTF Chair, the IRSG, or an
   independent reviewer selected by the IRTF Chair.  Occasionally,
   review by the IETF or IESG may be appropriate.













Weinrib & Postel         Best Current Practice                 [Page 12]

RFC 2014             IRTF Research Group Guidelines         October 1996


7.  SECURITY CONSIDERATIONS

   Security issues are not discussed in this memo.

8.  REFERENCES

   [1] Internet Architecture Board and Internet Engineering Steering
       Group, "The Internet Standards Process -- Revision 2", RFC 1602,
       IAB, IESG, March 1994.  Soon to be replaced by "The Internet
       Standards Process -- Revision 3", Work in Progress.

   [2] Huizer, E. and D. Crocker, "IETF Working Group Guidelines and
       Procedures", RFC 1603, March 1994.

9.  AUTHORS' ADDRESSES

   Abel Weinrib
   Intel Corporation, MS JF2-74
   2111 NE 25th Ave.
   Hillsboro, OR 97124

   Phone:  [phone]
   EMail:  [e-mail]


   Jon Postel
   USC - ISI, Suite 1001
   4676 Admiralty Way
   Marina del Rey, CA  90292-6695

   Phone: [phone]
   EMail: [e-mail]



















Weinrib & Postel         Best Current Practice                 [Page 13]