rfc1594.txt

来自「著名的RFC文档,其中有一些文档是已经翻译成中文的的.」· 文本 代码 · 共 1,545 行 · 第 1/5 页

      implementation.  Other RFCs report on the results of policy
      studies or summarize the work of technical committees or
      workshops.  All RFCs are considered public domain unless
      explicitly marked otherwise.

      While RFCs are not refereed publications, they do receive
      technical review from either the task forces, individual technical
      experts, or the RFC Editor, as appropriate.  Currently, most
      standards are published as RFCs, but not all RFCs specify
      standards.

      Anyone can submit a document for publication as an RFC.
      Submissions must be made via electronic mail to the RFC Editor.
      Please consult RFC 1543, "Instructions to RFC Authors" [10], for
      further information.  RFCs are accessible online in public access
      files, and a short message is sent to a notification distribution
      list indicating the availability of the memo.  Requests to be
      added to this distribution list should be sent to RFC-
      [e-mail].

      The online files are copied by interested people and printed or
      displayed at their sites on their equipment.  (An RFC may also be
      returned via electronic mail in response to an electronic mail
      query.) This means that the format of the online files must meet
      the constraints of a wide variety of printing and display



User Services Working Group                                     [Page 6]

RFC 1594            FYI Q/A - for New Internet Users          March 1994


      equipment.

      Once a document is assigned an RFC number and published, that RFC
      is never revised or re-issued with the same number.  There is
      never a question of having the most recent version of a particular
      RFC.  However, a protocol (such as File Transfer Protocol (FTP))
      may be improved and re-documented many times in several different
      RFCs.  It is important to verify that you have the most recent RFC
      on a particular protocol.  The "Internet Official Protocol
      Standards" [2] memo is the reference for determining the correct
      RFC to refer to for the current specification of each protocol.

   6.2  How do I obtain RFCs?

      RFCs are available online at several repositories around the
      world.  For a list of repositories and instructions about how to
      obtain RFCs from each of the major U.S. ones, send a message to
      [e-mail].  As the text of the message, type
      "help: ways_to_get_rfcs" (without the quotes).

      An example of obtaining RFCs online follows.

      RFCs can be obtained via FTP from ds.internic.net with the
      pathname rfc/rfcNNNN.txt (where "NNNN" refers to the number of the
      RFC).  Login using FTP, username "anonymous" and your email
      address as password.  The Directory Services portion of the
      InterNIC also makes RFCs available via electronic mail, WAIS, and
      gopher.

      To obtain RFCs via electronic mail, send a mail message to
      [e-mail] and include any of the following commands
      in the message body:

         document-by-name rfcnnnn      where 'nnnn' is the RFC number
                                       The text version is sent.

         file /ftp/rfc/rfcnnnn.yyy     where 'nnnn' is the RFC number.
                                       and 'yyy' is 'txt' or 'ps'.

         help                          to get information on how to use
                                       the mailserver.

   6.3  How do I obtain a list of RFCs?

      Several sites make an index of RFCs available.  These sites are
      indicated in the ways_to_get_rfcs file mentioned above and in the
      next question.




User Services Working Group                                     [Page 7]

RFC 1594            FYI Q/A - for New Internet Users          March 1994


   6.4  What is the RFC-INFO service?

      The Information Sciences Institute, University of Southern
      California (ISI) has a service called RFC-INFO.  Even though this
      is a service, rather than a document, we'll discuss it in this
      section because it is so closely tied to RFC information.

      RFC-INFO is an email based service to help in locating and
      retrieval of RFCs, FYIs, STDs, and IMRs.  Users can ask for
      "lists" of all RFCs and FYIs having certain attributes ("filters")
      such as their ID, keywords, title, author, issuing organization,
      and date.  Once an RFC is uniquely identified (e.g., by its RFC
      number) it may also be retrieved.

      To use the service, send email to: [e-mail] with your
      requests as the text of the message.  Feel free to put anything in
      the SUBJECT, the system ignores it.  All input is case
      independent.  Report problems to: [e-mail].

      To get started, you may send a message to [e-mail] with
      requests such as in the following examples (without the
      explanations between brackets):

      Help: Help              [to get this information]

      List: FYI               [list the FYI notes]
      List: RFC               [list RFCs with window as keyword or
                               in title]
        keywords: window
      List: FYI               [list FYIs about windows]
        Keywords: window
      List: *                 [list both RFCs and FYIs about windows]
        Keywords: window
      List: RFC               [list RFCs about ARPANET, ARPA NETWORK,
                               etc.]
        title: ARPA*NET
      List: RFC               [list RFCs issued by MITRE, dated
                               1989-1991]
        Organization: MITRE
        Dated-after:  Jan-01-1989
        Dated-before: Dec-31-1991
      List: RFC               [list RFCs obsoleting a given RFC]
        Obsoletes: RFC0010
      List: RFC               [list RFCs by authors starting with
                               "Bracken"]
        Author: Bracken*      [* is a wild card]
      List: RFC               [list RFCs by both Postel and Gillman]
        Authors: J. Postel    [note, the "filters" are ANDed]



User Services Working Group                                     [Page 8]

RFC 1594            FYI Q/A - for New Internet Users          March 1994


        Authors: R. Gillman
      List: RFC               [list RFCs by any Crocker]
        Authors: Crocker
      List: RFC               [list only RFCs by S.D. Crocker]
        Authors: S.D. Crocker
      List: RFC               [list only RFCs by D. Crocker]
        Authors: D. Crocker

      Retrieve: RFC           [retrieve RFC-822]
        Doc-ID: RFC0822       [note, always 4 digits in RFC#]

      Help: Manual            [to retrieve the long user manual,
                               30+ pages]
      Help: List              [how to use the LIST request]
      Help: Retrieve          [how to use the RETRIEVE request]
      Help: Topics            [list topics for which help is available]
      Help: Dates             ["Dates" is such a topic]
      List: keywords          [list the keywords in use]
      List: organizations     [list the organizations known to the
                               system]

   6.5  Which RFCs are Standards?

      See "Internet Official Protocol Standards" (currently RFC 1540)
      [2].  This RFC documents the status of each RFC on the Internet
      standards track, as well as the status of RFCs of other types.  It
      is updated periodically; make sure you are referring to the most
      recent version.  In addition, the RFC Index maintained at the
      ds.internic.net repository notes the status of each RFC listed.

   6.6  What is an FYI?

      FYI stands for For Your Information.  FYIs are a subset of the RFC
      series of online documents.

      FYI 1 states, "The FYI series of notes is designed to provide
      Internet users with a central repository of information about any
      topics which relate to the Internet.  FYI topics may range from
      historical memos on 'Why it was was done this way' to answers to
      commonly asked operational questions.  The FYIs are intended for a
      wide audience.  Some FYIs will cater to beginners, while others
      will discuss more advanced topics."

      In general, then, FYI documents tend to be more information
      oriented, while RFCs are usually (but not always) more technically
      oriented.

      FYI documents are assigned both an FYI number and an RFC number.



User Services Working Group                                     [Page 9]

RFC 1594            FYI Q/A - for New Internet Users          March 1994


      As RFCs, if an FYI is ever updated, it is issued again with a new
      RFC number; however, its FYI number remains unchanged.  This can
      be a little confusing at first, but the aim is to help users
      identify which FYIs are about which topics.  For example, FYI 4
      will always be FYI 4, even though it may be updated several times
      and during that process receive different RFC numbers.  Thus, you
      need only to remember the FYI number to find the proper document.
      Of course, remembering titles often works as well.

      FYIs can be obtained in the same way RFCs can and from the same
      repositories.  In general, their pathnames are fyi/fyiNN.txt or
      fyi/fyiNN.ps, where NN is the number of the FYI without leading
      zeroes.

   6.7  What is an STD?

      The newest subseries of RFCs are the STDs (Standards).  RFC 1311
      [12], which introduces this subseries, states that the intent of
      STDs is to identify clearly those RFCs that document Internet
      standards.  An STD number will be assigned only to those
      specifications that have completed the full process of
      standardization in the Internet.  Existing Internet standards have
      been assigned STD numbers; a list of them can be found both in RFC
      1311 and in the, "Internet Official Protocol Standards" RFC.

      Like FYIs, once a standard has been assigned an STD number, that
      number will not change, even if the standard is reworked and re-
      specified and later issued with a new RFC number.

      It is important to differentiate between a "standard" and
      "document".  Different RFC documents will always have different
      RFC numbers.  However, sometimes the complete specification for a
      standard will be contained in more than one RFC document.  When
      this happens, each of the RFC documents that is part of the
      specification for that standard will carry the same STD number.
      For example, the Domain Name System (DNS) is specified by the
      combination of RFC 1034 and RFC 1035; therefore, both of those
      RFCs are labeled STD 13.

   6.8  What is the Internet Monthly Report?

      The Internet Monthly Report (IMR) communicates online to the
      Internet community the accomplishments, milestones reached, or
      problems discovered by the participating organizations.  Many
      organizations involved in the Internet provide monthly updates of
      their activities for inclusion in this report.  The IMR is for
      Internet information purposes only.




User Services Working Group                                    [Page 10]

RFC 1594            FYI Q/A - for New Internet Users          March 1994


      You can receive the report online by joining the mailing list that
      distributes the report.  Requests to be added or deleted from the
      Internet Monthly Report list should be sent to "imr-
      [e-mail]".

      In addition, back issues of the Report are available for anonymous
      FTP from the host ftp.isi.edu in the in-notes/imr directory, with
      the file names in the form imryymm.txt, where yy is the last two
      digits of the year and mm two digits for the month.  For example,
      the July 1992 Report is in the file imr9207.txt.

   6.9  What is an Internet Draft?  Are there any guidelines available
        for writing one?

      Internet Drafts (I-Ds) are the current working documents of the
      IETF.  Internet Drafts are generally in the format of an RFC with
      some key differences:

         -  The Internet Drafts are not RFCs and are not a numbered
            document series.

         -  The words INTERNET-DRAFT appear in place of RFC XXXX
            in the upper left-hand corner.

         -  The document does not refer to itself as an RFC or as a
            Draft RFC.

         -  An Internet Draft does not state nor imply that it is a
            proposed standard.  To do so conflicts with the role of
            the IAB, the RFC Editor, and the Internet Engineering
            Steering Group (IESG).

      An Internet Drafts directory has been installed to make draft
      documents available for review and comment by the IETF members.
      These draft documents that will ultimately be submitted to the IAB
      and the RFC Editor to be considered for publishing as RFCs.  The
      Internet Drafts Directories are maintained on several Internet
      sites.  There are several "shadow" machines which contain the IETF
      and Internet Drafts Directories.  They are:

         West Coast (US) Address:  ftp.isi.edu (128.9.0.32)
         East Coast (US) Address:  ds.internic.net (198.49.45.10)
         Europe Address:  nic.nordu.net (192.36.148.17)
         Pacific Rim Address:  munnari.oz.au (128.250.1.21)

      To access these directories, use anonymous FTP.  Login with
      username "anonymous" and your email address as password (or
      "guest" if that fails).  Once logged in, change to the desired



User Services Working Group                                    [Page 11]