rfc1718.txt

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

                       e-mailed registration forms - Debra Legare

   o proceedings       queries about ordering hard copies of previous
                       proceedings, and general questions about on-line
                       proceedings - Debra Legare and John Stewart

   o ietf-request      requests to join/leave IETF lists - Cynthia Clark

   o internet-drafts   Internet-Draft submissions and queries - Cynthia
                       Clark and John Stewart

   o iesg-secretary    John Stewart

   o ietf-secretariat  Steve Coya













Internet Engineering Task Force                                [Page 12]

RFC 1718                    The Tao of IETF                November 1994


IETF Proceedings

   The IETF proceedings are compiled in the two months following each
   IETF meeting.  The proceedings usually start with a message from
   Steve Coya, the Executive Director of the IETF.  Each contains the
   final (hindsight) agenda, an IETF overview, a report from the IESG,
   area and working group reports, network status briefings, slides from
   the protocol and technical presentations and the attendees list.  The
   attendees list includes names, affiliations, work and fax phone
   numbers and e-mail addresses as provided on the registration form.

   Folks who register and pay to attend the IETF are eligible to receive
   a hard copy of the proceedings. They must indicate so on the line
   provided on the registration form.  The proceedings are sent to the
   mailing addresses provided on the registration forms.  Please notify
   the Secretariat immediately if your address information changes after
   the meeting ends so you can be assured of receiving your copy.

   For those who could not attend a meeting but would like a copy of the
   proceedings, send a check for US$35 (made payable to CNRI) to:

      Corporation for National Research Initiatives
      Attn: Accounting Department - IETF Proceedings
      1895 Preston White Drive, Suite 100
      Reston, VA   22091
      USA

   Please indicate which meeting proceedings you would like to receive
   by specifying the meeting date (e.g., July 1993) or meeting number
   and location (e.g., 27th meeting in Amsterdam).  Availability of
   previous meetings' proceedings is limited, so ask BEFORE sending
   payment.

   The proceedings are also available on-line via:

   o Gopher: <[e-mail]>
   o WorldWide Web: <http://www.ietf.cnri.reston.va.us/home.html>
   o Anonymous FTP: <ftp.ietf.cnri.reston.va.us> in /ietf-online-
      proceedings

   People are encouraged to use the on-line version of the proceedings
   to save paper and money, as well as to have the Internet community
   use its own technology.








Internet Engineering Task Force                                [Page 13]

RFC 1718                    The Tao of IETF                November 1994


InterNIC Archives

   There is a tremendous amount of material available for those who
   follow the work of the IETF.  To make it easier to know what to read
   to prepare for a meeting, the InterNIC has established a document
   archive.  Beginning about one month prior to an IETF meeting, working
   group/BOF chairs and area directors put documents relevant to the
   discussions to be held into the archives.  Those people who plan to
   attend a working group/BOF session should check the archives for
   documents which need to be read.  The documents are left in the
   archives for about two months after the end of the IETF meeting.

   On the host "ds.internic.net", documents are stored in the directory
   "/pub/current-ietf-docs" under subdirectories named for each area and
   then for each working group.  For example, a document for the NISI
   Working Group, which is in the User Services Area, would be stored as
   "current-ietf-docs/usv/nisi/nisi-doc1.txt".  Each area will also have
   a subdirectory called "bof", where documents to be discussed in BOF
   sessions will be placed.  A directory called "plenary" will also be
   created under "/pub/current-ietf-docs" to put documents or viewgraphs
   related to a plenary session.  Any filename conflicts will be
   resolved by the archive administrator working with the submitter of
   the document via e-mail.

   It is important to note that the service is provided by the InterNIC
   and that the documents are submitted by the people who work on them.
   The IETF Secretariat does not manage or monitor the archive service.

   Access via anonymous FTP:

      Anonymous FTP to ds.internic.net
      Change directory to /pub/current-ietf-docs
      Browse and get the document of interest

   Access via Gopher (from a Gopher client):

      Point to gopher.internic.net
      Select the "InterNIC Directory and Database Services ..." item
      Then menu item named "Internet Documentation (RFCs FYIs, etc.)/"
      Lastly menu item named "Current IETF Conference Documents (...)/"

   If you do not have a Gopher client, use the InterNIC's public-access
   Gopher client.  Simply telnet to "gopher.internic.net" and login as
   "gopher" (no password required).







Internet Engineering Task Force                                [Page 14]

RFC 1718                    The Tao of IETF                November 1994


Be Prepared

   This topic cannot be stressed enough.  As the IETF grows, it becomes
   more and more important for attendees to arrive prepared for the
   working group meetings they plan to attend.  This doesn't apply only
   to newcomers--everybody should come prepared.

   Being prepared means having read the documents which the working
   group or BOF chair has distributed.  It means having followed the
   discussions on the working group's mailing list or having reviewed
   the archives.  For the working group/BOF chairs, it means getting all
   of the documents out early (i.e., several weeks) to give everybody
   time to read them and announcing an agenda and sticking to it.

   At the chair's discretion, some time may be devoted to bringing new
   working group attendees up to speed.  In fact, long lived working
   groups have occasionally held entire sessions which were introductory
   in nature.  As a rule, however, a working group is not the place to
   go for training.  Observers are always welcome, but they must realize
   that the work effort cannot be delayed for education.  Anyone wishing
   to attend a working group for the first time might seek out the chair
   prior to the meeting and ask for some introduction.

   Another thing for everybody to consider is that working groups go
   through phases.  In the initial phase (say, the first two meetings),
   all ideas are welcome.  The idea is to gather all the possible
   solutions together for consideration.  In the development phase, a
   solution is chosen and developed.  Trying to reopen issues which were
   decided more than a couple of meetings back is considered bad form.
   The final phase (the last two meetings) is where the "spit and
   polish" are applied to the architected solution.  This is not the
   time to suggest architectural changes or open design issues already
   resolved.  It's a bad idea to wait until the last minute to speak out
   if a problem is discovered.  This is especially true for people whose
   excuse is that they hadn't read the documents until the day before a
   comments period ended.

   Time at the IETF meetings is a precious thing.  Working groups are
   encouraged to meet between IETF meetings, either in person or by
   video or telephone conference.  Doing as much work as possible over
   the mailing lists would also reduce the amount of work which must be
   done at the meeting.









Internet Engineering Task Force                                [Page 15]

RFC 1718                    The Tao of IETF                November 1994


RFCs and Internet-Drafts

   Originally, RFCs were just what the name implies:  requests for
   comments.  The early RFCs were messages between the ARPANET
   architects about how to resolve certain problems.  Over the years,
   RFCs became more formal.  It reached the point that they were being
   cited as standards, even when they weren't.

   To help clear up some confusion, there are now two special sub-series
   within the RFCs: FYIs and STDs.  The For Your Information RFC sub-
   series was created to document overviews and topics which are
   introductory.  Frequently, FYIs are created by groups within the IETF
   User Services Area.  The STD RFC sub-series was created to identify
   those RFCs which do in fact specify Internet standards.

   Every RFC, including FYIs and STDs, have an RFC number by which they
   are indexed and by which they can be retrieved.  FYIs and STDs have
   FYI numbers and STD numbers, respectively, in addition to RFC
   numbers.  This makes it easier for a new Internet user, for example,
   to find all of the helpful, informational documents by looking for
   the FYIs amongst all the RFCs.  If an FYI or STD is revised, its RFC
   number will change, but its FYI or STD number will remain constant
   for ease of reference.

   There is also an RTR subseries of RFCs for Reseaux Associes pour la
   Recherche Europeenne (RARE) Technical Reports.  These are technical
   reports developed in the RARE community that are published as RFCs to
   provide easy access to the general Internet community.

   Internet-Drafts are working documents of the IETF.  Any group or
   individual may submit a document for distribution as an Internet-
   Draft.  These documents are valid for six months, and may be updated,
   replaced or obsoleted at any time.  Guidelines require that an
   expiration date appear on every page of an Internet-Draft.  It is not
   appropriate to use Internet-Drafts as reference material or to cite
   them, other than as "working drafts" or "works in progress."

   For additional information, read the following documents:

   o  Request for Comments on Request for Comments [RFC 1111]
   o  F.Y.I. on F.Y.I: Introduction to the F.Y.I notes [FYI1]
   o  Introduction to the STD Notes [RFC 1311]
   o  Guidelines to Authors of Internet-Drafts [GAID]
   o  The Internet Activities Board [RFC 1160]
   o  The Internet Standards Process [RFC 1602]
   o  Internet Official Protocol Standards [STD1]





Internet Engineering Task Force                                [Page 16]

RFC 1718                    The Tao of IETF                November 1994


Frequently Asked Questions (and Their Answers)

   Q: My working group moved this morning.  Where is it now?
   A: Check the at-a-glance sheet and the message board for
      announcements.

   Q: Where is room 'foo'?
   A: Check the map on the at-a-glance sheet.  An enlarged version is on
      the bulletin board.

   Q: Where can I get a copy of the proceedings?
   A: If you have registered and paid to attend an IETF meeting simply
      indicate you wish to receive a hardcopy of the proceedings and it
      will be mailed to you.  For on-line retrieval refer to "IETF
      Proceedings" section which appears on page thirteen of this RFC.
      Both the hardcopy and on-line version of the proceedings are
      generally available two months after the meeting.

   Q: When is on-site registration?
   A: On-site registration is first possible from 18:00 to 20:00 on the
      Sunday night before the meeting starts. The IETF registration desk
      will be set up in the same room in which the reception is held.
      On-site registration on Monday begins at 8:00, Tuesday through
      Friday at 8:30, and is open until 18:00 every day but Friday.

   Q: Where is lunch served?
   A: The meeting does not include lunch or dinner.  Ask a local host
      (somebody with a green dotted badge) for a recommendation.

   Q: Where are the receipts for the social event?
   A: The social is not managed by the IETF Secretariat.  Ask a local
      host.



















Internet Engineering Task Force                                [Page 17]

RFC 1718                    The Tao of IETF                November 1994


Pointers to Useful Documents and Files

   This is a list of documents and files that provide useful information
   about the IETF meetings, working groups and documentation.  These
   files reside in the "ietf" directory on the anonymous FTP sites
   listed below.  File names beginning with "0" (zero) pertain to IETF
   meetings; these may refer to a recently held meeting if the first
   announcement of the next meeting has not yet been sent to the IETF
   mailing list.  File names beginning with "1" (one) contain general
   IETF information.  This is only a partial list of the available
   files.  (The 'yymm' below refers to the year and month.)