This memo is an official status report on the numbers used in protocols in the Internet community. Distribution of this memo is unlimited.
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 Joyce Reynolds. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, etc., please contact Joyce to receive a number assignment.
Joyce K. Reynolds USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695
Phone: (213) 822-1511
Electronic mail: JKREYNOLDS@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" [91]. The more prominent and more generally used are documented in the "DDN Protocol Handbook, Volume Two, DARPA Internet Protocols" [36] prepared by the NIC. Other collections of older or obsolete protocols are contained in the "Internet Protocol Transition Workbook" [57], or in the "ARPANET Protocol Transition Handbook" [38]. 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, Meno Park, CA., 94025; or call: 1-800-235-3155.
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 [14]. 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.
Reynolds & Postel [Page 2]
RFC 1010 - Assigned Numbers May 1987 Version Numbers
VERSION NUMBERS
In the Internet Protocol (IP) [36,80] 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 [80,JBP] 5 ST ST Datagram Mode [41,JWF] 6-14 Unassigned [JBP] 15 Reserved [JBP]
Reynolds & Postel [Page 3]
RFC 1010 - Assigned Numbers May 1987 Protocol Numbers
PROTOCOL NUMBERS
In the Internet Protocol (IP) [36,80] there is a field, called Protocol, to identify the the next level protocol. This is an 8 bit field.
Ports are used in the TCP [36,81] 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 [37,79].
To the extent possible, these same port assignments are used with the ISO-TP4 [52].
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.
Port Assignments:
Decimal Keyword Description References ------- ------- ----------- ---------- 0 Reserved [JBP] 1-4 Unassigned [JBP] 5 RJE Remote Job Entry [9,JBP] 7 ECHO Echo [70,JBP] 9 DISCARD Discard [69,JBP] 11 USERS Active Users [65,JBP] 13 DAYTIME Daytime [68,JBP] 15 Unassigned [JBP] 17 QUOTE Quote of the Day [75,JBP] 19 CHARGEN Character Generator [67,JBP] 20 FTP-DATA File Transfer [Default Data] [71,JBP] 21 FTP File Transfer [Control] [71,JBP] 23 TELNET Telnet [87,JBP] 25 SMTP Simple Mail Transfer [77,JBP] 27 NSW-FE NSW User System FE [17,RHT] 29 MSG-ICP MSG ICP [63,RHT] 31 MSG-AUTH MSG Authentication [63,RHT] 33 DSP Display Support Protocol [MLC] 35 any private printer server [JBP] 37 TIME Time [83,JBP] 39 RLP Resource Location Protocol [MA] 41 GRAPHICS Graphics [98,JBP] 42 NAMESERVER Host Name Server [74,JBP] 43 NICNAME Who Is [46,JAKE] 44 MPM-FLAGS MPM FLAGS Protocol [JBP]
127 LOCUS-CON Locus PC-Interface Conn Server [105,BXG] 129 PWDGEN Password Generator Protocol [107,FJW] 130 CISCO-FNA CISCO FNATIVE [WXB] 131 CISCO-TNA CISCO TNATIVE [WXB] 132 CISCO-SYS CISCO SYSMAINT [WXB] 133 STATSRV Statistics Service [DLM1] 134 INGRES-NET INGRES-NET Service [MXB] 135 LOC-SRV Location Service [JXP] 136 PROFILE PROFILE Naming System [LLP] 137 NETBIOS-NS NETBIOS Name Service [JBP] 138 NETBIOS-DGM NETBIOS Datagram Service [JBP] 139 NETBIOS-SSN NETBIOS Session Service [JBP] 140 EMFIS-DATA EMFIS Data Service [GB7] 141 EMFIS-CNTL EMFIS Control Service [GB7] 142 BL-IDM Britton-Lee IDM [SXS1] 143-159 Unassigned [JBP] 160-223 Reserved [JBP] 224-241 Unassigned [JBP] 243 SUR-MEAS Survey Measurement [5,AV] 245 LINK LINK [10,RDB2] 247-255 Unassigned [JBP]
Reynolds & Postel [Page 8]
RFC 1010 - Assigned Numbers May 1987 Domain System Parameters
DOMAIN SYSTEM PARAMETERS
The Internet Domain Naming System (DOMAIN) includes several parameters. These are documented in RFC 883 [61]. The CLASS parameter is listed here. The per CLASS parameters are defined in separate RFCs as indicated.
RFC 1010 - Assigned Numbers May 1987 ARPANET Logical Addresses
ARPANET LOGICAL ADDRESSES
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 Joyce Reynolds. Assignments for other logical host addresses are made by the NIC.
RFC 1010 - Assigned Numbers May 1987 ARPANET Link Numbers
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 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.
RFC 1010 - Assigned Numbers May 1987 IEEE 802 SAP Numbers
IEEE 802 NUMBERS OF INTEREST
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 binary binary decimal 00000000 00000000 0 Null LSAP [IEEE]
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 on 802 networks was developed.
Reynolds & Postel [Page 12]
RFC 1010 - Assigned Numbers May 1987 IEEE 802 SAP Numbers
Due to some evolution of the IEEE 802.2 standards and the need to provide for a standard way to do additional DoD-IP related protocols (such as the Address Resolution Protocol (ARP) on IEEE 802 network, the following new policy is established, which will replace the old policy (see RFC 960 and RFC 948 [108]).
The new policy is for the Internet community to use the IEEE 802.2 encapsulation on 802.3, 802.4, and 802.5 networks by using the SNAP with an organization code indicating that the following 16 bits specify the EtherType code (where IP = 2048 (0800 hex), see Ethernet Numbers of Interest).
Header
...--------+--------+--------+ MAC Header| Length | 802.{3/4/5} MAC ...--------+--------+--------+
+--------+--------+--------+ | Dsap=K1| Ssap=K1| control| 802.2 SAP +--------+--------+--------+
+--------+--------+---------+--------+--------+ |protocol id or org code =K2| Ether Type | 802.2 SNAP +--------+--------+---------+--------+--------+
The total length of the SAP Header and the SNAP header is 8-octets, making the 802.2 protocol overhead come out on a nice boundary.
K1 is 170. The IEEE likes to talk about things in little-endian bit transmission order and specifies this value as 01010101. In big-endian order, as used in Internet specifications, this becomes 10101010 binary, or AA hex, or 170 decimal.
K2 is 0 (zero).
The use of the IP LSAP (K1 = 6) is to be phased out as quickly as possible.
Reynolds & Postel [Page 13]
RFC 1010 - Assigned Numbers May 1987 Ethernet Numbers
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.
If you need an Ethernet type, contact the XEROX Corporation, 2300 Geng Road, Palo Alto, California 94303, ATTN: Ms. Pam Cance.
Use the same codes as listed in the section called "Ethernet Numbers of Interest" (all hardware types use this code set for the protocol type).
Reynolds & Postel [Page 16]
RFC 1010 - Assigned Numbers May 1987 Public Data Network Numbers
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).
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.
The standard for transmission of IP datagrams over the Public Data Network is specified in RFC 877 [55].
Reynolds & Postel [Page 17]
RFC 1010 - Assigned Numbers May 1987 Telnet Options
TELNET OPTIONS
The Telnet Protocol has a number of options that may be negotiated. These options are listed here. "Official Internet Protocols" [91] provides more detailed information.
RFC 1010 - Assigned Numbers May 1987 Machine Names
MACHINE NAMES
These are the Official Machine Names as they appear in the NIC Host Table. Their use is described in RFC 810 [39].
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 NIC Host Table. Their use is described in RFC 810 [39].
A system name 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.
AEGIS APOLLO BS-2000 CEDAR CGW CHRYSALIS CMOS CMS COS CPIX CTOS CTSS DCN DDNOS DOMAIN EDX ELF EMBOS EMMOS EPOS FOONEX FUZZ GCOS GPOS HDOS IMAGEN INTERCOM IMPRESS INTERLISP IOS ITS LISP LISPM LOCUS MINOS MOS MPE5 MSDOS
MULTICS MVS MVS/SP NEXUS NMS NONSTOP NOS-2 OS/DDP OS4 OS86 OSX PCDOS PERQ/OS PLI PSDOS/MIT PRIMOS RMX/RDOS ROS RSX11M SATOPS SCS SIMP SWIFT TAC TANDEM TENEX TOPS10 TOPS20 TP3010 TRSDOS ULTRIX UNIX UT2D V VM VM/370 VM/CMS VM/SP VMS VMS/EUNICE VRTX WAITS WANG XDE XENIX
Reynolds & Postel [Page 25]
RFC 1010 - Assigned Numbers May 1987 Protocol Names
PROTOCOL AND SERVICE NAMES
These are the Official Protocol Names. Their use is described in greater detail in RFC 810 [39].
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.
ARGUS - ARGUS Protocol AUTH - Authentication Service BBN-RCC-MON - BBN RCC Monitoring BL-IDM - Britton Lee Intelligent Database Machine BOOTPC - Bootstrap Protocol Client BOOTPS - Bootstrap Protocol Server BR-SAT-MON - Backroom SATNET Monitoring CFTP - CFTP CHAOS - CHAOS Protocol CHARGEN - Character Generator Protocol CISCO-FNA - CISCO FNATIVE CISCO-TNA - CISCO TNATIVE CISCO-SYS - CISCO SYSMAINT CLOCK - DCNET Time Server Protocol COOKIE-JAR - Cookie Jar Authentication Procedure CSNET-NS - CSNET Mailbox Nameserver Protocol DAYTIME - Daytime Protocol DCN-MEAS - DCN Measurement Subsystems Protocol DCP - Device Control Protocol DISCARD - Discard Protocol DOMAIN - Domain Name Server ECHO - Echo Protocol EGP - Exterior Gateway Protocol 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 INGRES-NET - INGRES-NET Service IP - Internet Protocol
Reynolds & Postel [Page 26]
RFC 1010 - Assigned Numbers May 1987 Protocol Names
IPCU - Internet Packet Core Utility IPPC - Internet Pluribus Packet Core 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 LEAF-1 - Leaf-1 Protocol LEAF-2 - Leaf-2 Protocol LINK - Link Protocol LOC-SRV - Location Service LOGIN - Login Host Protocol MERIT-INP - MERIT Internodal Protocol METAGRAM - Metagram Relay MIT-ML-DEV - MIT ML Device MFE-NSP - MFE Network Services Protocol MIT-SUBNET - MIT Subnet Support MIT-DOV - MIT Dover Spooler MPM - Internet Message Protocol (Multimedia Mail) MPM-FLAGS - MPM Flags Protocol MPM-SND - MPM Send Protocol MSG-AUTH - MSG Authentication Protocol MSG-ICP - MSG ICP Protocol 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 NSW-FE - NSW User System Front End NTP - Network Time Protocol NVP-II - Network Voice Protocol POP2 - Post Office Protocol - Version 2 PRM - Packet Radio Measurement PUP - PUP Protocol PWDGEN - Password Generator Protocol QUOTE - Quote of the Day Protocol RDP - Reliable Data Protocol RJE - Remote Job Entry RLP - Resource Location Protocol RTELNET - Remote Telnet Service RVD - Remote Virtual Disk Protocol SAT-EXPAK - Satnet and Backroom EXPAK
Reynolds & Postel [Page 27]
RFC 1010 - Assigned Numbers May 1987 Protocol Names
SAT-MON - SATNET Monitoring SEP - Sequential Exchange Protocol SFTP - Simple File Transfer Protocol SMTP - Simple Mail Transfer Protocol ST - Stream Protocol STATSRV - Statistics Service SU-MIT-TG - SU/MIT Telnet Gateway Protocol SUNRPC - 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 TIME - Time Server Protocol 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 WB-EXPAK - Wideband EXPAK WB-MON - Wideband Monitoring XNET - Cross Net Debugger XNS-IDP - Xerox NS IDP
Reynolds & Postel [Page 28]
RFC 1010 - Assigned Numbers May 1987 Terminal Type Names
TERMINAL TYPE NAMES
These are the Official Terminal Type Names. Their use is described in RFC 930 [97]. The maximum length of a name is 40 characters.
A terminal names 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.
[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] Bennett, C., "A Simple NIFTP-Based Mail System", IEN 169, University College, London, January 1981.
[5] Bhushan, A., "A Report on the Survey Project", RFC 530, NIC 17375, June 1973.
[6] Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language (version 2.1)", ISI/TM-80-18, Information Sciences Institute, July 1980.
[7] 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.
[8] Braden, R., "NETRJS Protocol", RFC 740, NIC 42423, November 1977.
[9] Bressler, B., "Remote Job Entry Protocol", RFC 407, NIC 12112, October 1972.
[10] Bressler, R., "Inter-Entity Communication -- An Experiment", RFC 441, NIC 13773, January 1973.
[11] Butler, M., J. Postel, D. Chase, J. Goldberger, and J. K. Reynolds, "Post Office Protocol - Version 2", RFC 937, Information Sciences Institute, February 1985.
[12] Cass, D. E., and M. T. Rose, "ISO Transport Services on Top of the TCP", RFC 983, NTRC, April 1986.
[13] Clark, D., M. Lambert, and L. Zhang, "NETBLT: A Bulk Data Transfer Protocol", RFC 969, MIT Laboratory for Computer Science, December 1985.
[28] Crocker, D. H. and R. H. Gumpertz, "Revised Telnet Byte Marco Option", RFC 735, November 1977.
[29] Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)", RFC 951, Stanford and SUN Microsytems, September 1985.
[30] Day, J., "Telnet Data Entry Terminal Option", RFC 732, September 1977.
[31] DDN Protocol Handbook, "Telnet Output Line Width Option", NIC 50005, December 1985.
[32] DDN Protocol Handbook, "Telnet Output Page Size Option", NIC 50005, December 1985.
[33] DDN Protocol Handbook, "Telnet Reconnection Option", NIC 50005, December 1985.
[34] Deering, S. E., "Host Extensions for IP Multicasting", RFC 988, Stanford University, December 1985.
[35] Elvy, M., and R. Nedved, "Network Mail Path Service", RFC 915, Harvard and CMU, July 1986.
[36] Feinler, E., editor, "DDN Protocol Handbook", Network Information Center, SRI International, December 1985.
[37] Feinler, E., editor, "Internet Protocol Transition Workbook", Network Information Center, SRI International, March 1982.
[38] 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.
[39] Feinler, E., K. Harrenstien, Z. Su, and V. White, "DoD Internet Host Table Specification", RFC 810, SRI International, March 1982.
[40] Finlayson, R., T. Mann, J. Mogul, and M. Theimer, "A Reverse Address Resolution Protocol", RFC 903, Stanford University, June 1984.
[41] Forgie, J., "ST - A Proposed Internet Stream Protocol", IEN 119, MIT Lincoln Laboratory, September 1979.
[42] Forsdick, H., "CFTP", Network Message, Bolt Beranek and Newman, January 1982.
[58] 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.
[60] Mills, D., "Network Time Protocol", RFC 958, M/A-COM Linkabit, September 1985.
[61] Mockapetris, P., "Domain Names - Implementation and Specification", RFC 883, Information Sciences Institute, November 1983.
[62] Nedved, R., "Telnet Terminal Location Number Option", RFC 946, Carnegie-Mellon University, May 1985.
[63] 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.
[64] 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.
[65] Postel, J., "Active Users", RFC 866, Information Sciences Institute, May 1983.
[66] Postel, J., "A Standard for the Transmission of IP Datagrams over Experimental Ethernet Networks, RFC 895, Information Sciences Institute, April 1984.
[67] Postel, J., "Character Generator Protocol", RFC 864, Information Sciences Institute, May 1983.
[68] Postel, J., "Daytime Protocol", RFC 867, Information Sciences Institute, May 1983.
[69] Postel, J., "Discard Protocol", RFC 863, Information Sciences Institute, May 1983.
[70] Postel, J., "Echo Protocol", RFC 862, Information Sciences Institute, May 1983.
[71] Postel, J. and J. Reynolds, "File Transfer Protocol", RFC 959, Information Sciences Institute, October 1985.
[72] Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification", RFC 792, Information Sciences Institute, September 1981.
[73] Postel, J., "Internet Message Protocol", RFC 759, IEN 113, Information Sciences Institute, August 1980.
[74] Postel, J., "Name Server", IEN 116, Information Sciences Institute, August 1979.
[75] Postel, J., "Quote of the Day Protocol", RFC 865, Information Sciences Institute, May 1983.
[76] Postel, J., "Remote Telnet Service", RFC 818, Information Sciences Institute, November 1982.
[77] Postel, J., "Simple Mail Transfer Protocol", RFC 821, Information Sciences Institute, August 1982.
[78] Postel, J., "Telnet End of Record Option", RFC 885, Information Sciences Institute, December 1983.
[79] Postel, J., "User Datagram Protocol", RFC 768 Information Sciences Institute, August 1980.
[80] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", RFC 791, Information Sciences Institute, September 1981.
[81] Postel, J., ed., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", RFC 793, Information Sciences Institute, September 1981.
[82] Postel, J. and D. Crocker, "Remote Controlled Transmission and Echoing Telnet Option", RFC 726, March 1977.
[83] Postel, J., and K. Harrenstien, "Time Protocol", RFC 868, Information Sciences Institute, May 1983.
[84] Postel, J. and J. Reynolds, "Telnet Extended Options - List Option", RFC 861, Information Sciences Institute, May 1983.
[85] Postel, J. and J. Reynolds, "Telnet Binary Transmission", RFC 856, Information Sciences Institute, May 1983.
[86] Postel, J. and J. Reynolds, "Telnet Echo Option", RFC 857, Information Sciences Institute, May 1983.
[102] "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.
[103] The High Level Protocol Group, "A Network Independent File Transfer Protocol", INWG Protocol Note 86, December 1977.