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.............................................47X.25 TYPE NUMBERS...............................................48 PUBLIC DATA NETWORK NUMBERS.....................................49 TELNET OPTIONS..................................................51 MAIL ENCRYPTION TYPES...........................................52 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
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: (213) 822-1511
Electronic mail: JKREY@ISI.EDU
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 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.
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.
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).
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.
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:
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.
Ports are used in the TCP [45,106] to name the ends of logical connections which carry long term conversations. For the purpose of providing services to unknown callers, a service contact port is defined. This list specifies the port used by the server process as its contact port. The contact port is sometimes called the "well-known port".
To the extent possible, these same port assignments are used with the UDP [46,104].
To the extent possible, these same port assignments are used with the ISO-TP4 [64].
The assigned ports use a small portion of the possible port numbers. The assigned ports have all except the low order eight bits cleared to zero. The low order eight bits are specified here.
time 37/tcp timserver name 42/tcp nameserver whois 43/tcp nicname nameserver 53/tcp domain apts 57/tcp any private terminal service apfs 59/tcp any private file service
login 513/tcp remote login a la telnet;
automatic authentication performed based on priviledged port numbers and distributed data bases which identify "authentication domains"
cmd 514/tcp like exec, but automatic
authentication is performed as for login server printer 515/tcp spooler efs 520/tcp extended file name server tempo 526/tcp newdate courier 530/tcp rpc conference 531/tcp chat netnews 532/tcp readnews
at-8 208/udp biff 512/udp used by mail system to notify users of new mail received; currently receives messages only from processes on the same machine
who 513/udp maintains data bases showing who's
logged in to machines on a local net and the load average of the
machine
syslog 514/udp
talk 517/udp like tenex link, but across
machine - unfortunately, doesn't use link protocol (this is actually just a rendezvous port from which a tcp connection is established)
Host Extensions for IP Multicasting (RFC-1112) [43] specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Current addresses are listed below.
224.0.0.0 Reserved [43,JBP] 224.0.0.1 All Hosts on this Subnet [43,JBP] 224.0.0.2 All Gateways on this Subnet (proposed) [JBP] 224.0.0.3 Unassigned [JBP] 224.0.0.4 DVMRP Routers [140,JBP] 224.0.0.5 OSPFIGP OSPFIGP All Routers [83,JXM1] 224.0.0.6 OSPFIGP OSPFIGP Designated Routers [83,JXM1] 244.0.0.7-244.0.0.255 Unassigned [JBP] 224.0.1.0 VMTP Managers Group [17,DRC3] 224.0.1.1 NTP Network Time Protocol [80,DLM1] 224.0.1.2 SGI-Dogfight [AXC] 224.0.1.3 Rwhod [SXD] 224.0.1.4 VNP [DRC3] 244.0.1.5-244.0.1.255 Unassigned [JBP] 224.0.2.1 "rwho" Group (BSD) (unofficial) [JBP] 232.x.x.x VMTP transient groups [17,DRC3]
Note that when used on an Ethernet or IEEE 802 network, the 23 low-order bits of the IP Multicast address are placed in the low- order 23 bits of the Ethernet or IEEE 802 net multicast address 1.0.94.0.0.0. See the next section on "IANA ETHERNET ADDRESS BLOCK".
The IANA owns an Ethernet address block which may be used for multicast address asignments or other special purposes.
The address block in IEEE binary is (which is in bit transmission order):
0000 0000 0000 0000 0111 1010
In the normal Internet dotted decimal notation this is 0.0.94 since the bytes are transmitted higher order first and bits within bytes are transmitted lower order first (see "Data Notation" in the Introduction).
IEEE CSMA/CD and Token Bus bit transmission order: 00 00 5E
IEEE Token Ring bit transmission order: 00 00 7A
Appearance on the wire (bits transmitted from left to right):
The latter representation corresponds to the Internet standard bit- order, and is the format that most programmers have to deal with. Using this representation, the range of Internet Multicast addresses is:
01-00-5E-00-00-00 to 01-00-5E-7F-FF-FF in hex, or
1.0.94.0.0.0 to 1.0.94.127.255.255 in dotted decimal
This documents the default Type-of-Service values that are currently recommended for the most important Internet protocols.
There are three binary TOS attributes: low delay, high throughput, and high reliability; in each case, an attribute bit is turned on to indicate "better". The three attributes cannot all be optimized simultanously, and in fact the TOS algorithms that have been discussed tend to make "better" values of the attributes mutually exclusive. Therefore, the recommended values have at most one bit on.
Generally, protocols which are involved in direct interaction with a human should select low delay, while data transfers which may involve large blocks of data are need high throughput. Finally, high reliability is most important for datagram-based Internet management functions.
Application protocols not included in these tables should be able to make appropriate choice of low delay (1 0 0) or high throughput (0 1 0).
The following are recommended values for TOS:
----- Type-of-Service Value -----
Low High High
Protocol Delay Throughput Reliability
TELNET (1) 1 0 0
FTP Control 1 0 0 Data (2) 0 1 0
TFTP 1 0 0
SMTP (3)
Cmd phase 1 0 0 DATA phase 0 1 0
Domain Name Service
UDP Query 1 0 0 TCP Query 0 0 0 Zone Tnsfr 0 1 0
(1) Includes all interactive user protocols (e.g., rlogin).
(2) Includes all bulk data transfer protocols (e.g., rcp).
(3) If the implementation does not support changing the TOS during the lifetime of the connection, then the recommended TOS on opening the connection is (0,0,0).
The Internet Domain Naming System (DOMAIN) includes several parameters. These are documented in RFC-1034, [81] and RFC-1035[82]. The CLASS parameter is listed here. The per CLASS parameters are defined in separate RFCs as indicated.
Domain System Parameters:
Decimal Name References
------- ---- ----------
0 Reserved [PM1]
The Bootstrap Protocol (BOOTP) RFC-951[36] describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The BOOTP Vendor Information Extensions RFC-1084[117] proposes an addition to the Bootstrap Protocol (BOOTP).
Vendor Extensions are listed below:
Tag Name Data Length Meaning References
--- ---- ----------- ------- ----------
0 Pad 0 None
1 Subnet Mask 4 Subnet Mask Value
2 Time Zone 4 Time Offset in
Seconds from UTC
3 Gateways N N/4 Gateway addresses
4 Time Server N N/4 Timeserver addresses
5 Name Server N N/4 IEN-116 Server addresses
6 Domain Server N N/4 DNS Server addresses
7 Log Server N N/4 Logging Server addresses
8 Quotes Server N N/4 Quotes Server addresses
9 LPR Server N N/4 Printer Server addresses
10 Impress Server N N/4 Impress Server addresses
11 RLP Server N N/4 RLP Server addresses
12 Hostname N Hostname string
13 Boot File Size 2 Size of boot file in 512 byte
checks
14 Merit Dump File Client to dump and name
the file to dump it to
15-127 Unassigned
For the management of hosts and gateways on the Internet a data structure for the information has been defined. This data structure should be used with any of several possible management protocols, such as the "Simple Network Management Protocol" (SNMP) RFC-1098[15], or the "Common Management Information Protocol over TCP" (CMOT) [142].
The data structure is the "Structure and Indentification of Management Information for TCP/IP-based Internets" (SMI) RFC-1065[120], and the "Management Information Base for Network Management of TCP/IP-based Internets" (MIB) [121].
The SMI includes the provision for parameters or codes to indicate experimental or private data structures. These parameter assignments are listed here.
The older "Simple Gateway Monitoring Protocol" (SGMP) RFC-1028[37] also defined a data structure. The parameter assignments used with SGMP are included here for hist orical completeness.
The ARPANET facility for "logical addressing" is described in RFC-878[57] and RFC-1005[109]. A portion of the possible logical addresses are reserved for standard uses.
There are 49,152 possible logical host addresses. Of these, 256 are reserved for assignment to well-known functions. Assignments for well-known functions are made by the IANA. Assignments for other logical host addresses are made by the NIC.
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 Host/IMP interface is defined in BBN Report 1822 [2].
The low-order 4 bits of the message-id field are called the sub-link. Unless explicitly specified otherwise for a particular protocol, there is no sender to receiver significance to the sub-link. The sender may use the sub-link in any way he chooses (it is returned in the RFNM by the destination IMP), the receiver should ignore the sub-link.
All MILNET hosts are assigned addresses by the Defense Data Network (DDN). The address of a MILNET host may be obtained from the Network Information Center (NIC), represented as an ASCII text string in what is called "host table format". This section describes the process by which MILNET X.25 addresses may be derived from addresses in the NIC host table format.
A NIC host table address consists of the ASCII text string representations of four decimal numbers separated by periods, corresponding to the four octeted of a thirty-two bit Internet address. The four decimal numbers are referred to in this section as "n", "h' "l", and "i". Thus, a host table address may be represented as: "n.h.l.i". Each of these four numbers will have either one, two, or three decimal digits and will never have a value greater than 255. For example, in the host table, address: "10.2.0.124", n=10, h=2, l=0, and i=124. To convert a host table address to a MILNET X.25 address:
1. If h < 64, the host table address corresponds to the X.25 physical address:
ZZZZ F IIIHHZZ (SS)
where:
ZZZZ = 0000 as required
F = 0 because the address is a physical address;
III is a three decimal digit respresentation of
"i", right-adjusted and padded with leading zeros if required;
HH is a two decimal digit representation of "h",
right-adjusted and padded with leading zeros if required;
ZZ = 00 and
(SS) is optional
In the example given above, the host table address 10.2.0.124 corresponds to the X.25 physical address 000001240200. 2. If h > 64 or h = 64, the host table address corresponds to the X.25 logical address
Some of the networks of all classes are IEEE 802 Networks. These systems may use a Link Service Access Point (LSAP) field in much the same way the ARPANET uses the "link" field. Further, there is an extension of the LSAP header called the Sub-Network Access Protocol (SNAP).
The IEEE likes to describe numbers in binary in bit transmission order, which is the opposite of the big-endian order used throughout the Internet protocol documentation.
Assignments:
Link Service Access Point Description References
------------------------- ----------- ----------
IEEE Internet
These numbers (and others) are assigned by the IEEE Standards Office. The address is: IEEE Standards Office, 345 East 47th Street, New York, N.Y. 10017, Attn: Vince Condello. Phone: (212) 705-7092.
At an ad hoc special session on "IEEE 802 Networks and ARP", held during the TCP Vendors Workshop (August 1986), an approach to a consistent way to send DoD-IP datagrams and other IP related protocols (such as the Address Resolution Protocol (ARP)) on 802 networks was developed, using the SNAP extension (see RFC-1010 and RFC-1042[90]).
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.
If you need an Ethernet type, contact the Xerox Corporation, Xerox Systems Institute, 475 Oakmead Parkway, Sunnyvale, CA 94086, Attn: Ms. Fonda Pallone, (408) 737-4652.
The following list is contributed unverified information from various sources.
Ethernet hardware addresses are 48 bits, expressed as 12 hexadecimal digits (0-9, plus A-F, capitalized). These 12 hex digits consist of the first/left 6 digits (which should match the vendor of the Ethernet interface within the station) and the last/right 6 digits which specify the interface serial number for that interface vendor.
Ethernet addresses might be written unhyphenated (e.g., 123456789ABC), or with one hyphen (e.g., 123456-789ABC), but should be written hyphenated by octets (e.g., 12-34-56-78-9A-BC).
These addresses are physical station addresses, not multicast nor broadcast, so the second hex digit (reading from the left) will be even, not odd.
At present, it is not clear how the IEEE assigns Ethernet block addresses. Whether in blocks of 2**24 or 2**25, and whether multicasts are assigned with that block or separately. A portion of the vendor block address is reportedly assigned serially, with the other portion intentionally assigned randomly. If there is a global algorithm for which addresses are designated to be physical (in a chipset) versus logical (assigned in software), or globally-assigned versus locally-assigned addresses, some of the known addresses do not follow the scheme (e.g., AA0003; 02xxxx).
00000C Cisco 00000F NeXT 000010 Sytek 00001D Cabletron 000020 DIAB (Data Intdustrier AB) 000022 Visual Technology 00002A TRW 00005A S & Koch 00005E IANA 000065 Network General 00006B MIPS 000077 MIPS 00007A Ardent 000089 Cayman Systems Gatorbox 000093 Proteon 00009F Ameristar Technology 0000A2 Wellfleet 0000A3 Network Application Technology 0000A6 Network General (internal assignment, not for products) 0000A7 NCD X-terminals 0000A9 Network Systems 0000AA Xerox Xerox machines 0000B3 CIMLinc 0000B7 Dove Fastnet 0000BC Allen-Bradley 0000C0 Western Digital 0000C6 HP Intelligent Networks Operation (formerly Eon Systems)
Reynolds & Postel [Page 38]
RFC 1060 Assigned Numbers March 1990
0000C8 Altos
0000C9 Emulex Terminal Servers
0000D7 Dartmouth College (NED Router)
0000D8 3Com? Novell? PS/2 0000DD Gould 0000DE Unigraph 0000E2 Acer Counterpoint 0000EF Alantec 0000FD High Level Hardvare (Orion, UK) 000102 BBN BBN internal usage (not registered) 001700 Kabel 00802D Xylogics, Inc. Annex terminal servers 00808C Frontier Software Development 00AA00 Intel 00DD00 Ungermann-Bass 00DD01 Ungermann-Bass 020701 MICOM/Interlan UNIBUS or QBUS machines, Apollo 020406 BBN BBN internal usage (not registered) 026086 Satelcom MegaPac (UK) 02608C 3Com IBM PC; Imagen; Valid; Cisco 02CF1F CMC Masscomp; Silicon Graphics; Prime EXL 080002 3Com (Formerly Bridge) 080003 ACC (Advanced Computer Communications) 080005 Symbolics Symbolics LISP machines 080008 BBN 080009 Hewlett-Packard 08000A Nestar Systems 08000B Unisys 080010 AT&T 080011 Tektronix, Inc. 080014 Excelan BBN Butterfly, Masscomp, Silicon Graphics 080017 NSC 08001A Data General 08001B Data General 08001E Apollo 080020 Sun Sun machines 080022 NBI 080025 CDC 080026 Norsk Data (Nord) 080027 PCS Computer Systems GmbH 080028 TI Explorer 08002B DEC 08002E Metaphor 08002F Prime Computer Prime 50-Series LHC300 080036 Intergraph CAE stations 080037 Fujitsu-Xerox 080038 Bull 080039 Spider Systems 080041 DCA Digital Comm. Assoc. 080045 ???? (maybe Xylogics, but they claim not to know this number) 080046 Sony 080047 Sequent 080049 Univation 08004C Encore 08004E BICC 080056 Stanford University 080058 ??? DECsystem-20 08005A IBM 080067 Comdesign 080068 Ridge 080069 Silicon Graphics 08006E Excelan 080075 DDE (Danish Data Elektronik A/S) 08007C Vitalink TransLAN III 080080 XIOS
08008B Pyramid 08008D XyVision XyVision machines 080090 Retix Inc Bridges 484453 HDS ??? 800010 AT&T [misrepresentation of 080010?] AA0000 DEC obsolete AA0001 DEC obsolete AA0002 DEC obsolete AA0003 DEC Global physical address for some DEC machines AA0004 DEC Local logical address for systems running DECNET
01-00-5E-00-00-00- 0800 Internet Multicast (RFC-1112) [43] 01-00-5E-7F-FF-FF 01-00-5E-80-00-00- ???? Internet reserved by IANA 01-00-5E-FF-FF-FF 01-80-C2-00-00-00 -802- Spanning tree (for bridges) 09-00-02-04-00-01? 8080? Vitalink printer 09-00-02-04-00-02? 8080? Vitalink management 09-00-09-00-00-01 8005 HP Probe 09-00-09-00-00-01 -802- HP Probe 09-00-09-00-00-04 8005? HP DTC 09-00-1E-00-00-00 8019? Apollo DOMAIN 09-00-2B-00-00-00 6009? DEC MUMPS? 09-00-2B-00-00-01 8039? DEC DSM/DTP? 09-00-2B-00-00-02 803B? DEC VAXELN? 09-00-2B-00-00-03 8038 DEC Lanbridge Traffic Monitor (LTM) 09-00-2B-00-00-04 ???? DEC MAP End System Hello? 09-00-2B-00-00-05 ???? DEC MAP Intermediate System Hello? 09-00-2B-00-00-06 803D? DEC CSMA/CD Encryption? 09-00-2B-00-00-07 8040? DEC NetBios Emulator? 09-00-2B-00-00-0F 6004 DEC Local Area Transport (LAT) 09-00-2B-00-00-1x ???? DEC Experimental 09-00-2B-01-00-00 8038 DEC LanBridge Copy packets (All bridges) 09-00-2B-01-00-01 8038 DEC LanBridge Hello packets (All local bridges) 1 packet per second, sent by the designated LanBridge 09-00-2B-02-00-00 ???? DEC DNA Level 2 Routing Layer routers? 09-00-2B-02-01-00 803C? DEC DNA Naming Service Advertisement? 09-00-2B-02-01-01 803C? DEC DNA Naming Service Solicitation? 09-00-2B-02-01-02 803E? DEC DNA Time Service? 09-00-2B-03-xx-xx ???? DEC default filtering by bridges? 09-00-2B-04-00-00 8041? DEC Local Area System Transport (LAST)? 09-00-2B-23-00-00 803A? DEC Argonaut Console? 09-00-4E-00-00-02? 8137? Novell IPX 09-00-56-00-00-00- ???? Stanford reserved 09-00-56-FE-FF-FF 09-00-56-FF-00-00- 805C Stanford V Kernel, version 6.0 09-00-56-FF-FF-FF 09-00-77-00-00-01 ???? Retix spanning tree bridges 09-00-7C-02-00-05 8080? Vitalink diagnostics 09-00-7C-05-00-01 8080? Vitalink gateway? 0D-1E-15-BA-DD-06 ???? HP AB-00-00-01-00-00 6001 DEC Maintenance Operation Protocol (MOP)
Dump/Load Assistance
AB-00-00-02-00-00 6002 DEC Maintenance Operation Protocol (MOP)
Remote Console 1 System ID packet every 8-10 minutes, by every: DEC LanBridge DEC DEUNA interface DEC DELUA interface DEC DEQNA interface (in a certain mode)
AB-00-00-03-00-00 6003 DECNET Phase IV end node Hello packets
1 packet every 15 seconds, sent by
each DECNET host AB-00-00-04-00-00 6003 DECNET Phase IV Router Hello packets
1 packet every 15 seconds, sent by the
DECNET router AB-00-00-05-00-00 ???? Reserved DEC through AB-00-03-FF-FF-FF AB-00-03-00-00-00 6004 DEC Local Area Transport (LAT) - old AB-00-04-00-xx-xx ???? Reserved DEC customer private use AB-00-04-01-xx-yy 6007 DEC Local Area VAX Cluster groups
System Communication Architecture (SCA)
CF-00-00-00-00-00 9000 Ethernet Configuration Test protocol (Loopback)
Broadcast Address: FF-FF-FF-FF-FF-FF 0600 XNS packets, Hello or gateway search?
6 packets every 15 seconds, per XNS station
FF-FF-FF-FF-FF-FF 0800 IP (e.g. RWHOD via UDP) as needed FF-FF-FF-FF-FF-FF 0804 CHAOS FF-FF-FF-FF-FF-FF 0806 ARP (for IP and CHAOS) as needed FF-FF-FF-FF-FF-FF 0BAD Banyan FF-FF-FF-FF-FF-FF 1600 VALID packets, Hello or gateway search?
1 packets every 30 seconds, per VALID station
FF-FF-FF-FF-FF-FF 8035 Reverse ARP FF-FF-FF-FF-FF-FF 807C Merit Internodal (INP) FF-FF-FF-FF-FF-FF 809B EtherTalk
Below are two tables describing the arrangement of protocol fields or type field assignments so that one could send NS Datagrams on the ARPANET or Internet Datagrams on 10Mb Ethernet, and also protocol and type fields so one could encapsulate each kind of Datagram in the other.
\ upper| DoD IP | PUP | NS IP |
lower \ | | | |
--------------|--------|--------|--------|
| Type | Type | Type |
3Mb Ethernet | 1001 | 1000 | 3000 |
| octal | octal | octal |
--------------|--------|--------|--------|
| Type | Type | Type |
10 Mb Ethernet| 0800 | 0200 | 0600 |
| hex | hex | hex |
--------------|--------|--------|--------|
| Link | Link | Link |
ARPANET | 155 | 152 | 150 |
| decimal| decimal| decimal|
--------------|--------|--------|--------|
\ upper| DoD IP | PUP | NS IP |
lower \ | | | |
--------------|--------|--------|--------|
| |Protocol|Protocol|
DoD IP | X | 12 | 22 |
| | decimal| decimal|
--------------|--------|--------|--------|
| | | |
PUP | ? | X | ? |
| | | |
--------------|--------|--------|--------|
| Type | Type | |
NS IP | 13 | 12 | X |
| decimal| decimal| |
--------------|--------|--------|--------|
Reynolds & Postel [Page 44]
Below is the current list of PRONET 80 Type Numbers. Note: a protocol that is on this list does not necessarily mean that there is any implementation of it on ProNET.
Of these, protocols 1, 14, and 20 are the only ones that have ever been seen in ARP packets.
For reference, the header is (one byte/line):
destination hardware address source hardware address data link header version (2) data link header protocol number data link header reserved (0) data link header reserved (0)
Some protocols have been known to tuck stuff in the reserved fields.
Those who need a protocol number on ProNET-10/80 should contact John Shriver (jas@proteon.com).
1 IP 2 IP with trailing headers 3 Address Resoloution Protocol 4 Proteon HDLC 5 VAX Debugging Protocol (MIT) 10 Novell NetWare (IPX and pre-IPX) (old format,
3 byte trailer)
11 Vianetix 12 PUP 13 Watstar protocol (University of Waterloo) 14 XNS 15 Diganostics 16 Echo protocol (link level) 17 Banyan Vines 20 DECnet (DEUNA Emulation) 21 Chaosnet 23 IEEE 802.2 or ISO 8802/2 Data Link 24 Reverse Address Resolution Protocol 29 TokenVIEW-10 31 AppleTalk LAP Data Packet 33 Cornell Boot Server Location Protocol 34 Novell NetWare IPX (new format, no trailer,
new XOR checksum)
CCITT defines the high order two bits of the first octet of call user data as follows:
00 - Used for other CCITT recomendations (such as X.29) 01 - Reserved for use by "national" administrative
authorities
10 - Reserved for use by international administrative authoorities 11 - Reserved for arbitrary use between consenting DTEs
Call User Data (hex) Protocol Reference
------------------- -------- ---------
01 PAD [GS2] C5 Blacker front-end descr dev [AGM] CC IP [69,AGM]* CD ISO-IP [AGM]
* NOTE: ISO SC6/WG2 approved assignment in ISO 9577 (January 1990).
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).
The numbers below are assigned for networks that are connected to the Internet, and for independent networks. These independent networks are marked with an asterisk preceding the number.
Assignments:
* Internet Public Data Net Description References
- -------------- ----------------- ----------- ----------
014.000.000.000 Reserved [JBP]
The Telnet Protocol has a number of options that may be negotiated. These options are listed here. "Official Internet Protocols" [118] provides more detailed information.
Options Name References
------- ----------------------- ----------
0 Binary Transmission [110,JBP]
1 Echo [111,JBP] 2 Reconnection [42,JBP] 3 Suppress Go Ahead [114,JBP] 4 Approx Message Size Negotiation [133,JBP] 5 Status [113,JBP] 6 Timing Mark [115,JBP] 7 Remote Controlled Trans and Echo [107,JBP] 8 Output Line Width [40,JBP] 9 Output Page Size [41,JBP] 10 Output Carriage-Return Disposition [28,JBP] 11 Output Horizontal Tab Stops [32,JBP] 12 Output Horizontal Tab Disposition [31,JBP] 13 Output Formfeed Disposition [29,JBP] 14 Output Vertical Tabstops [34,JBP] 15 Output Vertical Tab Disposition [33,JBP] 16 Output Linefeed Disposition [30,JBP] 17 Extended ASCII [136,JBP] 18 Logout [25,MRC] 19 Byte Macro [35,JBP] 20 Data Entry Terminal [145,38,JBP] 22 SUPDUP [26,27,MRC] 22 SUPDUP Output [51,MRC] 23 Send Location [68,EAK1] 24 Terminal Type [128,MS56] 25 End of Record [103,JBP] 26 TACACS User Identification [1,BA4] 27 Output Marking [125,SXS] 28 Terminal Location Number [84,RN6] 29 Telnet 3270 Regime [116,JXR] 30 X.3 PAD [70,SL70] 31 Negotiate About Window Size [139,DW183] 32 Terminal Speed [57,CLH3] 33 Remote Flow Control [58,CLH3] 34 Linemode [9,DB14] 35 X Display Location [75,GM23]
255 Extended-Options-List [109,JBP]
RFC-822 specifies that Encryption Types for mail may be assigned. There are currently no RFC-822 encryption types assigned. Please use instead the Mail Privacy procedures defined in [71,72,66].
These are the Official Machine Names as they appear in the Domain Name System WKS records and the NIC Host Table. Their use is described in RFC-952[53].
A machine name or CPU type may be up to 40 characters taken from the set of uppercase letters, digits, and the two punctuation characters hyphen and slash. It must start with a letter, and end with a letter or digit.
These are the Official System Names as they appear in the Domain Name System WKS records and the NIC Host Table. Their use is described in RFC-952[53].
A system name may be up to 40 characters taken from the set of upper- case letters, digits, and the two punctuation characters hyphen and slash. It must start with a letter, and end with a letter or digit.
AEGIS MACOS TP3010 APOLLO MINOS TRSDOS BS-2000 MOS ULTRIX CEDAR MPE5 UNIX CGW MSDOS UNIX-BSD CHORUS MULTICS UNIX-V1AT CHRYSALIS MVS UNIX-V CMOS MVS/SP UNIX-V.1 CMS NEXUS UNIX-V.2 COS NMS UNIX-V.3 CPIX NONSTOP UNIX-PC CTOS NOS-2 UNKNOWN CTSS OS/DDP UT2D DCN OS4 V DDNOS OS86 VM DOMAIN OSX VM/370 DOS PCDOS VM/CMS EDX PERQ/OS VM/SP ELF PLI VMS EMBOS PSDOS/MIT VMS/EUNICE EMMOS PRIMOS VRTX EPOS RMX/RDOS WAITS FOONEX ROS WANG FUZZ RSX11M X11R3 GCOS SATOPS XDE GPOS SCO-XENIX/386 XENIX HDOS SCS IMAGEN SIMP INTERCOM SUN IMPRESS SUN OS 3.5 INTERLISP SUN OS 4.0 IOS SWIFT IRIX TAC ISI-68020 TANDEM ITS TENEX LISP TOPS10 LISPM TOPS20 LOCUS TOS
These are the Official Protocol Names as they appear in the Domain Name System WKS records and the NIC Host Table. Their use is described in RFC-952[53].
A protocol or service may be up to 40 characters taken from the set of uppercase letters, digits, and the punctuation character hyphen. It must start with a letter, and end with a letter or digit.
EMCON - Emission Control Protocol
EMFIS-CNTL - EMFIS Control Service
EMFIS-DATA - EMFIS Data Service
FINGER - Finger Protocol
FTP - File Transfer Protocol FTP-DATA - File Transfer Protocol Data GGP - Gateway Gateway Protocol GRAPHICS - Graphics Protocol HMP - Host Monitoring Protocol HOST2-NS - Host2 Name Server HOSTNAME - Hostname Protocol ICMP - Internet Control Message Protocol IGMP - Internet Group Management Protocol IGP - Interior Gateway Protocol
Reynolds & Postel [Page 58]
RFC 1060 Assigned Numbers March 1990
IMAP2 - Interim Mail Access Protocol version 2
INGRES-NET - INGRES-NET Service
IP - Internet Protocol
IPCU - Internet Packet Core Utility IPPC - Internet Pluribus Packet Core IP-ARC - Internet Protocol on ARCNET IP-ARPA - Internet Protocol on ARPANET IP-DC - Internet Protocol on DC Networks IP-DVMRP - Distance Vector Multicast Routing Protocol IP-E - Internet Protocol on Ethernet Networks IP-EE - Internet Protocol on Exp. Ethernet Nets IP-FDDI - Transmission of IP over FDDI IP-HC - Internet Protocol on Hyperchannnel IP-IEEE - Internet Protocol on IEEE 802 IP-IPX - Transmission of 802.2 over IPX Networks
IP-MTU - IP MTU Discovery Options
IP-NETBIOS - Internet Protocol Datagrams over NetBIOS Networks
IP-SLIP - Transmission of IP over Serial Lines
IP-WB - Internet Protocol on Wideband Network IP-X25 - Internet Protocol on X.25 Networks IRTP - Internet Reliable Transaction Protocol ISI-GL - ISI Graphics Language Protocol ISO-TP4 - ISO Transport Protocol Class 4 ISO-TSAP - ISO TSAP LA-MAINT - IMP Logical Address Maintenance LARP - Locus Address Resoultion Protocol LDP - Loader Debugger Protocol LEAF-1 - Leaf-1 Protocol LEAF-2 - Leaf-2 Protocol LINK - Link Protocol LOC-SRV - Location Service LOGIN - Login Host Protocol MAIL - Format of Electronic Mail Messages MERIT-INP - MERIT Internodal Protocol METAGRAM - Metagram Relay
MIB - Management Information Base
MIT-ML-DEV - MIT ML Device
MFE-NSP - MFE Network Services Protocol
MIT-SUBNET - MIT Subnet Support
MIT-DOV - MIT Dover Spooler
RFC 1060 Assigned Numbers March 1990
MUX - Multiplexing Protocol
NAMESERVER - Host Name Server
NETBIOS-DGM - NETBIOS Datagram Service
NETBIOS-NS - NETBIOS Name Service
NETBIOS-SSN - NETBIOS Session Service
NETBLT - Bulk Data Transfer Protocol NETED - Network Standard Text Editor NETRJS - Remote Job Service NI-FTP - NI File Transfer Protocol NI-MAIL - NI Mail Protocol NICNAME - Who Is Protocol NFILE - A File Access Protocol NNTP - Network News Transfer Protocol NSW-FE - NSW User System Front End NTP - Network Time Protocol NVP-II - Network Voice Protocol OSPF - Open Shortest Path First Interior GW Protocol PCMAIL - Pcmail Transport Protocol POP2 - Post Office Protocol - Version 2 POP3 - Post Office Protocol - Version 3 PPP - Point-to-Point Protocol PRM - Packet Radio Measurement PUP - PUP Protocol PWDGEN - Password Generator Protocol QUOTE - Quote of the Day Protocol RARP - A Reverse Address Resolution Protocol RATP - Reliable Asynchronous Transfer Protocol RDP - Reliable Data Protocol RIP - Routing Information Protocol RJE - Remote Job Entry RLP - Resource Location Protocol RTELNET - Remote Telnet Service RVD - Remote Virtual Disk Protocol SAT-EXPAK - Satnet and Backroom EXPAK SAT-MON - SATNET Monitoring SEP - Sequential Exchange Protocol SFTP - Simple File Transfer Protocol SGMP - Simple Gateway Monitoring Protocol SNMP - Simple Network Management Protocol SMI - Structure of Management Information SMTP - Simple Mail Transfer Protocol SQLSRV - SQL Service ST - Stream Protocol STATSRV - Statistics Service SU-MIT-TG - SU/MIT Telnet Gateway Protocol SUN-RPC - SUN Remote Procedure Call SUPDUP - SUPDUP Protocol SUR-MEAS - Survey Measurement SWIFT-RVF - Remote Virtual File Protocol TACACS-DS - TACACS-Database Service TACNEWS - TAC News TCP - Transmission Control Protocol TELNET - Telnet Protocol TFTP - Trivial File Transfer Protocol THINWIRE - Thinwire Protocol TIME - Time Server Protocol TP-TCP - ISO Transport Service on top of the TCP TRUNK-1 - Trunk-1 Protocol TRUNK-2 - Trunk-2 Protocol UCL - University College London Protocol UDP - User Datagram Protocol NNTP - Network News Transfer Protocol USERS - Active Users Protocol UUCP-PATH - UUCP Path Service VIA-FTP - VIA Systems-File Transfer Protocol VISA - VISA Protocol VMTP - Versatile Message Transaction Protocol WB-EXPAK - Wideband EXPAK WB-MON - Wideband Monitoring XNET - Cross Net Debugger XNS-IDP - Xerox NS IDP
Reynolds & Postel [Page 60]
RFC 1060 Assigned Numbers March 1990Reynolds & Postel [Page 61]
These are the Official Terminal Type Names. Their use is described in RFC-930[128]. The maximum length of a name is 40 characters.
A terminal names may be up to 40 characters taken from the set of upper- case letters, digits, and the two punctuation characters hyphen and slash. It must start with a letter, and end with a letter or digit.
[1] Anderson, B., "TACACS User Identification Telnet Option", RFC-927, BBN, December 1984.
[2] BBN, "Specifications for the Interconnection of a Host and an
IMP", Report 1822, Bolt Beranek and Newman, Cambridge, Massachusetts, revised, December 1981.
[3] BBN, "User Manual for TAC User Database Tool", Bolt Beranek
and Newman, September 1984.
[4] Ben-Artzi, Amatzia, "Network Management for TCP/IP Network: An
Overview", 3Com, May 1988.
[5] Bennett, C., "A Simple NIFTP-Based Mail System", IEN 169,
University College, London, January 1981.
[6] Bhushan, A., "A Report on the Survey Project", RFC-530,
NIC 17375, June 1973.
[7] Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language
(version 2.1)", ISI/TM-80-18, Information Sciences Institute, July 1980.
[8] 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.
[9] Borman, D., Editor, "Telnet Linemode Option", RFC 1116, Cray Research, Inc., August 1989.
[10] Braden, R., "NETRJS Protocol", RFC-740, NIC 42423,
Information Sciences Institute, November 1977.
[11] Braden, R., and J. Postel, "Requirements for Internet
Gateways", RFC-1009, Obsoletes RFC-985, Information Sciences Institute, June 1987.
[12] Bressler, B., "Remote Job Entry Protocol", RFC-407,
NIC 12112, October 1972.
[13] Bressler, R., "Inter-Entity Communication -- An Experiment", RFC-441, NIC 13773, January 1973.
[14] Butler, M., J. Postel, D. Chase, J. Goldberger, and
J. K. Reynolds, "Post Office Protocol - Version 2", RFC-937, Information Sciences Institute, February 1985.
[15] Case, J., M. Fedor, M. Schoffstall, and C. Davin,
"A Simple Network Management Protocol", RFC-1098, (Obsoletes RFC-1067), University of Tennessee at Knoxville, NYSERNet, Inc., Rensselaer Polytechnic Institute, and MIT Laboratory for Computer Science, April 1989.
[16] Cass, D., and M. Rose, "ISO Transport Services on Top of
the TCP", RFC-983, NTRC, April 1986.
[17] Cheriton, D., "VMTP: Versatile Message Transaction
Protocol Specification", RFC-1045, pgs 103 & 104, Stanford University, February 1988.
[18] Cisco Systems, "Gateway Server Reference Manual", Manual
Revision B, January 10, 1988.
[19] Clark, D., "PCMAIL: A Distributed Mail System for Personal
Computers", RFC-984, MIT, May 1986.
[20] Clark, D., M. Lambert, and L. Zhang, "NETBLT: A Bulk Data
Transfer Protocol", RFC-969, MIT Laboratory for Computer Science, December 1985.
[21] Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer
Magazine, October 1981.
[22] Cohen, D., "Specifications for the Network Voice Protocol", RFC-741, ISI/RR 7539, Information Sciences Institute, March 1976.
[23] Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90,
Information Sciences Institute, May 1979.
[24] 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, August 1976.
[25] Crispin, M., "Telnet Logout Option", Stanford University-AI, RFC-727, April 1977.
[26] Crispin, M., "Telnet SUPDUP Option", Stanford University-AI,
[43] Deering, S., "Host Extensions for IP Multicasting", RFC-1112, Obsoletes RFC-988, RFC-1054, Stanford University, August 1989.
[44] Elvy, M., and R. Nedved, "Network Mail Path Service", RFC-915,
Harvard and CMU, July 1986.
[45] Feinler, E., editor, "DDN Protocol Handbook", Network
Information Center, SRI International, December 1985.
[46] Feinler, E., editor, "Internet Protocol Transition Workbook",
Network Information Center, SRI International, March 1982.
[47] 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.
[48] Finlayson, R., T. Mann, J. Mogul, and M. Theimer, "A Reverse
Address Resolution Protocol", RFC-903, Stanford University, June 1984.
[49] Forgie, J., "ST - A Proposed Internet Stream Protocol",
IEN 119, MIT Lincoln Laboratory, September 1979.
[50] Forsdick, H., "CFTP", Network Message, Bolt Beranek and
Newman, January 1982.
[51] Greenberg, B., "Telnet SUPDUP-OUTPUT Option", RFC-749,
MIT-Multics, September 1978.
[52] Harrenstien, K., "Name/Finger", RFC-742, NIC 42758,
SRI International, December 1977.
[53] Harrenstien, K., M. Stahl, and E. Feinler, "DOD Internet Host
Table Specification", RFC-952, Obsoletes RFC-810, October 1985.
[54] Harrenstien, K., V. White, and E. Feinler, "Hostnames Server", RFC-811, SRI International, March 1982.
[55] Harrenstien, K., and V. White, "Nicname/Whois", RFC-812,
SRI International, March 1982.
[56] Haverty, J., "XNET Formats for Internet Protocol Version 4",
IEN 158, October 1980.
[58] Hedrick, C., "Telnet Remote Flow Control Option", RFC-1080, Rutgers University, December 1988.
[59] Hinden, R., "A Host Monitoring Protocol", RFC-869,
Bolt Beranek and Newman, December 1983.
[60] Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway", RFC-823, September 1982.
[61] Hornig, C., "A Standard for the Transmission of IP Datagrams
over Ethernet Networks, RFC-894, Symbolics, April 1984.
[62] Internet Activities Board, J. Postel, Editor, "IAB Official
Protocol Standards", RFC-1130, Internet Activities October 1989.
[63] International Standards Organization, "ISO Transport Protocol
Specification - ISO DP 8073", RFC-905, April 1984.
[64] International Standards Organization, "Protocol for Providing
the Connectionless-Mode Network Services", RFC-926, ISO, December 1984.
[65] Kantor, B., and P. Lapsley, "Network News Transfer Protocol", RFC-977, UC San Diego & UC Berkeley, February 1986.
[66] Kent, S., and J. Linn, "Privacy Enhancement for Internet
Electronic Mail: Part II -- Certificate-Based Key Management", BBNCC and DEC, August 1989.
[67] Khanna, A., and A. Malis, "The ARPANET AHIP-E Host Access
Protocol (Enhanced AHIP)", RFC-1005, BBN Communications Corporation, May 1987.
[68] Killian, E., "Telnet Send-Location Option", RFC-779,
April 1981.
[69] Korb, J., "A Standard for the Transmission of IP Datagrams
Over Public Data Networks", RFC-877, Purdue University, September 1983.
[70] Levy, S., and T. Jacobson, "Telnet X.3 PAD Option", RFC-1053,
Minnesota Supercomputer Center, April 1988.
[71] Linn, J., "Privacy Enhancement for Internet Electronic
Mail: Part I: Message Encipherment and Authentication Procedures", RFC-1113, Obsoletes RFC-989 and RFC-1040, DEC, August 1989.
[78] 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.
[80] Mills, D., "Network Time Protocol (Version 1), Specification
and Implementation", RFC-1059, University of Delaware, July 1988.
[81] Mockapetris, P., "Domain Names - Concepts and
Facilities", RFC-1034, Obsoletes RFCs 882, 883, and 973, Information Sciences Institute, November 1987.
[82] Mockapetris, P., "Domain Names - Implementation and
Specification", RFC-1035, Obsoletes RFCs 882, 883, and 973, Information Sciences Institute, November 1987.
[83] Moy, J., "The OSPF Specification", RFC 1131, Proteon,
October 1989.
[84] Nedved, R., "Telnet Terminal Location Number Option", RFC-946,
Carnegie-Mellon University, May 1985.
[85] 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 December 1976.
[86] Onions, J., and M. Rose, "ISO-TP0 bridge between TCP
and X.25", RFC-1086, Nottingham, TWG, December 1988.
[87] Partridge, C. and G. Trewitt, The High-Level Entity Management
System (HEMS), RFCs 1021, 1022, 1023, and 1024, BBN/NNSC, Stanford, October, 1987.
[88] 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.
[89] Postel, J., "Active Users", RFC-866, Information
Sciences Institute, May 1983.
[90] Postel, J., and J. Reynolds, "A Standard for the Transmission
of IP Datagrams over IEEE 802 Networks", RFC-1042, USC/Information Sciences Institute, February 1988.
[91] Postel, J., "A Standard for the Transmission of IP Datagrams
over Experimental Ethernet Networks, RFC-895, Information Sciences Institute, April 1984.
[92] Postel, J., "Character Generator Protocol", RFC-864,
Information Sciences Institute, May 1983.
[93] Postel, J., "Daytime Protocol", RFC-867, Information Sciences
Institute, May 1983.
[94] Postel, J., "Discard Protocol", RFC-863, Information Sciences
Institute, May 1983.
[95] Postel, J., "Echo Protocol", RFC-862, Information Sciences
Institute, May 1983.
[96] Postel, J. and J. Reynolds, "File Transfer Protocol", RFC-959,
Information Sciences Institute, October 1985.
[97] Postel, J., "Internet Control Message Protocol - DARPA
Internet Program Protocol Specification", RFC-792, Information Sciences Institute, September 1981.
[98] Postel, J., "Internet Message Protocol", RFC-759, IEN 113,
Information Sciences Institute, August 1980.
[99] Postel, J., "Name Server", IEN 116, Information Sciences
[100] Postel, J., "Quote of the Day Protocol", RFC-865,
Information Sciences Institute, May 1983.
[101] Postel, J., "Remote Telnet Service", RFC-818,
Information Sciences Institute, November 1982.
[102] Postel, J., "Simple Mail Transfer Protocol", RFC-821,
Information Sciences Institute, August 1982.
[103] Postel, J., "Telnet End of Record Option", RFC-885,
Information Sciences Institute, December 1983.
[104] Postel, J., "User Datagram Protocol", RFC-768
Information Sciences Institute, August 1980.
[105] Postel, J., ed., "Internet Protocol - DARPA Internet Program
Protocol Specification", RFC-791, Information Sciences Institute, September 1981.
[106] Postel, J., ed., "Transmission Control Protocol - DARPA
Internet Program Protocol Specification", RFC-793, Information Sciences Institute, September 1981.
[107] Postel, J. and D. Crocker, "Remote Controlled Transmission and
Echoing Telnet Option", RFC-726, March 1977.
[108] Postel, J., and K. Harrenstien, "Time Protocol", RFC-868,
Information Sciences Institute, May 1983.
[109] Postel, J. and J. Reynolds, "Telnet Extended Options - List
Option", RFC-861, Information Sciences Institute, May 1983.
[110] Postel, J. and J. Reynolds, "Telnet Binary Transmission", RFC-856, Information Sciences Institute, May 1983.
[111] Postel, J. and J. Reynolds, "Telnet Echo Option", RFC-857,
Information Sciences Institute, May 1983.
[112] Postel, J., and J. Reynolds, "Telnet Protocol Specification", RFC-854, Information Sciences Institute, May 1983.
[113] Postel, J. and J. Reynolds, "Telnet Status Option", RFC-859,
Information Sciences Institute, May 1983.
[114] Postel, J. and J. Reynolds, "Telnet Suppress Go Ahead Option", RFC-858, Information Sciences Institute, May 1983.
[130] St. Johns, M., "Authentication Service", RFC-931, TPSC,
January 1985.
[131] Tappan, D., "The CRONUS Virtual Local Network", RFC-824,
Bolt Beranek and Newman, August 1982.
[132] Taylor, J., "ERPC Functional Specification", Version 1.04,
HYDRA Computer Systems, Inc., July 1984.
[133] "The Ethernet, A Local Area Network: Data Link Layer and
Physical Layer Specification", AA-K759B-TK, Digital Equipment Corporation, Maynard, MA. Also as: "The Ethernet - A Local Area Network", Version 1.0, Digital Equipment Corporation, Intel Corporation, Xerox Corporation, September 1980. And: "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specifications", Digital, Intel and Xerox, November 1982. And: XEROX, "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", X3T51/80-50, Xerox Corporation, Stamford, CT., October 1980.
[134] The High Level Protocol Group, "A Network Independent File
Transfer Protocol", INWG Protocol Note 86, December 1977.
[135] Thomas, Bob, "The Interhost Protocol to Support CRONUS/DIAMOND
Interprocess Communication", BBN, September 1983.
[140] Waitzman, D., C. Partridge, and S. Deering
"Distance Vector Multicast Routing Protocol", RFC-1075, BBN STC and Stanford University, November 1988.
[141] Wancho, F., "Password Generator Protocol", RFC-972, WSMR,
January 1986.
[142] Warrier, U., and L. Besaw, "The Common Management
Information Services and Protocol over TCP/IP (CMOT)", RFC-1095, Unisys Corp. and Hewlett-Packard, April 1989.
[143] Welch, B., "The Sprite Remote Procedure Call System",
Technical Report, UCB/Computer Science Dept., 86/302, University of California at Berkeley, June 1986.
[144] Xerox, "Courier: The Remote Procedure Protocol", XSIS 038112,
December 1981.
[145] Yasuda, A., and T. Thompson, "TELNET Data Entry Terminal
Option DODIIS Implementation", RFC-1043, DIA, February 1988.
[JXF] Josh Fielk Optical Data Systems ---none---
[JXG] Jerry Geisler Boeing ---none---
[JXG1] Jim Greuel HP jimg%hpcndpc@hplabs.hp.com
[JXH] Jeff Honig Cornell jch@sonne.tn.cornell.edu
Reynolds & Postel [Page 80]
Joyce K. Reynolds University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292
Phone: (213) 822-1511
Email: JKREY@ISI.EDU
Jon Postel University of Southern California Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292
Phone: (213) 822-1511
Email: POSTEL@ISI.EDU
Reynolds & Postel [Page 86]
Ad
Translate documents to 日本語, svenska, Nederlands, Deutsch, français, русский, italiano, español, Tiếng Việt, polski, português, 中文, українська, català, norsk, فارسی, suomi, Bahasa Indonesia, العربية, čeština, 한국어, Bahasa Melayu, magyar, română, српски and other languages.
