rfc1340.txt

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

Network	Working	Group					     J.	Reynolds
Request	for Comments: 1340				       J. Postel
Obsoletes RFCs:	1060, 1010, 990, 960,				     ISI
943, 923, 900, 870, 820, 790, 776, 770,			       July 1992
762, 758,755, 750, 739,	604, 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
   WELL	KNOWN PORT NUMBERS........................................  9
   REGISTERED PORT NUMBERS........................................ 23
   INTERNET MULTICAST ADDRESSES................................... 27
   IANA	ETHERNET ADDRESS BLOCK.................................... 29
   IP TOS PARAMETERS.............................................. 30
   IP TIME TO LIVE PARAMETER...................................... 32
   DOMAIN SYSTEM PARAMETERS....................................... 33
   BOOTP PARAMETERS............................................... 35
   NETWORK MANAGEMENT PARAMETERS.................................. 36
   MILNET LOGICAL ADDRESSES....................................... 49
   MILNET LINK NUMBERS............................................ 50
   MILNET X.25 ADDRESS MAPPINGS................................... 51
   IEEE	802 NUMBERS OF INTEREST................................... 53
   ETHERNET NUMBERS OF INTEREST................................... 54
   ETHERNET VENDOR ADDRESS COMPONENTS............................. 57
   ETHERNET MULTICAST ADDRESSES................................... 60
   XNS PROTOCOL	TYPES............................................. 62
   PROTOCOL/TYPE FIELD ASSIGNMENTS................................ 63
   PRONET 80 TYPE NUMBERS......................................... 64
   POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTS...................... 65
   ADDRESS RESOLUTION PROTOCOL PARAMETERS......................... 69
   REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES............ 70
   DYNAMIC REVERSE ARP............................................ 70
   INVERSE ADDRESS RESOULUTION PROTOCOL........................... 70
   X.25	TYPE NUMBERS.............................................. 71



Reynolds & Postel					        [Page 1]

RFC 1340		    Assigned Numbers		       July 1992


   PUBLIC DATA NETWORK NUMBERS.................................... 72
   TELNET OPTIONS................................................. 75
   MAIL	ENCRYPTION TYPES.......................................... 76
   MIME	TYPES..................................................... 77
   CHARACTER SETS................................................. 79
   MACHINE NAMES.................................................. 83
   SYSTEM NAMES................................................... 87
   PROTOCOL AND	SERVICE	NAMES..................................... 88
   TERMINAL TYPE NAMES............................................ 92
   DOCUMENTS...................................................... 96
   PEOPLE.........................................................109
   Security Considerations........................................139
   Authors' Addresses.............................................139

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 "IAB Official
   Protocol Standards" [62].

   In the entries below, the name and mailbox of the responsible
   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.





Reynolds & Postel					        [Page 2]

RFC 1340		    Assigned Numbers		       July 1992


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






Reynolds & Postel					        [Page 3]

RFC 1340		    Assigned Numbers		       July 1992


Special	Addresses:

   There are five classes of IP	addresses: Class A through Class E
   [119].  Of these, Class E addresses are reserved for	experimental
   use.	 A gateway which is not	participating in these experiments must
   ignore all datagrams	with a 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.

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

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



Reynolds & Postel					        [Page 4]

RFC 1340		    Assigned Numbers		       July 1992


	 (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 1340		    Assigned Numbers		       July 1992


			      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 1340		    Assigned Numbers		       July 1992


			       PROTOCOL	NUMBERS

   In the Internet Protocol (IP) [45,105] there	is a field, called
   Protocol, to	identify the the next level protocol.  This is an 8 bit
   field.

   Assigned Internet Protocol Numbers

      Decimal	 Keyword     Protocol			      References
      -------	 -------     --------			      ----------
	   0		     Reserved				   [JBP]
	   1	 ICMP	     Internet Control Message		[97,JBP]
	   2	 IGMP	     Internet Group Management		[43,JBP]
	   3	 GGP	     Gateway-to-Gateway			 [60,MB]
	   4	 IP	     IP	in IP (encasulation)		   [JBP]
	   5	 ST	     Stream				[49,JWF]
	   6	 TCP	     Transmission Control	       [106,JBP]
	   7	 UCL	     UCL				    [PK]
	   8	 EGP	     Exterior Gateway Protocol	      [123,DLM1]
	   9	 IGP	     any private interior gateway	   [JBP]
	  10	 BBN-RCC-MON BBN RCC Monitoring			   [SGC]
	  11	 NVP-II	     Network Voice Protocol		[22,SC3]
	  12	 PUP	     PUP			       [8,XEROX]
	  13	 ARGUS	     ARGUS				  [RWS4]
	  14	 EMCON	     EMCON				   [BN7]
	  15	 XNET	     Cross Net Debugger		       [56,JFH2]
	  16	 CHAOS	     Chaos				   [NC3]
	  17	 UDP	     User Datagram		       [104,JBP]
	  18	 MUX	     Multiplexing			[23,JBP]
	  19	 DCN-MEAS    DCN Measurement Subsystems		  [DLM1]
	  20	 HMP	     Host Monitoring			[59,RH6]
	  21	 PRM	     Packet Radio Measurement		   [ZSU]
	  22	 XNS-IDP     XEROX NS IDP		     [133,XEROX]
	  23	 TRUNK-1     Trunk-1				  [BWB6]
	  24	 TRUNK-2     Trunk-2				  [BWB6]
	  25	 LEAF-1	     Leaf-1				  [BWB6]
	  26	 LEAF-2	     Leaf-2				  [BWB6]
	  27	 RDP	     Reliable Data Protocol	       [138,RH6]
	  28	 IRTP	     Internet Reliable Transaction	[79,TXM]
	  29	 ISO-TP4     ISO Transport Protocol Class 4    [63,RC77]
	  30	 NETBLT	     Bulk Data Transfer	Protocol       [20,DDC1]
	  31	 MFE-NSP     MFE Network Services Protocol    [124,BCH2]
	  32	 MERIT-INP   MERIT Internodal Protocol		   [HWB]
	  33	 SEP	     Sequential	Exchange Protocol	 [JC120]
	  34	 3PC	     Third Party Connect Protocol	  [SAF3]
	  35	 IDPR	     Inter-Domain Policy Routing Protocol [MXS1]
	  36	 XTP	     XTP				   [GXC]
	  37	 DDP	     Datagram Delivery Protocol		   [WXC]



Reynolds & Postel					        [Page 7]