Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc1010.txt.pdf Дата изменения: Wed Mar 27 23:02:33 2002 Дата индексирования: Tue Oct 2 18:25:46 2012 Кодировка: Поисковые слова: apollo 11

Network Working Group Request for Comments: Obsoletes 820, 790, 755, 750, Obsoletes RFCs: 776, 739, IENs: 990, 770, 604, 127,

1010 943, 923, 900, 870, 758, 433, 349 93

960, 762, 503, 117,

J. Reynolds J. Postel ISI May 1987

ASSIGNED NUMBERS

Status of this Memo 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

Reynolds & Postel

[Page 1]


RFC 1010 - Assigned Numbers

May 1987

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.

0 1 2 3 01234567890123456789012345678901 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 | 2 | 3 | 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 5 | 6 | 7 | 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 9 | 10 | 11 | 12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Transmission Order of Bytes Whenever an octet represents a numeric the diagram is the high order or most bit labeled 0 is the most significant following diagram represents the value quantity the left most bit in significant bit. That is, the bit. For example, the 170 (decimal).

01234567 +-+-+-+-+-+-+-+-+ |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 2]


RFC 1010 - Assigned Numbers Version Numbers

May 1987

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 ------0 1-3 4 5 6-14 15 Keyword ------Version ------Reserved Unassigned Internet Protocol ST Datagram Mode Unassigned Reserved References ---------[JBP] [JBP] [80,JBP] [41,JWF] [JBP] [JBP]

IP ST

Reynolds & Postel

[Page 3]


RFC 1010 - Assigned Numbers Protocol Numbers

May 1987

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. Assigned Internet Protocol Numbers Decimal ------0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34-60 61 62 63 Keyword ------Protocol -------Reserved ICMP Internet Control Message IGMP Internet Group Management GGP Gateway-to-Gateway Unassigned ST Stream TCP Transmission Control UCL UCL EGP Exterior Gateway Protocol IGP any private interior gateway BBN-RCC-MON BBN RCC Monitoring NVP-II Network Voice Protocol PUP PUP ARGUS ARGUS EMCON EMCON XNET Cross Net Debugger CHAOS Chaos UDP User Datagram MUX Multiplexing DCN-MEAS DCN Measurement Subsystems HMP Host Monitoring PRM Packet Radio Measurement XNS-IDP XEROX NS IDP TRUNK-1 Trunk-1 TRUNK-2 Trunk-2 LEAF-1 Leaf-1 LEAF-2 Leaf-2 RDP Reliable Data Protocol IRTP Internet Reliable Transaction ISO-TP4 ISO Transport Protocol Class 4 NETBLT Bulk Data Transfer Protocol MFE-NSP MFE Network Services Protocol MERIT-INP MERIT Internodal Protocol SEP Sequential Exchange Protocol Unassigned any host internal protocol CFTP CFTP any local network References ---------[JBP] [72,JBP] [34,JBP] [49,MB] [JBP] [41,JWF] [81,JBP] [PK] [92,DLM1] [JBP] [SGC] [15,SC3] [7,XEROX] [RWS4] [BN7] [47,JFH2] [NC3] [79,JBP] [16,JBP] [DLM1] [48,RH6] [ZSU] [102,XEROX] [SA2] [SA2] [SA2] [SA2] [106,RH6] [59,TXM] [51,RC77] [13,DDC1] [93,BCH2] [HWB] [JC120] [JBP] [JBP] [42,HCF2] [JBP]

Reynolds & Postel

[Page 4]


RFC 1010 - Assigned Numbers Protocol Numbers

May 1987

64 65 66 67 68 69 70 71 72-75 76 77 78 79 80-254 255

SAT-EXPAK MIT-SUBNET RVD IPPC SAT-MON IPCV BR-SAT-MON WB-MON WB-EXPAK

SATNET and Backroom EXPAK MIT Subnet Support MIT Remote Virtual Disk Protocol Internet Pluribus Packet Core any distributed file system SATNET Monitoring Unassigned Internet Packet Core Utility Unassigned Backroom SATNET Monitoring Unassigned WIDEBAND Monitoring WIDEBAND EXPAK Unassigned Reserved

[SHB] [NC3] [MBG] [SHB] [JBP] [SHB] [JBP] [SHB] [JBP] [SHB] [JBP] [SHB] [SHB] [JBP] [JBP]

Reynolds & Postel

[Page 5]


RFC 1010 - Assigned Numbers Port Numbers

May 1987

PORT NUMBERS 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 ------0 1-4 5 7 9 11 13 15 17 19 20 21 23 25 27 29 31 33 35 37 39 41 42 43 44 Description ----------Reserved Unassigned RJE Remote Job Entry ECHO Echo DISCARD Discard USERS Active Users DAYTIME Daytime Unassigned QUOTE Quote of the Day CHARGEN Character Generator FTP-DATA File Transfer [Default Data] FTP File Transfer [Control] TELNET Telnet SMTP Simple Mail Transfer NSW-FE NSW User System FE MSG-ICP MSG ICP MSG-AUTH MSG Authentication DSP Display Support Protocol any private printer server TIME Time RLP Resource Location Protocol GRAPHICS Graphics NAMESERVER Host Name Server NICNAME Who Is MPM-FLAGS MPM FLAGS Protocol Keyword ------References ---------[JBP] [JBP] [9,JBP] [70,JBP] [69,JBP] [65,JBP] [68,JBP] [JBP] [75,JBP] [67,JBP] [71,JBP] [71,JBP] [87,JBP] [77,JBP] [17,RHT] [63,RHT] [63,RHT] [MLC] [JBP] [83,JBP] [MA] [98,JBP] [74,JBP] [46,JAKE] [JBP]

Reynolds & Postel

[Page 6]


RFC 1010 - Assigned Numbers Port Numbers

May 1987

45 46 47 49 51 53 55 57 59 61 63 65 67 68 69 71 72 73 74 75 77 79 81 83 85 87 89 91 93 95 97 98 99 101 102 103 104 105 107 109 111 113 115 117 119 121 123 125

MPM MPM-SND NI-FTP LOGIN LA-MAINT DOMAIN ISI-GL

Message Processing Module [recv] [73,JBP] MPM [default send] [73,JBP] NI FTP [103,SK8] Login Host Protocol [PHD1] IMP Logical Address Maintenance [58,AGM] Domain Name Server [61,70,PM1] ISI Graphics Language [6,RB9] any private terminal access [JBP] any private file service [JBP] NI-MAIL NI MAIL [4,SK8] VIA-FTP VIA Systems - FTP [DXD] TACACS-DS TACACS-Database Service [3,RHT] BOOTPS Bootstrap Protocol Server [29,WJC2] BOOTPC Bootstrap Protocol Client [29,WJC2] TFTP Trivial File Transfer [95,DDC1] NETRJS-1 Remote Job Service [8,RTB3] NETRJS-2 Remote Job Service [8,RTB3] NETRJS-3 Remote Job Service [8,RTB3] NETRJS-4 Remote Job Service [8,RTB3] any private dial out service [JBP] any private RJE service [JBP] FINGER Finger [44,KLH] HOSTS2-NS HOSTS2 Name Server [EAK1] MIT-ML-DEV MIT ML Device [DPR] MIT-ML-DEV MIT ML Device [DPR] any private terminal link [JBP] SU-MIT-TG SU/MIT Telnet Gateway [MRC] MIT-DOV MIT Dover Spooler [EBM] DCP Device Control Protocol [DT15] SUPDUP SUPDUP [20,MRC] SWIFT-RVF Swift Remote Vitural File Protocol [MXR] TACNEWS TAC News [FRAN] METAGRAM Metagram Relay [GEOF] HOSTNAME NIC Host Name Server [45,JAKE] ISO-TSAP ISO-TSAP [12,MTR] X400 X400 [HCF2] X400-SND X400-SND [HCF2] CSNET-NS Mailbox Name Nameserver [96,MAS3] RTELNET Remote Telnet Service [76,JBP] POP-2 Post Office Protocol - Version 2 [11,JKR1] SUNRPC SUN Remote Procedure Call [DXG] AUTH Authentication Service [99,MCSJ] SFTP Simple File Transfer Protocol [56,MKL1] UUCP-PATH UUCP Path Service [35,MAE] NNTP Network News Transfer Protocol [53,PL4] ERPC HYDRA Expedited Remote Procedure Call[101,JXO] NTP Network Time Protocol [60,DLM1] LOCUS-MAP Locus PC-Interface Net Map Server [105,BXG]

Reynolds & Postel

[Page 7]


RFC 1010 - Assigned Numbers Port Numbers

May 1987

127 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143-159 160-223 224-241 243 245 247-255

LOCUS-CON PWDGEN CISCO-FNA CISCO-TNA CISCO-SYS STATSRV INGRES-NET LOC-SRV PROFILE NETBIOS-NS NETBIOS-DGM NETBIOS-SSN EMFIS-DATA EMFIS-CNTL BL-IDM

SUR-MEAS LINK

Locus PC-Interface Conn Server Password Generator Protocol CISCO FNATIVE CISCO TNATIVE CISCO SYSMAINT Statistics Service INGRES-NET Service Location Service PROFILE Naming System NETBIOS Name Service NETBIOS Datagram Service NETBIOS Session Service EMFIS Data Service EMFIS Control Service Britton-Lee IDM Unassigned Reserved Unassigned Survey Measurement LINK Unassigned

[105,BXG] [107,FJW] [WXB] [WXB] [WXB] [DLM1] [MXB] [JXP] [LLP] [JBP] [JBP] [JBP] [GB7] [GB7] [SXS1] [JBP] [JBP] [JBP] [5,AV] [10,RDB2] [JBP]

Reynolds & Postel

[Page 8]


RFC 1010 - Assigned Numbers Domain System Parameters

May 1987

DOMAIN SYSTEM PARAMETERS The Internet parameters. parameter is separate RFCs Domain Naming System (DOMAIN) includes several These are documented in RFC 883 [61]. The CLASS listed here. The per CLASS parameters are defined in as indicated.

Domain System Parameters: Decimal ------0 1 2 3 4-65534 65535 Name ---Reserved Internet Unassigned Chaos Unassigned Reserved References ---------[PM1] [61,PM1] [PM1] [PM1] [PM1] [PM1]

Reynolds & Postel

[Page 9]


RFC 1010 - Assigned Numbers ARPANET Logical Addresses

May 1987

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 reserved for assignment to well-known well-known functions are made by Joyce other logical host addresses are made Logical Address Assignments: Decimal ------0 1 2-254 255 Description ----------Reserved The BBN Core Gateways Unassigned Reserved References ---------[JBP] [MB] [JBP] [JBP] addresses. Of these, 256 are functions. Assignments for Reynolds. Assignments for by the NIC.

Reynolds & Postel

[Page 10]


RFC 1010 - Assigned Numbers ARPANET Link Numbers

May 1987

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. Link Assignments: Decimal ------0 1-149 150 151 152 153 154 155 156-158 159 160-194 195 196-247 248-255 Description ----------Reserved Unassigned Xerox NS IDP Unassigned PARC Universal Protocol TIP Status Reporting TIP Accounting Internet Protocol [regular] Internet Protocol [experimental] Figleaf Link Unassigned ISO-IP Experimental Protocols Network Maintenance References ---------[JBP] [JBP] [102,XEROX] [JBP] [7,XEROX] [JGH] [JGH] [80,JBP] [80,JBP] [JBW1] [JBP] [52,RXM] [JBP] [JGH]

Reynolds & Postel

[Page 11]


RFC 1010 - Assigned Numbers IEEE 802 SAP Numbers

May 1987

IEEE 802 NUMBERS OF INTEREST Some of the systems may same way the extension of (SNAP). networks of all classes are IEEE 802 Networks. use a Link Service Access Point (LSAP) field in ARPANET uses the "link" field. Further, there the LSAP header called the Sub-Network Access These much the is an Protocol

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 -------------------------IEEE Internet binary binary decimal 00000000 00000000 0 01000000 00000010 11000000 00000011 00100000 00000100 01100000 00000110 01110000 00001110 01110010 01001110 01110001 10001110 01010101 10101010 01111111 11111110 11111111 11111111 2 3 4 6 14 78 142 170 254 255 Description ----------References ----------

Null LSAP Indiv LLC Sublayer Mgt Group LLC Sublayer Mgt SNA Path Control DOD IP PROWAY-LAN EIA-RS 511 PROWAY-LAN SNAP ISO DIS 8473 Global DSAP

[IEEE] [IEEE] [IEEE] [IEEE] [79,JBP] [IEEE] [IEEE] [IEEE] [IEEE] [52,JXJ] [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 IEEE 802 SAP Numbers

May 1987

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 | ...--------+--------+--------+ +--------+--------+--------+ | Dsap=K1| Ssap=K1| control| +--------+--------+--------+ +--------+--------+---------+--------+--------+ |protocol id or org code =K2| Ether Type | +--------+--------+---------+--------+--------+

802.{3/4/5} MAC

802.2 SAP

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 Ethernet Numbers

May 1987

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. Assignments: Ethernet ------------decimal Hex 512 0200 513 0201 1536 0600 2048 0800 2049 0801 2050 0802 2051 0803 2052 0804 2053 0805 2054 0806 2055 0807 2076 081C 4096 1000 5632 1600 21000 5208 24577 6001 24578 6002 24579 6003 24580 6004 24581 6005 24582 6006 32771 8003 32772 8004 32773 8005 32774 8006 32784 8010 32821 8035 32824 8038 32859 805B [XEROX] 32860 805C [XEROX] 32892 807C 32923 809B Exp. Ethernet ------------decimal octal 512 1000 1536 3000 513 1001 Description ----------References ----------

XEROX PUP [7,XEROX] PUP Addr. Trans. [XEROX] XEROX NS IDP [102,XEROX] DOD IP [80,JBP] X.75 Internet [XEROX] NBS Internet [XEROX] ECMA Internet [XEROX] Chaosnet [XEROX] X.25 Level 3 [XEROX] ARP [64,JBP] XNS Compatability [XEROX] Symbolics Private [DCP1] Berkeley Trailer [XEROX] Valid [XEROX] BBN Simnet [XEROX] DEC MOP Dump/Load [XEROX] DEC MOP Remote Console [XEROX] DEC DECNET Phase IV [XEROX] DEC LAT [XEROX] DEC [XEROX] DEC [XEROX] Cronus VLN [100,DT15] Cronus Direct [100,DT15] HP Probe [XEROX] Nestar [XEROX] Excelan [XEROX] Reverse ARP [40,JXM] DEC LANBridge [XEROX] Stanford V Kernel experimental Stanford V Kernel production Merit Internodal Appletalk [HWB] [XEROX]

Reynolds & Postel

[Page 14]


RFC 1010 - Assigned Numbers Ethernet Numbers

May 1987

36864

9000

-

-

Loopback

[XEROX]

The standard for transmission of IP datagrams over Ethernets and Experimental Ethernets is specified in RFC 894 [50] and RFC 895 [66] respectively. NOTE: Ethernet 48-bit address blocks are now assigned by the IEEE.

IEEE Standards Office, 345 East 47th Street, New York, N.Y. 10017, Attn: Vince Condello. Phone: (212) 705-7092.

Reynolds & Postel

[Page 15]


RFC 1010 - Assigned Numbers Address Resolution Protocol

May 1987

ADDRESS RESOLUTION PROTOCOL PARAMETERS The Address Resolution Protocol (ARP) specified in RFC 826 [64] has several parameters. The assigned values for these parameters are listed here. Assignments: Operation Code (op) 1 2 REQUEST REPLY

Hardware Type (hrd) Type ---1 2 3 4 5 6 7 Description ----------Ethernet (10Mb) Experimental Ethernet (3Mb) Amateur Radio AX.25 Proteon ProNET Token Ring Chaos IEEE 802 Networks ARCNET References ---------[JBP] [JBP] [PXK] [JBP] [GXP] [JBP] [JBP]

Protocol Type (pro) 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 Public Data Network Numbers

May 1987

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. Assignments: * Internet Public Data Net - -----------------------------014.000.000.000 014.000.000.001 3110-317-00035 00 014.000.000.002 3110-608-00027 00 014.000.000.003 3110-302-00024 00 014.000.000.004 2342-192-00149 23 014.000.000.005 2342-192-00300 23 014.000.000.006 2342-192-00300 25 014.000.000.007 3110-608-00024 00 014.000.000.008 3110-213-00045 00 014.000.000.009 2342-192-00300 23 014.000.000.010 3110-617-00025 00 *014.000.000.011 2405-015-50300 00 014.000.000.012 3110-713-00165 00 014.000.000.013 3110-415-00261 00 014.000.000.014 3110-408-00051 00 014.000.000.015 2041-117-01000 00 014.000.000.016 2628-153-90075 00 014.000.000.017 3110-213-00032 00 014.000.000.018 2624-522-80900 52 014.000.000.019 2041-170-10000 00 014.000.000.020 5052-737-20000 50 014.000.000.021 3020-801-00057 50 014.000.000.022 2624-522-80902 77 *014.000.000.023 2624-589-00908 01 014.000.000.024 2342-905-24242 83 014.000.000.025 2342-905-24242 82 014.000.000.026-014.255.255.254 014.255.255.255 Description ----------Reserved PURDUE-TN UWISC-TN UDEL-TN UCL-VTEST UCL-TG UK-SATNET UWISC-IBM RAND-TN UCL-CS BBN-VAN-GW CHALMERS RICE DECWRL IBM-SJ SHAPE DFVLR4-X25 ISI-VAN-GW DFVLR5-X25 SHAPE-X25 UQNET DMC-CRC1 DFVLRVAX-X25 ECRC-X25 UK-MOD-RSRE UK-VAN-RSRE Unassigned Reserved References ---------[JBP] [CAK] [CAK] [CAK] [PK] [PK] [PK] [MAS3] [MO2] [PK] [JD21] [UXB] [PAM6] [PAM6] [SA1] [JFW] [GB7] [JD21] [GB7] [JFW] [AXH] [JR17] [GB7] [PXD] [JXE2] [AXM] [JBP] [JBP]

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 Telnet Options

May 1987

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. Options ------0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 22 23 24 25 26 27 28 255 Name ----------------------Binary Transmission Echo Reconnection Suppress Go Ahead Approx Message Size Negotiation Status Timing Mark Remote Controlled Trans and Echo Output Line Width Output Page Size Output Carriage-Return Disposition Output Horizontal Tab Stops Output Horizontal Tab Disposition Output Formfeed Disposition Output Vertical Tabstops Output Vertical Tab Disposition Output Linefeed Disposition Extended ASCII Logout Byte Macro Data Entry Terminal SUPDUP SUPDUP Output Send Location Terminal Type End of Record TACACS User Identification Output Marking Terminal Location Number Extended-Options-List References ---------[85,JBP] [86,JBP] [33,JBP] [89,JBP] [102,JBP] [88,JBP] [90,JBP] [82,JBP] [31,JBP] [32,JBP] [21,JBP] [25,JBP] [24,JBP] [22,JBP] [27,JBP] [26,JBP] [23,JBP] [104,JBP] [18,MRC] [28,JBP] [30,JBP] [19,20,MRC] [43,MRC] [54,EAK1] [97,MAS3] [78,JBP] [1,BA4] [94,SXS] [62,RN6] [84,JBP]

Reynolds & Postel

[Page 18]


RFC 1010 - Assigned Numbers Machine Names

May 1987

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. ALTO AMDAHL-V7 APOLLO ATT-3B20 BBN-C/60 BURROUGHS-B/29 BURROUGHS-B/4800 BUTTERFLY C/30 C/70 CADLINC CADR CDC-170 CDC-170/750 CDC-173 CELERITY-1200 COMTEN-3690 CP8040 CRAY-1 CRAY-X/MP CRAY-2 CTIWS-117 DANDELION DEC-10 DEC-1050 DEC-1077 DEC-1080 DEC-1090 DEC-1090B DEC-1090T DEC-2020T DEC-2040 DEC-2040T DEC-2050T DEC-2060 DEC-2060T DEC-2065 DEC-FALCON

Reynolds & Postel

[Page 19]


RFC 1010 - Assigned Numbers Machine Names

May 1987

DEC-KS10 DORADO DPS8/70M ELXSI-6400 FOONLY-F2 FOONLY-F3 FOONLY-F4 GOULD GOULD-6050 GOULD-6080 GOULD-9050 GOULD-9080 H-316 H-60/68 H-68 H-68/80 H-89 HONEYWELL-DPS-6 HONEYWELL-DPS-8/70 HP3000 HP3000/64 IBM-158 IBM-360/67 IBM-370/3033 IBM-3081 IBM-3084QX IBM-3101 IBM-4331 IBM-4341 IBM-4361 IBM-4381 IBM-4956 IBM-PC IBM-PC/AT IBM-PC/XT IBM-SERIES/1 IMAGEN IMAGEN-8/300 IMSAI INTEGRATED-SOLUTIONS INTEGRATED-SOLUTIONS-68K INTEGRATED-SOLUTIONS-CREATOR INTEGRATED-SOLUTIONS-CREATOR-8 INTEL-IPSC IS-1 IS-68010 LMI LSI-11

Reynolds & Postel

[Page 20]


RFC 1010 - Assigned Numbers Machine Names

May 1987

LSI-11/2 LSI-11/23 LSI-11/73 M68000 MASSCOMP MC500 MC68000 MICROVAX MICROVAX-I MV/8000 NAS3-5 NCR-COMTEN-3690 NOW ONYX-Z8000 PDP-11 PDP-11/3 PDP-11/23 PDP-11/24 PDP-11/34 PDP-11/40 PDP-11/44 PDP-11/45 PDP-11/50 PDP-11/70 PDP-11/73 PE-7/32 PE-3205 PERQ PLEXUS-P/60 PLI PLURIBUS PRIME-2350 PRIME-2450 PRIME-2755 PRIME-9655 PRIME-9755 PRIME-9955II PRIME-2250 PRIME-2655 PRIME-9955 PRIME-9950 PRIME-9650 PRIME-9750 PRIME-2250 PRIME-750 PRIME-850 PRIME-550II PYRAMID-90

Reynolds & Postel

[Page 21]


RFC 1010 - Assigned Numbers Machine Names

May 1987

PYRAMID-90MX PYRAMID-90X RIDGE RIDGE-32 RIDGE-32C ROLM-1666 S1-MKIIA SMI SEQUENT-BALANCE-8000 SIEMENS SILICON-GRAPHICS SILICON-GRAPHICS-IRIS SPERRY-DCP/10 SUN SUN-2 SUN-2/50 SUN-2/100 SUN-2/120 SUN-2/140 SUN-2/150 SUN-2/160 SUN-2/170 SUN-3/160 SUN-3/50 SUN-3/75 SUN-3/110 SUN-50 SUN-100 SUN-120 SUN-130 SUN-150 SUN-170 SUN-68000 SYMBOLICS-3600 SYMBOLICS-3670 TANDEM-TXP TEK-6130 TI-EXPLORER TP-4000 TRS-80 UNIVAC-1100 UNIVAC-1100/60 UNIVAC-1100/62 UNIVAC-1100/63 UNIVAC-1100/64 UNIVAC-1100/70 UNIVAC-1160 VAX-11/725

Reynolds & Postel

[Page 22]


RFC 1010 - Assigned Numbers Machine Names

May 1987

VAX-11/730 VAX-11/750 VAX-11/780 VAX-11/785 VAX-11/790 VAX-11/8600 VAX-8600 WANG-PC002 WANG-VS100 WANG-VS400 XEROX-1108 XEROX-8010

Reynolds & Postel

[Page 23]


RFC 1010 - Assigned Numbers System Names

May 1987

SYSTEM NAMES 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

Reynolds & Postel

[Page 24]


RFC 1010 - Assigned Numbers System Names

May 1987

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 Protocol Names

May 1987

PROTOCOL AND SERVICE NAMES These are the Official Protocol Names. greater detail in RFC 810 [39]. Their use is described in

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 AUTH BBN-RCC-MON BL-IDM BOOTPC BOOTPS BR-SAT-MON CFTP CHAOS CHARGEN CISCO-FNA CISCO-TNA CISCO-SYS CLOCK COOKIE-JAR CSNET-NS DAYTIME DCN-MEAS DCP DISCARD DOMAIN ECHO EGP EMCON EMFIS-CNTL EMFIS-DATA FINGER FTP FTP-DATA GGP GRAPHICS HMP HOST2-NS HOSTNAME ICMP IGMP IGP INGRES-NET IP ARGUS Protocol Authentication Service BBN RCC Monitoring Britton Lee Intelligent Database Machine Bootstrap Protocol Client Bootstrap Protocol Server Backroom SATNET Monitoring CFTP CHAOS Protocol Character Generator Protocol CISCO FNATIVE CISCO TNATIVE CISCO SYSMAINT DCNET Time Server Protocol Cookie Jar Authentication Procedure CSNET Mailbox Nameserver Protocol Daytime Protocol DCN Measurement Subsystems Protocol Device Control Protocol Discard Protocol Domain Name Server Echo Protocol Exterior Gateway Protocol Emission Control Protocol EMFIS Control Service EMFIS Data Service Finger Protocol File Transfer Protocol File Transfer Protocol Data Gateway Gateway Protocol Graphics Protocol Host Monitoring Protocol Host2 Name Server Hostname Protocol Internet Control Message Protocol Internet Group Management Protocol Interior Gateway Protocol INGRES-NET Service Internet Protocol

Reynolds & Postel

[Page 26]


RFC 1010 - Assigned Numbers Protocol Names

May 1987

IPCU IPPC IRTP ISI-GL ISO-TP4 ISO-TSAP LA-MAINT LEAF-1 LEAF-2 LINK LOC-SRV LOGIN MERIT-INP METAGRAM MIT-ML-DEV MFE-NSP MIT-SUBNET MIT-DOV MPM MPM-FLAGS MPM-SND MSG-AUTH MSG-ICP MUX NAMESERVER NETBIOS-DGM NETBIOS-NS NETBIOS-SSN NETBLT NETED NETRJS NI-FTP NI-MAIL NICNAME NSW-FE NTP NVP-II POP2 PRM PUP PWDGEN QUOTE RDP RJE RLP RTELNET RVD SAT-EXPAK

-

Internet Packet Core Utility Internet Pluribus Packet Core Internet Reliable Transaction Protocol ISI Graphics Language Protocol ISO Transport Protocol Class 4 ISO TSAP IMP Logical Address Maintenance Leaf-1 Protocol Leaf-2 Protocol Link Protocol Location Service Login Host Protocol MERIT Internodal Protocol Metagram Relay MIT ML Device MFE Network Services Protocol MIT Subnet Support MIT Dover Spooler Internet Message Protocol (Multimedia Mail) MPM Flags Protocol MPM Send Protocol MSG Authentication Protocol MSG ICP Protocol Multiplexing Protocol Host Name Server NETBIOS Datagram Service NETBIOS Name Service NETBIOS Session Service Bulk Data Transfer Protocol Network Standard Text Editor Remote Job Service NI File Transfer Protocol NI Mail Protocol Who Is Protocol NSW User System Front End Network Time Protocol Network Voice Protocol Post Office Protocol - Version 2 Packet Radio Measurement PUP Protocol Password Generator Protocol Quote of the Day Protocol Reliable Data Protocol Remote Job Entry Resource Location Protocol Remote Telnet Service Remote Virtual Disk Protocol Satnet and Backroom EXPAK

Reynolds & Postel

[Page 27]


RFC 1010 - Assigned Numbers Protocol Names

May 1987

SAT-MON SEP SFTP SMTP ST STATSRV SU-MIT-TG SUNRPC SUPDUP SUR-MEAS SWIFT-RVF TACACS-DS TACNEWS TCP TELNET TFTP TIME TRUNK-1 TRUNK-2 UCL UDP NNTP USERS UUCP-PATH VIA-FTP WB-EXPAK WB-MON XNET XNS-IDP

-

SATNET Monitoring Sequential Exchange Protocol Simple File Transfer Protocol Simple Mail Transfer Protocol Stream Protocol Statistics Service SU/MIT Telnet Gateway Protocol SUN Remote Procedure Call SUPDUP Protocol Survey Measurement Remote Virtual File Protocol TACACS-Database Service TAC News Transmission Control Protocol Telnet Protocol Trivial File Transfer Protocol Time Server Protocol Trunk-1 Protocol Trunk-2 Protocol University College London Protocol User Datagram Protocol Network News Transfer Protocol Active Users Protocol UUCP Path Service VIA Systems-File Transfer Protocol Wideband EXPAK Wideband Monitoring Cross Net Debugger Xerox NS IDP

Reynolds & Postel

[Page 28]


RFC 1010 - Assigned Numbers Terminal Type Names

May 1987

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. ADDS-CONSUL-980 ADDS-REGENT-100 ADDS-REGENT-20 ADDS-REGENT-200 ADDS-REGENT-25 ADDS-REGENT-40 ADDS-REGENT-60 AMPEX-DIALOGUE-80 ANDERSON-JACOBSON-630 ANDERSON-JACOBSON-832 ANDERSON-JACOBSON-841 ANN-ARBOR-AMBASSADOR ARDS BITGRAPH BUSSIPLEXER CALCOMP-565 CDC-456 CDI-1030 CDI-1203 CLNZ COMPUCOLOR-II CONCEPT-100 CONCEPT-104 CONCEPT-108 DATA-100 DATA-GENERAL-6053 DATAGRAPHIX-132A DATAMEDIA-1520 DATAMEDIA-1521 DATAMEDIA-2500 DATAMEDIA-3025 DATAMEDIA-3025A DATAMEDIA-3045 DATAMEDIA-3045A DATAMEDIA-DT80/1 DATAPOINT-2200 DATAPOINT-3000 DATAPOINT-3300

Reynolds & Postel

[Page 29]


RFC 1010 - Assigned Numbers Terminal Type Names

May 1987

DATAPOINT-3360 DEC-DECWRITER-I DEC-DECWRITER-II DEC-GT40 DEC-GT40A DEC-GT42 DEC-LA120 DEC-LA30 DEC-LA36 DEC-LA38 DEC-VT05 DEC-VT100 DEC-VT132 DEC-VT50 DEC-VT50H DEC-VT52 DELTA-DATA-5000 DELTA-TELTERM-2 DIABLO-1620 DIABLO-1640 DIGILOG-333 DTC-300S EDT-1200 EXECUPORT-4000 EXECUPORT-4080 GENERAL-TERMINAL-100A GSI HAZELTINE-1500 HAZELTINE-1510 HAZELTINE-1520 HAZELTINE-2000 HP-2621 HP-2621A HP-2621P HP-2626 HP-2626A HP-2626P HP-2640 HP-2640A HP-2640B HP-2645 HP-2645A HP-2648 HP-2648A HP-2649 HP-2649A IBM-3101 IBM-3101-10

Reynolds & Postel

[Page 30]


RFC 1010 - Assigned Numbers Terminal Type Names

May 1987

IBM-3275-2 IBM-3276-2 IBM-3276-3 IBM-3276-4 IBM-3277-2 IBM-3278-2 IBM-3278-3 IBM-3278-4 IBM-3278-5 IBM-3279-2 IBM-3279-3 IMLAC INFOTON-100 INFOTONKAS ISC-8001 LSI-ADM-3 LSI-ADM-31 LSI-ADM-3A LSI-ADM-42 MEMOREX-1240 MICROBEE MICROTERM-ACT-IV MICROTERM-ACT-V MICROTERM-MIME-1 MICROTERM-MIME-2 NETRONICS NETWORK-VIRTUAL-TERMINAL OMRON-8025AG PERKIN-ELMER-1100 PERKIN-ELMER-1200 PERQ PLASMA-PANEL QUME-SPRINT-5 SOROC SOROC-120 SOUTHWEST-TECHNICAL-PRODUCTS-CT82 SUPERBEE SUPERBEE-III-M TEC TEKTRONIX-4010 TEKTRONIX-4012 TEKTRONIX-4013 TEKTRONIX-4014 TEKTRONIX-4023 TEKTRONIX-4024 TEKTRONIX-4025 TEKTRONIX-4027 TELERAY-1061

Reynolds & Postel

[Page 31]


RFC 1010 - Assigned Numbers Terminal Type Names

May 1987

TELERAY-3700 TELERAY-3800 TELETEC-DATASCREEN TELETERM-1030 TELETYPE-33 TELETYPE-35 TELETYPE-37 TELETYPE-38 TELETYPE-43 TELEVIDEO-912 TELEVIDEO-920 TELEVIDEO-920B TELEVIDEO-920C TELEVIDEO-950 TERMINET-1200 TERMINET-300 TI-700 TI-733 TI-735 TI-743 TI-745 TYCOM UNIVAC-DCT-500 VIDEO-SYSTEMS-1200 VIDEO-SYSTEMS-5000 VISUAL-200 XEROX-1720 ZENITH-H19 ZENTEC-30

Reynolds & Postel

[Page 32]


RFC 1010 - Assigned Numbers Documents

May 1987

DOCUMENTS [1] Anderson, B., "TACACS User Identification Telnet Option", RFC 927, BBN, December 1984. BBN, "Specifications for the Interconnection of a Host and an IMP", Report 1822, Bolt Beranek and Newman, Cambridge, Massachusetts, revised, December 1981. BBN, "User Manual for TAC User Database Tool", Bolt Beranek and Newman, September 1984. Bennett, C., "A Simple NIFTP-Based Mail System", IEN 169, University College, London, January 1981. Bhushan, A., "A Report on the Survey Project", RFC 530, NIC 17375, June 1973. Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language (version 2.1)", ISI/TM-80-18, Information Sciences Institute, July 1980. 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. Braden, R., "NETRJS Protocol", RFC 740, NIC 42423, November 1977. Bressler, B., "Remote Job Entry Protocol", NIC 12112, October 1972. RFC 407,

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

Bressler, R., "Inter-Entity Communication -- An Experiment", RFC 441, NIC 13773, January 1973. Butler, M., J. Postel, D. Chase, J. Goldberger, and J. K. Reynolds, "Post Office Protocol - Version 2", RFC 937, Information Sciences Institute, February 1985. Cass, D. E., and M. T. Rose, "ISO Transport Services on Top of the TCP", RFC 983, NTRC, April 1986. Clark, D., M. Lambert, and L. Zhang, "NETBLT: A Bulk Data Transfer Protocol", RFC 969, MIT Laboratory for Computer Science, December 1985.

[11]

[12]

[13]

Reynolds & Postel

[Page 33]


RFC 1010 - Assigned Numbers Documents

May 1987

[14]

Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer Magazine, October 1981. Cohen, D., "Specifications for the Network Voice Protocol", RFC 741, ISI/RR 7539, Information Sciences Institute, March 1976. Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90, Information Sciences Institute, May 1979. 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. Crispin, M., "Telnet Logout Option", Stanford University-AI, RFC 727, April 1977. Crispin, M., "Telnet SUPDUP Option", Stanford University-AI, RFC 736, October 1977. Crispin, M., "SUPDUP Protocol", RFC 734, NIC 41953, October 1977. Crocker, D., "Telnet Output Carriage-Return Disposition Option", RFC 652, October 1974. Crocker, D., "Telnet Output Formfeed Disposition Option", RFC 655, October 1974. Crocker, D., "Telnet Output Linefeed Disposition", RFC 658, October 1974. Crocker, D., "Telnet Output Horizontal Tab Disposition Option", RFC 654, October 1974. Crocker, D., "Telnet Output Horizontal Tabstops Option", RFC 653, October 1974. Crocker, D., "Telnet Output Vertical Tab Disposition Option", RFC 657, October 1974. Crocker, D., "Telnet Output Vertical Tabstops Option", RFC 656, October 1974.

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

[26]

[27]

Reynolds & Postel

[Page 34]


RFC 1010 - Assigned Numbers Documents

May 1987

[28]

Crocker, D. H. and R. H. Gumpertz, "Revised Telnet Byte Marco Option", RFC 735, November 1977. Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)", RFC 951, Stanford and SUN Microsytems, September 1985. Day, J., "Telnet Data Entry Terminal Option", RFC 732, September 1977. DDN Protocol Handbook, "Telnet Output Line Width Option", NIC 50005, December 1985. DDN Protocol Handbook, "Telnet Output Page Size Option", NIC 50005, December 1985. DDN Protocol Handbook, "Telnet Reconnection Option", NIC 50005, December 1985. Deering, S. E., "Host Extensions for IP Multicasting", RFC 988, Stanford University, December 1985. Elvy, M., and R. Nedved, "Network Mail Path Service", RFC 915, Harvard and CMU, July 1986. Feinler, E., editor, "DDN Protocol Handbook", Network Information Center, SRI International, December 1985. Feinler, E., editor, "Internet Protocol Transition Workbook", Network Information Center, SRI International, March 1982. 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. Feinler, E., K. Harrenstien, Z. Su, and V. White, "DoD Internet Host Table Specification", RFC 810, SRI International, March 1982. Finlayson, R., T. Mann, J. Mogul, and M. Theimer, "A Reverse Address Resolution Protocol", RFC 903, Stanford University, June 1984. Forgie, J., "ST - A Proposed Internet Stream Protocol", IEN 119, MIT Lincoln Laboratory, September 1979. Forsdick, H., "CFTP", Network Message, Bolt Beranek and Newman, January 1982.

[29]

[30]

[31]

[32]

[33]

[34]

[35]

[36]

[37]

[38]

[39]

[40]

[41]

[42]

Reynolds & Postel

[Page 35]


RFC 1010 - Assigned Numbers Documents

May 1987

[43]

Greenberg, B., "Telnet SUPDUP-OUTPUT Option", RFC 749, MIT-Multics, September 1978. Harrenstien, K., "Name/Finger", RFC 742, NIC 42758, SRI International, December 1977. Harrenstien, K., V. White, and E. Feinler, "Hostnames Server", RFC 811, SRI International, March 1982. Harrenstien, K., and V. White, "Nicname/Whois", RFC 812, SRI International, March 1982. Haverty, J., "XNET Formats for Internet Protocol Version 4", IEN 158, October 1980. Hinden, R. M., "A Host Monitoring Protocol", RFC 869, Bolt Beranek and Newman, December 1983. Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway", RFC 823, September 1982. Hornig, C., "A Standard for the Transmission of IP Datagrams over Ethernet Networks, RFC 894, Symbolics, April 1984. International Standards Organization, "ISO Transport Protocol Specification - ISO DP 8073", RFC 905, April 1984. International Standards Organization, "Protocol for Providing the Connectionless-Mode Network Services", RFC 926, ISO, December 1984. Kantor, B., and P. Lapsley, "Network News Transfer Protocol", RFC 977, UC San Diego & UC Berkeley, February 1986. Killian, E., "Telnet Send-Location Option", RFC 779, April 1981. Korb, J. T., "A Standard for the Transmission of IP Datagrams Over Public Data Networks", RFC 877, Purdue University, September 1983. Lottor, M. K., "Simple File Transfer Protocol", RFC 913, MIT, September 1984. Malis, A., "Logical Addressing Implementation Specification", BBN Report 5256, pp 31-36, May 1983.

[44]

[45]

[46]

[47]

[48]

[49]

[50]

[51]

[52]

[53]

[54]

[55]

[56]

[57]

Reynolds & Postel

[Page 36]


RFC 1010 - Assigned Numbers Documents

May 1987

[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. Miller, T., "Internet Reliable Transaction Protocol", RFC 938, ACC, February 1985. Mills, D., "Network Time Protocol", RFC 958, M/A-COM Linkabit, September 1985. Mockapetris, P., "Domain Names - Implementation and Specification", RFC 883, Information Sciences Institute, November 1983. Nedved, R., "Telnet Terminal Location Number Option", RFC 946, Carnegie-Mellon University, May 1985. 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. 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. Postel, J., "Active Users", RFC 866, Information Sciences Institute, May 1983. Postel, J., "A Standard for the Transmission of IP Datagrams over Experimental Ethernet Networks, RFC 895, Information Sciences Institute, April 1984. Postel, J., "Character Generator Protocol", RFC 864, Information Sciences Institute, May 1983. Postel, J., "Daytime Protocol", RFC 867, Information Sciences Institute, May 1983. Postel, J., "Discard Protocol", RFC 863, Information Sciences Institute, May 1983. Postel, J., "Echo Protocol", RFC 862, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "File Transfer Protocol", RFC 959, Information Sciences Institute, October 1985.

[59]

[60]

[61]

[62]

[63]

[64]

[65]

[66]

[67]

[68]

[69]

[70]

[71]

Reynolds & Postel

[Page 37]


RFC 1010 - Assigned Numbers Documents

May 1987

[72]

Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification", RFC 792, Information Sciences Institute, September 1981. Postel, J., "Internet Message Protocol", RFC 759, IEN 113, Information Sciences Institute, August 1980. Postel, J., "Name Server", IEN 116, Information Sciences Institute, August 1979. Postel, J., "Quote of the Day Protocol", RFC 865, Information Sciences Institute, May 1983. Postel, J., "Remote Telnet Service", RFC 818, Information Sciences Institute, November 1982. Postel, J., "Simple Mail Transfer Protocol", RFC 821, Information Sciences Institute, August 1982. Postel, J., "Telnet End of Record Option", RFC 885, Information Sciences Institute, December 1983. Postel, J., "User Datagram Protocol", RFC 768 Information Sciences Institute, August 1980. Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", RFC 791, Information Sciences Institute, September 1981. Postel, J., ed., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", RFC 793, Information Sciences Institute, September 1981. Postel, J. and D. Crocker, "Remote Controlled Transmission and Echoing Telnet Option", RFC 726, March 1977. Postel, J., and K. Harrenstien, "Time Protocol", RFC 868, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Extended Options - List Option", RFC 861, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Binary Transmission", RFC 856, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Echo Option", RFC 857, Information Sciences Institute, May 1983.

[73]

[74]

[75]

[76]

[77]

[78]

[79]

[80]

[81]

[82]

[83]

[84]

[85]

[86]

Reynolds & Postel

[Page 38]


RFC 1010 - Assigned Numbers Documents

May 1987

[87]

Postel, J., and J. Reynolds, "Telnet Protocol Specification", RFC 854, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Status Option", RFC 859, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Suppress Go Ahead Option", RFC 858, Information Sciences Institute, May 1983. Postel, J. and J. Reynolds, "Telnet Timing Mark Option", RFC 860, Information Sciences Institute, May 1983. Reynolds, J. and J. Postel, "Official Internet Protocols", RFC 1011, Information Sciences Institute, May 1987. Seamonson, L. J., and E. C. Rosen, "STUB" Exterior Gateway Protocol", RFC 888, BBN Communications Corporation, January 1984. Shuttleworth, B., "A Documentary of MFENet, a National Computer Network", UCRL-52317, Lawrence Livermore Labs, Livermore, California, June 1977. Silverman, S., "Output Marking Telnet Option", RFC 933, MITRE, January 1985. Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, MIT/LCS, June 1981. Solomon, M., L. Landweber, and D. Neuhengen, "The CSNET Name Server", Computer Networks, v.6, n.3, pp. 161-172, July 1982. Solomon, M., and E. Wimmers, "Telnet Terminal Type Option", RFC 930, Supercedes RFC 884, University of Wisconsin, Madison, January 1985. Sproull, R., and E. Thomas, "A Networks Graphics Protocol", NIC 24308, August 1974. StJohns, M., "Authentication Service", RFC 931, TPSC, January 1985. Tappan, D. C., "The CRONUS Virtual Local Network", RFC 824, Bolt Beranek and Newman, August 1982. Taylor, J., "ERPC Functional Specification", Version 1.04, HYDRA Computer Systems, Inc., July 1984.

[88]

[89]

[90]

[91]

[92]

[93]

[94]

[95]

[96]

[97]

[98]

[99]

[100]

[101]

Reynolds & Postel

[Page 39]


RFC 1010 - Assigned Numbers Documents

May 1987

[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. The High Level Protocol Group, "A Network Independent File Transfer Protocol", INWG Protocol Note 86, December 1977. Tovar, "Telnet Extended ASCII Option", RFC 698, Stanford University-AI, July 1975. Uttal, J, J. Rothschild, and C. Kline, "Transparent Integration of UNIX and MS-DOS", Locus Computing Corporation. Velten, D., R. Hinden, and J. Sax, "Reliable Data Protocol", RFC 908, BBN Communications Corporation, July 1984. Wancho, F., "Password Generator Protocol", January 1986. RFC 972, WSMR,

[103]

[104]

[105]

[106]

[107]

[108]

Winston, I., "Two Methods for the Transmission of IP Datagrams Over IEEE 802.3 Networks", RFC 948, University Of Pennsylvania, June 1985. Khanna, A., and A. Malis, "The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)", RFC 1005, BBN Communications Corporation, May 1987.

[109]

Reynolds & Postel

[Page 40]


RFC 1010 - Assigned Numbers People

May 1987

PEOPLE [AGM] [AV] [AXH] [BA4] [BCH2] [BN4] [CAK] [DCP1] [DDC1] [DLM1] [DPR] [DT15] [DXD] [DXG] [EAK1] [EBM] [FJW] [FRAN] [GB7] [GEOF] [GXP] [HCF2] [HWB] Andy Malis Al Vezza Arthur Hartwig Brian Anderson Barry Howard Bill Nowicki Chris Kent David Plummer David Clark David Mills David Reed Daniel Tappan Dennis J.W. Dube David Goldberg Earl Killian Eliot Moss Frank J. Wancho Francine Perillo Gerd Beling Geoff Goodfellow Gill Pratt Harry Forsdick Hans-Werner Braun BBN MIT UQNET BBN LLL SUN PURDUE MIT MIT LINKABIT MIT-LCS BBN Malis@CCS.BBN.COM AV@XX.LCS.MIT.EDU ---none--baanders@CCQ.BBN.COM Howard@LLL-MFE.ARPA Nowicki@SUN.COM CAK@PURDUE.EDU DCP@SYMBOLICS.ARPA DClark@MIT-MULTICS.ARPA Mills@D.ISI.EDU Reed@MIT-MULTICS.ARPA Tappan@BBN.COM

VIA SYSTEMS ---none--SMI LLL MIT WSMR SRI DFVLR SRI MIT BBN MICHIGAN sun!dg@UCBARPA.BERKELEY.EDU EAK@S1-C.ARPA EBM@XX.LCS.MIT.EDU WANCHO@SIMTEL20.ARPA Perillo@NIC.SRI.COM GBELING@ISI.EDU Geoff@SRI-CSL.ARPA gill%mit-ccc@MC.LCS.MIT.EDU Forsdick@A.BBN.COM HWB@MCR.UMICH.EDU

Reynolds & Postel

[Page 41]


RFC 1010 - Assigned Numbers People

May 1987

[IEEE] [JAKE] [JBP] [JBW1] [JD21] [JFH2] [JFW] [JGH] [JR17] [JWF] [JXE2] [JXM] [JXO] [JXP] [KLH] [LLP] [MA] [MAE] [MAS3] [MB] [MBG] [MCSJ] [MKL1] [MLC]

Vince Condello Jake Feinler Jon Postel

IEEE SRI ISI

---none--Feinler@SRI-NIC.ARPA Postel@ISI.EDU JWalters@CCX.BBN.COM JDreyer@CCV.BBN.COM Haverty@CCV.BBN.COM Wilkes@STC.ARPA Herman@CCJ.BBN.COM Robinson@DMC-CRC.ARPA jwf@LL-EN.ARPA JME%RSRE.MOD.UK@CS.UCL.AC.UK ---none-----none--apollo!pato@EDDIE.MIT.EDU KLH@NIC.SRI.COM llp@PURDUE.EDU MIKE.ACCETTA@CMU-CS-A.EDU elvy@HARVARD.EDU solomon@OFFICE-1.ARPA Brescia@CCV.BBN.COM Greenwald@MIT-MULTICS.ARPA StJohns@MIT-MULTICS.ARPA MKL@NIC.SRI.COM Corrigan@DDN1.ARPA

Joseph Walters, Jr. BBN Jonathan Dreyer Jack Haverty Jon F. Wilkes Jim Herman John L. Robinson Jim Forgie Jeanne Evans Jeff Mogul Jack O'Neil Joe Pato Ken Harrenstien Larry Peterson Mike Accetta Marc A. Elvy Marc Solomon Michael Brescia Michael Greenwald Mike StJohns Mark Lottor Mike Corrigan BBN BBN STC BBN CANADA LL UKMOD Stanford ENCORE Apollo SRI PURDUE CMU HARVARD MDAC BBN MIT-LCS TPSC MIT DDN

Reynolds & Postel

[Page 42]


RFC 1010 - Assigned Numbers People

May 1987

[MO2] [MRC]

Michael O'Brien Mark Crispin

RAND STANFORD

OBrien@RAND-UNIX.ARPA

Admin.MRC@SU-SCORE.STANFORD.EDU [MTR] [MXB] [MXR] [NC3] [PAM6] [PHD1] [PK] [PL4] [PM1] [PXD] [RDB2] [RH6] [RHT] [RN6] [RTB3] [RWS4] [RXM] [SA1] [SA2] [SC3] [SGC] [SHB] Marshall Rose Mike Berrow Mark A. Rosenstein J. Noel Chiappa Paul McNabb Pieter Ditmars Peter Kirstein Phil Lapsley Paul Mockapetris Pete Delaney Robert Bressler Robert Hinden Robert Thomas Rudy Nedved Bob Braden NRTC MRose@NRTC.ARPA ---none---

Relational Technology MIT MIT RICE BBN UCL BERKELEY ISI ECRC BBN BBN BBN CMU ISI

mark@BORAX.LCS.MIT.EDU JNC@XX.LCS.MIT.EDU pam@PURDUE.EDU pditmars@CCX.BBN.COM Kirstein@ISI.EDU phil@UCBARPA.BERKELEY.EDU Mockapetris@ISI.EDU pete%ecrcvax@CSNET-RELAY.ARPA Bressler@CCW.BBN.COM Hinden@CCV.BBN.COM BThomas@F.BBN.COM Rudy.Nedved@CMU-CS-A.EDU Braden@ISI.EDU RWS@XX.LCS.MIT.EDU Myhill@CCS.BBN.COM andler.ibm-sj@RAND-RELAY.ARPA Amarel@ISI.EDU Casner@ISI.EDU Chipman@F.BBN.COM BLUMENTHAL@VAX.BBN.COM

Robert W. Scheifler ARGUS Robert Myhill Sten Andler Saul Amarel Steve Casner Steve Chipman Steven Blumenthal BBN ARPA ARPA ISI BBN BBN

Reynolds & Postel

[Page 43]


RFC 1010 - Assigned Numbers People

May 1987

[SXS] [SXS1] [TXM] [UXB] [WJC2] [WXB] [XEROX] [ZSU]

Steve Silverman Susie Snitzer Trudy Miller Ulf Bilting Bill Croft William L. Biagi Pam Cance Zaw-Sing Su

MITRE

Blankert@MITRE-GATEWAY.ORG

Britton-Lee ---none--ACC CHALMERS STANFORD CISCO XEROX SRI Trudy@ACC.ARPA bilting@PURDUE.EDU Croft@SUMEX-AIM.ARPA ---none--Cance.OSBUnorth@XEROX.COM ZSu@SRI-TSC.ARPA

Reynolds & Postel

[Page 44]