rfc870.txt

RFC 相关的技术文档

Assigned Numbers                                                 RFC 870
ARPANET Link Numbers


                     ASSIGNED ARPANET LINK NUMBERS

   The word "link" here refers to a field in the original ARPANET
   Host/IMP interface leader.  The link was originally defined as an
   8-bit field.  Later specifications defined this field as the
   "Message-ID" with a length of 12 bits.  The name link now refers to
   the high order 8 bits of this 12-bit message-id field.  The low order
   4 bits of the message-id field are to be zero unless explicitly
   specified otherwise for the particular protocol used on that link.
   The Host/IMP interface is defined in BBN Report 1822 [2].

   Link Assignments:

      Decimal   Octal     Description                         References
      -------   -----     -----------                         ----------
      0         0         Reserved                                 [JBP]
      1-149     1-225     Unassigned                               [JBP]
      150       226       Xerox NS IP                           [62,LLG]
      151       227       Unassigned                               [JBP]
      152       230       PARC Universal Protocol               [6,EAT3]
      153       231       TIP Status Reporting                     [JGH]
      154       232       TIP Accounting                           [JGH]
      155       233       Internet Protocol (regular)        [16,47,JBP]
      156-158   234-236   Internet Protocol (experimental)   [16,47,JBP]
      159-195   237-303   Unassigned                               [JBP]
      196-255   304-377   Experimental Protocols                   [JBP]
      248-255   370-377   Network Maintenance                      [JGH]

                      ETHERNET NUMBERS OF INTEREST

   Many of the networks of all classes are Ethernets (10Mb) or
   Experimental Ethernets (3Mb).  These systems use a message "type"
   field in much the same way the ARPANET uses the "link" field.

   Assignments:

      Ethernet          Exp. Ethernet    Description          References
      --------------    --------------   -----------          ----------
      decimal    Hex    decimal  octal
         512   02,00        512   1000   XEROX PUP              [6,EAT3]
        1536   06,00       1536   3000   XEROX NS IDP           [62,LLG]
        2048   08,00        513   1001   DOD IP              [16,47,JBP]
        2054   08,06        -      -     Address Res           [33,DCP1]







Reynolds & Postel                                              [Page 14]



Assigned Numbers                                                 RFC 870
Public Data Network Numbers


                  ASSIGNED PUBLIC DATA NETWORK NUMBERS

   One of the Internet Class A Networks is the international system of
   Public Data Networks.  This section lists the mapping between the
   Internet Addresses and the Public Data Network Addresses (X.121).

   Assignments:

      Internet           Public Data Net    Description       References
      ---------------   -----------------   -----------       ----------
      014.000.000.000                       Reserved               [JBP]
      014.000.000.001   3110-317-00035 00   PURDUE-TN              [CAK]
      014.000.000.002   3110-608-00027 00   UWISC-TN               [CAK]
      014.000.000.003   3110-302-00024 00   UDEL-TN                [CAK]
      014.000.000.004   2342-192-00149 23   UCL-VTEST               [PK]
      014.000.000.005   2342-192-00300 23   UCL-TG                  [PK]
      014.000.000.006   2342-192-00300 25   UK-SATNET               [PK]
      014.000.000.007   3110-608-00024 00   UWISC-IBM             [MHS1]
      014.000.000.008   3110-213-00045 00   RAND-TN                [MO2]
      014.000.000.009   2342-192-00300 23   UCL-CS                  [PK]
      014.000.000.010   3110-617-00025 00   BBN-VAN-GW            [JD21]
      014.000.000.011-014.255.255.254       Unassigned             [JBP]
      014.255.255.255                       Reserved               [JBP]

   The standard for transmission of IP datagrams over the Public Data
   Network is specified in [27].
























Reynolds & Postel                                              [Page 15]



Assigned Numbers                                                 RFC 870
Documents


                               DOCUMENTS
                               ---------

   [1]    Aerospace, Internal Report, ATM-83(3920-01)-3, 1982.

   [2]    BBN, "Specifications for the Interconnection of a Host and an
          IMP", Report 1822, Bolt Beranek and Newman, Cambridge,
          Massachusetts, revised, December 1981.

   [3]    Bennett, C., "A Simple NIFTP-Based Mail System", IEN 169,
          University College, London, January 1981.

   [4]    Bhushan, A., "A Report on the Survey Project", RFC 530,
          NIC 17375, 22 June 1973.

   [5]    Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language
          (version 2.1)", ISI/TM-80-18, USC/Information Sciences
          Institute, July 1980.

   [6]    Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An
          Internetwork Architecture", XEROX Palo Alto Research Center,
          CSL-79-10, July 1979; also in IEEE Transactions on
          Communication, Volume COM-28, Number 4, April 1980.

   [7]    Braden, R., "NETRJS Protocol", RFC 740, NIC 42423,
          22 November 1977.  Also in [17].

   [8]    Bressler, B., "Remote Job Entry Protocol",  RFC 407, NIC
          12112, 16 October 72.  Also in [17].

   [9]    Bressler, R., "Inter-Entity Communication -- An Experiment",
          RFC 441, NIC 13773, 19 January 1973.

   [10]   CCA, "Datacomputer Version 5/4 User Manual", Computer
          Corporation of America, August 1979.

   [11]   Clark, D., "Revision of DSP Specification", Local Network
          Note 9, Laboratory for Computer Science, MIT, 17 June 1977.

   [12]   Cohen, D., "Specifications for the Network Voice Protocol",
          RFC 741, ISI/RR 7539, USC/Information Sciences Institute,
          March 1976.

   [13]   Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90,
          USC/Information Sciences Institute, May 1979.





Reynolds & Postel                                              [Page 16]



Assigned Numbers                                                 RFC 870
Documents


   [14]   COMPASS, "Semi-Annual Technical Report", CADD-7603-0411,
          Massachusetts Computer Associates, 4 March 1976. Also as,
          "National Software Works, Status Report No. 1,"
          RADC-TR-76-276, Volume 1, September 1976. And COMPASS. "Second
          Semi-Annual Report," CADD-7608-1611, Massachusetts Computer
          Associates, 16 August 1976.

   [15]   Crispin, M., "SUPDUP Protocol", RFC 734, NIC 41953,
          7 October 1977.  Also in [17].

   [16]   Feinler, E., "Internet Protocol Transition Workbook", Network
          Information Center, SRI International, March 1982.

   [17]   Feinler, E. and J. Postel, eds., "ARPANET Protocol Handbook",
          NIC 7104, for the Defense Communications Agency by SRI
          International, Menlo Park, California, Revised January 1978.

   [18]   Forgie, J., "ST - A Proposed Internet Stream Protocol",
          IEN 119, M.I.T. Lincoln Laboratory, September 1979.

   [19]   Forsdick, H., "CFTP", Network Message, Bolt Berenak and
          Newman, January 1982.

   [20]   Harrenstien, K., "Name/Finger", RFC 742, NIC 42758,
          30 December 1977.  Also in [17].

   [21]   Harrenstien, K., V. White, and E. Feinler, "Hostnames Server",
          RFC 811, SRI International, March 1982.

   [22]   Harrenstien, K., and V. White, "Nicname/Whois", RFC 812, SRI
          International, March 1982.

   [23]   Haverty, J., "XNET Formats for Internet Protocol Version 4",
          IEN 158, October 1980.

   [24]   Hinden, R., A. Sheltzer, "The DARPA Internet Gateway",
          RFC 823, September 1982.

   [25]   Honeywell CISL, Internal Document, "AFSDSC Hyperchannel RPQ
          Project Plan".

   [26]   Honeywell CISL, Internal Document, "Multics MR11 PFS".

   [27]   Korb, John T., "A Standard for the Transmission of IP
          Datagrams Over Public Data Networks", RFC 877, Purdue
          University, September 1983.




Reynolds & Postel                                              [Page 17]



Assigned Numbers                                                 RFC 870
Documents


   [28]   Littauer, B., "A Host Monitoring Protocol", IEN 197, Bolt
          Berenak and Newman, September 1981.

   [29]   Macgregor, W., and D. Tappan, "The CRONUS Virtual Local
          Network", RFC 824, Bolt Beranek and Newman, 22 August 1982.

   [30]   Malis, A., "Logical Addressing Implementation Specification",
          BBN Report 5256, pp 31-36, May 1983.

   [31]   Metcalfe, R.M. and D.R. Boggs, "Ethernet: Distributed Packet
          Switching for Local Computer Networks", Communications of the
          ACM, 19 (7), pp 395-402, July 1976.

   [32]   NSW Protocol Committee, "MSG: The Interprocess Communication
          Facility for the National Software Works", CADD-7612-2411,
          Massachusetts Computer Associates, BBN 3237, Bolt Beranek and
          Newman, Revised 24 December 1976.

   [33]   Plummer, D., "An Ethernet Address Resolution Protocol or
          Converting Network Protocol Addresses to 48-bit Ethernet
          Addresses for Transmission on Ethernet Hardware", RFC 826, MIT
          LCS, November 1982.

   [34]   Postel, J., "Active Users", RFC 866, USC/Information Sciences
          Institute, May 1983.

   [35]   Postel, J., "Character Generator Protocol", RFC 864,
          USC/Information Sciences Institute, May 1983.

   [36]   Postel, J., "Daytime Protocol", RFC 867, USC/Information
          Sciences Institute, May 1983.

   [37]   Postel, J., "Discard Protocol", RFC 863, USC/Information
          Sciences Institute, May 1983.

   [38]   Postel, J., "Echo Protocol", RFC 862, USC/Information Sciences
          Institute, May 1983.

   [39]   Postel, J., "File Transfer Protocol", RFC 765, IEN 149,
          USC/Information Sciences Institute, June 1980.

   [40]   Postel, J., "Internet Control Message Protocol - DARPA
          Internet Program Protocol Specification", RFC 792,
          USC/Information Sciences Institute, September 1981.

   [41]   Postel, J., "Internet Message Protocol", RFC 759, IEN 113,
          USC/Information Sciences Institute, August 1980.



Reynolds & Postel                                              [Page 18]



Assigned Numbers                                                 RFC 870
Documents


   [42]   Postel, J., "Name Server", IEN 116, USC/Information Sciences
          Institute, August 1979.

   [43]   Postel, J., "Quote of the Day Protocol", RFC 865,
          USC/Information Sciences Institute, May 1983.

   [44]   Postel, J., "Remote Telnet Service", RFC 818, USC/Information
          Sciences Institute, November 1982.

   [45]   Postel, J., "Simple Mail Transfer Protocol", RFC 821,
          USC/Information Sciences Institute, August 1982.

   [46]   Postel, J., "User Datagram Protocol", RFC 768 USC/Information
          Sciences Institute, August 1980.

   [47]   Postel, J., ed., "Internet Protocol - DARPA Internet Program
          Protocol Specification", RFC 791, USC/Information Sciences
          Institute, September 1981.

   [48]   Postel, J., ed., "Transmission Control Protocol - DARPA
          Internet Program Protocol Specification", RFC 793,
          USC/Information Sciences Institute, September 1981.

   [49]   Postel, J., and K. Harrenstien, "Time Protocol", RFC 868,
          USC/Information Sciences Institute, May 1983.

   [50]   Postel, J., and J. Reynolds, "Telnet Protocol Specification",
          RFC 854, USC/Information Sciences Institute, May 1983.

   [51]   Reed, D., "Protocols for the LCS Network", Local Network Note
          3, Laboratory for Computer Science, MIT, 29 November 1976.

   [52]   Reynolds, J. and J. Postel, "Official Protocols", RFC 880,
          USC/Information Sciences Institute, October 1983.

   [53]   Rosen, E., "Exterior Gateway Protocol" RFC 827, Bolt Berenak
          and Newman, October 1982.

   [54]   Skelton, A., S. Holmgren, and D. Wood, "The MITRE Cablenet
          Project", IEN 96, April 1979.

   [55]   Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783,
          MIT/LCS, June 1981.

   [56]   Solomon, M., L. Landweber, and D, Neuhengen, "The CSNET Name
          Server", Computer Networks, v.6, n.3, pp. 161-172, July 1982.




Reynolds & Postel                                              [Page 19]



Assigned Numbers                                                 RFC 870
Documents


   [57]   Sproull, R., and E. Thomas, "A Networks Graphics Protocol",
          NIC 24308, 16 August 1974.  Also in [17].

   [58]   "The Ethernet - A Local Area Network", Version 1.0, Digital
          Equipment Corporation, Intel Corporation, Xerox Corporation,
          September 1980.

   [59]   The High Level Protocol Group, "A Network Independent File
          Transfer Protocol",  INWG Protocol Note 86, December 1977.

   [60]   Whelan, D., "The Caltech Computer Science Department Network",
          5052:DF:82, Caltech Computer Science Department, 1982.

   [61]   XEROX, "The Ethernet, A Local Area Network: Data Link Layer
          and Physical Layer Specification", X3T51/80-50, Xerox
          Corporation, Stamford, CT., October 1980.

   [62]   XEROX, "Internet Transport Protocols",  XSIS 028112, Xerox
          Corporation, Stamford, Connecticut, December 1981.