rfc1060.txt

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

Network Working Group                                        J. Reynolds
Request for Comments: 1060                                     J. Postel
Obsoletes RFCs: 1010, 990, 960, 943, 923, 900, 870,                  ISI
820, 790, 776, 770, 762, 758,755, 750, 739, 604,              March 1990
503, 433, 349
Obsoletes IENs: 127, 117, 93

                            ASSIGNED NUMBERS

STATUS OF THIS MEMO

   This memo is a status report on the parameters (i.e., numbers and
   keywords) used in protocols in the Internet community.  Distribution
   of this memo is unlimited.

                             Table of Contents

INTRODUCTION.................................................... 2
Data Notations.................................................. 3
Special Addresses............................................... 4
VERSION NUMBERS................................................. 6
PROTOCOL NUMBERS................................................ 7
PORT NUMBERS.................................................... 9
UNIX PORTS......................................................13
INTERNET MULTICAST ADDRESSES....................................19
IANA ETHERNET ADDRESS BLOCK.....................................20
IP TOS PARAMETERS...............................................21
IP TIME TO LIVE PARAMETER.......................................23
DOMAIN SYSTEM PARAMETERS........................................24
BOOTP PARAMETERS................................................25
NETWORK MANAGEMENT PARAMETERS...................................26
ARPANET AND MILNET LOGICAL ADDRESSES............................30
ARPANET AND MILNET LINK NUMBERS.................................31
ARPANET AND MILNET X. 25 ADDRESS MAPPINGS.......................32
IEEE 802 NUMBERS OF INTEREST....................................34
ETHERNET NUMBERS OF INTEREST....................................35
ETHERNET VENDOR ADDRESS COMPONENTS..............................38
ETHERNET MULTICAST ADDRESSES....................................41
XNS PROTOCOL TYPES..............................................43
PROTOCOL/TYPE FIELD ASSIGNMENTS.................................44
PRONET 80 TYPE NUMBERS..........................................45
ADDRESS RESOLUTION PROTOCOL PARAMETERS..........................46
REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES.............47
DYNAMIC REVERSE ARP.............................................47
X.25 TYPE NUMBERS...............................................48
PUBLIC DATA NETWORK NUMBERS.....................................49
TELNET OPTIONS..................................................51
MAIL ENCRYPTION TYPES...........................................52



Reynolds & Postel                                               [Page 1]

RFC 1060                    Assigned Numbers                  March 1990


MACHINE NAMES...................................................53
SYSTEM NAMES....................................................57
PROTOCOL AND SERVICE NAMES......................................58
TERMINAL TYPE NAMES.............................................62
DOCUMENTS.......................................................65
PEOPLE..........................................................76
Security Considerations.........................................86
Authors' Addresses..............................................86

INTRODUCTION

   This Network Working Group Request for Comments documents the
   currently assigned values from several series of numbers used in
   network protocol implementations.  This RFC will be updated
   periodically, and in any case current information can be obtained from
   the Internet Assigned Numbers Authority (IANA).  If you are developing
   a protocol or application that will require the use of a link, socket,
   port, protocol, etc., please contact the IANA to receive a number
   assignment.

   Joyce K. Reynolds
   Internet Assigned Numbers Authority
   USC - Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, California  90292-6695

   Phone: [phone]

   Electronic mail: [e-mail]

   Most of the protocols mentioned here are documented in the RFC series
   of notes.  Some of the items listed are undocumented.  Further
   information on protocols can be found in the memo "Official Internet
   Protocols" [118].  The more prominent and more generally used are
   documented in the "DDN Protocol Handbook, Volume Two, DARPA Internet
   Protocols" [45] prepared by the NIC.  Other collections of older or
   obsolete protocols are contained in the "Internet Protocol Transition
   Workbook" [76], or in the "ARPANET Protocol Transition Handbook"
   [47].  For further information on ordering the complete 1985 DDN
   Protocol Handbook, write: SRI International (SRI-NIC), DDN Network
   Information Center, Room EJ291, 333 Ravenswood Avenue, Menlo Park,
   CA., 94025; or call: 1-800-235-3155.  Also, the Internet Activities
   Board (IAB) publishes the "IAB Official Protocol Standards" [62],
   which describes the state of standardization of protocols used in the
   Internet.  This document is issued quarterly.  Current copies may be
   obtained from the DDN Network Information Center or from the IANA.

   In the entries below, the name and mailbox of the responsible



Reynolds & Postel                                               [Page 2]

RFC 1060                    Assigned Numbers                  March 1990


   individual is indicated.  The bracketed entry, e.g., [nn,iii], at the
   right hand margin of the page indicates a reference for the listed
   protocol, where the number ("nn") cites the document and the letters
   ("iii") cites the person.  Whenever possible, the letters are a NIC
   Ident as used in the WhoIs (NICNAME) service.

Data Notations

   The convention in the documentation of Internet Protocols is to
   express numbers in decimal and to picture data in "big-endian" order
   [21].  That is, fields are described left to right, with the most
   significant octet on the left and the least significant octet on the
   right.

   The order of transmission of the header and data described in this
   document is resolved to the octet level.  Whenever a diagram shows a
   group of octets, the order of transmission of those octets is the
   normal order in which they are read in English.  For example, in the
   following diagram the octets are transmitted in the order they are
   numbered.


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |       1       |       2       |       3       |       4       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |       5       |       6       |       7       |       8       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |       9       |      10       |      11       |      12       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                        Transmission Order of Bytes

   Whenever an octet represents a numeric quantity the left most bit in
   the diagram is the high order or most significant bit.  That is, the
   bit labeled 0 is the most significant bit.  For example, the
   following diagram represents the value 170 (decimal).


                             0 1 2 3 4 5 6 7
                            +-+-+-+-+-+-+-+-+
                            |1 0 1 0 1 0 1 0|
                            +-+-+-+-+-+-+-+-+

                           Significance of Bits

   Similarly, whenever a multi-octet field represents a numeric quantity



Reynolds & Postel                                               [Page 3]

RFC 1060                    Assigned Numbers                  March 1990


   the left most bit of the whole field is the most significant bit.
   When a multi-octet quantity is transmitted the most significant octet
   is transmitted first.

Special Addresses:

   There are five classes of IP addresses:  Class A through Class E
   [119].  Of these, Class D and Class E addresses are reserved for
   experimental use.  A gateway which is not participating in these
   experiments must ignore all datagrams with a Class D or Class E
   destination IP address.  ICMP Destination Unreachable or ICMP
   Redirect messages must not result from receiving such datagrams.

   There are certain special cases for IP addresses [11].  These special
   cases can be concisely summarized using the earlier notation for an
   IP address:

         IP-address ::=  { <Network-number>, <Host-number> }

            or

         IP-address ::=  { <Network-number>, <Subnet-number>,
                                                         <Host-number> }

   if we also use the notation "-1" to mean the field contains all 1
   bits.  Some common special cases are as follows:

         (a)   {0, 0}

            This host on this network.  Can only be used as a source
            address (see note later).

         (b)   {0, <Host-number>}

            Specified host on this network.  Can only be used as a
            source address.

         (c)   { -1, -1}

            Limited broadcast.  Can only be used as a destination
            address, and a datagram with this address must never be
            forwarded outside the (sub-)net of the source.

         (d)   {<Network-number>, -1}

            Directed broadcast to specified network.  Can only be used
            as a destination address.




Reynolds & Postel                                               [Page 4]

RFC 1060                    Assigned Numbers                  March 1990


         (e)   {<Network-number>, <Subnet-number>, -1}

            Directed broadcast to specified subnet.  Can only be used as
            a destination address.

         (f)   {<Network-number>, -1, -1}

            Directed broadcast to all subnets of specified subnetted
            network.  Can only be used as a destination address.

         (g)   {127, <any>}

            Internal host loopback address.  Should never appear outside
            a host.





































Reynolds & Postel                                               [Page 5]

RFC 1060                    Assigned Numbers                  March 1990


                              VERSION NUMBERS

   In the Internet Protocol (IP) [45,105] there is a field to identify
   the version of the internetwork general protocol.  This field is 4
   bits in size.

   Assigned Internet Version Numbers

      Decimal   Keyword    Version                            References
      -------   -------    -------                            ----------
          0                Reserved                                [JBP]
        1-3                Unassigned                              [JBP]
          4       IP       Internet Protocol                   [105,JBP]
          5       ST       ST Datagram Mode                     [49,JWF]
        6-14               Unassigned                              [JBP]
          15               Reserved                                [JBP]



































Reynolds & Postel                                               [Page 6]

RFC 1060                    Assigned Numbers                  March 1990


                               PROTOCOL NUMBERS