rfc1325.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 1,536 行 · 第 1/5 页

      the top-level domain (the root domain is always null).  For
      example, PARIS.NISC.SRI.COM is a Fully Qualified Domain Name for
      the host at 192.33.33.109.  In addition, NISC.SRI.COM is the FQDN
      for the NISC domain.

6. Questions About Internet Documentation

   What is an RFC?

      The Request for Comments documents (RFCs) are working notes of the
      Internet research and development community.  A document in this
      series may be on essentially any topic related to computer
      communication, and may be anything from a meeting report to the
      specification of a standard.  Submissions for Requests for
      Comments may be sent to the RFC Editor ([e-mail]).  The
      RFC Editor is Jon Postel.

      Most RFCs are the descriptions of network protocols or services,
      often giving detailed procedures and formats for their
      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



User Services Working Group                                     [Page 6]

RFC 1325            FYI Q/A - for New Internet Users            May 1992


      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 1111, "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
      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 "IAB Official Protocol Standards"
      [2] memo is the reference for determining the correct RFC to refer
      to for the current specification of each protocol.

   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 US ones, FTP the file in-
      notes/rfc-retrieval.txt from the host ISI.EDU.  That host supports
      anonymous login.  You can also get information about RFC
      repositories via electronic mail.  Send a message to rfc-
      [e-mail].  In the body of the message, type
      "help: ways_to_get_rfcs" (without the quotes).

      Two examples of obtaining RFCs online follow.

      RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
      rfc/rfcNNNN.txt (where "NNNN" refers to the number of the RFC).
      Login using FTP, username "anonymous" and password "guest".

      RFCs can also be obtained via FTP from NIS.NSF.NET.  Using FTP,



User Services Working Group                                     [Page 7]

RFC 1325            FYI Q/A - for New Internet Users            May 1992


      login with username "anonymous" and password "guest"; then connect
      to the RFC directory ("cd RFC").  The file name is of the form
      RFCnnnn.TXT-1 (where "nnnn" refers to the number of the RFC).  The
      NIS also provides an automatic mail service for those sites which
      cannot use FTP.  Address the request to [e-mail] and
      leave the subject field of the message blank.  The first line of
      the text of the message must be "SEND RFCnnnn.TXT-1", where nnnn
      is replaced by the RFC number.

      Requests for special distribution should be addressed to either
      the author of the RFC in question, to [e-mail], or to
      [e-mail].  SRI International operates the
      FTP.NISC.SRI.COM online repository of RFCs and other files, and
      makes the RFCs available in hardcopy for those people who have
      neither FTP nor e-mail access to the Internet.  Hardcopy RFCs are
      sold by SRI on a cost-recovery basis.  In addition, SRI has a
      hardcopy subscription service for RFCs, as well as several
      publications that incorporate selections of RFCs.  Unless
      specifically noted otherwise on the RFC itself, all RFCs are for
      unlimited distribution.

   How do I obtain a list of RFCs?

      SRI maintains a file that is an index of the RFCs.  It lists each
      RFC, starting with the most recent, and for each RFC provides the
      number, title, author(s), issue date, and number of hardcopy
      pages.  In addition, it lists the online formats (PostScript or
      ASCII text) for each RFC and the number of bytes each such version
      is online.  If an RFC is also an FYI, that fact is noted, with the
      corresponding FYI number.  (There is a parallel FYI Index
      available).  Finally, the Index notes whether or not an RFC is
      obsoleted or updated by another RFC, and gives the number of that
      RFC, or if an RFC itself obsoletes or updates another RFC, and
      gives that RFC number.  The index is updated online each time an
      RFC is issued.

      This RFC Index is available online for anonymous FTP from the
      FTP.NISC.SRI.COM host as rfc/rfc-index.txt.  The FYI Index is
      online as fyi/fyi-index.txt.  They are also available via
      electronic mail by sending a message to [e-mail].
      In the body of the message, say "send rfc-index" or "send fyi-
      index" (don't use quotes, but do use lowercase).  The RFC Index is
      also available from the SRI in hardcopy for $12, as are individual
      RFCs.  Call SRI at 1-415-859-3695 for help in obtaining the Index.







User Services Working Group                                     [Page 8]

RFC 1325            FYI Q/A - for New Internet Users            May 1992


   What is the RFC-INFO service?

      The Information Sciences Institute, University of Southern
      California (ISI) has announced 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 e-mail based service to help in locating and
      retrival of RFCs and FYIs.  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 e-mail to [e-mail] with your
      requests in the body 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 matches everything]
List: RFC               [list RFCs by both Postel and Gillman]
  Authors: J. Postel    [note, the "filters" are ANDed]
  Authors: R. Gillman
List: RFC               [list RFCs by any Crocker]
  Authors: Crocker
List: RFC               [list only RFCs by S.D. Crocker]



User Services Working Group                                     [Page 9]

RFC 1325            FYI Q/A - for New Internet Users            May 1992


  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]

   Which RFCs are Standards?

      See "IAB Official Protocol Standards" (currently, RFC 1280) [2].

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



User Services Working Group                                    [Page 10]

RFC 1325            FYI Q/A - for New Internet Users            May 1992


      zeroes.

   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 IAB 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.

   What is the Internet Monthly Report?

      The Internet Monthly Report communicates online to the Internet
      Research Group 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 Internet Monthly Report is for Internet information purposes
      only.

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

      In addition, back issues of the Report are available for anonymous
      FTP from the host NIS.NSF.NET in the 'imr' directory with the file
      names in the form IMRYY-MM.TXT, where YY is the last two digits of
      the year and MM two digits for the month.  For example, the June
      1991 Report is in the file IMR91-06.TXT.