Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page]
Obsoleted by:3232 HISTORIC
Network Working Group J. ReynoldsRequest for Comments: 1700 J. PostelSTD: 2 ISIObsoletes RFCs:1340,1060,1010,990,960, October 1994943,923,900,870,820,790,776,770,762, 758,755, 750, 739, 604, 503, 433, 349Obsoletes IENs: 127, 117, 93Category: Standards TrackASSIGNED NUMBERSStatus 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.OVERVIEWThis RFC is a snapshot of the ongoing process of the assignment ofprotocol parameters for the Internet protocol suite. To make thecurrent information readily available the assignments are kept up-to-date in a set of online text files. This RFC has been assembled bycatinating these files together with a minimum of formatting "glue".The authors appologize for the somewhat rougher formatting and stylethan is typical of most RFCs.We expect that various readers will notice specific items that should becorrected. Please send any specific corrections via email to<iana@isi.edu>.Reynolds & Postel [Page 1]
RFC 1700 Assigned Numbers October 1994INTRODUCTIONThe files in this directory document the currently assigned values forseveral series of numbers used in network protocol implementations.ftp://ftp.isi.edu/in-notes/iana/assignmentsThe Internet Assigned Numbers Authority (IANA) is the centralcoordinator for the assignment of unique parameter values for Internetprotocols. The IANA is chartered by the Internet Society (ISOC) andthe Federal Network Council (FNC) to act as the clearinghouse toassign and coordinate the use of numerous Internet protocolparameters.The Internet protocol suite, as defined by the Internet EngineeringTask Force (IETF) and its steering group (the IESG), contains numerousparameters, such as internet addresses, domain names, autonomoussystem numbers (used in some routing protocols), protocol numbers,port numbers, management information base object identifiers,including private enterprise numbers, and many others.The common use of the Internet protocols by the Internet communityrequires that the particular values used in these parameter fields beassigned uniquely. It is the task of the IANA to make those uniqueassignments as requested and to maintain a registry of the currentlyassigned values.Requests for parameter assignments (protocols, ports, etc.) should besent to <iana@isi.edu>.Requests for SNMP network management private enterprise numberassignments should be sent to <iana-mib@isi.edu>.The IANA is located at and operated by the Information SciencesInstitute (ISI) of the University of Southern California (USC).If you are developing a protocol or application that will require theuse of a link, socket, port, protocol, etc., please contact the IANAto receive a number assignment. Joyce K. Reynolds Internet Assigned Numbers Authority USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Electronic mail: IANA@ISI.EDU Phone: +1 310-822-1511Reynolds & Postel [Page 2]
RFC 1700 Assigned Numbers October 1994Most of the protocols are documented in the RFC series of notes. Someof the items listed are undocumented. Further information onprotocols can be found in the memo, "Internet Official ProtocolStandards" (STD 1).Data NotationsThe convention in the documentation of Internet Protocols is toexpress numbers in decimal and to picture data in "big-endian" order[COHEN]. That is, fields are described left to right, with the mostsignificant octet on the left and the least significant octet on theright.The order of transmission of the header and data described in thisdocument is resolved to the octet level. Whenever a diagram shows agroup of octets, the order of transmission of those octets is thenormal order in which they are read in English. For example, in thefollowing diagram the octets are transmitted in the order they arenumbered. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 | 2 | 3 | 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 5 | 6 | 7 | 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 9 | 10 | 11 | 12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Transmission Order of BytesWhenever an octet represents a numeric quantity the left most bit in thediagram is the high order or most significant bit. That is, the bitlabeled 0 is the most significant bit. For example, the followingdiagram represents the value 170 (decimal). 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ |1 0 1 0 1 0 1 0| +-+-+-+-+-+-+-+-+ Significance of BitsSimilarly, whenever a multi-octet field represents a numeric quantitythe left most bit of the whole field is the most significant bit. WhenReynolds & Postel [Page 3]
RFC 1700 Assigned Numbers October 1994a multi-octet quantity is transmitted the most significant octet istransmitted first.Special AddressesThere are five classes of IP addresses: Class A through Class E. Ofthese, Classes A, B, and C are used for unicast addresses, Class D isused for multicast addresses, and Class E addresses are reserved forfuture use.With the advent of classless addressing [CIDR1,CIDR2], thenetwork-number part of an address may be of any length, and the wholenotion of address classes becomes less important.There are certain special cases for IP addresses. These special casescan be concisely summarized using the earlier notation for an IPaddress: IP-address ::= { <Network-number>, <Host-number> } or IP-address ::= { <Network-number>, <Subnet-number>, <Host-number> }if we also use the notation "-1" to mean the field contains all 1bits. Some common special cases are as follows: (a) {0, 0} This host on this network. Can only be used as a source address (see note later). (b) {0, <Host-number>} Specified host on this network. Can only be used as a source address. (c) { -1, -1} Limited broadcast. Can only be used as a destination address, and a datagram with this address must never be forwarded outside the (sub-)net of the source. (d) {<Network-number>, -1} Directed broadcast to specified network. Can only be used as a destination address.Reynolds & Postel [Page 4]
RFC 1700 Assigned Numbers October 1994 (e) {<Network-number>, <Subnet-number>, -1} Directed broadcast to specified subnet. Can only be used as a destination address. (f) {<Network-number>, -1, -1} Directed broadcast to all subnets of specified subnetted network. Can only be used as a destination address. (g) {127, <any>} Internal host loopback address. Should never appear outside a host.REFERENCES[COHEN] Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer Magazine, October 1981.[CIDR1] Fuller, V., T. Li, J. Yu, and K. Varadhan, "Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy",RFC 1519, September 1993.[CIDR2] Rekhter, Y., and T. Li, "An Architecture for IP Address Allocation with CIDR",RFC 1518, September 1993.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/introductionReynolds & Postel [Page 5]
RFC 1700 Assigned Numbers October 1994VERSION NUMBERSIn the Internet Protocol (IP) [RFC791] there is a field to identifythe version of the internetwork general protocol. This field is 4bits in size.Assigned Internet Version NumbersDecimal Keyword Version References------- ------- ------- ---------- 0 Reserved [JBP] 1-3 Unassigned [JBP] 4 IP Internet Protocol [RFC791,JBP] 5 ST ST Datagram Mode [RFC1190,JWF] 6 SIP Simple Internet Protocol [RH6] 7 TP/IX TP/IX: The Next Internet [RXU] 8 PIP The P Internet Protocol [PXF] 9 TUBA TUBA [RXC]10-14 Unassigned [JBP] 15 Reserved [JBP]REFERENCES[RFC791] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5,RFC 791, USC/Information Sciences Institute, September 1981.[RFC1190] Topolcic, C., Editor, "Experimental Internet Stream Protocol, Version 2 (ST-II)",RFC 1190, CIP Working Group, October 1990.PEOPLE[JPB] Jon Postel <postel@isi.edu>[JWF] Jim Forgie <FORGIE@XN.LL.MIT.ED>[RH6] Robert Hinden <Hinden@ENG.SUN.COM>[RXU] Robert Ullmann <ariel@world.std.com>[PXF] Paul Francis <francis@cactus.ntt.jp>[RXC] Ross Callon <callon@wellfleet.com>[]Reynolds & Postel [Page 6]
RFC 1700 Assigned Numbers October 1994URL =ftp://ftp.isi.edu/in-notes/iana/assignments/version-numbersReynolds & Postel [Page 7]
RFC 1700 Assigned Numbers October 1994PROTOCOL NUMBERSIn the Internet Protocol (IP) [DDN], [RFC791] there is a field, calledProtocol, to identify the next level protocol. This is an 8 bitfield.Assigned Internet Protocol NumbersDecimal Keyword Protocol References------- ------- -------- ---------- 0 Reserved [JBP] 1 ICMP Internet Control Message [RFC792,JBP] 2 IGMP Internet Group Management [RFC1112,JBP] 3 GGP Gateway-to-Gateway [RFC823,MB] 4 IP IP in IP (encasulation) [JBP] 5 ST Stream [RFC1190,IEN119,JWF] 6 TCP Transmission Control [RFC793,JBP] 7 UCL UCL [PK] 8 EGP Exterior Gateway Protocol [RFC888,DLM1] 9 IGP any private interior gateway [JBP] 10 BBN-RCC-MON BBN RCC Monitoring [SGC] 11 NVP-II Network Voice Protocol [RFC741,SC3] 12 PUP PUP [PUP,XEROX] 13 ARGUS ARGUS [RWS4] 14 EMCON EMCON [BN7] 15 XNET Cross Net Debugger [IEN158,JFH2] 16 CHAOS Chaos [NC3] 17 UDP User Datagram [RFC768,JBP] 18 MUX Multiplexing [IEN90,JBP] 19 DCN-MEAS DCN Measurement Subsystems [DLM1] 20 HMP Host Monitoring [RFC869,RH6] 21 PRM Packet Radio Measurement [ZSU] 22 XNS-IDP XEROX NS IDP [ETHERNET,XEROX] 23 TRUNK-1 Trunk-1 [BWB6] 24 TRUNK-2 Trunk-2 [BWB6] 25 LEAF-1 Leaf-1 [BWB6] 26 LEAF-2 Leaf-2 [BWB6] 27 RDP Reliable Data Protocol [RFC908,RH6] 28 IRTP Internet Reliable Transaction [RFC938,TXM] 29 ISO-TP4 ISO Transport Protocol Class 4 [RFC905,RC77] 30 NETBLT Bulk Data Transfer Protocol [RFC969,DDC1] 31 MFE-NSP MFE Network Services Protocol [MFENET,BCH2] 32 MERIT-INP MERIT Internodal Protocol [HWB] 33 SEP Sequential Exchange Protocol [JC120] 34 3PC Third Party Connect Protocol [SAF3] 35 IDPR Inter-Domain Policy Routing Protocol [MXS1]Reynolds & Postel [Page 8]
RFC 1700 Assigned Numbers October 1994 36 XTP XTP [GXC] 37 DDP Datagram Delivery Protocol [WXC] 38 IDPR-CMTP IDPR Control Message Transport Proto [MXS1] 39 TP++ TP++ Transport Protocol [DXF] 40 IL IL Transport Protocol [DXP2] 41 SIP Simple Internet Protocol [SXD] 42 SDRP Source Demand Routing Protocol [DXE1] 43 SIP-SR SIP Source Route [SXD] 44 SIP-FRAG SIP Fragment [SXD] 45 IDRP Inter-Domain Routing Protocol [Sue Hares] 46 RSVP Reservation Protocol [Bob Braden] 47 GRE General Routing Encapsulation [Tony Li] 48 MHRP Mobile Host Routing Protocol[David Johnson] 49 BNA BNA [Gary Salamon] 50 SIPP-ESP SIPP Encap Security Payload [Steve Deering] 51 SIPP-AH SIPP Authentication Header [Steve Deering] 52 I-NLSP Integrated Net Layer Security TUBA [GLENN] 53 SWIPE IP with Encryption [JI6] 54 NHRP NBMA Next Hop Resolution Protocol 55-60 Unassigned [JBP] 61 any host internal protocol [JBP] 62 CFTP CFTP [CFTP,HCF2] 63 any local network [JBP] 64 SAT-EXPAK SATNET and Backroom EXPAK [SHB] 65 KRYPTOLAN Kryptolan [PXL1] 66 RVD MIT Remote Virtual Disk Protocol [MBG] 67 IPPC Internet Pluribus Packet Core [SHB] 68 any distributed file system [JBP] 69 SAT-MON SATNET Monitoring [SHB] 70 VISA VISA Protocol [GXT1] 71 IPCV Internet Packet Core Utility [SHB] 72 CPNX Computer Protocol Network Executive [DXM2] 73 CPHB Computer Protocol Heart Beat [DXM2] 74 WSN Wang Span Network [VXD] 75 PVP Packet Video Protocol [SC3] 76 BR-SAT-MON Backroom SATNET Monitoring [SHB] 77 SUN-ND SUN ND PROTOCOL-Temporary [WM3] 78 WB-MON WIDEBAND Monitoring [SHB] 79 WB-EXPAK WIDEBAND EXPAK [SHB] 80 ISO-IP ISO Internet Protocol [MTR] 81 VMTP VMTP [DRC3] 82 SECURE-VMTP SECURE-VMTP [DRC3] 83 VINES VINES [BXH] 84 TTP TTP [JXS] 85 NSFNET-IGP NSFNET-IGP [HWB] 86 DGP Dissimilar Gateway Protocol [DGP,ML109] 87 TCF TCF [GAL5] 88 IGRP IGRP [CISCO,GXS]Reynolds & Postel [Page 9]
RFC 1700 Assigned Numbers October 1994 89 OSPFIGP OSPFIGP [RFC1583,JTM4] 90 Sprite-RPC Sprite RPC Protocol [SPRITE,BXW] 91 LARP Locus Address Resolution Protocol [BXH] 92 MTP Multicast Transport Protocol [SXA] 93 AX.25 AX.25 Frames [BK29] 94 IPIP IP-within-IP Encapsulation Protocol [JI6] 95 MICP Mobile Internetworking Control Pro. [JI6] 96 SCC-SP Semaphore Communications Sec. Pro. [HXH] 97 ETHERIP Ethernet-within-IP Encapsulation [RXH1] 98 ENCAP Encapsulation Header [RFC1241,RXB3] 99 any private encryption scheme [JBP] 100 GMTP GMTP [RXB5]101-254 Unassigned [JBP] 255 Reserved [JBP]REFERENCES[CFTP] Forsdick, H., "CFTP", Network Message, Bolt Beranek and Newman, January 1982.[CISCO] Cisco Systems, "Gateway Server Reference Manual", Manual Revision B, January 10, 1988.[DDN] Feinler, E., Editor, "DDN Protocol Handbook", Network Information Center, SRI International, December 1985.[DGP] M/A-COM Government Systems, "Dissimilar Gateway Protocol Specification, Draft Version", Contract no. CS901145, November 16, 1987.[ETHERNET] "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.[IEN90] Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90, USC/Information Sciences Institute, May 1979.[IEN119] Forgie, J., "ST - A Proposed Internet Stream Protocol", IEN 119, MIT Lincoln Laboratory, September 1979.Reynolds & Postel [Page 10]
RFC 1700 Assigned Numbers October 1994[IEN158] Haverty, J., "XNET Formats for Internet Protocol Version 4", IEN 158, October 1980.[MFENET] Shuttleworth, B., "A Documentary of MFENet, a National Computer Network", UCRL-52317, Lawrence Livermore Labs, Livermore, California, June 1977.[PUP] 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.[SPRITE] Welch, B., "The Sprite Remote Procedure Call System", Technical Report, UCB/Computer Science Dept., 86/302, University of California at Berkeley, June 1986.[RFC741] Cohen, D., "Specifications for the Network Voice Protocol",RFC 741, ISI/RR 7539, USC/Information Sciences Institute, March 1976.[RFC768] Postel, J., "User Datagram Protocol", STD 6,RFC 768, USC/Information Sciences Institute, August 1980.[RFC791] Postel, J., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5,RFC 791, DARPA, September 1981.[RFC792] Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification", STD 5,RFC 792, USC/Information Sciences Institute, September 1981.[RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", STD 7,RFC 793, USC/Information Sciences Institute, September 1981.[RFC823] Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway",RFC 823, BBN, September 1982.[RFC869] Hinden, R., "A Host Monitoring Protocol",RFC 869, Bolt Beranek and Newman, December 1983.[RFC888] Seamonson, L., and E. Rosen, "STUB" Exterior Gateway Protocol",RFC 888, BBN Communications Corporation, January 1984.[RFC905] International Standards Organization, "ISO Transport Protocol Specification - ISO DP 8073",RFC 905, April 1984.Reynolds & Postel [Page 11]
RFC 1700 Assigned Numbers October 1994[RFC908] Velten, D., R. Hinden, and J. Sax, "Reliable Data Protocol",RFC 908, BBN Communications Corporation, July 1984.[RFC938] Miller, T., "Internet Reliable Transaction Protocol",RFC 938, ACC, February 1985.[RFC969] Clark, D., M. Lambert, and L. Zhang, "NETBLT: A Bulk Data Transfer Protocol",RFC 969, MIT Laboratory for Computer Science, December 1985.[RFC1112] Deering, S., "Host Extensions for IP Multicasting", STD 5,RFC 1112, Stanford University, August 1989.[RFC1190] Topolcic, C., Editor, "Experimental Internet Stream Protocol, Version 2 (ST-II)",RFC 1190, CIP Working Group, October 1990.[RFC1241] Woodburn, W., and D. Mills, " A Scheme for an Internet Encapsulation Protocol: Version 1",RFC 1241, SAIC, University of Delaware, July 1991.[RFC1583] Moy, J., "The OSPF Specification",RFC 1583, Proteon, March 1994.PEOPLE[BCH2] Barry Howard <Howard@NMFECC.LLNL.GOV>[BK29] Brian Kantor <brian@UCSD.EDU>[BN7] <mystery contact>[BWB6] Barry Boehm <boehm@ARPA.MIL>[BXH] Brian Horn <---none--->[BXW] Bruce Willins <---none--->[DDC1] David Clark <ddc@LCS.MIT.EDU>[DLM1] David Mills <Mills@HUEY.UDEL.EDU>[DRC3] Dave Cheriton <cheriton@PESCADERO.STANFORD.EDU>[DXE1] Deborah Estrin <estrin@usc.edu>[DXF] Dirk Fromhein <df@watershed.com>Reynolds & Postel [Page 12]
RFC 1700 Assigned Numbers October 1994[DXM2] David Mittnacht <---none--->[DXP2] Dave Presotto <presotto@reseach.att.co[David Johnson] <mystery contact>[GAL5] Guillermo A. Loyola <LOYOLA@IBM.COM>[GLENN] K. Robert Glenn <glenn@osi.ncsl.nist.gov>[GXC] Greg Chesson <Greg@SGI.COM>[GXS] Guenther Schreiner <snmp-admin@ira.uka.de>[GXT1] Gene Tsudik <tsudik@USC.EDU>[HCF2] Harry Forsdick <Forsdick@BBN.COM>[HWB] Hans-Werner Braun <HWB@MCR.UMICH.EDU>[HXH] Howard Hart <hch@hybrid.com>[JBP] Jon Postel <postel@isi.edu>[JC120] <mystery contact>[JFH2] Jack Haverty <jhaverty@ORACLE.COM>[JI6] John Ioannidis <ji@CS.COLUMBIA.EDU>[JTM4] John Moy <jmoy@PROTEON.COM>[JWF] Jim Forgie <FORGIE@XN.LL.MIT.EDU>[JXS] Jim Stevens <Stevens@ISI.EDU>[KATZ] Dave Katz <dkatz@cisco.com>[MB] Mike Brescia <Brescia@CCV.BBN.COM>[MBG] Michael Greenwald <Greenwald@SCRC-STONY-BROOK.SYMBOLICS.COM>[ML109] Mike Little <little@MACOM4.ARPA>[MTR] Marshall T. Rose <mrose@dbc.mtview.ca.us>[MXS1] Martha Steenstrup <MSteenst@BBN.COM>Reynolds & Postel [Page 13]
RFC 1700 Assigned Numbers October 1994[NC3] J. Noel Chiappa <JNC@XX.LCS.MIT.EDU>[PK] Peter Kirstein <Kirstein@NSS.CS.UCL.AC.UK>[PXL1] Paul Liu <---none--->[RH6] Robert Hinden <Hinden@ENG.SUN.COM>[RTB3] Bob Braden <braden@isi.edu>[RC77] <mystery contact>[RWS4] Robert W. Scheifler <RWS@XX.LCS.MIT.EDU>[RXB3] Robert Woodburn <woody@cseic.saic.com>[RXH1] Russ Housley <Russ_Housley.McLean_CSD@xerox.com>[SAF3] Stuart A. Friedberg <stuart@CS.WISC.EDU>[SC3] Steve Casner <casner@isi.edu[SGC] Steve Chipman <Chipman@F.BBN.COM>[SHB] Steven Blumenthal <BLUMENTHAL@VAX.BBN.COM>[Sue Hares] Sue Hares <skh@merit.edu>[SXA] Susie Armstrong <Armstrong.wbst128@XEROX.COM>[SXD] Steve Deering <deering@PARC.XEROX.COM>[Tony Li] Tony Li <tli@cisco.com>[TXM] Trudy Miller <Trudy@ACC.COM>[VXD] Victor Dafoulas <---none--->[WM3] William Melohn <Melohn@SUN.COM>[WXC] Wesley Craig <Wesley.Craig@terminator.cc.umich.edu>[ZSU] Zaw-Sing Su <ZSu@TSCA.ISTC.SRI.>[]Reynolds & Postel [Page 14]
RFC 1700 Assigned Numbers October 1994URL =ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbersReynolds & Postel [Page 15]
RFC 1700 Assigned Numbers October 1994WELL KNOWN PORT NUMBERSThe Well Known Ports are controlled and assigned by the IANA and onmost systems can only be used by system (or root) processes or byprograms executed by privileged users.Ports are used in the TCP [RFC793] to name the ends of logicalconnections which carry long term conversations. For the purpose ofproviding services to unknown callers, a service contact port isdefined. This list specifies the port used by the server process asits contact port. The contact port is sometimes called the"well-known port".To the extent possible, these same port assignments are used with theUDP [RFC768].The assigned ports use a small portion of the possible port numbers.For many years the assigned ports were in the range 0-255. Recently,the range for assigned ports managed by the IANA has been expanded tothe range 0-1023.Port Assignments:Keyword Decimal Description References------- ------- ----------- ---------- 0/tcp Reserved 0/udp Reserved# Jon Postel <postel@isi.edu>tcpmux 1/tcp TCP Port Service Multiplexertcpmux 1/udp TCP Port Service Multiplexer# Mark Lottor <MKL@nisc.sri.com>compressnet 2/tcp Management Utilitycompressnet 2/udp Management Utilitycompressnet 3/tcp Compression Processcompressnet 3/udp Compression Process# Bernie Volz <VOLZ@PROCESS.COM># 4/tcp Unassigned# 4/udp Unassignedrje 5/tcp Remote Job Entryrje 5/udp Remote Job Entry# Jon Postel <postel@isi.edu># 6/tcp Unassigned# 6/udp Unassignedecho 7/tcp Echoecho 7/udp Echo# Jon Postel <postel@isi.edu># 8/tcp UnassignedReynolds & Postel [Page 16]
RFC 1700 Assigned Numbers October 1994# 8/udp Unassigneddiscard 9/tcp Discarddiscard 9/udp Discard# Jon Postel <postel@isi.edu># 10/tcp Unassigned# 10/udp Unassignedsystat 11/tcp Active Userssystat 11/udp Active Users# Jon Postel <postel@isi.edu># 12/tcp Unassigned# 12/udp Unassigneddaytime 13/tcp Daytimedaytime 13/udp Daytime# Jon Postel <postel@isi.edu># 14/tcp Unassigned# 14/udp Unassigned# 15/tcp Unassigned [was netstat]# 15/udp Unassigned# 16/tcp Unassigned# 16/udp Unassignedqotd 17/tcp Quote of the Dayqotd 17/udp Quote of the Day# Jon Postel <postel@isi.edu>msp 18/tcp Message Send Protocolmsp 18/udp Message Send Protocol# Rina Nethaniel <---none--->chargen 19/tcp Character Generatorchargen 19/udp Character Generatorftp-data 20/tcp File Transfer [Default Data]ftp-data 20/udp File Transfer [Default Data]ftp 21/tcp File Transfer [Control]ftp 21/udp File Transfer [Control]# Jon Postel <postel@isi.edu># 22/tcp Unassigned# 22/udp Unassignedtelnet 23/tcp Telnettelnet 23/udp Telnet# Jon Postel <postel@isi.edu> 24/tcp any private mail system 24/udp any private mail system# Rick Adam <rick@UUNET.UU.NET>smtp 25/tcp Simple Mail Transfersmtp 25/udp Simple Mail Transfer# Jon Postel <postel@isi.edu># 26/tcp Unassigned# 26/udp Unassignednsw-fe 27/tcp NSW User System FEnsw-fe 27/udp NSW User System FEReynolds & Postel [Page 17]
RFC 1700 Assigned Numbers October 1994# Robert Thomas <BThomas@F.BBN.COM># 28/tcp Unassigned# 28/udp Unassignedmsg-icp 29/tcp MSG ICPmsg-icp 29/udp MSG ICP# Robert Thomas <BThomas@F.BBN.COM># 30/tcp Unassigned# 30/udp Unassignedmsg-auth 31/tcp MSG Authenticationmsg-auth 31/udp MSG Authentication# Robert Thomas <BThomas@F.BBN.COM># 32/tcp Unassigned# 32/udp Unassigneddsp 33/tcp Display Support Protocoldsp 33/udp Display Support Protocol# Ed Cain <cain@edn-unix.dca.mil># 34/tcp Unassigned# 34/udp Unassigned 35/tcp any private printer server 35/udp any private printer server# Jon Postel <postel@isi.edu># 36/tcp Unassigned# 36/udp Unassignedtime 37/tcp Timetime 37/udp Time# Jon Postel <postel@isi.edu>rap 38/tcp Route Access Protocolrap 38/udp Route Access Protocol# Robert Ullmann <ariel@world.std.com>rlp 39/tcp Resource Location Protocolrlp 39/udp Resource Location Protocol# Mike Accetta <MIKE.ACCETTA@CMU-CS-A.EDU># 40/tcp Unassigned# 40/udp Unassignedgraphics 41/tcp Graphicsgraphics 41/udp Graphicsnameserver 42/tcp Host Name Servernameserver 42/udp Host Name Servernicname 43/tcp Who Isnicname 43/udp Who Ismpm-flags 44/tcp MPM FLAGS Protocolmpm-flags 44/udp MPM FLAGS Protocolmpm 45/tcp Message Processing Module [recv]mpm 45/udp Message Processing Module [recv]mpm-snd 46/tcp MPM [default send]mpm-snd 46/udp MPM [default send]# Jon Postel <postel@isi.edu>ni-ftp 47/tcp NI FTPReynolds & Postel [Page 18]
RFC 1700 Assigned Numbers October 1994ni-ftp 47/udp NI FTP# Steve Kille <S.Kille@isode.com>auditd 48/tcp Digital Audit Daemonauditd 48/udp Digital Audit Daemon# Larry Scott <scott@zk3.dec.com>login 49/tcp Login Host Protocollogin 49/udp Login Host Protocol# Pieter Ditmars <pditmars@BBN.COM>re-mail-ck 50/tcp Remote Mail Checking Protocolre-mail-ck 50/udp Remote Mail Checking Protocol# Steve Dorner <s-dorner@UIUC.EDU>la-maint 51/tcp IMP Logical Address Maintenancela-maint 51/udp IMP Logical Address Maintenance# Andy Malis <malis_a@timeplex.com>xns-time 52/tcp XNS Time Protocolxns-time 52/udp XNS Time Protocol# Susie Armstrong <Armstrong.wbst128@XEROX>domain 53/tcp Domain Name Serverdomain 53/udp Domain Name Server# Paul Mockapetris <PVM@ISI.EDU>xns-ch 54/tcp XNS Clearinghousexns-ch 54/udp XNS Clearinghouse# Susie Armstrong <Armstrong.wbst128@XEROX>isi-gl 55/tcp ISI Graphics Languageisi-gl 55/udp ISI Graphics Languagexns-auth 56/tcp XNS Authenticationxns-auth 56/udp XNS Authentication# Susie Armstrong <Armstrong.wbst128@XEROX> 57/tcp any private terminal access 57/udp any private terminal access# Jon Postel <postel@isi.edu>xns-mail 58/tcp XNS Mailxns-mail 58/udp XNS Mail# Susie Armstrong <Armstrong.wbst128@XEROX> 59/tcp any private file service 59/udp any private file service# Jon Postel <postel@isi.edu> 60/tcp Unassigned 60/udp Unassignedni-mail 61/tcp NI MAILni-mail 61/udp NI MAIL# Steve Kille <S.Kille@isode.com>acas 62/tcp ACA Servicesacas 62/udp ACA Services# E. Wald <ewald@via.enet.dec.com># 63/tcp Unassigned# 63/udp Unassignedcovia 64/tcp Communications Integrator (CI)Reynolds & Postel [Page 19]
RFC 1700 Assigned Numbers October 1994covia 64/udp Communications Integrator (CI)# "Tundra" Tim Daneliuk# <tundraix!tundra@clout.chi.il.us>tacacs-ds 65/tcp TACACS-Database Servicetacacs-ds 65/udp TACACS-Database Service# Kathy Huber <khuber@bbn.com>sql*net 66/tcp Oracle SQL*NETsql*net 66/udp Oracle SQL*NET# Jack Haverty <jhaverty@ORACLE.COM>bootps 67/tcp Bootstrap Protocol Serverbootps 67/udp Bootstrap Protocol Serverbootpc 68/tcp Bootstrap Protocol Clientbootpc 68/udp Bootstrap Protocol Client# Bill Croft <Croft@SUMEX-AIM.STANFORD.EDU>tftp 69/tcp Trivial File Transfertftp 69/udp Trivial File Transfer# David Clark <ddc@LCS.MIT.EDU>gopher 70/tcp Gophergopher 70/udp Gopher# Mark McCahill <mpm@boombox.micro.umn.edu>netrjs-1 71/tcp Remote Job Servicenetrjs-1 71/udp Remote Job Servicenetrjs-2 72/tcp Remote Job Servicenetrjs-2 72/udp Remote Job Servicenetrjs-3 73/tcp Remote Job Servicenetrjs-3 73/udp Remote Job Servicenetrjs-4 74/tcp Remote Job Servicenetrjs-4 74/udp Remote Job Service# Bob Braden <Braden@ISI.EDU> 75/tcp any private dial out service 75/udp any private dial out service# Jon Postel <postel@isi.edu>deos 76/tcp Distributed External Object Storedeos 76/udp Distributed External Object Store# Robert Ullmann <ariel@world.std.com> 77/tcp any private RJE service 77/udp any private RJE service# Jon Postel <postel@isi.edu>vettcp 78/tcp vettcpvettcp 78/udp vettcp# Christopher Leong <leong@kolmod.mlo.dec.com>finger 79/tcp Fingerfinger 79/udp Finger# David Zimmerman <dpz@RUTGERS.EDU>www-http 80/tcp World Wide Web HTTPwww-http 80/udp World Wide Web HTTP# Tim Berners-Lee <timbl@nxoc01.cern.ch>hosts2-ns 81/tcp HOSTS2 Name ServerReynolds & Postel [Page 20]
RFC 1700 Assigned Numbers October 1994hosts2-ns 81/udp HOSTS2 Name Server# Earl Killian <EAK@MORDOR.S1.GOV>xfer 82/tcp XFER Utilityxfer 82/udp XFER Utility# Thomas M. Smith <tmsmith@esc.syr.ge.com>mit-ml-dev 83/tcp MIT ML Devicemit-ml-dev 83/udp MIT ML Device# David Reed <--none--->ctf 84/tcp Common Trace Facilityctf 84/udp Common Trace Facility# Hugh Thomas <thomas@oils.enet.dec.com>mit-ml-dev 85/tcp MIT ML Devicemit-ml-dev 85/udp MIT ML Device# David Reed <--none--->mfcobol 86/tcp Micro Focus Cobolmfcobol 86/udp Micro Focus Cobol# Simon Edwards <--none---> 87/tcp any private terminal link 87/udp any private terminal link# Jon Postel <postel@isi.edu>kerberos 88/tcp Kerberoskerberos 88/udp Kerberos# B. Clifford Neuman <bcn@isi.edu>su-mit-tg 89/tcp SU/MIT Telnet Gatewaysu-mit-tg 89/udp SU/MIT Telnet Gateway# Mark Crispin <MRC@PANDA.COM>dnsix 90/tcp DNSIX Securit Attribute Token Mapdnsix 90/udp DNSIX Securit Attribute Token Map# Charles Watt <watt@sware.com>mit-dov 91/tcp MIT Dover Spoolermit-dov 91/udp MIT Dover Spooler# Eliot Moss <EBM@XX.LCS.MIT.EDU>npp 92/tcp Network Printing Protocolnpp 92/udp Network Printing Protocol# Louis Mamakos <louie@sayshell.umd.edu>dcp 93/tcp Device Control Protocoldcp 93/udp Device Control Protocol# Daniel Tappan <Tappan@BBN.COM>objcall 94/tcp Tivoli Object Dispatcherobjcall 94/udp Tivoli Object Dispatcher# Tom Bereiter <--none--->supdup 95/tcp SUPDUPsupdup 95/udp SUPDUP# Mark Crispin <MRC@PANDA.COM>dixie 96/tcp DIXIE Protocol Specificationdixie 96/udp DIXIE Protocol Specification# Tim Howes <Tim.Howes@terminator.cc.umich.edu>swift-rvf 97/tcp Swift Remote Vitural File ProtocolReynolds & Postel [Page 21]
RFC 1700 Assigned Numbers October 1994swift-rvf 97/udp Swift Remote Vitural File Protocol# Maurice R. Turcotte# <mailrus!uflorida!rm1!dnmrt%rmatl@uunet.UU.NET>tacnews 98/tcp TAC Newstacnews 98/udp TAC News# Jon Postel <postel@isi.edu>metagram 99/tcp Metagram Relaymetagram 99/udp Metagram Relay# Geoff Goodfellow <Geoff@FERNWOOD.MPK.CA.U>newacct 100/tcp [unauthorized use]hostname 101/tcp NIC Host Name Serverhostname 101/udp NIC Host Name Server# Jon Postel <postel@isi.edu>iso-tsap 102/tcp ISO-TSAPiso-tsap 102/udp ISO-TSAP# Marshall Rose <mrose@dbc.mtview.ca.us>gppitnp 103/tcp Genesis Point-to-Point Trans Netgppitnp 103/udp Genesis Point-to-Point Trans Netacr-nema 104/tcp ACR-NEMA Digital Imag. & Comm. 300acr-nema 104/udp ACR-NEMA Digital Imag. & Comm. 300# Patrick McNamee <--none--->csnet-ns 105/tcp Mailbox Name Nameservercsnet-ns 105/udp Mailbox Name Nameserver# Marvin Solomon <solomon@CS.WISC.EDU>3com-tsmux 106/tcp 3COM-TSMUX3com-tsmux 106/udp 3COM-TSMUX# Jeremy Siegel <jzs@NSD.3Com.COM>rtelnet 107/tcp Remote Telnet Servicertelnet 107/udp Remote Telnet Service# Jon Postel <postel@isi.edu>snagas 108/tcp SNA Gateway Access Serversnagas 108/udp SNA Gateway Access Server# Kevin Murphy <murphy@sevens.lkg.dec.com>pop2 109/tcp Post Office Protocol - Version 2pop2 109/udp Post Office Protocol - Version 2# Joyce K. Reynolds <jkrey@isi.edu>pop3 110/tcp Post Office Protocol - Version 3pop3 110/udp Post Office Protocol - Version 3# Marshall Rose <mrose@dbc.mtview.ca.us>sunrpc 111/tcp SUN Remote Procedure Callsunrpc 111/udp SUN Remote Procedure Call# Chuck McManis <cmcmanis@sun.com>mcidas 112/tcp McIDAS Data Transmission Protocolmcidas 112/udp McIDAS Data Transmission Protocol# Glenn Davis <davis@unidata.ucar.edu>auth 113/tcp Authentication Serviceauth 113/udp Authentication Service# Mike St. Johns <stjohns@arpa.mil>Reynolds & Postel [Page 22]
RFC 1700 Assigned Numbers October 1994audionews 114/tcp Audio News Multicastaudionews 114/udp Audio News Multicast# Martin Forssen <maf@dtek.chalmers.se>sftp 115/tcp Simple File Transfer Protocolsftp 115/udp Simple File Transfer Protocol# Mark Lottor <MKL@nisc.sri.com>ansanotify 116/tcp ANSA REX Notifyansanotify 116/udp ANSA REX Notify# Nicola J. Howarth <njh@ansa.co.uk>uucp-path 117/tcp UUCP Path Serviceuucp-path 117/udp UUCP Path Servicesqlserv 118/tcp SQL Servicessqlserv 118/udp SQL Services# Larry Barnes <barnes@broke.enet.dec.com>nntp 119/tcp Network News Transfer Protocolnntp 119/udp Network News Transfer Protocol# Phil Lapsley <phil@UCBARPA.BERKELEY.EDU>cfdptkt 120/tcp CFDPTKTcfdptkt 120/udp CFDPTKT# John Ioannidis <ji@close.cs.columbia.ed>erpc 121/tcp Encore Expedited Remote Pro.Callerpc 121/udp Encore Expedited Remote Pro.Call# Jack O'Neil <---none--->smakynet 122/tcp SMAKYNETsmakynet 122/udp SMAKYNET# Mike O'Dowd <odowd@ltisun8.epfl.ch>ntp 123/tcp Network Time Protocolntp 123/udp Network Time Protocol# Dave Mills <Mills@HUEY.UDEL.EDU>ansatrader 124/tcp ANSA REX Traderansatrader 124/udp ANSA REX Trader# Nicola J. Howarth <njh@ansa.co.uk>locus-map 125/tcp Locus PC-Interface Net Map Serlocus-map 125/udp Locus PC-Interface Net Map Ser# Eric Peterson <lcc.eric@SEAS.UCLA.EDU>unitary 126/tcp Unisys Unitary Loginunitary 126/udp Unisys Unitary Login# <feil@kronos.nisd.cam.unisys.com>locus-con 127/tcp Locus PC-Interface Conn Serverlocus-con 127/udp Locus PC-Interface Conn Server# Eric Peterson <lcc.eric@SEAS.UCLA.EDU>gss-xlicen 128/tcp GSS X License Verificationgss-xlicen 128/udp GSS X License Verification# John Light <johnl@gssc.gss.com>pwdgen 129/tcp Password Generator Protocolpwdgen 129/udp Password Generator Protocol# Frank J. Wacho <WANCHO@WSMR-SIMTEL20.ARMY.MIL>cisco-fna 130/tcp cisco FNATIVEReynolds & Postel [Page 23]
RFC 1700 Assigned Numbers October 1994cisco-fna 130/udp cisco FNATIVEcisco-tna 131/tcp cisco TNATIVEcisco-tna 131/udp cisco TNATIVEcisco-sys 132/tcp cisco SYSMAINTcisco-sys 132/udp cisco SYSMAINTstatsrv 133/tcp Statistics Servicestatsrv 133/udp Statistics Service# Dave Mills <Mills@HUEY.UDEL.EDU>ingres-net 134/tcp INGRES-NET Serviceingres-net 134/udp INGRES-NET Service# Mike Berrow <---none--->loc-srv 135/tcp Location Serviceloc-srv 135/udp Location Service# Joe Pato <apollo!pato@EDDIE.MIT.EDU>profile 136/tcp PROFILE Naming Systemprofile 136/udp PROFILE Naming System# Larry Peterson <llp@ARIZONA.EDU>netbios-ns 137/tcp NETBIOS Name Servicenetbios-ns 137/udp NETBIOS Name Servicenetbios-dgm 138/tcp NETBIOS Datagram Servicenetbios-dgm 138/udp NETBIOS Datagram Servicenetbios-ssn 139/tcp NETBIOS Session Servicenetbios-ssn 139/udp NETBIOS Session Service# Jon Postel <postel@isi.edu>emfis-data 140/tcp EMFIS Data Serviceemfis-data 140/udp EMFIS Data Serviceemfis-cntl 141/tcp EMFIS Control Serviceemfis-cntl 141/udp EMFIS Control Service# Gerd Beling <GBELING@ISI.EDU>bl-idm 142/tcp Britton-Lee IDMbl-idm 142/udp Britton-Lee IDM# Susie Snitzer <---none--->imap2 143/tcp Interim Mail Access Protocol v2imap2 143/udp Interim Mail Access Protocol v2# Mark Crispin <MRC@PANDA.COM>news 144/tcp NewSnews 144/udp NewS# James Gosling <JAG@SUN.COM>uaac 145/tcp UAAC Protocoluaac 145/udp UAAC Protocol# David A. Gomberg <gomberg@GATEWAY.MITRE.ORG>iso-tp0 146/tcp ISO-IP0iso-tp0 146/udp ISO-IP0iso-ip 147/tcp ISO-IPiso-ip 147/udp ISO-IP# Marshall Rose <mrose@dbc.mtview.ca.us>cronus 148/tcp CRONUS-SUPPORTcronus 148/udp CRONUS-SUPPORTReynolds & Postel [Page 24]
RFC 1700 Assigned Numbers October 1994# Jeffrey Buffun <jbuffum@APOLLO.COM>aed-512 149/tcp AED 512 Emulation Serviceaed-512 149/udp AED 512 Emulation Service# Albert G. Broscius <broscius@DSL.CIS.UPENN.EDU>sql-net 150/tcp SQL-NETsql-net 150/udp SQL-NET# Martin Picard <<---none--->hems 151/tcp HEMShems 151/udp HEMS# Christopher Tengi <tengi@Princeton.EDU>bftp 152/tcp Background File Transfer Programbftp 152/udp Background File Transfer Program# Annette DeSchon <DESCHON@ISI.EDU>sgmp 153/tcp SGMPsgmp 153/udp SGMP# Marty Schoffstahl <schoff@NISC.NYSER.NET>netsc-prod 154/tcp NETSCnetsc-prod 154/udp NETSCnetsc-dev 155/tcp NETSCnetsc-dev 155/udp NETSC# Sergio Heker <heker@JVNCC.CSC.ORG>sqlsrv 156/tcp SQL Servicesqlsrv 156/udp SQL Service# Craig Rogers <Rogers@ISI.EDU>knet-cmp 157/tcp KNET/VM Command/Message Protocolknet-cmp 157/udp KNET/VM Command/Message Protocol# Gary S. Malkin <GMALKIN@XYLOGICS.COM>pcmail-srv 158/tcp PCMail Serverpcmail-srv 158/udp PCMail Server# Mark L. Lambert <markl@PTT.LCS.MIT.EDU>nss-routing 159/tcp NSS-Routingnss-routing 159/udp NSS-Routing# Yakov Rekhter <Yakov@IBM.COM>sgmp-traps 160/tcp SGMP-TRAPSsgmp-traps 160/udp SGMP-TRAPS# Marty Schoffstahl <schoff@NISC.NYSER.NET>snmp 161/tcp SNMPsnmp 161/udp SNMPsnmptrap 162/tcp SNMPTRAPsnmptrap 162/udp SNMPTRAP# Marshall Rose <mrose@dbc.mtview.ca.us>cmip-man 163/tcp CMIP/TCP Managercmip-man 163/udp CMIP/TCP Managercmip-agent 164/tcp CMIP/TCP Agentsmip-agent 164/udp CMIP/TCP Agent# Amatzia Ben-Artzi <---none--->xns-courier 165/tcp Xeroxxns-courier 165/udp XeroxReynolds & Postel [Page 25]
RFC 1700 Assigned Numbers October 1994# Susie Armstrong <Armstrong.wbst128@XEROX.COM>s-net 166/tcp Sirius Systemss-net 166/udp Sirius Systems# Brian Lloyd <---none--->namp 167/tcp NAMPnamp 167/udp NAMP# Marty Schoffstahl <schoff@NISC.NYSER.NET>rsvd 168/tcp RSVDrsvd 168/udp RSVD# Neil Todd <mcvax!ist.co.uk!neil@UUNET.UU.NET>send 169/tcp SENDsend 169/udp SEND# William D. Wisner <wisner@HAYES.FAI.ALASKA.EDU>print-srv 170/tcp Network PostScriptprint-srv 170/udp Network PostScript# Brian Reid <reid@DECWRL.DEC.COM>multiplex 171/tcp Network Innovations Multiplexmultiplex 171/udp Network Innovations Multiplexcl/1 172/tcp Network Innovations CL/1cl/1 172/udp Network Innovations CL/1# Kevin DeVault <<---none--->xyplex-mux 173/tcp Xyplexxyplex-mux 173/udp Xyplex# Bob Stewart <STEWART@XYPLEX.COM>mailq 174/tcp MAILQmailq 174/udp MAILQ# Rayan Zachariassen <rayan@AI.TORONTO.EDU>vmnet 175/tcp VMNETvmnet 175/udp VMNET# Christopher Tengi <tengi@Princeton.EDU>genrad-mux 176/tcp GENRAD-MUXgenrad-mux 176/udp GENRAD-MUX# Ron Thornton <thornton@qm7501.genrad.com>xdmcp 177/tcp X Display Manager Control Protocolxdmcp 177/udp X Display Manager Control Protocol# Robert W. Scheifler <RWS@XX.LCS.MIT.EDU>nextstep 178/tcp NextStep Window ServerNextStep 178/udp NextStep Window Server# Leo Hourvitz <leo@NEXT.COM>bgp 179/tcp Border Gateway Protocolbgp 179/udp Border Gateway Protocol# Kirk Lougheed <LOUGHEED@MATHOM.CISCO.COM>ris 180/tcp Intergraphris 180/udp Intergraph# Dave Buehmann <ingr!daveb@UUNET.UU.NET>unify 181/tcp Unifyunify 181/udp Unify# Vinod Singh <--none--->Reynolds & Postel [Page 26]
RFC 1700 Assigned Numbers October 1994audit 182/tcp Unisys Audit SITPaudit 182/udp Unisys Audit SITP# Gil Greenbaum <gcole@nisd.cam.unisys.com>ocbinder 183/tcp OCBinderocbinder 183/udp OCBinderocserver 184/tcp OCServerocserver 184/udp OCServer# Jerrilynn Okamura <--none--->remote-kis 185/tcp Remote-KISremote-kis 185/udp Remote-KISkis 186/tcp KIS Protocolkis 186/udp KIS Protocol# Ralph Droms <rdroms@NRI.RESTON.VA.US>aci 187/tcp Application Communication Interfaceaci 187/udp Application Communication Interface# Rick Carlos <rick.ticipa.csc.ti.com>mumps 188/tcp Plus Five's MUMPSmumps 188/udp Plus Five's MUMPS# Hokey Stenn <hokey@PLUS5.COM>qft 189/tcp Queued File Transportqft 189/udp Queued File Transport# Wayne Schroeder <schroeder@SDS.SDSC.EDU>gacp 190/tcp Gateway Access Control Protocolcacp 190/udp Gateway Access Control Protocol# C. Philip Wood <cpw@LANL.GOV>prospero 191/tcp Prospero Directory Serviceprospero 191/udp Prospero Directory Service# B. Clifford Neuman <bcn@isi.edu>osu-nms 192/tcp OSU Network Monitoring Systemosu-nms 192/udp OSU Network Monitoring System# Doug Karl <KARL-D@OSU-20.IRCC.OHIO-STATE.EDU>srmp 193/tcp Spider Remote Monitoring Protocolsrmp 193/udp Spider Remote Monitoring Protocol# Ted J. Socolofsky <Teds@SPIDER.CO.UK>irc 194/tcp Internet Relay Chat Protocolirc 194/udp Internet Relay Chat Protocol# Jarkko Oikarinen <jto@TOLSUN.OULU.FI>dn6-nlm-aud 195/tcp DNSIX Network Level Module Auditdn6-nlm-aud 195/udp DNSIX Network Level Module Auditdn6-smm-red 196/tcp DNSIX Session Mgt Module Audit Redirdn6-smm-red 196/udp DNSIX Session Mgt Module Audit Redir# Lawrence Lebahn <DIA3@PAXRV-NES.NAVY.MIL>dls 197/tcp Directory Location Servicedls 197/udp Directory Location Servicedls-mon 198/tcp Directory Location Service Monitordls-mon 198/udp Directory Location Service Monitor# Scott Bellew <smb@cs.purdue.edu>smux 199/tcp SMUXReynolds & Postel [Page 27]
RFC 1700 Assigned Numbers October 1994smux 199/udp SMUX# Marshall Rose <mrose@dbc.mtview.ca.us>src 200/tcp IBM System Resource Controllersrc 200/udp IBM System Resource Controller# Gerald McBrearty <---none--->at-rtmp 201/tcp AppleTalk Routing Maintenanceat-rtmp 201/udp AppleTalk Routing Maintenanceat-nbp 202/tcp AppleTalk Name Bindingat-nbp 202/udp AppleTalk Name Bindingat-3 203/tcp AppleTalk Unusedat-3 203/udp AppleTalk Unusedat-echo 204/tcp AppleTalk Echoat-echo 204/udp AppleTalk Echoat-5 205/tcp AppleTalk Unusedat-5 205/udp AppleTalk Unusedat-zis 206/tcp AppleTalk Zone Informationat-zis 206/udp AppleTalk Zone Informationat-7 207/tcp AppleTalk Unusedat-7 207/udp AppleTalk Unusedat-8 208/tcp AppleTalk Unusedat-8 208/udp AppleTalk Unused# Rob Chandhok <chandhok@gnome.cs.cmu.edu>tam 209/tcp Trivial Authenticated Mail Protocoltam 209/udp Trivial Authenticated Mail Protocol# Dan Bernstein <brnstnd@stealth.acf.nyu.edu>z39.50 210/tcp ANSI Z39.50z39.50 210/udp ANSI Z39.50# Mark Needleman# <mhnur%uccmvsa.bitnet@cornell.cit.cornell.edu>914c/g 211/tcp Texas Instruments 914C/G Terminal914c/g 211/udp Texas Instruments 914C/G Terminal# Bill Harrell <---none--->anet 212/tcp ATEXSSTRanet 212/udp ATEXSSTR# Jim Taylor <taylor@heart.epps.kodak.com>ipx 213/tcp IPXipx 213/udp IPX# Don Provan <donp@xlnvax.novell.com>vmpwscs 214/tcp VM PWSCSvmpwscs 214/udp VM PWSCS# Dan Shia <dset!shia@uunet.UU.NET>softpc 215/tcp Insignia Solutionssoftpc 215/udp Insignia Solutions# Martyn Thomas <---none--->atls 216/tcp Access Technology License Serveratls 216/udp Access Technology License Server# Larry DeLuca <henrik@EDDIE.MIT.EDU>dbase 217/tcp dBASE UnixReynolds & Postel [Page 28]
RFC 1700 Assigned Numbers October 1994dbase 217/udp dBASE Unix# Don Gibson# <sequent!aero!twinsun!ashtate.A-T.COM!dong@uunet.UU.NET>mpp 218/tcp Netix Message Posting Protocolmpp 218/udp Netix Message Posting Protocol# Shannon Yeh <yeh@netix.com>uarps 219/tcp Unisys ARPsuarps 219/udp Unisys ARPs# Ashok Marwaha <---none--->imap3 220/tcp Interactive Mail Access Protocol v3imap3 220/udp Interactive Mail Access Protocol v3# James Rice <RICE@SUMEX-AIM.STANFORD.EDU>fln-spx 221/tcp Berkeley rlogind with SPX authfln-spx 221/udp Berkeley rlogind with SPX authrsh-spx 222/tcp Berkeley rshd with SPX authrsh-spx 222/udp Berkeley rshd with SPX authcdc 223/tcp Certificate Distribution Centercdc 223/udp Certificate Distribution Center# Kannan Alagappan <kannan@sejour.enet.dec.com># 224-241 Reserved# Jon Postel <postel@isi.edu># 242/tcp Unassigned# 242/udp Unassignedsur-meas 243/tcp Survey Measurementsur-meas 243/udp Survey Measurement# Dave Clark <ddc@LCS.MIT.EDU># 244/tcp Unassigned# 244/udp Unassignedlink 245/tcp LINKlink 245/udp LINKdsp3270 246/tcp Display Systems Protocoldsp3270 246/udp Display Systems Protocol# Weldon J. Showalter <Gamma@MINTAKA.DCA.MIL># 247-255 Reserved# Jon Postel <postel@isi.edu># 256-343 Unassignedpdap 344/tcp Prospero Data Access Protocolpdap 344/udp Prospero Data Access Protocol# B. Clifford Neuman <bcn@isi.edu>pawserv 345/tcp Perf Analysis Workbenchpawserv 345/udp Perf Analysis Workbenchzserv 346/tcp Zebra serverzserv 346/udp Zebra serverfatserv 347/tcp Fatmen Serverfatserv 347/udp Fatmen Servercsi-sgwp 348/tcp Cabletron Management Protocolcsi-sgwp 348/udp Cabletron Management Protocol# 349-370 UnassignedReynolds & Postel [Page 29]
RFC 1700 Assigned Numbers October 1994clearcase 371/tcp Clearcaseclearcase 371/udp Clearcase# Dave LeBlang <leglang@atria.com>ulistserv 372/tcp Unix Listservulistserv 372/udp Unix Listserv# Anastasios Kotsikonas <tasos@cs.bu.edu>legent-1 373/tcp Legent Corporationlegent-1 373/udp Legent Corporationlegent-2 374/tcp Legent Corporationlegent-2 374/udp Legent Corporation# Keith Boyce <---none--->hassle 375/tcp Hasslehassle 375/udp Hassle# Reinhard Doelz <doelz@comp.bioz.unibas.ch>nip 376/tcp Amiga Envoy Network Inquiry Protonip 376/udp Amiga Envoy Network Inquiry Proto# Kenneth Dyke <kcd@cbmvax.cbm.commodore.com>tnETOS 377/tcp NEC CorporationtnETOS 377/udp NEC CorporationdsETOS 378/tcp NEC CorporationdsETOS 378/udp NEC Corporation# Tomoo Fujita <tf@arc.bs1.fc.nec.co.jp>is99c 379/tcp TIA/EIA/IS-99 modem clientis99c 379/udp TIA/EIA/IS-99 modem clientis99s 380/tcp TIA/EIA/IS-99 modem serveris99s 380/udp TIA/EIA/IS-99 modem server# Frank Quick <fquick@qualcomm.com>hp-collector 381/tcp hp performance data collectorhp-collector 381/udp hp performance data collectorhp-managed-node 382/tcp hp performance data managed nodehp-managed-node 382/udp hp performance data managed nodehp-alarm-mgr 383/tcp hp performance data alarm managerhp-alarm-mgr 383/udp hp performance data alarm manager# Frank Blakely <frankb@hpptc16.rose.hp.com>arns 384/tcp A Remote Network Server Systemarns 384/udp A Remote Network Server System# David Hornsby <djh@munnari.OZ.AU>ibm-app 385/tcp IBM Applicationibm-app 385/tcp IBM Application# Lisa Tomita <---none--->asa 386/tcp ASA Message Router Object Def.asa 386/udp ASA Message Router Object Def.# Steve Laitinen <laitinen@brutus.aa.ab.com>aurp 387/tcp Appletalk Update-Based Routing Pro.aurp 387/udp Appletalk Update-Based Routing Pro.# Chris Ranch <cranch@novell.com>unidata-ldm 388/tcp Unidata LDM Version 4unidata-ldm 388/udp Unidata LDM Version 4Reynolds & Postel [Page 30]
RFC 1700 Assigned Numbers October 1994# Glenn Davis <davis@unidata.ucar.edu>ldap 389/tcp Lightweight Directory Access Protocolldap 389/udp Lightweight Directory Access Protocol# Tim Howes <Tim.Howes@terminator.cc.umich.edu>uis 390/tcp UISuis 390/udp UIS# Ed Barron <---none--->synotics-relay 391/tcp SynOptics SNMP Relay Portsynotics-relay 391/udp SynOptics SNMP Relay Portsynotics-broker 392/tcp SynOptics Port Broker Portsynotics-broker 392/udp SynOptics Port Broker Port# Illan Raab <iraab@synoptics.com>dis 393/tcp Data Interpretation Systemdis 393/udp Data Interpretation System# Paul Stevens <pstevens@chinacat.Metaphor.COM>embl-ndt 394/tcp EMBL Nucleic Data Transferembl-ndt 394/udp EMBL Nucleic Data Transfer# Peter Gad <peter@bmc.uu.se>netcp 395/tcp NETscout Control Protocolnetcp 395/udp NETscout Control Protocol# Anil Singhal <---none--->netware-ip 396/tcp Novell Netware over IPnetware-ip 396/udp Novell Netware over IPmptn 397/tcp Multi Protocol Trans. Net.mptn 397/udp Multi Protocol Trans. Net.# Soumitra Sarkar <sarkar@vnet.ibm.com>kryptolan 398/tcp Kryptolankryptolan 398/udp Kryptolan# Peter de Laval <pdl@sectra.se># 399/tcp Unassigned# 399/udp Unassignedwork-sol 400/tcp Workstation Solutionswork-sol 400/udp Workstation Solutions# Jim Ward <jimw@worksta.com>ups 401/tcp Uninterruptible Power Supplyups 401/udp Uninterruptible Power Supply# Guenther Seybold <gs@hrz.th-darmstadt.de>genie 402/tcp Genie Protocolgenie 402/udp Genie Protocol# Mark Hankin <---none--->decap 403/tcp decapdecap 403/udp decapnced 404/tcp ncednced 404/udp ncedncld 405/tcp ncldncld 405/udp ncld# Richard Jones <---none--->imsp 406/tcp Interactive Mail Support ProtocolReynolds & Postel [Page 31]
RFC 1700 Assigned Numbers October 1994imsp 406/udp Interactive Mail Support Protocol# John Myers <jgm+@cmu.edu>timbuktu 407/tcp Timbuktutimbuktu 407/udp Timbuktu# Marc Epard <marc@waygate.farallon.com>prm-sm 408/tcp Prospero Resource Manager Sys. Man.prm-sm 408/udp Prospero Resource Manager Sys. Man.prm-nm 409/tcp Prospero Resource Manager Node Man.prm-nm 409/udp Prospero Resource Manager Node Man.# B. Clifford Neuman <bcn@isi.edu>decladebug 410/tcp DECLadebug Remote Debug Protocoldecladebug 410/udp DECLadebug Remote Debug Protocol# Anthony Berent <berent@rdgeng.enet.dec.com>rmt 411/tcp Remote MT Protocolrmt 411/udp Remote MT Protocol# Peter Eriksson <pen@lysator.liu.se>synoptics-trap 412/tcp Trap Convention Portsynoptics-trap 412/udp Trap Convention Port# Illan Raab <iraab@synoptics.com>smsp 413/tcp SMSPsmsp 413/udp SMSPinfoseek 414/tcp InfoSeekinfoseek 414/udp InfoSeek# Steve Kirsch <stk@frame.com>bnet 415/tcp BNetbnet 415/udp BNet# Jim Mertz <JMertz+RV09@rvdc.unisys.com>silverplatter 416/tcp Silverplattersilverplatter 416/udp Silverplatter# Peter Ciuffetti <petec@silverplatter.com>onmux 417/tcp Onmuxonmux 417/udp Onmux# Stephen Hanna <hanna@world.std.com>hyper-g 418/tcp Hyper-Ghyper-g 418/udp Hyper-G# Frank Kappe <fkappe@iicm.tu-graz.ac.at>ariel1 419/tcp Arielariel1 419/udp Ariel# Jonathan Lavigne <BL.JPL@RLG.Stanford.EDU>smpte 420/tcp SMPTEsmpte 420/udp SMPTE# Si Becker <71362.22@CompuServe.COM>ariel2 421/tcp Arielariel2 421/udp Arielariel3 422/tcp Arielariel3 422/udp Ariel# Jonathan Lavigne <BL.JPL@RLG.Stanford.EDU>opc-job-start 423/tcp IBM Operations Planning and Control StartReynolds & Postel [Page 32]
RFC 1700 Assigned Numbers October 1994opc-job-start 423/udp IBM Operations Planning and Control Startopc-job-track 424/tcp IBM Operations Planning and Control Trackopc-job-track 424/udp IBM Operations Planning and Control Track# Conny Larsson <cocke@VNET.IBM.COM>icad-el 425/tcp ICADicad-el 425/udp ICAD# Larry Stone <lcs@icad.com>smartsdp 426/tcp smartsdpsmartsdp 426/udp smartsdp# Alexander Dupuy <dupuy@smarts.com>svrloc 427/tcp Server Locationsvrloc 427/udp Server Location# <veizades@ftp.com>ocs_cmu 428/tcp OCS_CMUocs_cmu 428/udp OCS_CMUocs_amu 429/tcp OCS_AMUocs_amu 429/udp OCS_AMU# Florence Wyman <wyman@peabody.plk.af.mil>utmpsd 430/tcp UTMPSDutmpsd 430/udp UTMPSDutmpcd 431/tcp UTMPCDutmpcd 431/udp UTMPCDiasd 432/tcp IASDiasd 432/udp IASD# Nir Baroz <nbaroz@encore.com>nnsp 433/tcp NNSPnnsp 433/udp NNSP# Rob Robertson <rob@gangrene.berkeley.edu>mobileip-agent 434/tcp MobileIP-Agentmobileip-agent 434/udp MobileIP-Agentmobilip-mn 435/tcp MobilIP-MNmobilip-mn 435/udp MobilIP-MN# Kannan Alagappan <kannan@sejour.lkg.dec.com>dna-cml 436/tcp DNA-CMLdna-cml 436/udp DNA-CML# Dan Flowers <flowers@smaug.lkg.dec.com>comscm 437/tcp comscmcomscm 437/udp comscm# Jim Teague <teague@zso.dec.com>dsfgw 438/tcp dsfgwdsfgw 438/udp dsfgw# Andy McKeen <mckeen@osf.org>dasp 439/tcp dasp Thomas Obermairdasp 439/udp dasp tommy@inlab.m.eunet.de# Thomas Obermair <tommy@inlab.m.eunet.de>sgcp 440/tcp sgcpsgcp 440/udp sgcp# Marshall Rose <mrose@dbc.mtview.ca.us>Reynolds & Postel [Page 33]
RFC 1700 Assigned Numbers October 1994decvms-sysmgt 441/tcp decvms-sysmgtdecvms-sysmgt 441/udp decvms-sysmgt# Lee Barton <barton@star.enet.dec.com>cvc_hostd 442/tcp cvc_hostdcvc_hostd 442/udp cvc_hostd# Bill Davidson <billd@equalizer.cray.com>https 443/tcp https MComhttps 443/udp https MCom# Kipp E.B. Hickman <kipp@mcom.com>snpp 444/tcp Simple Network Paging Protocolsnpp 444/udp Simple Network Paging Protocol# [RFC1568]microsoft-ds 445/tcp Microsoft-DSmicrosoft-ds 445/udp Microsoft-DS# Arnold Miller <arnoldm@microsoft.com>ddm-rdb 446/tcp DDM-RDBddm-rdb 446/udp DDM-RDBddm-dfm 447/tcp DDM-RFMddm-dfm 447/udp DDM-RFMddm-byte 448/tcp DDM-BYTEddm-byte 448/udp DDM-BYTE# Jan David Fisher <jdfisher@VNET.IBM.COM>as-servermap 449/tcp AS Server Mapperas-servermap 449/udp AS Server Mapper# Barbara Foss <BGFOSS@rchvmv.vnet.ibm.com>tserver 450/tcp TServertserver 450/udp TServer# Harvey S. Schultz <hss@mtgzfs3.mt.att.com># 451-511 Unassignedexec 512/tcp remote process execution;# authentication performed using# passwords and UNIX loppgin namesbiff 512/udp used by mail system to notify users# of new mail received; currently# receives messages only from# processes on the same machinelogin 513/tcp remote login a la telnet;# automatic authentication performed# based on priviledged port numbers# and distributed data bases which# identify "authentication domains"who 513/udp maintains data bases showing who's# logged in to machines on a local# net and the load average of the# machinecmd 514/tcp like exec, but automatic# authentication is performed as for# login serverReynolds & Postel [Page 34]
RFC 1700 Assigned Numbers October 1994syslog 514/udpprinter 515/tcp spoolerprinter 515/udp spooler# 516/tcp Unassigned# 516/udp Unassignedtalk 517/tcp 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)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)ntalk 518/tcpntalk 518/udputime 519/tcp unixtimeutime 519/udp unixtimeefs 520/tcp extended file name serverrouter 520/udp local routing process (on site);# uses variant of Xerox NS routing# information protocol# 521-524 Unassignedtimed 525/tcp timeservertimed 525/udp timeservertempo 526/tcp newdatetempo 526/udp newdate# 527-529 Unassignedcourier 530/tcp rpccourier 530/udp rpcconference 531/tcp chatconference 531/udp chatnetnews 532/tcp readnewsnetnews 532/udp readnewsnetwall 533/tcp for emergency broadcastsnetwall 533/udp for emergency broadcasts# 534-538 Unassignedapertus-ldp 539/tcp Apertus Technologies Load Determinationapertus-ldp 539/udp Apertus Technologies Load Determinationuucp 540/tcp uucpduucp 540/udp uucpduucp-rlogin 541/tcp uucp-rlogin Stuart Lynneuucp-rlogin 541/udp uucp-rlogin sl@wimsey.com# 542/tcp Unassigned# 542/udp Unassignedklogin 543/tcpklogin 543/udpReynolds & Postel [Page 35]
RFC 1700 Assigned Numbers October 1994kshell 544/tcp krcmdkshell 544/udp krcmd# 545-549 Unassignednew-rwho 550/tcp new-whonew-rwho 550/udp new-who# 551-555 Unassigneddsf 555/tcpdsf 555/udpremotefs 556/tcp rfs serverremotefs 556/udp rfs server# 557-559 Unassignedrmonitor 560/tcp rmonitordrmonitor 560/udp rmonitordmonitor 561/tcpmonitor 561/udpchshell 562/tcp chcmdchshell 562/udp chcmd# 563/tcp Unassigned# 563/udp Unassigned9pfs 564/tcp plan 9 file service9pfs 564/udp plan 9 file servicewhoami 565/tcp whoamiwhoami 565/udp whoami# 566-569 Unassignedmeter 570/tcp demonmeter 570/udp demonmeter 571/tcp udemonmeter 571/udp udemon# 572-599 Unassignedipcserver 600/tcp Sun IPC serveripcserver 600/udp Sun IPC servernqs 607/tcp nqsnqs 607/udp nqsurm 606/tcp Cray Unified Resource Managerurm 606/udp Cray Unified Resource Manager# Bill Schiefelbein <schief@aspen.cray.com>sift-uft 608/tcp Sender-Initiated/Unsolicited File Transfersift-uft 608/udp Sender-Initiated/Unsolicited File Transfer# Rick Troth <troth@rice.edu>npmp-trap 609/tcp npmp-trapnpmp-trap 609/udp npmp-trapnpmp-local 610/tcp npmp-localnpmp-local 610/udp npmp-localnpmp-gui 611/tcp npmp-guinpmp-gui 611/udp npmp-gui# John Barnes <jbarnes@crl.com>ginad 634/tcp ginadginad 634/udp ginadReynolds & Postel [Page 36]
RFC 1700 Assigned Numbers October 1994# Mark Crother <mark@eis.calstate.edu>mdqs 666/tcpmdqs 666/udpdoom 666/tcp doom Id Softwaredoom 666/tcp doom Id Software# <ddt@idcube.idsoftware.com>elcsd 704/tcp errlog copy/server daemonelcsd 704/udp errlog copy/server daemonentrustmanager 709/tcp EntrustManagerentrustmanager 709/udp EntrustManager# Peter Whittaker <pww@bnr.ca>netviewdm1 729/tcp IBM NetView DM/6000 Server/Clientnetviewdm1 729/udp IBM NetView DM/6000 Server/Clientnetviewdm2 730/tcp IBM NetView DM/6000 send/tcpnetviewdm2 730/udp IBM NetView DM/6000 send/tcpnetviewdm3 731/tcp IBM NetView DM/6000 receive/tcpnetviewdm3 731/udp IBM NetView DM/6000 receive/tcp# Philippe Binet (phbinet@vnet.IBM.COM)netgw 741/tcp netGWnetgw 741/udp netGWnetrcs 742/tcp Network based Rev. Cont. Sys.netrcs 742/udp Network based Rev. Cont. Sys.# Gordon C. Galligher <gorpong@ping.chi.il.us>flexlm 744/tcp Flexible License Managerflexlm 744/udp Flexible License Manager# Matt Christiano# <globes@matt@oliveb.atc.olivetti.com>fujitsu-dev 747/tcp Fujitsu Device Controlfujitsu-dev 747/udp Fujitsu Device Controlris-cm 748/tcp Russell Info Sci Calendar Managerris-cm 748/udp Russell Info Sci Calendar Managerkerberos-adm 749/tcp kerberos administrationkerberos-adm 749/udp kerberos administrationrfile 750/tcploadav 750/udppump 751/tcppump 751/udpqrh 752/tcpqrh 752/udprrh 753/tcprrh 753/udptell 754/tcp sendtell 754/udp sendnlogin 758/tcpnlogin 758/udpcon 759/tcpcon 759/udpReynolds & Postel [Page 37]
RFC 1700 Assigned Numbers October 1994ns 760/tcpns 760/udprxe 761/tcprxe 761/udpquotad 762/tcpquotad 762/udpcycleserv 763/tcpcycleserv 763/udpomserv 764/tcpomserv 764/udpwebster 765/tcpwebster 765/udpphonebook 767/tcp phonephonebook 767/udp phonevid 769/tcpvid 769/udpcadlock 770/tcpcadlock 770/udprtip 771/tcprtip 771/udpcycleserv2 772/tcpcycleserv2 772/udpsubmit 773/tcpnotify 773/udprpasswd 774/tcpacmaint_dbd 774/udpentomb 775/tcpacmaint_transd 775/udpwpages 776/tcpwpages 776/udpwpgs 780/tcpwpgs 780/udpconcert 786/tcp Concertconcert 786/udp Concert# Josyula R. Rao <jrrao@watson.ibm.com>mdbs_daemon 800/tcpmdbs_daemon 800/udpdevice 801/tcpdevice 801/udpxtreelic 996/tcp Central Point Softwarextreelic 996/udp Central Point Software# Dale Cabell <dacabell@smtp.xtree.com>maitrd 997/tcpmaitrd 997/udpbusboy 998/tcppuparp 998/udpgarcon 999/tcpapplix 999/udp Applix acReynolds & Postel [Page 38]
RFC 1700 Assigned Numbers October 1994puprouter 999/tcppuprouter 999/udpcadlock 1000/tcpock 1000/udp 1023/tcp Reserved 1024/udp Reserved# IANA <iana@isi.edu>REGISTERED PORT NUMBERSThe Registered Ports are not controlled by the IANA and on mostsystems can be used by ordinary user processes or programs executed byordinary users.Ports are used in the TCP [RFC793] to name the ends of logicalconnections which carry long term conversations. For the purpose ofproviding services to unknown callers, a service contact port isdefined. This list specifies the port used by the server process asits contact port. While the IANA can not control uses of these portsit does register or list uses of these ports as a convienence to thecommunity.To the extent possible, these same port assignments are used with theUDP [RFC768].The Registered Ports are in the range 1024-65535.Port Assignments:Keyword Decimal Description References------- ------- ----------- ---------- 1024/tcp Reserved 1024/udp Reserved# IANA <iana@isi.edu>blackjack 1025/tcp network blackjackblackjack 1025/udp network blackjackiad1 1030/tcp BBN IADiad1 1030/udp BBN IADiad2 1031/tcp BBN IADiad2 1031/udp BBN IADiad3 1032/tcp BBN IADiad3 1032/udp BBN IAD# Andy Malis <malis_a@timeplex.com>instl_boots 1067/tcp Installation Bootstrap Proto. Serv.instl_boots 1067/udp Installation Bootstrap Proto. Serv.instl_bootc 1068/tcp Installation Bootstrap Proto. Cli.Reynolds & Postel [Page 39]
RFC 1700 Assigned Numbers October 1994instl_bootc 1068/udp Installation Bootstrap Proto. Cli.# David Arko <<darko@hpfcrn.fc.hp.com>socks 1080/tcp Sockssocks 1080/udp Socks# Ying-Da Lee <ylee@syl.dl.nec.comansoft-lm-1 1083/tcp Anasoft License Manageransoft-lm-1 1083/udp Anasoft License Manageransoft-lm-2 1084/tcp Anasoft License Manageransoft-lm-2 1084/udp Anasoft License Managernfa 1155/tcp Network File Accessnfa 1155/udp Network File Access# James Powell <james@mailhost.unidata.com>nerv 1222/tcp SNI R&D networknerv 1222/udp SNI R&D network# Martin Freiss <freiss.pad@sni.de>hermes 1248/tcphermes 1248/udpalta-ana-lm 1346/tcp Alta Analytics License Manageralta-ana-lm 1346/udp Alta Analytics License Managerbbn-mmc 1347/tcp multi media conferencingbbn-mmc 1347/udp multi media conferencingbbn-mmx 1348/tcp multi media conferencingbbn-mmx 1348/udp multi media conferencingsbook 1349/tcp Registration Network Protocolsbook 1349/udp Registration Network Protocoleditbench 1350/tcp Registration Network Protocoleditbench 1350/udp Registration Network Protocol# Simson L. Garfinkel <simsong@next.cambridge.ma.us>equationbuilder 1351/tcp Digital Tool Works (MIT)equationbuilder 1351/udp Digital Tool Works (MIT)# Terrence J. Talbot <lexcube!tjt@bu.edu>lotusnote 1352/tcp Lotus Notelotusnote 1352/udp Lotus Note# Greg Pflaum <iris.com!Greg_Pflaum@uunet.uu.net>relief 1353/tcp Relief Consultingrelief 1353/udp Relief Consulting# John Feiler <relief!jjfeiler@uu2.psi.com>rightbrain 1354/tcp RightBrain Softwarerightbrain 1354/udp RightBrain Software# Glenn Reid <glann@rightbrain.com>intuitive edge 1355/tcp Intuitive Edgeintuitive edge 1355/udp Intuitive Edge# Montgomery Zukowski# <monty@nextnorth.acs.ohio-state.edu>cuillamartin 1356/tcp CuillaMartin Companycuillamartin 1356/udp CuillaMartin Companypegboard 1357/tcp Electronic PegBoardpegboard 1357/udp Electronic PegBoardReynolds & Postel [Page 40]
RFC 1700 Assigned Numbers October 1994# Chris Cuilla# <balr!vpnet!cuilla!chris@clout.chi.il.us>connlcli 1358/tcp CONNLCLIconnlcli 1358/udp CONNLCLIftsrv 1359/tcp FTSRVftsrv 1359/udp FTSRV# Ines Homem de Melo <sidinf@brfapesp.bitnet>mimer 1360/tcp MIMERmimer 1360/udp MIMER# Per Schroeder <Per.Schroder@mimer.se>linx 1361/tcp LinXlinx 1361/udp LinX# Steffen Schilke <---none--->timeflies 1362/tcp TimeFliestimeflies 1362/udp TimeFlies# Doug Kent <mouthers@slugg@nwnexus.wa.com>ndm-requester 1363/tcp Network DataMover Requesterndm-requester 1363/udp Network DataMover Requesterndm-server 1364/tcp Network DataMover Serverndm-server 1364/udp Network DataMover Server# Toshio Watanabe# <watanabe@godzilla.rsc.spdd.ricoh.co.j>adapt-sna 1365/tcp Network Software Associatesadapt-sna 1365/udp Network Software Associates# Jeffery Chiao <714-768-401>netware-csp 1366/tcp Novell NetWare Comm Service Platformnetware-csp 1366/udp Novell NetWare Comm Service Platform# Laurie Lindsey <llindsey@novell.com>dcs 1367/tcp DCSdcs 1367/udp DCS# Stefan Siebert <ssiebert@dcs.de>screencast 1368/tcp ScreenCastscreencast 1368/udp ScreenCast# Bill Tschumy <other!bill@uunet.UU.NET>gv-us 1369/tcp GlobalView to Unix Shellgv-us 1369/udp GlobalView to Unix Shellus-gv 1370/tcp Unix Shell to GlobalViewus-gv 1370/udp Unix Shell to GlobalView# Makoto Mita <mita@ssdev.ksp.fujixerox.co.jp>fc-cli 1371/tcp Fujitsu Config Protocolfc-cli 1371/udp Fujitsu Config Protocolfc-ser 1372/tcp Fujitsu Config Protocolfc-ser 1372/udp Fujitsu Config Protocol# Ryuichi Horie <horie@spad.sysrap.cs.fujitsu.co.jp>chromagrafx 1373/tcp Chromagrafxchromagrafx 1373/udp Chromagrafx# Mike Barthelemy <msb@chromagrafx.com>molly 1374/tcp EPI Software SystemsReynolds & Postel [Page 41]
RFC 1700 Assigned Numbers October 1994molly 1374/udp EPI Software Systems# Jim Vlcek <vlcek@epimbe.com>bytex 1375/tcp Bytexbytex 1375/udp Bytex# Mary Ann Burt <bytex!ws054!maryann@uunet.UU.NET>ibm-pps 1376/tcp IBM Person to Person Softwareibm-pps 1376/udp IBM Person to Person Software# Simon Phipps <sphipps@vnet.ibm.com>cichlid 1377/tcp Cichlid License Managercichlid 1377/udp Cichlid License Manager# Andy Burgess <aab@cichlid.com>elan 1378/tcp Elan License Managerelan 1378/udp Elan License Manager# Ken Greer <kg@elan.com>dbreporter 1379/tcp Integrity Solutionsdbreporter 1379/udp Integrity Solutions# Tim Dawson <tdawson%mspboss@uunet.UU.NET>telesis-licman 1380/tcp Telesis Network License Managertelesis-licman 1380/udp Telesis Network License Manager# Karl Schendel, Jr. <wiz@telesis.com>apple-licman 1381/tcp Apple Network License Managerapple-licman 1381/udp Apple Network License Manager# Earl Wallace <earlw@apple.com>udt_os 1382/tcpudt_os 1382/udpgwha 1383/tcp GW Hannaway Network License Managergwha 1383/udp GW Hannaway Network License Manager# J. Gabriel Foster <fop@gwha.com>os-licman 1384/tcp Objective Solutions License Manageros-licman 1384/udp Objective Solutions License Manager# Donald Cornwell <don.cornwell@objective.com>atex_elmd 1385/tcp Atex Publishing License Manageratex_elmd 1385/udp Atex Publishing License Manager# Brett Sorenson <bcs@atex.com>checksum 1386/tcp CheckSum License Managerchecksum 1386/udp CheckSum License Manager# Andreas Glocker <glocker@sirius.com>cadsi-lm 1387/tcp Computer Aided Design Software Inc LMcadsi-lm 1387/udp Computer Aided Design Software Inc LM# Sulistio Muljadiobjective-dbc 1388/tcp Objective Solutions DataBase Cacheobjective-dbc 1388/udp Objective Solutions DataBase Cache# Donald Cornwelliclpv-dm 1389/tcp Document Managericlpv-dm 1389/udp Document Managericlpv-sc 1390/tcp Storage Controllericlpv-sc 1390/udp Storage Controllericlpv-sas 1391/tcp Storage Access ServerReynolds & Postel [Page 42]
RFC 1700 Assigned Numbers October 1994iclpv-sas 1391/udp Storage Access Servericlpv-pm 1392/tcp Print Managericlpv-pm 1392/udp Print Managericlpv-nls 1393/tcp Network Log Servericlpv-nls 1393/udp Network Log Servericlpv-nlc 1394/tcp Network Log Clienticlpv-nlc 1394/udp Network Log Clienticlpv-wsm 1395/tcp PC Workstation Manager softwareiclpv-wsm 1395/udp PC Workstation Manager software# A.P. Hobson <A.P.Hobson@bra0112.wins.icl.co.uk>dvl-activemail 1396/tcp DVL Active Maildvl-activemail 1396/udp DVL Active Mailaudio-activmail 1397/tcp Audio Active Mailaudio-activmail 1397/udp Audio Active Mailvideo-activmail 1398/tcp Video Active Mailvideo-activmail 1398/udp Video Active Mail# Ehud Shapiro <udi@wisdon.weizmann.ac.il>cadkey-licman 1399/tcp Cadkey License Managercadkey-licman 1399/udp Cadkey License Managercadkey-tablet 1400/tcp Cadkey Tablet Daemoncadkey-tablet 1400/udp Cadkey Tablet Daemon# Joe McCollough <joe@cadkey.com>goldleaf-licman 1401/tcp Goldleaf License Managergoldleaf-licman 1401/udp Goldleaf License Manager# John Fox <---none--->prm-sm-np 1402/tcp Prospero Resource Managerprm-sm-np 1402/udp Prospero Resource Managerprm-nm-np 1403/tcp Prospero Resource Managerprm-nm-np 1403/udp Prospero Resource Manager# B. Clifford Neuman <bcn@isi.edu>igi-lm 1404/tcp Infinite Graphics License Managerigi-lm 1404/udp Infinite Graphics License Manageribm-res 1405/tcp IBM Remote Execution Starteribm-res 1405/udp IBM Remote Execution Starternetlabs-lm 1406/tcp NetLabs License Managernetlabs-lm 1406/udp NetLabs License Managerdbsa-lm 1407/tcp DBSA License Managerdbsa-lm 1407/udp DBSA License Manager# Scott Shattuck <ss@dbsa.com>sophia-lm 1408/tcp Sophia License Managersophia-lm 1408/udp Sophia License Manager# Eric Brown <sst!emerald!eric@uunet.UU.net>here-lm 1409/tcp Here License Managerhere-lm 1409/udp Here License Manager# David Ison <here@dialup.oar.net>hiq 1410/tcp HiQ License Managerhiq 1410/udp HiQ License Manager# Rick Pugh <rick@bilmillennium.com>Reynolds & Postel [Page 43]
RFC 1700 Assigned Numbers October 1994af 1411/tcp AudioFileaf 1411/udp AudioFile# Jim Gettys <jg@crl.dec.com>innosys 1412/tcp InnoSysinnosys 1412/udp InnoSysinnosys-acl 1413/tcp Innosys-ACLinnosys-acl 1413/udp Innosys-ACL# Eric Welch <--none--->ibm-mqseries 1414/tcp IBM MQSeriesibm-mqseries 1414/udp IBM MQSeries# Roger Meli <rmmeli%winvmd@vnet.ibm.com>dbstar 1415/tcp DBStardbstar 1415/udp DBStar# Jeffrey Millman <jcm@dbstar.com>novell-lu6.2 1416/tcp Novell LU6.2novell-lu6.2 1416/udp Novell LU6.2# Peter Liu <--none--->timbuktu-srv1 1417/tcp Timbuktu Service 1 Porttimbuktu-srv1 1417/tcp Timbuktu Service 1 Porttimbuktu-srv2 1418/tcp Timbuktu Service 2 Porttimbuktu-srv2 1418/udp Timbuktu Service 2 Porttimbuktu-srv3 1419/tcp Timbuktu Service 3 Porttimbuktu-srv3 1419/udp Timbuktu Service 3 Porttimbuktu-srv4 1420/tcp Timbuktu Service 4 Porttimbuktu-srv4 1420/udp Timbuktu Service 4 Port# Marc Epard <marc@waygate.farallon.com>gandalf-lm 1421/tcp Gandalf License Managergandalf-lm 1421/udp Gandalf License Manager# gilmer@gandalf.caautodesk-lm 1422/tcp Autodesk License Managerautodesk-lm 1422/udp Autodesk License Manager# David Ko <dko@autodesk.com>essbase 1423/tcp Essbase Arbor Softwareessbase 1423/udp Essbase Arbor Softwarehybrid 1424/tcp Hybrid Encryption Protocolhybrid 1424/udp Hybrid Encryption Protocol# Howard Hart <hch@hybrid.com>zion-lm 1425/tcp Zion Software License Managerzion-lm 1425/udp Zion Software License Manager# David Ferrero <david@zion.com>sas-1 1426/tcp Satellite-data Acquisition System 1sas-1 1426/udp Satellite-data Acquisition System 1# Bill Taylor <sais@ssec.wisc.edu>mloadd 1427/tcp mloadd monitoring toolmloadd 1427/udp mloadd monitoring tool# Bob Braden <braden@isi.edu>informatik-lm 1428/tcp Informatik License Managerinformatik-lm 1428/udp Informatik License ManagerReynolds & Postel [Page 44]
RFC 1700 Assigned Numbers October 1994# Harald Schlangmann# <schlangm@informatik.uni-muenchen.de>nms 1429/tcp Hypercom NMSnms 1429/udp Hypercom NMStpdu 1430/tcp Hypercom TPDUtpdu 1430/udp Hypercom TPDU# Noor Chowdhury <noor@hypercom.com>rgtp 1431/tcp Reverse Gosip Transportrgtp 1431/udp Reverse Gosip Transport# <iwj10@cl.cam-orl.co.uk>blueberry-lm 1432/tcp Blueberry Software License Managerblueberry-lm 1432/udp Blueberry Software License Manager# Steve Beigel <ublueb!steve@uunet.uu.net>ms-sql-s 1433/tcp Microsoft-SQL-Serverms-sql-s 1433/udp Microsoft-SQL-Serverms-sql-m 1434/tcp Microsoft-SQL-Monitorms-sql-m 1434/udp Microsoft-SQL-Monitor# Peter Hussey <peterhus@microsoft.com>ibm-cics 1435/tcp IBM CISCibm-cics 1435/udp IBM CISC# Geoff Meacock <gbibmswl@ibmmail.COM>sas-2 1436/tcp Satellite-data Acquisition System 2sas-2 1436/udp Satellite-data Acquisition System 2# Bill Taylor <sais@ssec.wisc.edu>tabula 1437/tcp Tabulatabula 1437/udp Tabula# Marcelo Einhorn# <KGUNE%HUJIVM1.bitnet@taunivm.tau.ac.il>eicon-server 1438/tcp Eicon Security Agent/Servereicon-server 1438/udp Eicon Security Agent/Servereicon-x25 1439/tcp Eicon X25/SNA Gatewayeicon-x25 1439/udp Eicon X25/SNA Gatewayeicon-slp 1440/tcp Eicon Service Location Protocoleicon-slp 1440/udp Eicon Service Location Protocol# Pat Calhoun <CALHOUN@admin.eicon.qc.ca>cadis-1 1441/tcp Cadis License Managementcadis-1 1441/udp Cadis License Managementcadis-2 1442/tcp Cadis License Managementcadis-2 1442/udp Cadis License Management# Todd Wichers <twichers@csn.org>ies-lm 1443/tcp Integrated Engineering Softwareies-lm 1443/udp Integrated Engineering Software# David Tong <David_Tong@integrated.mb.ca>marcam-lm 1444/tcp Marcam License Managementmarcam-lm 1444/udp Marcam License Management# Therese Hunt <hunt@marcam.com>proxima-lm 1445/tcp Proxima License Managerproxima-lm 1445/udp Proxima License ManagerReynolds & Postel [Page 45]
RFC 1700 Assigned Numbers October 1994ora-lm 1446/tcp Optical Research Associates License Managerora-lm 1446/udp Optical Research Associates License Managerapri-lm 1447/tcp Applied Parallel Research LMapri-lm 1447/udp Applied Parallel Research LM# Jim Dillon <jed@apri.com>oc-lm 1448/tcp OpenConnect License Manageroc-lm 1448/udp OpenConnect License Manager# Sue Barnhill <snb@oc.com>peport 1449/tcp PEportpeport 1449/udp PEport# Qentin Neill <quentin@ColumbiaSC.NCR.COM>dwf 1450/tcp Tandem Distributed Workbench Facilitydwf 1450/udp Tandem Distributed Workbench Facility# Mike Bert <BERG_MIKE@tandem.com>infoman 1451/tcp IBM Information Managementinfoman 1451/udp IBM Information Management# Karen Burns <---none--->gtegsc-lm 1452/tcp GTE Government Systems License Mangtegsc-lm 1452/udp GTE Government Systems License Man# Mike Gregory <Gregory_Mike@msmail.iipo.gtegsc.com>genie-lm 1453/tcp Genie License Managergenie-lm 1453/udp Genie License Manager# Paul Applegate <p.applegate2@genie.geis.com>interhdl_elmd 1454/tcp interHDL License Managerinterhdl_elmd 1454/tcp interHDL License Manager# Eli Sternheim eli@interhdl.comesl-lm 1455/tcp ESL License Manageresl-lm 1455/udp ESL License Manager# Abel Chou <abel@willy.esl.com>dca 1456/tcp DCAdca 1456/udp DCA# Jeff Garbers <jgarbers@netcom.com>valisys-lm 1457/tcp Valisys License Managervalisys-lm 1457/udp Valisys License Manager# Leslie Lincoln <leslie_lincoln@valisys.com>nrcabq-lm 1458/tcp Nichols Research Corp.nrcabq-lm 1458/udp Nichols Research Corp.# Howard Cole <hcole@tumbleweed.nrcabq.com>proshare1 1459/tcp Proshare Notebook Applicationproshare1 1459/udp Proshare Notebook Applicationproshare2 1460/tcp Proshare Notebook Applicationproshare2 1460/udp Proshare Notebook Application# Robin Kar <Robin_Kar@ccm.hf.intel.com>ibm_wrless_lan 1461/tcp IBM Wireless LANibm_wrless_lan 1461/udp IBM Wireless LAN# <flanne@vnet.IBM.COM>world-lm 1462/tcp World License Managerworld-lm 1462/udp World License ManagerReynolds & Postel [Page 46]
RFC 1700 Assigned Numbers October 1994# Michael S Amirault <ambi@world.std.com>nucleus 1463/tcp Nucleusnucleus 1463/udp Nucleus# Venky Nagar <venky@fafner.Stanford.EDU>msl_lmd 1464/tcp MSL License Managermsl_lmd 1464/udp MSL License Manager# Matt Timmermanspipes 1465/tcp Pipes Platformpipes 1465/udp Pipes Platform mfarlin@peerlogic.com# Mark Farlin <mfarlin@peerlogic.com>oceansoft-lm 1466/tcp Ocean Software License Manageroceansoft-lm 1466/udp Ocean Software License Manager# Randy Leonard <randy@oceansoft.com>csdmbase 1467/tcp CSDMBASEcsdmbase 1467/udp CSDMBASEcsdm 1468/tcp CSDMcsdm 1468/udp CSDM# Robert Stabl <stabl@informatik.uni-muenchen.de>aal-lm 1469/tcp Active Analysis Limited License Manageraal-lm 1469/udp Active Analysis Limited License Manager# David Snocken +44 (71)437-7009uaiact 1470/tcp Universal Analyticsuaiact 1470/udp Universal Analytics# Mark R. Ludwig <Mark-Ludwig@uai.com>csdmbase 1471/tcp csdmbasecsdmbase 1471/udp csdmbasecsdm 1472/tcp csdmcsdm 1472/udp csdm# Robert Stabl <stabl@informatik.uni-muenchen.de>openmath 1473/tcp OpenMathopenmath 1473/udp OpenMath# Garth Mayville <mayville@maplesoft.on.ca>telefinder 1474/tcp Telefindertelefinder 1474/udp Telefinder# Jim White <Jim_White@spiderisland.com>taligent-lm 1475/tcp Taligent License Managertaligent-lm 1475/udp Taligent License Manager# Mark Sapsford <Mark_Sapsford@@taligent.com>clvm-cfg 1476/tcp clvm-cfgclvm-cfg 1476/udp clvm-cfg# Eric Soderberg <seric@cup.hp.com>ms-sna-server 1477/tcp ms-sna-serverms-sna-server 1477/udp ms-sna-serverms-sna-base 1478/tcp ms-sna-basems-sna-base 1478/udp ms-sna-base# Gordon Mangione <gordm@microsoft.com>dberegister 1479/tcp dberegisterdberegister 1479/udp dberegisterReynolds & Postel [Page 47]
RFC 1700 Assigned Numbers October 1994# Brian Griswold <brian@dancingbear.com>pacerforum 1480/tcp PacerForumpacerforum 1480/udp PacerForum# Peter Caswell <pfc@pacvax.pacersoft.com>airs 1481/tcp AIRSairs 1481/udp AIRS# Bruce Wilson, 905-771-6161miteksys-lm 1482/tcp Miteksys License Managermiteksys-lm 1482/udp Miteksys License Manager# Shane McRoberts <mcroberts@miteksys.com>afs 1483/tcp AFS License Managerafs 1483/udp AFS License Manager# Michael R. Pizolato <michael@afs.com>confluent 1484/tcp Confluent License Managerconfluent 1484/udp Confluent License Manager# James Greenfiel <jim@pa.confluent.com>lansource 1485/tcp LANSourcelansource 1485/udp LANSource# Doug Scott <lansourc@hookup.net>nms_topo_serv 1486/tcp nms_topo_servnms_topo_serv 1486/udp nms_topo_serv# Sylvia Siu <Sylvia_Siu@Novell.CO>localinfosrvr 1487/tcp LocalInfoSrvrlocalinfosrvr 1487/udp LocalInfoSrvr# Brian Matthews <brian_matthews@ibist.ibis.com>docstor 1488/tcp DocStordocstor 1488/udp DocStor# Brian Spears <bspears@salix.com>dmdocbroker 1489/tcp dmdocbrokerdmdocbroker 1489/udp dmdocbroker# Razmik Abnous <abnous@documentum.com>insitu-conf 1490/tcp insitu-confinsitu-conf 1490/udp insitu-conf# Paul Blacknell <paul@insitu.com>anynetgateway 1491/tcp anynetgatewayanynetgateway 1491/udp anynetgateway# Dan Poirier <poirier@VNET.IBM.COM>stone-design-1 1492/tcp stone-design-1stone-design-1 1492/udp stone-design-1# Andrew Stone <andrew@stone.com>netmap_lm 1493/tcp netmap_lmnetmap_lm 1493/udp netmap_lm# Phillip Magson <philm@extro.ucc.su.OZ.AU>ica 1494/tcp icaica 1494/udp ica# John Richardson, Citrix Systemscvc 1495/tcp cvccvc 1495/udp cvcReynolds & Postel [Page 48]
RFC 1700 Assigned Numbers October 1994# Bill Davidson <billd@equalizer.cray.com>liberty-lm 1496/tcp liberty-lmliberty-lm 1496/udp liberty-lm# Jim Rogers <trane!jimbo@pacbell.com>rfx-lm 1497/tcp rfx-lmrfx-lm 1497/udp rfx-lm# Bill Bishop <bil@rfx.rfx.com>watcom-sql 1498/tcp Watcom-SQLwatcom-sql 1498/udp Watcom-SQL# Rog Skubowius <rwskubow@ccnga.uwaterloo.ca>fhc 1499/tcp Federico Heinz Consultorafhc 1499/udp Federico Heinz Consultora# Federico Heinz <federico@heinz.com>vlsi-lm 1500/tcp VLSI License Managervlsi-lm 1500/udp VLSI License Manager# Shue-Lin Kuo <shuelin@mdk.sanjose.vlsi.com>sas-3 1501/tcp Satellite-data Acquisition System 3sas-3 1501/udp Satellite-data Acquisition System 3# Bill Taylor <sais@ssec.wisc.edu>shivadiscovery 1502/tcp Shivashivadiscovery 1502/udp Shiva# Jonathan Wenocur <jhw@Shiva.COM>imtc-mcs 1503/tcp Databeamimtc-mcs 1503/udp Databeam# Jim Johnstone <jjohnstone@databeam.com>evb-elm 1504/tcp EVB Software Engineering License Managerevb-elm 1504/udp EVB Software Engineering License Manager# B.G. Mahesh < mahesh@sett.com>funkproxy 1505/tcp Funk Software, Inc.funkproxy 1505/udp Funk Software, Inc.# Robert D. Vincent <bert@willowpond.com># 1506-1523 Unassignedingreslock 1524/tcp ingresingreslock 1524/udp ingresorasrv 1525/tcp oracleorasrv 1525/udp oracleprospero-np 1525/tcp Prospero Directory Service non-privprospero-np 1525/udp Prospero Directory Service non-privpdap-np 1526/tcp Prospero Data Access Prot non-privpdap-np 1526/udp Prospero Data Access Prot non-priv# B. Clifford Neuman <bcn@isi.edu>tlisrv 1527/tcp oracletlisrv 1527/udp oraclecoauthor 1529/tcp oraclecoauthor 1529/udp oracleissd 1600/tcpissd 1600/udpnkd 1650/tcpReynolds & Postel [Page 49]
RFC 1700 Assigned Numbers October 1994nkd 1650/udpproshareaudio 1651/tcp proshare conf audioproshareaudio 1651/udp proshare conf audioprosharevideo 1652/tcp proshare conf videoprosharevideo 1652/udp proshare conf videoprosharedata 1653/tcp proshare conf dataprosharedata 1653/udp proshare conf dataprosharerequest 1654/tcp proshare conf requestprosharerequest 1654/udp proshare conf requestprosharenotify 1655/tcp proshare conf notifyprosharenotify 1655/udp proshare conf notify# <gunner@ibeam.intel.com>netview-aix-1 1661/tcp netview-aix-1netview-aix-1 1661/udp netview-aix-1netview-aix-2 1662/tcp netview-aix-2netview-aix-2 1662/udp netview-aix-2netview-aix-3 1663/tcp netview-aix-3netview-aix-3 1663/udp netview-aix-3netview-aix-4 1664/tcp netview-aix-4netview-aix-4 1664/udp netview-aix-4netview-aix-5 1665/tcp netview-aix-5netview-aix-5 1665/udp netview-aix-5netview-aix-6 1666/tcp netview-aix-6netview-aix-6 1666/udp netview-aix-6# Martha Crisson <CRISSON@ralvm12.vnet.ibm.com>licensedaemon 1986/tcp cisco license managementlicensedaemon 1986/udp cisco license managementtr-rsrb-p1 1987/tcp cisco RSRB Priority 1 porttr-rsrb-p1 1987/udp cisco RSRB Priority 1 porttr-rsrb-p2 1988/tcp cisco RSRB Priority 2 porttr-rsrb-p2 1988/udp cisco RSRB Priority 2 porttr-rsrb-p3 1989/tcp cisco RSRB Priority 3 porttr-rsrb-p3 1989/udp cisco RSRB Priority 3 port#PROBLEMS!===================================================mshnet 1989/tcp MHSnet systemmshnet 1989/udp MHSnet system# Bob Kummerfeld <bob@sarad.cs.su.oz.au>#PROBLEMS!===================================================stun-p1 1990/tcp cisco STUN Priority 1 portstun-p1 1990/udp cisco STUN Priority 1 portstun-p2 1991/tcp cisco STUN Priority 2 portstun-p2 1991/udp cisco STUN Priority 2 portstun-p3 1992/tcp cisco STUN Priority 3 portstun-p3 1992/udp cisco STUN Priority 3 port#PROBLEMS!===================================================ipsendmsg 1992/tcp IPsendmsgipsendmsg 1992/udp IPsendmsg# Bob Kummerfeld <bob@sarad.cs.su.oz.au>Reynolds & Postel [Page 50]
RFC 1700 Assigned Numbers October 1994#PROBLEMS!===================================================snmp-tcp-port 1993/tcp cisco SNMP TCP portsnmp-tcp-port 1993/udp cisco SNMP TCP portstun-port 1994/tcp cisco serial tunnel portstun-port 1994/udp cisco serial tunnel portperf-port 1995/tcp cisco perf portperf-port 1995/udp cisco perf porttr-rsrb-port 1996/tcp cisco Remote SRB porttr-rsrb-port 1996/udp cisco Remote SRB portgdp-port 1997/tcp cisco Gateway Discovery Protocolgdp-port 1997/udp cisco Gateway Discovery Protocolx25-svc-port 1998/tcp cisco X.25 service (XOT)x25-svc-port 1998/udp cisco X.25 service (XOT)tcp-id-port 1999/tcp cisco identification porttcp-id-port 1999/udp cisco identification portcallbook 2000/tcpcallbook 2000/udpdc 2001/tcpwizard 2001/udp curryglobe 2002/tcpglobe 2002/udpmailbox 2004/tcpemce 2004/udp CCWS mm confberknet 2005/tcporacle 2005/udpinvokator 2006/tcpraid-cc 2006/udp raiddectalk 2007/tcpraid-am 2007/udpconf 2008/tcpterminaldb 2008/udpnews 2009/tcpwhosockami 2009/udpsearch 2010/tcppipe_server 2010/udpraid-cc 2011/tcp raidservserv 2011/udpttyinfo 2012/tcpraid-ac 2012/udpraid-am 2013/tcpraid-cd 2013/udptroff 2014/tcpraid-sf 2014/udpcypress 2015/tcpraid-cs 2015/udpbootserver 2016/tcpbootserver 2016/udpcypress-stat 2017/tcpReynolds & Postel [Page 51]
RFC 1700 Assigned Numbers October 1994bootclient 2017/udpterminaldb 2018/tcprellpack 2018/udpwhosockami 2019/tcpabout 2019/udpxinupageserver 2020/tcpxinupageserver 2020/udpservexec 2021/tcpxinuexpansion1 2021/udpdown 2022/tcpxinuexpansion2 2022/udpxinuexpansion3 2023/tcpxinuexpansion3 2023/udpxinuexpansion4 2024/tcpxinuexpansion4 2024/udpellpack 2025/tcpxribs 2025/udpscrabble 2026/tcpscrabble 2026/udpshadowserver 2027/tcpshadowserver 2027/udpsubmitserver 2028/tcpsubmitserver 2028/udpdevice2 2030/tcpdevice2 2030/udpblackboard 2032/tcpblackboard 2032/udpglogger 2033/tcpglogger 2033/udpscoremgr 2034/tcpscoremgr 2034/udpimsldoc 2035/tcpimsldoc 2035/udpobjectmanager 2038/tcpobjectmanager 2038/udplam 2040/tcplam 2040/udpinterbase 2041/tcpinterbase 2041/udpisis 2042/tcpisis 2042/udpisis-bcast 2043/tcpisis-bcast 2043/udprimsl 2044/tcprimsl 2044/udpcdfunc 2045/tcpcdfunc 2045/udpsdfunc 2046/tcpReynolds & Postel [Page 52]
RFC 1700 Assigned Numbers October 1994sdfunc 2046/udpdls 2047/tcpdls 2047/udpdls-monitor 2048/tcpdls-monitor 2048/udpshilp 2049/tcpshilp 2049/udpdlsrpn 2065/tcp Data Link Switch Read Port Numberdlsrpn 2065/udp Data Link Switch Read Port Numberdlswpn 2067/tcp Data Link Switch Write Port Numberdlswpn 2067/udp Data Link Switch Write Port Numberats 2201/tcp Advanced Training System Programats 2201/udp Advanced Training System Programrtsserv 2500/tcp Resource Tracking system serverrtsserv 2500/udp Resource Tracking system serverrtsclient 2501/tcp Resource Tracking system clientrtsclient 2501/udp Resource Tracking system client# Aubrey Turner# <S95525ta%etsuacad.bitnet@ETSUADMN.ETSU.EDU>hp-3000-telnet 2564/tcp HP 3000 NS/VT block mode telnetwww-dev 2784/tcp world wide web - developmentwww-dev 2784/udp world wide web - developmentNSWS 3049/tcpNSWS 3049/udpccmail 3264/tcp cc:mail/lotusccmail 3264/udp cc:mail/lotusdec-notes 3333/tcp DEC Notesdec-notes 3333/udp DEC Notes# Kim Moraros <moraros@via.enet.dec.com>mapper-nodemgr 3984/tcp MAPPER network node managermapper-nodemgr 3984/udp MAPPER network node managermapper-mapethd 3985/tcp MAPPER TCP/IP servermapper-mapethd 3985/udp MAPPER TCP/IP servermapper-ws_ethd 3986/tcp MAPPER workstation servermapper-ws_ethd 3986/udp MAPPER workstation server# John C. Horton <jch@unirsvl.rsvl.unisys.com>bmap 3421/tcp Bull Apprise portmapperbmap 3421/udp Bull Apprise portmapper# Jeremy Gilbert <J.Gilbert@ma30.bull.com>udt_os 3900/tcp Unidata UDT OSudt_os 3900/udp Unidata UDT OS# James Powell <james@mailhost.unidata.com>nuts_dem 4132/tcp NUTS Daemonnuts_dem 4132/udp NUTS Daemonnuts_bootp 4133/tcp NUTS Bootp Servernuts_bootp 4133/udp NUTS Bootp Server# Martin Freiss <freiss.pad@sni.>unicall 4343/tcp UNICALLReynolds & Postel [Page 53]
RFC 1700 Assigned Numbers October 1994unicall 4343/udp UNICALL# James Powell <james@enghp.unidata.comp>krb524 4444/tcp KRB524krb524 4444/udp KRB524# B. Clifford Neuman <bcn@isi.edu>rfa 4672/tcp remote file access serverrfa 4672/udp remote file access servercommplex-main 5000/tcpcommplex-main 5000/udpcommplex-link 5001/tcpcommplex-link 5001/udprfe 5002/tcp radio free ethernetrfe 5002/udp radio free ethernettelelpathstart 5010/tcp TelepathStarttelelpathstart 5010/udp TelepathStarttelelpathattack 5011/tcp TelepathAttacktelelpathattack 5011/udp TelepathAttack# Helmuth Breitenfellner <hbreitenf@vnet.imb.com>mmcc 5050/tcp multimedia conference control toolmmcc 5050/udp multimedia conference control toolrmonitor_secure 5145/tcprmonitor_secure 5145/udpaol 5190/tcp America-Onlineaol 5190/udp America-Online# Marty Lyons <marty@aol.com>padl2sim 5236/tcppadl2sim 5236/udphacl-hb 5300/tcp # HA cluster heartbeathacl-hb 5300/udp # HA cluster heartbeathacl-gs 5301/tcp # HA cluster general serviceshacl-gs 5301/udp # HA cluster general serviceshacl-cfg 5302/tcp # HA cluster configurationhacl-cfg 5302/udp # HA cluster configurationhacl-probe 5303/tcp # HA cluster probinghacl-probe 5303/udp # HA cluster probinghacl-local 5304/tcphacl-local 5304/udphacl-test 5305/tcphacl-test 5305/udp# Eric Soderberg <seric@hposl102.cup.hp>x11 6000-6063/tcp X Window Systemx11 6000-6063/udp X Window System# Stephen Gildea <gildea@expo.lcs.mit.edu>sub-process 6111/tcp HP SoftBench Sub-Process Controlsub-process 6111/udp HP SoftBench Sub-Process Controlmeta-corp 6141/tcp Meta Corporation License Managermeta-corp 6141/udp Meta Corporation License Manager# Osamu Masuda <--none--->Reynolds & Postel [Page 54]
RFC 1700 Assigned Numbers October 1994aspentec-lm 6142/tcp Aspen Technology License Manageraspentec-lm 6142/udp Aspen Technology License Manager# Kevin Massey <massey@aspentec.com>watershed-lm 6143/tcp Watershed License Managerwatershed-lm 6143/udp Watershed License Manager# David Ferrero <david@zion.com>statsci1-lm 6144/tcp StatSci License Manager - 1statsci1-lm 6144/udp StatSci License Manager - 1statsci2-lm 6145/tcp StatSci License Manager - 2statsci2-lm 6145/udp StatSci License Manager - 2# Scott Blachowicz <scott@statsci.com>lonewolf-lm 6146/tcp Lone Wolf Systems License Managerlonewolf-lm 6146/udp Lone Wolf Systems License Manager# Dan Klein <dvk@lonewolf.com>montage-lm 6147/tcp Montage License Managermontage-lm 6147/udp Montage License Manager# Michael Ubell <michael@montage.com>xdsxdm 6558/udpxdsxdm 6558/tcpafs3-fileserver 7000/tcp file server itselfafs3-fileserver 7000/udp file server itselfafs3-callback 7001/tcp callbacks to cache managersafs3-callback 7001/udp callbacks to cache managersafs3-prserver 7002/tcp users & groups databaseafs3-prserver 7002/udp users & groups databaseafs3-vlserver 7003/tcp volume location databaseafs3-vlserver 7003/udp volume location databaseafs3-kaserver 7004/tcp AFS/Kerberos authentication serviceafs3-kaserver 7004/udp AFS/Kerberos authentication serviceafs3-volser 7005/tcp volume managment serverafs3-volser 7005/udp volume managment serverafs3-errors 7006/tcp error interpretation serviceafs3-errors 7006/udp error interpretation serviceafs3-bos 7007/tcp basic overseer processafs3-bos 7007/udp basic overseer processafs3-update 7008/tcp server-to-server updaterafs3-update 7008/udp server-to-server updaterafs3-rmtsys 7009/tcp remote cache manager serviceafs3-rmtsys 7009/udp remote cache manager serviceups-onlinet 7010/tcp onlinet uninterruptable power suppliesups-onlinet 7010/udp onlinet uninterruptable power supplies# Brian Hammill <hamill@dolphin.exide.com>font-service 7100/tcp X Font Servicefont-service 7100/udp X Font Service# Stephen Gildea <gildea@expo.lcs.mit.edu>fodms 7200/tcp FODMS FLIPfodms 7200/udp FODMS FLIP# David Anthony <anthony@power.amasd.anatcp.rockwell.com>Reynolds & Postel [Page 55]
RFC 1700 Assigned Numbers October 1994man 9535/tcpman 9535/udpisode-dua 17007/tcpisode-dua 17007/udpREFERENCES[RFC768] Postel, J., "User Datagram Protocol", STD 6,RFC 768, USC/Information Sciences Institute, August 1980.[RFC793] Postel, J., ed., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", STD 7,RFC 793, USC/Information Sciences Institute, September 1981.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbersReynolds & Postel [Page 56]
RFC 1700 Assigned Numbers October 1994INTERNET MULTICAST ADDRESSESHost Extensions for IP Multicasting [RFC1112] specifies theextensions required of a host implementation of the Internet Protocol(IP) to support multicasting. Current addresses are listed below.224.0.0.0 Base Address (Reserved) [RFC1112,JBP]224.0.0.1 All Systems on this Subnet [RFC1112,JBP]224.0.0.2 All Routers on this Subnet [JBP]224.0.0.3 Unassigned [JBP]224.0.0.4 DVMRP Routers [RFC1075,JBP]224.0.0.5 OSPFIGPOSPFIGP All Routers [RFC1583,JXM1]224.0.0.6 OSPFIGPOSPFIGP Designated Routers [RFC1583,JXM1]224.0.0.7 ST Routers [RFC1190,KS14]224.0.0.8 ST Hosts [RFC1190,KS14]224.0.0.9 RIP2 Routers [GSM11]224.0.0.10 IGRP Routers [Dino Farinacci]224.0.0.11 Mobile-Agents [Bill Simpson]224.0.0.12-224.0.0.255 Unassigned [JBP]224.0.1.0 VMTP Managers Group [RFC1045,DRC3]224.0.1.1 NTP Network Time Protocol [RFC1119,DLM1]224.0.1.2 SGI-Dogfight [AXC]224.0.1.3 Rwhod [SXD]224.0.1.4 VNP [DRC3]224.0.1.5 Artificial Horizons - Aviator [BXF]224.0.1.6 NSS - Name Service Server [BXS2]224.0.1.7 AUDIONEWS - Audio News Multicast [MXF2]224.0.1.8 SUN NIS+ Information Service [CXM3]224.0.1.9 MTP Multicast Transport Protocol [SXA]224.0.1.10 IETF-1-LOW-AUDIO [SC3]224.0.1.11 IETF-1-AUDIO [SC3]224.0.1.12 IETF-1-VIDEO [SC3]224.0.1.13 IETF-2-LOW-AUDIO [SC3]224.0.1.14 IETF-2-AUDIO [SC3]224.0.1.15 IETF-2-VIDEO [SC3]224.0.1.16 MUSIC-SERVICE [Guido van Rossum]224.0.1.17 SEANET-TELEMETRY [Andrew Maffei]224.0.1.18 SEANET-IMAGE [Andrew Maffei]224.0.1.19 MLOADD [Braden]224.0.1.20 any private experiment [JBP]224.0.1.21 DVMRP on MOSPF [John Moy]224.0.1.22 SVRLOC <veizades@ftp.com>224.0.1.23 XINGTV <hgxing@aol.com>224.0.1.24 microsoft-ds <arnoldm@microsoft.com>224.0.1.25 nbc-pro <bloomer@birch.crd.ge.com>224.0.1.26 nbc-pfn <bloomer@birch.crd.ge.com>224.0.1.27-224.0.1.255 Unassigned [JBP]Reynolds & Postel [Page 57]
RFC 1700 Assigned Numbers October 1994224.0.2.1 "rwho" Group (BSD) (unofficial) [JBP]224.0.2.2 SUN RPC PMAPPROC_CALLIT [BXE1]224.0.3.000-224.0.3.255 RFE Generic Service [DXS3]224.0.4.000-224.0.4.255 RFE Individual Conferences [DXS3]224.0.5.000-224.0.5.127 CDPD Groups [Bob Brenner]224.0.5.128-224.0.5.255 Unassigned [IANA]224.0.6.000-224.0.6.127 Cornell ISIS Project [Tim Clark]224.0.6.128-224.0.6.255 Unassigned [IANA]224.1.0.0-224.1.255.255 ST Multicast Groups [RFC1190,KS14]224.2.0.0-224.2.255.255 Multimedia Conference Calls [SC3]224.252.0.0-224.255.255.255 DIS transient groups [Joel Snyder]232.0.0.0-232.255.255.255 VMTP transient groups [RFC1045,DRC3]These addresses are listed in the Domain Name Service under MCAST.NETand 224.IN-ADDR.ARPA.Note that when used on an Ethernet or IEEE 802 network, the 23low-order bits of the IP Multicast address are placed in the low-order23 bits of the Ethernet or IEEE 802 net multicast address1.0.94.0.0.0. See the next section on "IANA ETHERNET ADDRESS BLOCK".REFERENCES[RFC1045] Cheriton, D., "VMTP: Versatile Message Transaction Protocol Specification",RFC 1045, Stanford University, February 1988.[RFC1075] Waitzman, D., C. Partridge, and S. Deering "Distance Vector Multicast Routing Protocol",RFC-1075, BBN STC, Stanford University, November 1988.[RFC1112] Deering, S., "Host Extensions for IP Multicasting", STD 5,RFC 1112, Stanford University, August 1989.[RFC1119] Mills, D., "Network Time Protocol (Version 1), Specification and Implementation", STD 12,RFC 1119, University of Delaware, July 1988.[RFC1190] Topolcic, C., Editor, "Experimental Internet Stream Protocol, Version 2 (ST-II)",RFC 1190, CIP Working Group, October 1990.[RFC1583] Moy, J., "The OSPF Specification",RFC 1583, Proteon, March 1994.Reynolds & Postel [Page 58]
RFC 1700 Assigned Numbers October 1994PEOPLE<arnoldm@microsoft.com>[AXC] Andrew Cherenson <arc@SGI.COM>[Bob Brenner]<bloomer@birch.crd.ge.com>[Braden] Bob Braden <braden@isi.edu[BXE1] Brendan Eic <brendan@illyria.wpd.sgi.com>[BXF] Bruce Factor <ahi!bigapple!bruce@uunet.UU.NET>[BXS2] Bill Schilit <schilit@parc.xerox.com>[CXM3] Chuck McManis <cmcmanis@sun.com>[Tim Clark][DLM1] David Mills <Mills@HUEY.UDEL.EDU>[DRC3] Dave Cheriton <cheriton@PESCADERO.STANFORD.EDU>[DXS3] Daniel Steinber <Daniel.Steinberg@Eng.Sun.COM>[Dino Farinacci][GSM11] Gary S. Malkin <GMALKIN@XYLOGICS.COM><hgxing@aol.com>[IANA] IANA <iana@isi.edu>[JBP] Jon Postel <postel@isi.edu>[JXM1] Jim Miner <miner@star.com>[KS14] <mystery contact>[Andrew Maffei][John Moy] John Moy <jmoy@PROTEON.COM>[MXF2] Martin Forssen <maf@dtek.chalmers.se>Reynolds & Postel [Page 59]
RFC 1700 Assigned Numbers October 1994[Guido van Rossum][SC3] Steve Casner <casner@isi.edu>[Joel Snyder][SXA] Susie Armstrong <Armstrong.wbst128@XEROX.COM>[SXD] Steve Deering <deering@PARC.XEROX.COM><veizades@ftp.com>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/multicast-addressesReynolds & Postel [Page 60]
RFC 1700 Assigned Numbers October 1994SUN RPC NUMBERSTo obtain SUN Remote Procedure Call (RPC) numbers send an e-mailrequest to "rpc@sun.com".The RPC port management service ('portmap' in SunOS versions less than5.0 and 'rpcbind' in SunOS versions greater than 5.0) "registers" theIP port number that is allocated to a particular service when thatservice is created. It does not allocate ports on behalf of thoseservices.For an exact specification of the semantics refer to the source codeof svcudp_create() and svctcp_create() in the archives. In shorthowever is that these interfaces, and svc_tli_create their TransportIndependent RPC equivalent, take either a user specified port numberor RPC_ANY (-1) which effectively means "I don't care." In the "Idon't care" case the create code simply calls socket(2) or t_open(3n)which allocates an IP port based on the rules: if euid of the requesting process is 0 (i.e., root) allocate the next available port number in the reserved port range. else allocate the next available port in the non-reserved range.Port numbers count up sequentially.Can a port that is "assigned" can be used when the assignee's serviceis not present? Say port 501 is assigned to the "jeans" service. Ona machine that does not have the "jeans" service, nor has any clientsthat might be expecting to use it, is port 501 available for otheruses? Any dynamic allocation process, like the portmapper, thatchooses the next unused port might allocate port 501 dynamically to aprocess that asked for a "I don't care" port. So any dynamicallocation scheme may pick an unused port that happened to correspondto a port number that had been "assigned" but was currently unused.While it might be desirable, it is impossible to guarantee that anyunused port, even though officially assigned to a service, is notpicked by a dynamic allocator since such an assignment might occurlong after the delivery of the system into a site that doesn't watchfor the latest list.There is the restriction that only "superuser" on BSD derived systemssuch as SunOS can bind to a port number that is less than 1024. Soprograms have used this information in the past to identify whether orReynolds & Postel [Page 61]
RFC 1700 Assigned Numbers October 1994not the service they were talking to was started by the superuser onthe remote system. Making this assumption is dangerous because notall system enforce this restriction.Sun RPC services use ports that are currently unused. If someonenoted that an RPC service was using port 781, it would be just ashappy using port 891, or 951. The service doesn't care what port itgets, remote clients will query the portmapper to ask it what portnumber was assigned to the service when it was started. The key isthat the port was not currently in use. The only port that ONC/RPCmust have is 111 its assigned port for the portmap service.The most common complaint comes when people put a new service on theirsystem. When they configure their systems they put the new serviceconfiguration commands at the end of their system startup scripts.During startup, several network services may be started. Thoseservices that are ONC/RPC based just pick the next available port,those that have pre-assigned ports bind to their pre-assigned port.Clearly the correct sequence is to have all services that need aparticular port to be started first (or if they are "latent" servicesthat are started by inetd, to have inetd started). Finally, the RPCservices should be started as they will be assigned unused ports. (Inthe BSD networking code (which we use) the algorithm for pickingports is in the file in_pcb.c, function in_pcbbind().)Services should be started in this order: a) Services that will "run" continuously and have an assigned port. Note that this includes rpcbind (nee portmap) that has port 111 assigned to it. b) inetd - which will automatically create sockets for those services that have reserved ports but only run on demand (like finger) c) RPC services - which will automatically pick unused ports and maximize efficiency of the "IP Port" namespace.The include file /usr/include/netinet/in.h defines a constantIPPORT_RESERVED to be 1024. The relevant text is: /* * Ports < IPPORT_RESERVED are reserved for * privileged processes (e.g. root). * Ports > IPPORT_USERRESERVED are reserved * for servers, not necessarily privileged. */ #define IPPORT_RESERVED 1024Reynolds & Postel [Page 62]
RFC 1700 Assigned Numbers October 1994 #define IPPORT_USERRESERVED 5000Portmap does not allocate ports, the kernel allocates ports. The codethat does this is part of nearly every UNIX system in the world (andsince the BSD code is 'free' it is often the same code). RPC servicesask the kernel to allocate them a port by calling the "bind()" systemcall. The parameter they pass is "INADDR_ANY" which means "allocateme any IP port you want". The kernel does that by looking at all ofthe ports that are currently in use and picking one that is notcurrently used. The number picked is either less that 1024 if theprocess is privledged, or greater than 1024 if the process is notprivledged. After the kernel has allocated a port, the serviceregisters this allocation with portmap. The portmapper is merely aregistry of previously allocated ports. Note "allocated" here isbeing used in the sense that they are used by an open socket, notassigned a well known name.The role of /etc/services is to provide an idea to people who arelooking at network traffic as to where a packet may have originatedfrom or is headed to. For services like finger that have assignedports, they can just hard code the port they want into theirexecutable. (it isn't like it will change, and if they read it from/etc/services and someone had mistyped the port number it won'tinteroperate with clients anyway!)It is not practical to read the /etc/services file into the kernel toprevent it from giving out port numbers that are "pre-assigned", noris it generally desirable since with the correct ordering of startupit is completely unneccesary.Editors Note: This information was supplied by Chuck McManis of Sun.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbersReynolds & Postel [Page 63]
RFC 1700 Assigned Numbers October 1994IP OPTION NUMBERSThe Internet Protocol (IP) has provision for optional header fieldsidentified by an option type field. Options 0 and 1 are exactly oneoctet which is their type field. All other options have their oneoctet type field, followed by a one octet length field, followed bylength-2 octets of option data. The option type field is sub-dividedinto a one bit copied flag, a two bit class field, and a five bitoption number. These taken together form an eight bit value for theoption type field. IP options are commonly refered to by this value.Copy Class Number Value Name Reference---- ----- ------ ----- ------------------------------- --------- 0 0 0 0 EOOL - End of Options List [RFC791,JBP] 0 0 1 1 NOP - No Operation [RFC791,JBP] 1 0 2 130 SEC - Security [RFC1108] 1 0 3 131 LSR - Loose Source Route [RFC791,JBP] 0 2 4 68 TS - Time Stamp [RFC791,JBP] 1 0 5 133 E-SEC - Extended Security [RFC1108] 1 0 6 134 CIPSO - Commercial Security [???] 0 0 7 7 RR - Record Route [RFC791,JBP] 1 0 8 136 SID - Stream ID [RFC791,JBP] 1 0 9 137 SSR - Strict Source Route [RFC791,JBP] 0 0 10 10 ZSU - Experimental Measurement [ZSu] 0 0 11 11 MTUP - MTU Probe [RFC1191] 0 0 12 12 MTUR - MTU Reply [RFC1191] 1 2 13 205 FINN - Experimental Flow Control [Finn] 1 0 14 142 VISA - Expermental Access Control [Estrin] 0 0 15 15 ENCODE - ??? [VerSteeg] 1 0 16 144 IMITD - IMI Traffic Descriptor [Lee] 1 0 17 145 EIP - ??? [RFC1358] 0 2 18 82 TR - Traceroute [RFC1393] 1 0 19 147 ADDEXT - Address Extension [Ullmann IPv7]IP TIME TO LIVE PARAMETERThe current recommended default time to live (TTL) for theInternet Protocol (IP) [45,105] is 64.IP TOS PARAMETERSThis documents the default Type-of-Service values that are currentlyrecommended for the most important Internet protocols.Reynolds & Postel [Page 64]
RFC 1700 Assigned Numbers October 1994TOS Value Description Reference--------- -------------------------- --------- 0000 Default [RFC1349] 0001 Minimize Monetary Cost [RFC1349] 0010 Maximize Reliability [RFC1349] 0100 Maximize Throughput [RFC1349] 1000 Minimize Delay [RFC1349] 1111 Maximize Security [RFC1455]The TOS value is used to indicate "better". Only one TOS value orproperty can be requested in any one IP datagram.Generally, protocols which are involved in direct interaction with ahuman should select low delay, while data transfers which may involvelarge blocks of data are need high throughput. Finally, high reliabilityis most important for datagram-based Internet management functions.Application protocols not included in these tables should be able tomake appropriate choice of low delay (8 decimal, 1000 binary) or highthroughput (4 decimal, 0100 binary).The following are recommended values for TOS: ----- Type-of-Service Value -----Protocol TOS ValueTELNET (1) 1000 (minimize delay)FTP Control 1000 (minimize delay) Data (2) 0100 (maximize throughput)TFTP 1000 (minimize delay)SMTP (3) Command phase 1000 (minimize delay) DATA phase 0100 (maximize throughput)Domain Name Service UDP Query 1000 (minimize delay) TCP Query 0000 Zone Transfer 0100 (maximize throughput)NNTP 0001 (minimize monetary cost)ICMPReynolds & Postel [Page 65]
RFC 1700 Assigned Numbers October 1994 Errors 0000 Requests 0000 (4) Responses <same as request> (4)Any IGP 0010 (maximize reliability)EGP 0000SNMP 0010 (maximize reliability)BOOTP 0000Notes:(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 TOSduring the lifetime of the connection, then therecommended TOS on opening the connection is the defaultTOS (0000).(4) Although ICMP request messages are normally sent withthe default TOS, there are sometimes good reasons why theywould be sent with some other TOS value. An ICMPresponse always uses the same TOS value as was used in thecorresponding ICMP request message.An application may (at the request of the user) substitute0001 (minimize monetary cost) for any of the above values.REFERENCES[RFC791] Postel, J., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5,RFC 791, DARPA, September 1981.[RFC1108] Kent, S., "U.S. Department of Defense Security Options for the Internet Protocol",RFC 1108, BBN Communications, November 1991.[RFC1191] Mogul, J., and S. Deering, "Path MTU Discovery",RFC 1191, DECWRL, Stanford University, November 1990.[RFC1349] Almquist, P., "Type of Service in the Internet Protocol Suite",RFC 1349, Consultant, July 1992.Reynolds & Postel [Page 66]
RFC 1700 Assigned Numbers October 1994[RFC1358] Chapin, L., Chair, "Charter of the Internet Architecture Board (IAB)",RFC 1358, Internet Architecture Board, August 1992.[RFC1393] Malkin, G., "Traceroute Using an IP Option",RFC 1393, Xylogics, Inc., January 1993.[RFC1455] Eastlake, D., "Physical Link Security Type of Service",RFC 1455, Digital Equipment Corporation, May 1993.[Ullmann IPv7]PEOPLE[Estrin] Deborah Estrin <Estrin@usc.edu>[Finn] Greg Finn <Finn@isi.edu>[JBP] Jon Postel <postel@isi.edu>[Ullmann] Robert Ullmann <ariel@world.std.com>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ip-parametersReynolds & Postel [Page 67]
RFC 1700 Assigned Numbers October 1994ICMP TYPE NUMBERSThe Internet Control Message Protocol (ICMP) has many messages thatare identified by a "type" field.Type Name Reference---- ------------------------- --------- 0 Echo Reply [RFC792] 1 Unassigned [JBP] 2 Unassigned [JBP] 3 Destination Unreachable [RFC792] 4 Source Quench [RFC792] 5 Redirect [RFC792] 6 Alternate Host Address [JBP] 7 Unassigned [JBP] 8 Echo [RFC792] 9 Router Advertisement [RFC1256] 10 Router Selection [RFC1256] 11 Time Exceeded [RFC792] 12 Parameter Problem [RFC792] 13 Timestamp [RFC792] 14 Timestamp Reply [RFC792] 15 Information Request [RFC792] 16 Information Reply [RFC792] 17 Address Mask Request [RFC950] 18 Address Mask Reply [RFC950] 19 Reserved (for Security) [Solo] 20-29 Reserved (for Robustness Experiment) [ZSu] 30 Traceroute [RFC1393] 31 Datagram Conversion Error [RFC1475] 32 Mobile Host Redirect [David Johnson] 33 IPv6 Where-Are-You [Bill Simpson] 34 IPv6 I-Am-Here [Bill Simpson] 35 Mobile Registration Request [Bill Simpson] 36 Mobile Registration Reply [Bill Simpson] 37-255 Reserved [JBP]Many of these ICMP types have a "code" field. Here we list the typesagain with their assigned code fields.Type Name Reference---- ------------------------- --------- 0 Echo Reply [RFC792] Codes 0 No Code 1 Unassigned [JBP]Reynolds & Postel [Page 68]
RFC 1700 Assigned Numbers October 1994 2 Unassigned [JBP] 3 Destination Unreachable [RFC792] Codes 0 Net Unreachable 1 Host Unreachable 2 Protocol Unreachable 3 Port Unreachable 4 Fragmentation Needed and Don't Fragment was Set 5 Source Route Failed 6 Destination Network Unknown 7 Destination Host Unknown 8 Source Host Isolated 9 Communication with Destination Network is Administratively Prohibited 10 Communication with Destination Host is Administratively Prohibited 11 Destination Network Unreachable for Type of Service 12 Destination Host Unreachable for Type of Service 4 Source Quench [RFC792] Codes 0 No Code 5 Redirect [RFC792] Codes 0 Redirect Datagram for the Network (or subnet) 1 Redirect Datagram for the Host 2 Redirect Datagram for the Type of Service and Network 3 Redirect Datagram for the Type of Service and Host 6 Alternate Host Address [JBP] Codes 0 Alternate Address for Host 7 Unassigned [JBP] 8 Echo [RFC792] Codes 0 No Code 9 Router Advertisement [RFC1256] CodesReynolds & Postel [Page 69]
RFC 1700 Assigned Numbers October 1994 0 No Code 10 Router Selection [RFC1256] Codes 0 No Code 11 Time Exceeded [RFC792] Codes 0 Time to Live exceeded in Transit 1 Fragment Reassembly Time Exceeded 12 Parameter Problem [RFC792] Codes 0 Pointer indicates the error 1 Missing a Required Option [RFC1108] 2 Bad Length 13 Timestamp [RFC792] Codes 0 No Code 14 Timestamp Reply [RFC792] Codes 0 No Code 15 Information Request [RFC792] Codes 0 No Code 16 Information Reply [RFC792] Codes 0 No Code 17 Address Mask Request [RFC950] Codes 0 No Code 18 Address Mask Reply [RFC950]Reynolds & Postel [Page 70]
RFC 1700 Assigned Numbers October 1994 Codes 0 No Code 19 Reserved (for Security) [Solo] 20-29 Reserved (for Robustness Experiment) [ZSu] 30 Traceroute [RFC1393] 31 Datagram Conversion Error [RFC1475] 32 Mobile Host Redirect [David Johnson] 33 IPv6 Where-Are-You [Bill Simpson] 34 IPv6 I-Am-Here [Bill Simpson] 35 Mobile Registration Request [Bill Simpson] 36 Mobile Registration Reply [Bill Simpson]REFERENCES[RFC792] Postel, J., "Internet Control Message Protocol", STD 5,RFC 792, USC/Information Sciences Institute, September 1981.[RFC950] Mogul, J., and J. Postel, "Internet Standard Subnetting Procedure", STD 5,RFC 950, Stanford, USC/Information Sciences Institute, August 1985.[RFC1108] Kent, S., "U.S. Department of Defense Security Options for the Internet Protocol",RFC 1108, November 1991.[RFC1256] Deering, S., Editor, "ICMP Router Discovery Messages",RFC1256, Xerox PARC, September 1991.[RFC1393] Malkin, G., "Traceroute Using an IP Option",RFC 1393, Xylogics, Inc., January 1993.[RFC1475] Ullmann, R., "TP/IX: The Next Internet",RFC 1475, Process Software Corporation, June 1993.PEOPLE[JBP] Jon Postel <postel@isi.edu>[David Johnson]Reynolds & Postel [Page 71]
RFC 1700 Assigned Numbers October 1994[Bill Simpson] <Bill.Simpson@um.cc.umich.edu> September, 1994.[Solo][ZSu] Zaw-Sing Su <ZSu@TSCA.ISTC.SRI.COM>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/icmp-parametersReynolds & Postel [Page 72]
RFC 1700 Assigned Numbers October 1994TCP OPTION NUMBERSThe Transmission Control Protocol (TCP) has provision for optionalheader fields identified by an option kind field. Options 0 and 1 areexactly one octet which is their kind field. All other options havetheir one octet kind field, followed by a one octet length field,followed by length-2 octets of option data.Kind Length Meaning Reference---- ------ ------------------------------- --------- 0 - End of Option List [RFC793] 1 - No-Operation [RFC793] 2 4 Maximum Segment Lifetime [RFC793] 3 3 WSOPT - Window Scale [RFC1323] 4 2 SACK Permitted [RFC1072] 5 N SACK [RFC1072] 6 6 Echo (obsoleted by option 8) [RFC1072] 7 6 Echo Reply (obsoleted by option 8)[RFC1072] 8 10 TSOPT - Time Stamp Option [RFC1323] 9 2 Partial Order Connection Permitted[RFC1693] 10 5 Partial Order Service Profile [RFC1693] 11 CC [Braden] 12 CC.NEW [Braden] 13 CC.ECHO [Braden] 14 3 TCP Alternate Checksum Request [RFC1146] 15 N TCP Alternate Checksum Data [RFC1146] 16 Skeeter [Knowles] 17 Bubba [Knowles] 18 3 Trailer Checksum Option [Subbu & Monroe]TCP ALTERNATE CHECKSUM NUMBERSNumber Description Reference------- ------------------------------- ---------- 0 TCP Checksum [RFC-1146] 1 8-bit Fletchers's algorithm [RFC-1146] 2 16-bit Fletchers's algorithm [RFC-1146] 3 Redundant Checksum Avoidance [Kay]REFERENCES[KAY] Kay, J. and Pasquale, J., "Measurement, Analysis, and Improvement of UDP/IP Throughput for the DECstation 5000," Proceedings of the Winter 1993 Usenix Conference, January 1993 (available for anonymous FTP inReynolds & Postel [Page 73]
RFC 1700 Assigned Numbers October 1994 ucsd.edu:/pub/csl/fastnet/fastnet.tar.Z). <jkay@ucsd.edu>[RFC793] Postel, J., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", STD 7,RFC 793, DARPA, September 1981.[RFC1323] Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for High Performance",RFC 1323, LBL, ISI, Cray Research, May 1992.[RFC1072] Jacobson, V., and R. Braden, "TCP Extensions for Long-Delay Paths",RFC 1072, LBL, ISI, October 1988.[RFC1693] ?????[RFC1146] Zweig, J., and C. Partridge, "TCP Alternate Checksum Options",RFC 1146, UIUC, BBN, March 1990.PEOPLE[Braden] Bob Braden <braden@isi.edu>[Knowles] Stev Knowles <stev@ftp.com>[Kay] J. Kay <jkay@ucsd.edu>[Subbu & Monroe] <mystery contact>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/tcp-parametersReynolds & Postel [Page 74]
RFC 1700 Assigned Numbers October 1994TELNET OPTIONSThe Telnet Protocol has a number of options that may be negotiated.These options are listed here. "Internet Official Protocol Standards"(STD 1) provides more detailed information.Options Name References------- ----------------------- ---------- 0 Binary Transmission [RFC856,JBP] 1 Echo [RFC857,JBP] 2 Reconnection [NIC50005,JBP] 3 Suppress Go Ahead [RFC858,JBP] 4 Approx Message Size Negotiation [ETHERNET,JBP] 5 Status [RFC859,JBP] 6 Timing Mark [RFC860,JBP] 7 Remote Controlled Trans and Echo [RFC726,JBP] 8 Output Line Width [NIC50005,JBP] 9 Output Page Size [NIC50005,JBP] 10 Output Carriage-Return Disposition [RFC652,JBP] 11 Output Horizontal Tab Stops [RFC653,JBP] 12 Output Horizontal Tab Disposition [RFC654,JBP] 13 Output Formfeed Disposition [RFC655,JBP] 14 Output Vertical Tabstops [RFC656,JBP] 15 Output Vertical Tab Disposition [RFC657,JBP] 16 Output Linefeed Disposition [RFC657,JBP] 17 Extended ASCII [RFC698,JBP] 18 Logout [RFC727,MRC] 19 Byte Macro [RFC735,JBP] 20 Data Entry Terminal [RFC1043,RFC732,JBP] 22 SUPDUP [RFC736,RFC734,MRC] 22 SUPDUP Output [RFC749,MRC] 23 Send Location [RFC779,EAK1] 24 Terminal Type [RFC1091,MS56] 25 End of Record [RFC885,JBP] 26 TACACS User Identification [RFC927,BA4] 27 Output Marking [RFC933,SXS] 28 Terminal Location Number [RFC946,RN6] 29 Telnet 3270 Regime [RFC1041,JXR] 30 X.3 PAD [RFC1053,SL70] 31 Negotiate About Window Size [RFC1073,DW183] 32 Terminal Speed [RFC1079,CLH3] 33 Remote Flow Control [RFC1372,CLH3] 34 Linemode [RFC1184,DB14] 35 X Display Location [RFC1096,GM23] 36 Environment Option [RFC1408,DB14] 37 Authentication Option [RFC1409,DB14] 38 Encryption Option [DB14] 39 New Environment Option [RFC1572,DB14]Reynolds & Postel [Page 75]
RFC 1700 Assigned Numbers October 1994 40 TN3270E [RFC1647] 255 Extended-Options-List [RFC861,JBP]Telnet Authentication TypesIn [RFC1409], a list of authentication types is introduced. Additionsto the list are registerd by the IANA and documented here.Type Description Reference 0 NULL [RFC1409] 1 KERBEROS_V4 [RFC1409] 2 KERBEROS_V5 [RFC1409] 3 SPX [RFC1409] 4-5 Unassigned 6 RSA [RFC1409] 7-9 Unassigned 10 LOKI [RFC1409] 11 SSA [Schoch]REFERENCES[ETHERNET] "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.[NIC50005] DDN Protocol Handbook, "Telnet Reconnection Option", "Telnet Output Line Width Option", "Telnet Output Page Size Option", NIC 50005, December 1985.[RFC652] Crocker, D., "Telnet Output Carriage-Return Disposition Option",RFC 652, UCLA-NMC, October 1974.[RFC653] Crocker, D., "Telnet Output Horizontal Tabstops Option",RFC 653, UCLA-NMC, October 1974.[RFC654] Crocker, D., "Telnet Output Horizontal Tab Disposition Option",RFC 654, UCLA-NMC, October 1974.[RFC655] Crocker, D., "Telnet Output Formfeed Disposition Option",RFC 655, UCLA-NMC, October 1974.Reynolds & Postel [Page 76]
RFC 1700 Assigned Numbers October 1994[RFC656] Crocker, D., "Telnet Output Vertical Tabstops Option",RFC 656, UCLA-NMC, October 1974.[RFC657] Crocker, D., "Telnet Output Vertical Tab Disposition Option",RFC 657, UCLA-NMC, October 1974.[RFC658] Crocker, D., "Telnet Output Linefeed Disposition",RFC 658, UCLA-NMC, October 1974.[RFC698] Tovar, "Telnet Extended ASCII Option",RFC 698, Stanford University-AI, July 1975.[RFC726] Postel, J. and D. Crocker, "Remote Controlled Transmission and Echoing Telnet Option",RFC 726, SRI-ARC, UC Irvine, March 1977.[RFC727] Crispin, M., "Telnet Logout Option",RFC 727, Stanford University-AI, April 1977.[RFC734] Crispin, M., "SUPDUP Protocol",RFC 734, Stanford, October 1977.[RFC735] Crocker, D. and R. Gumpertz, "Revised Telnet Byte Marco Option",RFC 735, Rand, CMU, November 1977.[RFC736] Crispin, M., "Telnet SUPDUP Option", Stanford University-AI,RFC 736, Stanford, October 1977.[RFC749] Greenberg, B., "Telnet SUPDUP-OUTPUT Option",RFC 749, MIT-Multics, September 1978.[RFC779] Killian, E., "Telnet Send-Location Option",RFC 779, LLL, April 1981.[RFC856] Postel, J. and J. Reynolds, "Telnet Binary Transmission", STD 27,RFC 856, USC/Information Sciences Institute, May 1983.[RFC857] Postel, J. and J. Reynolds, "Telnet Echo Option", STD 28,RFC857, USC/Information Sciences Institute, May 1983.[RFC858] Postel, J. and J. Reynolds, "Telnet Suppress Go Ahead Option", STD 29,RFC 858, USC/Information Sciences Institute, May 1983.[RFC859] Postel, J. and J. Reynolds, "Telnet Status Option", STD 30,RFC 859, USC/Information Sciences Institute, May 1983.Reynolds & Postel [Page 77]
RFC 1700 Assigned Numbers October 1994[RFC860] Postel, J. and J. Reynolds, "Telnet Timing Mark Option", STD 31,RFC 860, USC/Information Sciences Institute, May 1983.[RFC861] Postel, J. and J. Reynolds, "Telnet Extended Options - List Option", STD 32,RFC 861, USC/Information Sciences Institute, May 1983.[RFC885] Postel, J., "Telnet End of Record Option",RFC 885, USC/Information Sciences Institute, December 1983.[RFC927] Anderson, B., "TACACS User Identification Telnet Option",RFC 927, BBN, December 1984.[RFC933] Silverman, S., "Output Marking Telnet Option",RFC 933, MITRE, January 1985.[RFC946] Nedved, R., "Telnet Terminal Location Number Option",RFC 946, Carnegie-Mellon University, May 1985.[RDC1041] Rekhter, J., "Telnet 3270 Regime Option",RFC 1041, IBM, January 1988.[RFC1043] Yasuda, A., and T. Thompson, "TELNET Data Entry Terminal Option DODIIS Implementation",RFC 1043, DIA, February 1988.[RFC1053] Levy, S., and T. Jacobson, "Telnet X.3 PAD Option",RFC 1053, Minnesota Supercomputer Center, April 1988.[RFC1073] Waitzman, D., "Telnet Window Size Option",RFC 1073, BBN STC, October, 1988.[RFC1079] Hedrick, C., "Telnet Terminal Speed Option",RFC 1079, Rutgers University, December 1988.[RFC1091] VanBokkelen, J., "Telnet Terminal Type Option",RFC 1091, FTP Software, Inc., February 1989.[RFC1096] Marcy, G., "Telnet X Display Location Option",RFC 1096, Carnegie Mellon University, March 1989.[RFC1184] Borman, D., Editor, "Telnet Linemode Option",RFC 1184, Cray Research, Inc., October 1990.[RFC1372] Hedrick, C., and D. Borman, "Telnet Remote Flow Control Option",RFC 1372, Rutgers University, Cray Research, Inc., October 1992.Reynolds & Postel [Page 78]
RFC 1700 Assigned Numbers October 1994[RFC1408] Borman, D., Editor, "Telnet Environment Option",RFC 1408, Cray Research, Inc., January 1993.[RFC1409] Borman, D., Editor, "Telnet Authentication Option",RFC1409, Cray Research, Inc., January 1993.[RFC1572] Alexander, S., Editor, "Telnet Environment Option",RFC1572, Lachman Technology, Inc., January 1994.[RFC1647] Kelly, B., "TN3270 Enhancements",RFC1647, Auburn University, July 1994.PEOPLE[BA4] Brian Anderson <baanders@CCQ.BBN.CO>[CLH3] Charles Hedrick <HEDRICK@ARAMIS.RUTGERS.EDU>[DB14] Dave Borman <dab@CRAY.COM>[DW183] David Waitzman <dwaitzman@BBN.COM>[EAK4] Earl Kill <EAK@MORDOR.S1.GOV>[GM23] Glenn Marcy <Glenn.Marcy@A.CS.CMU.EDU>[JBP] Jon Postel <postel@isi.edu>[MRC] Mark Crispin <MRC@WSMR-SIMTEL20.ARMY.MIL>[MS56] Marvin Solomon <solomon@CS.WISC.EDU>[RN6] Rudy Nedved <Rudy.Nedved@CMU-CS-A.>[Schoch] Steven Schoch <schoch@sheba.arc.nasa.gov>[SL70] Stuart Levy <slevy@UC.MSC.UMN.EDU>[SXS] Steve Silverman <Blankert@MITRE-GATEWAY.ORG>[YXR] Yakov Rekhter <Yakov@IBM.COM>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/telnet-optionsReynolds & Postel [Page 79]
RFC 1700 Assigned Numbers October 1994DOMAIN NAME SYSTEM PARAMETERSThe Internet Domain Naming System (DOMAIN) includes severalparameters. These are documented in [RFC1034] and [RFC1035]. TheCLASS parameter is listed here. The per CLASS parameters are definedin separate RFCs as indicated.Domain System Parameters:Decimal Name References-------- ---- ---------- 0 Reserved [PM1] 1 Internet (IN) [RFC1034,PM1] 2 Unassigned [PM1] 3 Chaos (CH) [PM1] 4 Hessoid (HS) [PM1] 5-65534 Unassigned [PM1] 65535 Reserved [PM1]In the Internet (IN) class the following TYPEs and QTYPEs are defined:TYPE value and meaningA 1 a host address [RFC1035]NS 2 an authoritative name server [RFC1035]MD 3 a mail destination (Obsolete - use MX) [RFC1035]MF 4 a mail forwarder (Obsolete - use MX) [RFC1035]CNAME 5 the canonical name for an alias [RFC1035]SOA 6 marks the start of a zone of authority [RFC1035]MB 7 a mailbox domain name (EXPERIMENTAL) [RFC1035]MG 8 a mail group member (EXPERIMENTAL) [RFC1035]MR 9 a mail rename domain name (EXPERIMENTAL)[RFC1035]NULL 10 a null RR (EXPERIMENTAL) [RFC1035]WKS 11 a well known service description [RFC1035]PTR 12 a domain name pointer [RFC1035]HINFO 13 host information [RFC1035]MINFO 14 mailbox or mail list information [RFC1035]MX 15 mail exchange [RFC1035]TXT 16 text strings [RFC1035]RP 17 for Responsible Person [RFC1183]AFSDB 18 for AFS Data Base location [RFC1183]X25 19 for X.25 PSDN address [RFC1183]ISDN 20 for ISDN address [RFC1183]RT 21 for Route Through [RFC1183]NSAP 22 for NSAP address, NSAP style A record [RFC1348]NSAP-PTR 23 for domain name pointer, NSAP style [RFC1348]Reynolds & Postel [Page 80]
RFC 1700 Assigned Numbers October 1994SIG 24 for security signature [Donald Eastlake]KEY 25 for security key [Donald Eastlake]PX 26 X.400 mail mapping information [RFC1664]GPOS 27 Geographical Position [Craig Farrell]AAAA 28 IP6 Address [Susan Thomson]AXFR 252 transfer of an entire zone [RFC1035]MAILB 253 mailbox-related RRs (MB, MG or MR) [RFC1035]MAILA 254 mail agent RRs (Obsolete - see MX) [RFC1035]* 255 A request for all records [RFC1035]REFERENCES[RFC1034] Mockapetris, P., "Domain Names - Concepts and Facilities", STD 13,RFC 1034, USC/Information Sciences Institute, November 1987.[RFC1035] Mockapetris, P., "Domain Names - Implementation and Specification", STD 13,RFC 1035, USC/Information Sciences Institute, November 1987.[RFC1183] Everhart, C., Mamakos, L., Ullmann, R., and P. Mockapetris, Editors, "New DNS RR Definitions",RFC 1183, Transarc, University of Maryland, Prime Computer, USC/Information Sciences Institute, October 1990.[RFC1348] Manning, B., "DNS NSAP RRs",RFC 1348, Rice University, July 1992.[RFC1664] Allocchio, C., Bonito, A., Cole, B., Giordano, S., and R. Hagens, "Using the Internet DNS to DistributeRFC1327 Mail Address Mapping Tables", GARR-Italy, Cisco Systems Inc., Centro Svizzero Calcolo Scientifico, Advanced Network & Services, August 1994.PEOPLE[Susan Thomson] Susan Thomson <set@swift.bellcore.com>[PM1] Paul Mockapetris <pvm@isi.edu>[Donald Eastlake] Donald E. Eastlake, III <dee@ranger.enet.dec.com>Reynolds & Postel [Page 81]
RFC 1700 Assigned Numbers October 1994[Craig Farrell][]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/dns-parametersReynolds & Postel [Page 82]
RFC 1700 Assigned Numbers October 1994MAIL ENCODING HEADER FIELD KEYWORDS[RFC1505] specifies an initial list of keywords for the experimentalencoding header field (EHF-MAIL), and provides that additionalkeywords may be registered with the IANA.Keyword Description Reference_______ ___________ ____________EDIFACT EDIFACT format [RFC1505]EDI-X12 EDI X12 format [ANSI-X12]EVFU FORTRAN format [RFC1505]FS File System format [RFC1505]Hex Hex binary format [RFC1505]LZJU90 LZJU90 format [RFC1505]LZW LZW format [RFC1505]Message Encapsulated Message [RFC822]PEM, PEM-Clear Privacy Enhanced Mail [RFC1421]PGP Pretty Good Privacy [RFC1505]Postscript Postscript format [POSTSCRIPT]Shar Shell Archive format [RFC1505]Signature Signature [RFC1505]Tar Tar format [RFC1505]Text Text [IS-10646]uuencode uuencode format [RFC1505]URL external URL-reference [RFC1505]MAIL ENCRYPTION TYPES[RFC822] specifies that Encryption Types for mail may be assigned.There are currently noRFC 822 encryption types assigned. Please useinstead the Mail Privacy procedures defined in [RFC1421,RFC1422,RFC1423].ESMTP MAIL KEYWORDS[RFC1651] specifies that extension to SMTP can be identified withkeywords.Keywords Description ReferenceReynolds & Postel [Page 83]
RFC 1700 Assigned Numbers October 1994------------ -------------------------------- ---------SEND Send as mail [RFC821]SOML Send as mail or terminal [RFC821]SAML Send as mail and terminal [RFC821]EXPN Expand the mailing list [RFC821]HELP Supply helpful information [RFC821]TURN Turn the operation around [RFC821]8BITMIME Use 8-bit data [RFC1652]SIZE Message size declaration [RFC1653]VERB Verbose [Eric Allman]ONEX One message transaction only [Eric Allman]MAIL EXTENSION TYPESThe Simple Mail Transfer Protocol [RFC821] specifies a set ofcommands or services for mail transfer. A general procedure forextending the set of services is defined in [RFC1651]. The set ofservice extensions is listed here.Service Ext EHLO Keyword Parameters Verb Reference----------- ------------ ---------- ---------- ---------Send SEND none SEND [RFC821]Send or Mail SOML none SOML [RFC821]Send and Mail SAML none SAML [RFC821]Expand EXPN none EXPN [RFC821]Help HELP none HELP [RFC821]Turn TURN none TURN [RFC821]8 Bit MIME 8BITMIME none none [RFC1652]Size SIZE number none [RFC1653]MAIL SYSTEM NAMESIn some places, an identification of other mail systems is used.One of these is in "The COSINE and Internet X.500 Schema" (section9.3.18) [RFC1274]. The mail system names listed here are used as thelegal values in that schema under the "otherMailbox" attribute"mailboxType" type (which must be a PrintableString).Another place is in "Mapping between X.400(1988) / ISO 10021 and RFC822" (section 4.2.2) [RFC1327]. The names listed here are used asReynolds & Postel [Page 84]
RFC 1700 Assigned Numbers October 1994the legal values in that schema under the "std-or-address" attribute"registered-dd-type" type (which must be a "key-string").Note that key-string = <a-z, A-Z, 0-9, and "-" >.Mail System Name Description Reference---------------- ------------------------------- ---------mcimail MCI MailMAIL TRANSMISSION TYPESThe Simple Mail Transfer Protocol [RFC821] and the Standard for theFormat of ARPA Internet Text Messages [RFC822] specify that a set of"Received" lines will be prepended to the headers of electronic mailmessages as they are transported through the Internet. These receivedline may optionally include either or both a "via" phrase and/or a"with" phrase. The legal values for the phrases are listed here. Thevia phrase is intended to indicate the link or physical medium overwhich the message was transferred. The with phrase is intended toindicate the protocol or logical process that was used to transfer themessage.VIA link types Description Reference-------------- ---------------------------- ---------UUCP Unix-to-Unix Copy Program [???]WITH protocol types Description Reference------------------- ---------------------------- ---------SMTP Simple Mail Transfer Protocol [RFC821]ESMTP SMTP with Service Extensions [RFC1651]REFERENCES[ANSI-X12][POSTSCRIPT] Adobe Systems Inc., "PostScript Langpuage ReferenceManual", 2nd Edition, 2nd Printing, January 1991.[IS-10646]Reynolds & Postel [Page 85]
RFC 1700 Assigned Numbers October 1994[RFC821] Postel, J., "Simple Mail Transfer Protocol", STD 10,RFC 821, USC/Information Sciences Institute, August 1982.[RFC822] Crocker, D., "Standard for the Format of ARPA-Internet Text Messages", STD 11,RFC 822, UDEL, August 1982.[RFC1274] Barker, P., and S. Kille, "The COSINE and Internet X.500 Schema",RFC 1274, University College London, November 1991.[RFC1327] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021 andRFC 822",RFC 1327, University College London, May 1992.[RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic Mail: Part I: Message Encipherment and Authentication Procedures",RFC 1421, IAB IRTF PSRG, IETF PEM WG, February 1993.[RFC1422] Kent, S., "Privacy Enhancement for Internet Electronic Mail: Part II -- Certificate-Based Key Management", BBN, IAB IRTF PSRG, IETF PEM, February 1993.[RFC1423] Balenson, D., "Privacy Enhancement for Internet Electronic Mail: Part III -- Algorithms, Modes, and Identifiers",RFC 1423, TIS, IAB IRTF PSRG, IETF PEM WG, February 1993.[RFC1505] Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header Field for Internet Messages",RFC 1505, AKC Consulting, Computervision Corporation, August 1993.[RFC1651] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker, "SMTP Service Extensions",RFC 1651, MCI, Innosoft, Dover Beach Consulting, Inc., Network Management Associates, Inc., Silicon Graphics, Inc., July 1994.[RFC1652] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker, "SMTP Service Extension for 8bit-MIMEtransport",RFC 1652, MCI, Innosoft, Dover Beach Consulting, Inc., Network Management Associates, Inc., Silicon Graphics, Inc., July 1994.[RFC1653] Klensin, J., Freed, N., and K. Moore, "SMTP Service Extension for Message Size Declaration",RFC 1653, MCI, Innosoft, University of Tennessee, July 1994.PEOPLEReynolds & Postel [Page 86]
RFC 1700 Assigned Numbers October 1994[Eric Allman][]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/mail-parametersReynolds & Postel [Page 87]
RFC 1700 Assigned Numbers October 1994BOOTP AND DHCP PARAMETERSThe Bootstrap Protocol (BOOTP) [RFC951] describes an IP/UDPbootstrap protocol (BOOTP) which allows a diskless client machine todiscover its own IP address, the address of a server host, and thename of a file to be loaded into memory and executed. The DynamicHost Configuration Protocol (DHCP) [RFC1531] provides a framework forautomatic configuration of IP hosts. The "DHCP Options and BOOTPVendor Information Extensions" [RFC1533] describes the additions to theBootstrap Protocol (BOOTP) which can also be used as options with theDynamic Host Configuration Protocol (DHCP).BOOTP Vendor Extensions and DHCP Options are listed below: Tag Name Data Length Meaning --- ---- ----------- ------- 0 Pad 0 None 1 Subnet Mask 4 Subnet Mask Value 2 Time Offset 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 chunks 14 Merit Dump File Client to dump and name the file to dump it to 15 Domain Name N The DNS domain name of the client 16 Swap Server N Swap Server addeess 17 Root Path N Path name for root disk 18 Extension File N Path name for more BOOTP info 19 Forward On/Off 1 Enable/Disable IP Forwarding 20 SrcRte On/Off 1 Enable/Disable Source Routing 21 Policy Filter N Routing Policy Filters 22 Max DG Assembly 2 Max Datagram Reassembly Size 23 Default IP TTL 1 Default IP Time to Live 24 MTU Timeout 4 Path MTU Aging Timeout 25 MTU Plateau N Path MTU Plateau TableReynolds & Postel [Page 88]
RFC 1700 Assigned Numbers October 1994 26 MTU Interface 2 Interface MTU Size 27 MTU Subnet 1 All Subnets are Local 28 Broadcast Address 4 Broadcast Address 29 Mask Discovery 1 Perform Mask Discovery 30 Mask Supplier 1 Provide Mask to Others 31 Router Discovery 1 Perform Router Discovery 32 Router Request 4 Router Solicitation Address 33 Static Route N Static Routing Table 34 Trailers 1 Trailer Encapsulation 35 ARP Timeout 4 ARP Cache Timeout 36 Ethernet 1 Ethernet Encapsulation 37 Default TCP TTL 1 Default TCP Time to Live 38 Keepalive Time 4 TCP Keepalive Interval 39 Keepalive Data 1 TCP Keepalive Garbage 40 NIS Domain N NIS Domain Name 41 NIS Servers N NIS Server Addresses 42 NTP Servers N NTP Server Addresses 43 Vendor Specific N Vendor Specific Information 44 NETBIOS Name Srv N NETBIOS Name Servers 45 NETBIOS Dist Srv N NETBIOS Datagram Distribution 46 NETBIOS Note Type 1 NETBIOS Note Type 47 NETBIOS Scope N NETBIOS Scope 48 X Window Font N X Window Font Server 49 X Window Manmager N X Window Display Manager 50 Address Request 4 Requested IP Address 51 Address Time 4 IP Address Lease Time 52 Overload 1 Overloaf "sname" or "file" 53 DHCP Msg Type 1 DHCP Message Type 54 DHCP Server Id 4 DHCP Server Identification 55 Parameter List N Parameter Request List 56 DHCP Message N DHCP Error Message 57 DHCP Max Msg Size 2 DHCP Maximum Message Size 58 Renewal Time 4 DHCP Renewal (T1) Time 59 Rebinding Time 4 DHCP Rebinding (T2) Time 60 Class Id N Class Identifier 61 Client Id N Client Identifier 62 Netware/IP Domain N Netware/IP Domain Name 63 Netware/IP Option N Netware/IP sub Options 64-127 Unassigned 128-154 Reserved 255 End 0 NoneREFERENCESReynolds & Postel [Page 89]
RFC 1700 Assigned Numbers October 1994[RFC951] Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)",RFC-951, Stanford and SUN Microsytems, September 1985.[RFC1531] Droms, R., "Dynamic Host Configuration Protocol", Bucknell University, October 1993.[RFC1533] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor Extensions", Lachman Technology, Inc., Bucknell University, October 1993.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/bootp-and-dhcp-parametersReynolds & Postel [Page 90]
RFC 1700 Assigned Numbers October 1994ADDRESS FAMILY NUMBERSSeveral protocols deal with multiple address families. The 16-bitassignments are listed here.Number Description Reference------ ---------------------------------------------------- --------- 0 Reserved 1 IP (IP version 4) 2 IP6 (IP version 6) 3 NSAP 4 HDLC (8-bit multidrop) 5 BBN 1822 6 802 (includes all 802 media plus Ethernet "canonical format") 7 E.163 8 E.164 (SMDS, Frame Relay, ATM) 9 F.69 (Telex) 10 X.121 (X.25, Frame Relay) 11 IPX 12 Appletalk 13 Decnet IV 14 Banyan Vines 65535 Reserved[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/address-family-numbersReynolds & Postel [Page 91]
RFC 1700 Assigned Numbers October 1994FOOBAR AF NUMBERSIn the FTP Operation Over Big Address Records (FOOBAR) Protocol[RFC1639] there is a field, called "address family" or "af", toidentify the lower level protocol addresses in use. This is an 8 bitfield. The first 16 assignments (0-15) of the af value are exactlythe same as the IP Version number. The assignment for values 16-255are listed here.Assigned FOOBAR Address FamiliesDecimal Keyword Address Family References------- ------- -------------- ---------- 16 IPX Novell IPX17-254 Unassigned 255 ReservedREFERENCES[RFC1639] Piscitello, D., "FTP Operation Over Big Address Records (FOOBAR)", Core Competence, Inc., June 1994.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/foobar-af-numbersReynolds & Postel [Page 92]
RFC 1700 Assigned Numbers October 1994DIRECTORY SYSTEM NAMESIn the representation of distinquished names (and possibly othercontexts) of the X.500 Directory system, several unique keywords maybe necessary. For example, in the string representation ofdistinguished names [RFC1485].Keyword Attribute (X.520 keys)------- --------------------------------- CN CommonName L LocalityName ST StateOrProvinceName O OrganizationName OU OrganizationalUnitName C CountryNameREFERENCES[RFC1485] Hardcastle-Kille, S., "A String Representation of Distinguished Names (OSI-DS 23 (v5))",RFC1485, ISODE Consortium, July 1993.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/directory-system-namesReynolds & Postel [Page 93]
RFC 1700 Assigned Numbers October 1994PUBLISHER IDENTIFICATION CODEThe RFC "A Format for E-Mailing Bibliographic Records" [RFC1357]establishs a "publisher-ID" code. The IANA registry of these codes islisted here.Code Publisher Reference------ ------------------------------------------------------- ---------DUMMY for testing only [RFC1357]TEST for testing only [RFC1357]ISI Information Sciences Institute [JBP] of the University of Southern CaliforniaUMCS University of Manchester Computer Science Department [TXC]REFERENCES[RFC1357] Cohen, D., Editor, "A Format for E-mailing Bibliographic Records",RFC 1357, USC/Information Sciences Institute, July 1992.PEOPLE[JBP] Jon Postel <postel@isi.edu>[TXC] Tim Clement <timc@cs.man.ac.uk>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/publisher-idReynolds & Postel [Page 94]
RFC 1700 Assigned Numbers October 1994OSPF AUTHENTICATION CODESThe Open Shotrest Path First (OSPF) protocols has a provision forauthentication, and the type of authentication can me indicated by acode number. The following are the registered authentication codes.Code Authentication Method Reference---- --------------------- --------- 0 No Authentication [RFC1583] 1 Simple Password Authentication [RFC1583]2-65535 ReservedREFERENCES[RFC1583] Moy, J., "OSPF Version 2",RFC 1583, Proteon, Inc., March 1994.[RFC1584] Moy, J., "Multicast Extensions to OSPF",RFC 1584, Proteon, Inc., March 1994.[RFC1585] Moy, J., "MOSPF: Analysis and Experience",RFC 1585, Proteon, Inc., March 1994.[RFC1586] deSouza, O., and M. Rodrigues, "Guidelines for Running OSPF Over Frame Relay Networks",RFC 1586, AT&T Bell Laboratories, March 1994.[RFC1587] Coltun, R., and V. Fuller, "The OSPF NSSA Option",RFC 1587, RainbowBridge Communications, BARRNet, March 1994.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ospf-authentication-codesReynolds & Postel [Page 95]
RFC 1700 Assigned Numbers October 1994MEDIA TYPES[RFC1521] specifies that Content Types, Content Subtypes, CharacterSets, Access Types, and Conversion values for MIME mail will beassigned and listed by the IANA.Content Types and Subtypes--------------------------Type Subtype Description Reference---- ------- ----------- ---------text plain [RFC1521,NSB] richtext [RFC1521,NSB] tab-separated-values [Paul Lindner]multipart mixed [RFC1521,NSB] alternative [RFC1521,NSB] digest [RFC1521,NSB] parallel [RFC1521,NSB] appledouble [MacMime,Patrik Faltstrom] header-set [Dave Crocker]messagerfc822 [RFC1521,NSB] partial [RFC1521,NSB] external-body [RFC1521,NSB] news [RFC 1036, Henry Spencer]application octet-stream [RFC1521,NSB] postscript [RFC1521,NSB] oda [RFC1521,NSB] atomicmail [atomicmail,NSB] andrew-inset [andrew-inset,NSB] slate [slate,terry crowley] wita [Wang Info Transfer,Larry Campbell] dec-dx [Digital Doc Trans, Larry Campbell] dca-rft [IBM Doc Content Arch, Larry Campbell] activemessage [Ehud Shapiro] rtf [Paul Lindner] applefile [MacMime,Patrik Faltstrom] mac-binhex40 [MacMime,Patrik Faltstrom] news-message-id [RFC1036, Henry Spencer] news-transmission [RFC1036, Henry Spencer] wordperfect5.1 [Paul Lindner] pdf [Paul Lindner] zip [Paul Lindner] macwriteii [Paul Lindner]Reynolds & Postel [Page 96]
RFC 1700 Assigned Numbers October 1994 msword [Paul Lindner] remote-printing [RFC1486,MTR]image jpeg [RFC1521,NSB] gif [RFC1521,NSB] ief Image Exchange Format [RFC1314] tiff Tag Image File Format [MTR]audio basic [RFC1521,NSB]video mpeg [RFC1521,NSB] quicktime [Paul Lindner]The "media-types" directory contains a subdirectory for each contenttype and each of those directories contains a file for each contentsubtype. |-application- |-audio------- |-image------- |-media-types-|-message----- |-multipart--- |-text-------- |-video------- URL =ftp://ftp.isi.edu/in-notes/iana/assignments/media-typesCharacter Sets--------------All of the character sets listed the section on Character Sets areregistered for use with MIME as MIME Character Sets. Thecorrespondance between the few character sets listed in the MIMEspecification [RFC1521] and the list in that section are:Type Description Reference---- ----------- ---------US-ASCII see ANSI_X3.4-1968 below [RFC1521,NSB]ISO-8859-1 see ISO_8859-1:1987 below [RFC1521,NSB]ISO-8859-2 see ISO_8859-2:1987 below [RFC1521,NSB]ISO-8859-3 see ISO_8859-3:1988 below [RFC1521,NSB]ISO-8859-4 see ISO_8859-4:1988 below [RFC1521,NSB]ISO-8859-5 see ISO_8859-5:1988 below [RFC1521,NSB]ISO-8859-6 see ISO_8859-6:1987 below [RFC1521,NSB]ISO-8859-7 see ISO_8859-7:1987 below [RFC1521,NSB]ISO-8859-8 see ISO_8859-8:1988 below [RFC1521,NSB]ISO-8859-9 see ISO_8859-9:1989 below [RFC1521,NSB]Reynolds & Postel [Page 97]
RFC 1700 Assigned Numbers October 1994Access Types------------Type Description Reference---- ----------- ---------FTP [RFC1521,NSB]ANON-FTP [RFC1521,NSB]TFTP [RFC1521,NSB]AFS [RFC1521,NSB]LOCAL-FILE [RFC1521,NSB]MAIL-SERVER [RFC1521,NSB]Conversion Values-----------------Conversion values or Content Transfer Encodings.Type Description Reference---- ----------- ---------7BIT [RFC1521,NSB]8BIT [RFC1521,NSB]BASE64 [RFC1521,NSB]BINARY [RFC1521,NSB]QUOTED-PRINTABLE [RFC1521,NSB]MIME / X.400 MAPPING TABLESMIME to X.400 Table MIME content-type X.400 Body Part Reference ----------------- ------------------ --------- text/plain charset=us-ascii ia5-text [RFC1494] charset=iso-8859-x EBP - GeneralText [RFC1494] text/richtext no mapping defined [RFC1494] application/oda EBP - ODA [RFC1494] application/octet-stream bilaterally-defined [RFC1494] application/postscript EBP - mime-postscript-body [RFC1494] image/g3fax g3-facsimile [RFC1494] image/jpeg EBP - mime-jpeg-body [RFC1494] image/gif EBP - mime-gif-body [RFC1494] audio/basic no mapping defined [RFC1494] video/mpeg no mapping defined [RFC1494] Abbreviation: EBP - Extended Body PartReynolds & Postel [Page 98]
RFC 1700 Assigned Numbers October 1994X.400 to MIME Table Basic Body Parts X.400 Basic Body Part MIME content-type Reference --------------------- -------------------- --------- ia5-text text/plain;charset=us-ascii [RFC1494] voice No Mapping Defined [RFC1494] g3-facsimile image/g3fax [RFC1494] g4-class1 no mapping defined [RFC1494] teletex no mapping defined [RFC1494] videotex no mapping defined [RFC1494] encrypted no mapping defined [RFC1494] bilaterally-defined application/octet-stream [RFC1494] nationally-defined no mapping defined [RFC1494] externally-defined See Extended Body Parts [RFC1494] X.400 Extended Body Part MIME content-type Reference ------------------------- -------------------- --------- GeneralText text/plain;charset=iso-8859-x[RFC1494] ODA application/oda [RFC1494] mime-postscript-body application/postscript [RFC1494] mime-jpeg-body image/jpeg [RFC1494] mime-gif-body image/gif [RFC1494]REFERENCES[MacMime] Work in Progress.[RFC1036] Horton, M., and R. Adams, "Standard for Interchange of USENET Messages",RFC 1036, AT&T Bell Laboratories, Center for Seismic Studies, December 1987.[RFC1494] Alvestrand, H., and S. Thompson, "Equivalences between 1988 X.400 andRFC-822 Message Bodies",RFC 1494, SINTEF DELAB, Soft*Switch, Inc., August 1993.[RFC1521] Borenstien, N., and N. Freed, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies",RFC 1521, Bellcore, Innosoft, September 1993.PEOPLE[Larry Campbell][Dave Crocker] Dave Crocker <dcrocker@mordor.stanford.edu>Reynolds & Postel [Page 99]
RFC 1700 Assigned Numbers October 1994[Terry Crowley][NSB] Nathaniel Borenstein <nsb@bellcore.com>[MTR] Marshall Rose <mrose@dbc.mtview.ca.us>[Paul Lindner][PXF] Patrik Faltstrom <paf@nada.kth.se>[Ehud Shapiro][Henry Spencer][]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/media-typesReynolds & Postel [Page 100]
RFC 1700 Assigned Numbers October 1994CHARACTER SETSThese are the official names for character sets that may be used inthe Internet and may be referred to in Internet documentation. Thesenames are expressed in ANSI_X3.4-1968 which is commonly calledUS-ASCII or simply ASCII. The character set most commonly use in theInternet and used especially in protocol standards is US-ASCII, thisis strongly encouraged. The use of the name US-ASCII is alsoencouraged.The character set names may be up to 40 characters taken from theprintable characters of US-ASCII. However, no distinction is madebetween use of upper and lower case letters.Character Set Reference------------- ---------Name: ANSI_X3.4-1968 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-6Alias: ANSI_X3.4-1986Alias: ISO_646.irv:1991Alias: ASCIIAlias: ISO646-USAlias: US-ASCIIAlias: usAlias: IBM367Alias: cp367Name: ISO-10646-UCS-2Source: the 2-octet Basic Multilingual Plane, aka Unicode this needs to specify network byte order: the standard does not specify (it is a 16-bit integer space)Name: ISO-10646-UCS-4Source: the full code space. (same comment about byte order, these are 31-bit numbers.Name: ISO-10646-UTF-1Source: Universal Transfer Format (1), this is the multibyte encoding, that subsets ASCII-7. It does not have byte ordering issues.Name: ISO_646.basic:1983 [RFC1345,KXS2]Source: ECMA registryAlias: refReynolds & Postel [Page 101]
RFC 1700 Assigned Numbers October 1994Name: INVARIANT [RFC1345,KXS2]Name: ISO_646.irv:1983 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-2Alias: irvName: BS_4730 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-4Alias: ISO646-GBAlias: gbAlias: ukName: NATS-SEFI [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-8-1Name: NATS-SEFI-ADD [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-8-2Name: NATS-DANO [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-9-1Name: NATS-DANO-ADD [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-9-2Name: SEN_850200_B [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-10Alias: FIAlias: ISO646-FIAlias: ISO646-SEAlias: seName: SEN_850200_C [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-11Alias: ISO646-SE2Alias: se2Name: KS_C_5601-1987 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-149Alias: KS_C_5601-1989Reynolds & Postel [Page 102]
RFC 1700 Assigned Numbers October 1994Alias: KSC_5601Alias: koreanName: ISO-2022-KR [RFC1557,Choi]Source:RFC-1557 (see also KS_C_5601-1987)Name: EUC-KR [RFC1557,Choi]Source:RFC-1557 (see also KS_C_5861-1992)Name: ISO-2022-JP [RFC1468,Murai]Source:RFC-1468Name: ISO-2022-JP-2 [RFC1554,Ohta]Source:RFC-1554Name: JIS_C6220-1969-jp [RFC1345,KXS2]Source: ECMA registryAlias: JIS_C6220-1969Alias: iso-ir-13Alias: katakanaAlias: x0201-7Name: JIS_C6220-1969-ro [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-14Alias: jpAlias: ISO646-JPName: IT [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-15Alias: ISO646-ITName: PT [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-16Alias: ISO646-PTName: ES [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-17Alias: ISO646-ESName: greek7-old [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-18Name: latin-greek [RFC1345,KXS2]Reynolds & Postel [Page 103]
RFC 1700 Assigned Numbers October 1994Source: ECMA registryAlias: iso-ir-19Name: DIN_66003 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-21Alias: deAlias: ISO646-DEName: NF_Z_62-010_(1973) [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-25Alias: ISO646-FR1Name: Latin-greek-1 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-27Name: ISO_5427 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-37Name: JIS_C6226-1978 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-42Name: BS_viewdata [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-47Name: INIS [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-49Name: INIS-8 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-50Name: INIS-cyrillic [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-51Name: ISO_5427:1981 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-54Name: ISO_5428:1980 [RFC1345,KXS2]Source: ECMA registryReynolds & Postel [Page 104]
RFC 1700 Assigned Numbers October 1994Alias: iso-ir-55Name: GB_1988-80 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-57Alias: cnAlias: ISO646-CNName: GB_2312-80 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-58Alias: chineseName: NS_4551-1 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-60Alias: ISO646-NOAlias: noName: NS_4551-2 [RFC1345,KXS2]Source: ECMA registryAlias: ISO646-NO2Alias: iso-ir-61Alias: no2Name: NF_Z_62-010 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-69Alias: ISO646-FRAlias: frName: videotex-suppl [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-70Name: PT2 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-84Alias: ISO646-PT2Name: ES2 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-85Alias: ISO646-ES2Name: MSZ_7795.3 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-86Reynolds & Postel [Page 105]
RFC 1700 Assigned Numbers October 1994Alias: ISO646-HUAlias: huName: JIS_C6226-1983 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-87Alias: x0208Alias: JIS_X0208-1983Name: greek7 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-88Name: ASMO_449 [RFC1345,KXS2]Source: ECMA registryAlias: ISO_9036Alias: arabic7Alias: iso-ir-89Name: iso-ir-90 [RFC1345,KXS2]Source: ECMA registryName: JIS_C6229-1984-a [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-91Alias: jp-ocr-aName: JIS_C6229-1984-b [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-92Alias: ISO646-JP-OCR-BAlias: jp-ocr-bName: JIS_C6229-1984-b-add [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-93Alias: jp-ocr-b-addName: JIS_C6229-1984-hand [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-94Alias: jp-ocr-handName: JIS_C6229-1984-hand-add [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-95Alias: jp-ocr-hand-addReynolds & Postel [Page 106]
RFC 1700 Assigned Numbers October 1994Name: JIS_C6229-1984-kana [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-96Name: ISO_2033-1983 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-98Alias: e13bName: ANSI_X3.110-1983 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-99Alias: CSA_T500-1983Alias: NAPLPSName: ISO_8859-1:1987 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-100Alias: ISO_8859-1Alias: ISO-8859-1Alias: latin1Alias: l1Alias: IBM819Alias: CP819Name: ISO_8859-2:1987 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-101Alias: ISO_8859-2Alias: ISO-8859-2Alias: latin2Alias: l2Name: T.61-7bit [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-102Name: T.61-8bit [RFC1345,KXS2]Alias: T.61Source: ECMA registryAlias: iso-ir-103Name: ISO_8859-3:1988 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-109Alias: ISO_8859-3Alias: ISO-8859-3Alias: latin3Reynolds & Postel [Page 107]
RFC 1700 Assigned Numbers October 1994Alias: l3Name: ISO_8859-4:1988 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-110Alias: ISO_8859-4Alias: ISO-8859-4Alias: latin4Alias: l4Name: ECMA-cyrillic [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-111Name: CSA_Z243.4-1985-1 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-121Alias: ISO646-CAAlias: csa7-1Alias: caName: CSA_Z243.4-1985-2 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-122Alias: ISO646-CA2Alias: csa7-2Name: CSA_Z243.4-1985-gr [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-123Name: ISO_8859-6:1987 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-127Alias: ISO_8859-6Alias: ISO-8859-6Alias: ECMA-114Alias: ASMO-708Alias: arabicName: ISO_8859-6-E [RFC1556,IANA]Source:RFC-1556Name: ISO_8859-6-I [RFC1556,IANA]Source:RFC-1556Name: ISO_8859-7:1987 [RFC1345,KXS2]Source: ECMA registryReynolds & Postel [Page 108]
RFC 1700 Assigned Numbers October 1994Alias: iso-ir-126Alias: ISO_8859-7Alias: ISO-8859-7Alias: ELOT_928Alias: ECMA-118Alias: greekAlias: greek8Name: T.101-G2 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-128Name: ISO_8859-8:1988 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-138Alias: ISO_8859-8Alias: ISO-8859-8Alias: hebrewName: ISO_8859-8-E [RFC1556,Nussbacher]Source:RFC-1556Name: ISO_8859-8-I [RFC1556,Nussbacher]Source:RFC-1556Name: CSN_369103 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-139Name: JUS_I.B1.002 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-141Alias: ISO646-YUAlias: jsAlias: yuName: ISO_6937-2-add [RFC1345,KXS2]Source: ECMA registry and ISO 6937-2:1983Alias: iso-ir-142Name: IEC_P27-1 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-143Name: ISO_8859-5:1988 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-144Alias: ISO_8859-5Reynolds & Postel [Page 109]
RFC 1700 Assigned Numbers October 1994Alias: ISO-8859-5Alias: cyrillicName: JUS_I.B1.003-serb [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-146Alias: serbianName: JUS_I.B1.003-mac [RFC1345,KXS2]Source: ECMA registryAlias: macedonianAlias: iso-ir-147Name: ISO_8859-9:1989 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-148Alias: ISO_8859-9Alias: ISO-8859-9Alias: latin5Alias: l5Name: greek-ccitt [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-150Name: NC_NC00-10:81 [RFC1345,KXS2]Source: ECMA registryAlias: cubaAlias: iso-ir-151Alias: ISO646-CUName: ISO_6937-2-25 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-152Name: GOST_19768-74 [RFC1345,KXS2]Source: ECMA registryAlias: ST_SEV_358-88Alias: iso-ir-153Name: ISO_8859-supp [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-154Alias: latin1-2-5Name: ISO_10367-box [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-155Reynolds & Postel [Page 110]
RFC 1700 Assigned Numbers October 1994Name: latin6 [RFC1345,KXS2]Source: ECMA registryAlias: iso-ir-157Alias: l6Name: latin-lap [RFC1345,KXS2]Source: ECMA registryAlias: lapAlias: iso-ir-158Name: JIS_X0212-1990 [RFC1345,KXS2]Source: ECMA registryAlias: x0212Alias: iso-ir-159Name: DS_2089 [RFC1345,KXS2]Source: Danish Standard, DS 2089, February 1974Alias: DS2089Alias: ISO646-DKAlias: dkName: us-dk [RFC1345,KXS2]Name: dk-us [RFC1345,KXS2]Name: JIS_X0201 [RFC1345,KXS2]Alias: X0201Name: KSC5636 [RFC1345,KXS2]Alias: ISO646-KRName: DEC-MCS [RFC1345,KXS2]Source: VAX/VMS User's Manual, Order Number: AI-Y517A-TE, April 1986.Alias: decName: hp-roman8 [RFC1345,KXS2]Source: LaserJet IIP Printer User's Manual, HP part no 33471-90901, Hewlet-Packard, June 1989.Alias: roman8Alias: r8Name: macintosh [RFC1345,KXS2]Source: The Unicode Standard ver1.0, ISBN 0-201-56788-1, Oct 1991Alias: macName: IBM037 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Reynolds & Postel [Page 111]
RFC 1700 Assigned Numbers October 1994Alias: cp037Alias: ebcdic-cp-usAlias: ebcdic-cp-caAlias: ebcdic-cp-wtAlias: ebcdic-cp-nlName: IBM038 [RFC1345,KXS2]Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990Alias: EBCDIC-INTAlias: cp038Name: IBM273 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP273Name: IBM274 [RFC1345,KXS2]Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990Alias: EBCDIC-BEAlias: CP274Name: IBM275 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: EBCDIC-BRAlias: cp275Name: IBM277 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: EBCDIC-CP-DKAlias: EBCDIC-CP-NOName: IBM278 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP278Alias: ebcdic-cp-fiAlias: ebcdic-cp-seName: IBM280 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP280Alias: ebcdic-cp-itName: IBM281 [RFC1345,KXS2]Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990Alias: EBCDIC-JP-EAlias: cp281Name: IBM284 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Reynolds & Postel [Page 112]
RFC 1700 Assigned Numbers October 1994Alias: CP284Alias: ebcdic-cp-esName: IBM285 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP285Alias: ebcdic-cp-gbName: IBM290 [RFC1345,KXS2]Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990Alias: cp290Alias: EBCDIC-JP-kanaName: IBM297 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp297Alias: ebcdic-cp-frName: IBM420 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990, IBM NLS RM p 11-11Alias: cp420Alias: ebcdic-cp-ar1Name: IBM423 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp423Alias: ebcdic-cp-grName: IBM424 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp424Alias: ebcdic-cp-heName: IBM437 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp437Alias: 437Name: IBM500 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP500Alias: ebcdic-cp-beAlias: ebcdic-cp-chName: IBM850 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp850Reynolds & Postel [Page 113]
RFC 1700 Assigned Numbers October 1994Alias: 850Name: IBM851 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp851Alias: 851Name: IBM852 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp852Alias: 852Name: IBM855 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp855Alias: 855Name: IBM857 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp857Alias: 857Name: IBM860 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp860Alias: 860Name: IBM861 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp861Alias: 861Alias: cp-isName: IBM862 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp862Alias: 862Name: IBM863 [RFC1345,KXS2]Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991Alias: cp863Alias: 863Name: IBM864 [RFC1345,KXS2]Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991Alias: cp864Name: IBM865 [RFC1345,KXS2]Reynolds & Postel [Page 114]
RFC 1700 Assigned Numbers October 1994Source: IBM DOS 3.3 Ref (Abridged), 94X9575 (Feb 1987)Alias: cp865Alias: 865Name: IBM868 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP868Alias: cp-arName: IBM869 [RFC1345,KXS2]Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991Alias: cp869Alias: 869Alias: cp-grName: IBM870 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP870Alias: ebcdic-cp-roeceAlias: ebcdic-cp-yuName: IBM871 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP871Alias: ebcdic-cp-isName: IBM880 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp880Alias: EBCDIC-CyrillicName: IBM891 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp891Name: IBM903 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp903Name: IBM904 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: cp904Alias: 904Name: IBM905 [RFC1345,KXS2]Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990Alias: CP905Alias: ebcdic-cp-trReynolds & Postel [Page 115]
RFC 1700 Assigned Numbers October 1994Name: IBM918 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP918Alias: ebcdic-cp-ar2Name: IBM1026 [RFC1345,KXS2]Source: IBM NLS RM Vol2 SE09-8002-01, March 1990Alias: CP1026Name: EBCDIC-AT-DE [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-AT-DE-A [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-CA-FR [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-DK-NO [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-DK-NO-A [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-FI-SE [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-FI-SE-A [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-FR [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-IT [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-PT [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-ES [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-ES-A [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-ES-S [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Reynolds & Postel [Page 116]
RFC 1700 Assigned Numbers October 1994Name: EBCDIC-UK [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: EBCDIC-US [RFC1345,KXS2]Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987Name: UNKNOWN-8BIT [RFC1428]Name: MNEMONIC [RFC1345,KXS2]Source:RFC 1345, also known as "mnemonic+ascii+38"Name: MNEM [RFC1345,KXS2]Source:RFC 1345, also known as "mnemonic+ascii+8200"Name: VISCII [RFC1456]Source:RFC 1456Name: VIQR [RFC1456]Source:RFC 1456Name: KOI8-R [RFC1489]Source:RFC 1489, based on GOST-19768-74, ISO-6937/8, INIS-Cyrillic, ISO-5427.Name: UNICODE-1-1 [RFC1641]Source:RFC 1641Name: UNICODE-1-1-UTF-7 [RFC1642]Source:RFC 1642REFERENCES[RFC1345] Simonsen, K., "Character Mnemonics & Character Sets",RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.[RFC1428] Vaudreuil, G., "Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME",RFC1428, CNRI, February 1993.[RFC1456] Vietnamese Standardization Working Group, "Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification Revision 1.1",RFC 1456, May 1993.[RFC1468] Murai, J., Crispin, M., and E. van der Poel, "Japanese Character Encoding for Internet Messages",RFC 1468,Reynolds & Postel [Page 117]
RFC 1700 Assigned Numbers October 1994 Keio University, Panda Programming, June 1993.[RFC1489] Chernov, A., "Registration of a Cyrillic Character Set",RFC1489, RELCOM Development Team, July 1993.[RFC1554] Ohta, M., and K. Handa, "ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP",RFC1554, Tokyo Institute of Technology, ETL, December 1993.[RFC1556] Nussbacher, H., "Handling of Bi-directional Texts in MIME",RFC1556, Israeli Inter-University, December 1993.[RFC1557] Choi, U., Chon, K., and H. Park, "Korean Character Encoding for Internet Messages", KAIST, Solvit Chosun Media, December 1993.[RFC1641] Goldsmith, D., and M. Davis, "Using Unicode with MIME",RFC1641, Taligent, Inc., July 1994.[RFC1642] Goldsmith, D., and M. Davis, "UTF-7",RFC1642, Taligent, Inc., July 1994.PEOPLE[KXS2] Keld Simonsen <Keld.Simonsen@dkuug.dk>[Choi] Uhhyung Choi <uhhyung@kaist.ac.kr>[Murai] Jun Murai <jun@wide.ad.jp>[Ohta] Masataka Ohta <mohta@cc.titech.ac.jp>[Nussbacher] Hank Nussbacher <hank@vm.tau.ac.il>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/character-setsReynolds & Postel [Page 118]
RFC 1700 Assigned Numbers October 1994NETWORK MANAGEMENT PARAMETERSFor the management of hosts and gateways on the Internet a datastructure for the information has been defined. This data structureshould be used with any of several possible management protocols, suchas the "Simple Network Management Protocol" (SNMP) [RFC1157], or the"Common Management Information Protocol over TCP" (CMOT) [RFC1095].The data structure is the "Structure and Indentification of ManagementInformation for TCP/IP-based Internets" (SMI) [RFC1155], and the"Management Information Base for Network Management of TCP/IP-basedInternets" (MIB-II) [RFC1213].The SMI includes the provision for panrameters or codes to indicateexperimental or private data structures. These parameter assignmentsare listed here.The older "Simple Gateway Monitoring Protocol" (SGMP) [RFC1028] alsodefined a data structure. The parameter assignments used with SGMPare included here for historical completeness.The network management object identifiers are under the iso (1), org(3), dod (6), internet (1), or 1.3.6.1, branch of the name space.The major branches are:1 iso1.3 org1.3.6 dod1.3.6.1 internet1.3.6.1.1 directory1.3.6.1.2 mgmt1.3.6.1.2.1 mib-21.3.6.1.2.1.2.2.1.3 ifType1.3.6.1.2.1.10 transmission1.3.6.1.2.1.10.23 transmission.ppp1.3.6.1.2.1.27 application1.3.6.1.2.1.28 mta1.3.6.1.3 experimental1.3.6.1.4 private1.3.6.1.4.1 enterprise1.3.6.1.5 security1.3.6.1.6 SNMPv21.3.6.1.7 mailSMI Network Management Directory Codes:Prefix: iso.org.dod.internet.directory (1.3.6.1.1.)Reynolds & Postel [Page 119]
RFC 1700 Assigned Numbers October 1994Decimal Name Description References------- ---- ----------- ---------- all Reserved Reserved for future use [IANA]SMI Network Management MGMT Codes:Prefix: iso.org.dod.internet.mgmt (1.3.6.1.2.)Decimal Name Description References------- ---- ----------- ---------- 0 Reserved [IANA] 1 MIB [KZM]Prefix: iso.org.dod.internet.mgmt.mib-2 (1.3.6.1.2.1)Decimal Name Description References------- ---- ----------- ---------- 0 Reserved Reserved [IANA] 1 system System [RFC1213,KZM] 2 interfaces Interfaces [RFC1213,KZM] 3 at Address Translation [RFC1213,KZM] 4 ip Internet Protocol [RFC1213,KZM] 5 icmp Internet Control Message [RFC1213,KZM] 6 tcp Transmission Control Protocol[RFC1213,KZM] 7 udp User Datagram Protocol [RFC1213,KZM] 8 egp Exterior Gateway Protocol [RFC1213,KZM] 9 cmot CMIP over TCP [RFC1213,KZM] 10 transmission Transmission [RFC1213,KZM] 11 snmp Simple Network Management [RFC1213,KZM] 12 GenericIF Generic Interface Extensions-- [RFC1229,RFC1239,KZM] 13 Appletalk Appletalk Networking [RFC1243,SXW] 14 ospf Open Shortest Path First [RFC1253,FB77] 15 bgp Border Gateway Protocol [RFC1657] 16 rmon Remote Network Monitoring [RFC1271,SXW] 17 bridge Bridge Objects [RFC1286,EXD] 18 DecnetP4 Decnet Phase 4 [RFC1559, Saperia] 19 Character Character Streams [RFC1658] 20 snmpParties SNMP Parties [RFC1353,KZM] 21 snmpSecrets SNMP Secrets [RFC1353,KZM] 22 snmpDot3RptrMgt [RFC1516] 23 rip-2 Routing Information Protocol [RFC1389] 24 ident Identification Protocol [RFC1414] 25 host Host Resources [RFC1514] 26 snmpDot3MauMgt 802.3 Medium Attachment Units [RFC1515] 27 application Network Services Monitoring [RFC1565] 28 mta Mail Monitoring [RFC1566] 29 dsa X.500 Directory Monitoring [RFC1567]Reynolds & Postel [Page 120]
RFC 1700 Assigned Numbers October 1994 30 IANAifType Interface Types [RFC1573] 31 ifMIB Interface Types [RFC1573] 32 dns Domain Name System [RFC1611] 33 upsMIB Uninterruptible Power Supplies [RFC1628] 34 sannauMIB SNA NAU MIB [RFC1665] 35 etherMIB Ethernet-like generic objects [RFC1650] 36 sipMIB SMDS inteface objects [RFC1694] 37 atmMIB ATM objects [RFC1695] 38 mdmMIB Dial-up modem objects [RFC1696] 39 rdbmsMIB relational database objects [RFC1697]Prefix: iso.org.dod.internet.mgmt.mib-2.interface (1.3.6.1.2.1.2)(1.3.6.1.2.1.2.2.1.3)ifType definitionsDecimal Name Description------- ---- ----------- 1 other none of the following [RFC1213] 2 regular1822 BBN Report 1822 [RFC1213] 3 hdh1822 BBN Report 1822 [RFC1213] 4 ddn-x25 BBN Report 1822 [RFC1213] 5 x25 X.25 [RFC1382] 6 ethernet-csmacd [RFC1213] 7 IEEE802.3 CSMACD--like Objects [RF1284,JXC] 8 IEEE802.4 Token Bus-like Objects-- [RFC1230,RFC1239,KZM] 9 IEEE802.5 Token Ring-like Objects-- [RFC1231,RFC1239,KZM] 10 iso88026-man [RFC1213] 11 starLan [RFC1213] 12 proteon-10Mbit [RFC1213] 13 proteon-80Mbit [RFC1213] 14 hyperchannel [RFC1213] 15 FDDI FDDI Objects [RFC1285,JDC20] 16 lapb LAP B [RFC1381] 17 sdlc [RFC1213] 18 ds1 T1/E1 Carrier Objects [RFC1406] 19 e1 obsolete 20 basicISDN [RFC1213] 21 primaryISDN [RFC1213] 22 propPointToPointSerial [RFC1213] 23 ppp Point-to-Point Protocol [RFC1471] 24 softwareLoopback [RFC1213] 25 eon [RFC1213] 26 ethernet-3Mbit [RFC1213] 27 nsip [RFC1213]Reynolds & Postel [Page 121]
RFC 1700 Assigned Numbers October 1994 28 slip [RFC1213] 29 ultra [RFC1213] 30 ds3 DS3/E3 Interface Objects [RFC1407] 31 sip SMDS Interface Objects [RFC1304,TXC] 32 frame-relay Frame Relay Objects [RFC1315,CXB] 33 RS-232 RS-232 Objects [RFC1659] 34 Parallel Parallel Printer Objects [RFC1660] 35 arcnet ARC network 36 arcnet-plus ARC network plus 37 atm ATM 38 MIOX25 MIOX25 [RFC1461] 39 SONET SONET or SDH 40 x25ple X.25 packet level [RFC1382] 41 iso88022llc 802.2 LLC 42 localTalk 43 smds-dxi SMDS DXI 44 frameRelayService Frame Relay DCE 45 v35 V.35 46 hssi HSSI 47 hippi HIPPI 48 modem generic modem 49 aal5 AAL5 over ATM 50 sonetPath 51 sonetVT 52 smds-icip SMDS Inter-Carrier Interface Protocol 53 propVirtual proprietary vitural/internal interface 54 propMultiLink proprietary multi-link multiplexing 55 IEEE802.12 100BaseVG 56 fibre-channel Fibre ChannelPrefix: iso.org.dod.internet.mgmt.mib-2.transmission (1.3.6.1.2.1.10)Decimal Name Description------- ---- ----------- 5 x25 X.25 [RFC1382] 7 IEEE802.3 CSMACD--like Objects [RFC1650] 8 IEEE802.4 Token Bus-like Objects-- [RFC1230,RFC1239,KZM] 9 IEEE802.5 Token Ring-like Objects-- [RFC1231,RFC1239,KZM] 15 FDDI FDDI Objects [RFC1285,JDC20] 16 lapb LAP B [RFC1381] 18 ds1 T1 Carrier Objects [RFC1406] 19 e1 E1 Carrier Objects [RFC1406] 23 ppp Point-to-Point Protocol [RFC1471] 30 ds3 DS3/E3 Interface Objects [RFC1407] 31 sip SMDS Interface Objects [RFC1694] 32 frame-relay Frame Relay Objects [RFC1315,CXB]Reynolds & Postel [Page 122]
RFC 1700 Assigned Numbers October 1994 33 RS-232 RS-232 Objects [RFC1659] 34 Parallel Parallel Printer Objects [RFC1660] 35 arcnet ARC network 36 arcnet-plus ARC network plus 37 atm ATM 38 MIOX25 MIOX25 [RFC1461] 39 sonetMIB SONET MIB [RFC1595] 44 frnetservMIB Frame Relay Service MIB for DCE [RFC1596]Prefix: iso.org.dod.internet.mgmt.mib-2.transmission (1.3.6.1.2.1.10)(1.3.6.1.2.1.10.23)Decimal Name Description References------- ---- ----------- ---------- 1 pppLcp ppp link control [RFC1471] 2 pppSecurity ppp security [RFC1472] 3 pppIp ppp IP network control [RFC1473] 4 pppBridge ppp bridge networl control [RFC1474]Prefix: iso.org.dod.internet.mgmt.mib-2.application (1.3.6.1.2.1.27)(1.3.6.1.2.1.27.2.1.3) assocApplicationProtocol OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "An identification of the protocol being used for the application. For an OSI Application, this will be the Application Context. For Internet applications, the IANA maintains a registry of the OIDs which correspond to well-known applications. If the application protocol is not listed in the registry, an OID value of the form {applTCPProtoID port} or {applUDProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol." ::= {assocEntry 3}Decimal Name Description------- ---- ----------- 0 Reserved(1.3.6.1.2.1.27.3)(1.3.6.1.2.1.27.4)Reynolds & Postel [Page 123]
RFC 1700 Assigned Numbers October 1994 -- OIDs of the form {applTCPProtoID port} are intended to be used -- for TCP-based protocols that don't have OIDs assigned by other -- means. {applUDPProtoID port} serves the same purpose for -- UDP-based protocols. In either case 'port' corresponds to -- the primary port number being used by the protocol. For example, -- assuming no other OID is assigned for SMTP, an OID of -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based -- protocol that uses port 25 as its primary port.Prefix: iso.org.dod.internet.mgmt.mib-2.mta (1.3.6.1.2.1.28)(1.3.6.1.2.1.28.2.1.24) mtaGroupMailProtocol OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "An identification of the protocol being used by this group. For an group employing OSI protocols, this will be the Application Context. For Internet applications, the IANA maintains a registry of the OIDs which correspond to well-known message transfer protocols. If the application protocol is not listed in the registry, an OID value of the form {applTCPProtoID port} or {applUDProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the group. applTCPProtoID and applUDPProtoID are defined in [5]." ::= {mtaGroupEntry 24}Decimal Name Description------- ---- ----------- 0 ReservedSMI Network Management Experimental Codes:Prefix: iso.org.dod.internet.experimental (1.3.6.1.3.)Decimal Name Description References------- ---- ----------- ---------- 0 Reserved [JKR1] 1 CLNS ISO CLNS Objects [GS2] * 2 T1-Carrier T1 Carrier Objects [FB77] * 3 IEEE802.3 Ethernet-like Objects [JXC] * 4 IEEE802.5 Token Ring-like Objects [EXD] * 5 DECNet-PHIV DECNet Phase IV [JXS2] * 6 Interface Generic Interface Objects [KZM]Reynolds & Postel [Page 124]
RFC 1700 Assigned Numbers October 1994 * 7 IEEE802.4 Token Bus-like Objects [KZM] * 8 FDDI FDDI Objects [JDC20] 9 LANMGR-1 LAN Manager V1 Objects [JXG1] 10 LANMGR-TRAPS LAN Manager Trap Objects [JXG1] 11 Views SNMP View Objects [CXD] 12 SNMP-AUTH SNMP Authentication Objects [KZM] * 13 BGP Border Gateway Protocol [SW159] * 14 Bridge Bridge MIB [FB77] * 15 DS3 DS3 Interface Type [TXB] * 16 SIP SMDS Interface Protocol [TXB] * 17 Appletalk Appletalk Networking [SXW] * 18 PPP PPP Objects [FJK2] * 19 Character MIB Character MIB [BS221] * 20 RS-232 MIB RS-232 MIB [BS221] * 21 Parallel MIB Parallel MIB [BS221] 22 atsign-proxy Proxy via Community [RXF] * 23 OSPF OSPF MIB [FB77] 24 Alert-Man Alert-Man [LS8] 25 FDDI-Synoptics FDDI-Synoptics [DXP1] * 26 Frame Relay Frame Relay MIB [CXB] * 27 rmon Remote Network Management MIB [SXW] 28 IDPR IDPR MIB [RAW44] 29 HUBMIB IEEE 802.3 Hub MIB [DXM5] 30 IPFWDTBLMIB IP Forwarding Table MIB [FB77] 31 LATM MIB [TXB] 32 SONET MIB [TXB] 33 IDENT [MTR] 34 MIME-MHS [MTR] 35 MAUMIB IEEE 802.3 Mau MIB [DXM5] 36 Host Resources Host Resources MIB [SXW] 37 ISIS-MIB Integrated ISIS protocol MIB [CXG] 38 Chassis Chassis MIB [JDC20] 39 ups ups [JDC20] 40 App-Mon Application Monitoring MIB [TXK] 41 ATM UNI ATM [MXA1] 42 FC Fibre Channel [JXC4]* 43 DNS Domain Name Service [Rob Austein] 44 X.25 X.25 MIB [Dean Throop] 45 Frame Relay Serv. Frame Relay Service MIB [Tracy Cox] 46 Madman-Applications [Ned Freed] 47 Madman-MTA [Ned Freed] 48 Madman-DSA [Ned Freed] 49 Modem [Steve Waldbusser] 50 SNA NAU [Deirdre Kostick] 51 SDLC SDLC [Jeff Hilgeman] 52 DNS Domain Name Service [Jon Saperia] 53 network-objects IP info ix X.500 [Johannsen] 54 printmib [Joel Gyllenskog]Reynolds & Postel [Page 125]
RFC 1700 Assigned Numbers October 1994 55 rdbmsmib [Robert Purvey] 56 sipMIB [Tracy Brown] 57 stIImib ST-II protocol MIB [Hartmut Wittig] 58 802.5 SSR MIB 802.5 Station Source Routing MIB [KZM] * = obsoletedSMI Private Codes:Prefix: iso.org.dod.internet.private (1.3.6.1.4)Decimal Name Description References------- ---- ----------- ---------- 0 Reserved [JKR1] 1 enterprise private enterprises [JKR1]SMI Private Enterprise Codes:Prefix: iso.org.dod.internet.private.enterprise (1.3.6.1.4.1)See the file "enterprise-numbers".SMI Security Codes:Prefix: iso.org.dod.internet.security (1.3.6.1.5)Decimal Name Description References------- ---- ----------- ---------- 0 Reserved [JKR1] 1 kerberosV4 Kerberos version 4 objects [1,BCN] 2 kerberosV5 Kerberos version 5 objects [2,BCN]SMI SNMPv2 Codes:Prefix: iso.org.dod.internet.snmpv2 (1.3.6.1.6)SMI mail Codes:Prefix: iso.org.dod.internet.mail (1.3.6.1.7) 1 mime-mhsREFERENCES[1] Miller, S.P., B.C. Neuman, J.I. Schiller, and J.H. Saltzer, "Project Athena Technical Plan Section E.2.1: Kerberos Authentication and Authorization System", Project Athena,Reynolds & Postel [Page 126]
RFC 1700 Assigned Numbers October 1994 MIT, December 1987.[2] Kohl, J., and B.C. Neuman, "The Kerberos Network Authentication Service (V5)" work in progress, September 1992.[RFC1028] Davin, J., J. Case, M. Fedor, and M. Schoffstall, "A Simple Gateway Monitoring Protocol",RFC 1028, Proteon, Inc., University of Tennessee at Knoxville, Cornell University, Rensselaer Polytechnic Institute, November 1987.[RFC1095] Warrier, U., and L. Besaw, "The Common Management Information Services and Protocol over TCP/IP (CMOT)",RFC 1095, Unisys Corp., Hewlett-Packard, April 1989.[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16,RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990.[RFC1157] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "A Simple Network Management Protocol", STD 15,RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990.[RFC1213] McCloghrie, K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17,RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991.[RFC1229] McCloghrie, K., Editor, "Extensions to the Generic-Interface MIB",RFC 1229, Hughes LAN Systems, Inc., May 1991.[RFC1230] McCloghrie, K., and R. Fox, "IEEE 802.4 Token Bus MIB",RFC 1230, Hughes LAN Systems, Inc., Synoptics, Inc., May 1991.[RFC1231] McCloghrie, K., Fox, R., and E. Decker, "IEEE 802.5 Token Ring MIB",RFC 1231, Hughes LAN Systems, Inc., Synoptics, Inc., cisco Systems, Inc., May 1991.[RFC1239] Reynolds, J., "Reassignment of Experimental MIBs to Standard MIBs",RFC 1239, USC/Information Sciences Institute, ISI, June 1991.[RFC1243] Waldbusser, S., Editor, "AppleTalk Management Information Base",RFC 1243, Carnegie Mellon University, July 1991.Reynolds & Postel [Page 127]
RFC 1700 Assigned Numbers October 1994[RFC1253] Baker, F., and R. Coltun, "OSPF Version 2 Management Information Base",RFC 1253, ACC, Computer Science Center, August 1991.[RFC1271] Waldbusser, S., "Remote Network Monitoring Management Information Base",RFC 1271, Carnegie Mellon University, November 1991.[RFC1284] Cook, J., Editor, "Definitions of Managed Objects for the Ethernet-like Interface Types",RFC 1284, Chipcom Corporation, December 1991.[RFC1285] Case, J., "FDDI Management Information Base",RFC 1285, SNMP Research, Incorporated, January 1992.[RFC1286] Decker, E., Langille, P., Rijsinghani, A., and K. McCloghrie, "Definitions of Managed Objects for Bridges",RFC 1286, cisco Systems, Inc., DEC, Hughes LAN Systems, Inc., December 1991.[RFC1304] Cox, T., and K. Tesnik, Editors, "Definitions of Managed Objects for the SIP Interface Type",RFC 1304, Bell Communications Research, February 1992.[RFC1315] Brown, C., Baker, F., and C. Carvalho, "Management Information Base for Frame Relay DTEs",RFC 1315, Wellfleet Communications, Inc., Advanced Computer Communications, April 1992.[RFC1353] McCloghrie, K., Davin, J., and J. Galvin, "Definitions of Managed Objects for Administration of SNMP Parties",RFC 1353, Hughes LAN Systems, Inc., MIT Laboratory for Computer Science, Trusted Information Systems, Inc., July 1992.[RFC1381] Throop, D., and F. Baker, "SNMP MIB Extension for X.25 LAPB",RFC 1381, Data General Corporation, Advanced Computer Communications, November 1992.[RFC1382] Throop, D., Editor, "SNMP MIB Extension for the X.25 Packet Layer",RFC 1382, Data General Corporation, November 1992.[RFC1389] Malkin, G., and F. Baker, "RIP Version 2 MIB Extension",RFC1389, Xylogics, Inc., Advanced Computer Communications, January 1993.[RFC1406] Baker, F., and J. Watt, Editors, "Definitions of Managed Objects for the DS1 and E1 Interface Types",RFC 1406,Reynolds & Postel [Page 128]
RFC 1700 Assigned Numbers October 1994 Advanced Computer Communications, Newbridge Networks Corporation, January 1993.[RFC1407] Cox, T., and K. Tesink, "Definitions of Managed Objects for the DS3/E3 Interface Type",RFC 1407, Bell Communications Research, January 1993.[RFC1414] St. Johns, M., and M. Rose, "Identification MIB",RFC 1414, US Department of Defense, Dover Beach Consulting, Inc., February 1993.[RFC1461] Throop, D., "SNMP MIB extension for Multiprotocol Interconnect over X.25",RFC 1461, Data General Corporation, May 1993.[RFC1471] Kastenholz, F., "The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol",RFC 1471, FTP Software, Inc., June 1993.[RFC1472] Kastenholz, F., "The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol",RFC1472, FTP Software, Inc., June 1993.[RFC1473] Kastenholz, F., "The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol",RFC 1473, FTP Software, Inc., June 1993.[RFC1474] Kastenholz, F., "The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol"RFC 1474, FTP Software, Inc., June 1993.[RFC1514] Grillo, P., and S. Waldbusser, "Host Resources MIB",RFC1514, Network Innovations, Intel Corporation, Carnegie Mellon University, September 1993.[RFC1515] McMaster, D., McCloghrie, K., and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)",RFC 1515, SynOptics Communications, Inc., Hughes LAN Systems, Inc., Farallon Computing, Inc., September 1993.[RFC1516] McMaster, D., and K. McCloghrie, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices",RFC 1516, SynOptics Communications, Inc., Hughes LAN Systems, Inc., September 1993.[RFC1559] Saperia, J., "DECnet Phase IV MIB Extensions",RFC 1559, Digital Equipment Corporation, December 1993.Reynolds & Postel [Page 129]
RFC 1700 Assigned Numbers October 1994[RFC1565] Kille, S., WG Chair, and N. Freed, Editor, "Network Services Monitoring MIB",RFC 1565, ISODE Consortium and Innosoft, January 1994.[RFC1566] Kille, S., WG Chair, and N. Freed, Editor, "Mail Monitoring MIB",RFC 1566, ISODE Consortium, Innosoft, January 1994.[RFC1567] Mansfield, G., and S. Kille, "X.500 Directory Monitoring MIB",RFC 1567, AIC Systems Laboratory, ISODE Consortium, January 1994.[RFC1573] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces Group of MIB-II",RFC 1573, Hughes LAN Systems, FTP Software, January 1994.[RFC1595] Brown, T., and K. Tesink, Editors, "Definitions of Managed Objects for the SONET/SDH Interface Type",RFC 1595, Bell Communications Research, March 1994.[RFC1596] Brown, T., Editor, Definitions of Managed Objects for Frame Relay Service",RFC 1596, Bell Communications Research, March 1994.[RFC1611] Austein, R., and J. Saperia, "DNS Server MIB Extensions",RFC 1611, Epilogue Technology Corporation, Digital Equipment Corporation, May 1994.[RFC1628] Case, J., Editor, "UPS Management Information Base",RFC1628, SNMP Research, Incorporated, May 1994.[RFC1650] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2",RFC 1650, FTP Software, Inc., August 1994.[RFC1657] Willis, S., Burruss, J., and J. Chu, Editor, "Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2",RFC 1657, Wellfleet Communications Inc., IBM Corp., July 1994.[RFC1658] Stewart, B., "Definitions of Managed Objects for Character Stream Devices using SMIv2",RFC 1658, Xyplex, Inc., July 1994.[RFC1659] Stewart, B., "Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2",RFC 1659, Xyplex, Inc., July 1994.[RFC1660] Stewart, B., "Definitions of Managed Objects forReynolds & Postel [Page 130]
RFC 1700 Assigned Numbers October 1994 Parallel-printer-like Hardware Devices using SMIv2",RFC1660, Xyplex, Inc., July 1994.[RFC1665] Kielczewski, Z., Kostick, D., and K. Shih, Editors, "Definitions of Managed Objects for SNA NAUs using SMIv2",RFC 1665, Eicon Technology Corporation, Bell Communications Research, Novell, July 1994.[RFC1694] Brown, T., and K. Tesink, Editors, "Definitions of Managed Objects for SMDS Interfaces using SMIv2",RFC 1694, Bell Communications Research, August 1994.[RFC1695] Ahmed, M., and K. Tesink, Editors, "Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2",RFC1695, Bell Communications Research, August 1994.[RFC1696] Barnes, J., Brown, L., Royston, R., and S. Waldbusser, "Modem Management Information Base (MIB) using SMIv2",RFC1696, Xylogics, Inc., Motorola, US Robotics, Inc., Carnegie Mellon University, August 1994.[RFC1697] Brower, D., Editor, Purvy, B., RDBMSMIB Working Group Chair, Daniel, A., Sinykin, M., and J. Smith, "Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2",RFC 1697, The ASK Group, INGRES DBMS Development, Oracle Corporation, Informix Software, Inc., Oracle Corporation, August 1994.PEOPLE[Rob Austein][BCN] B. Clifford Neuman <bcn@isi.edu>[BS221] Bob Stewart <STEWART@XYPLEX.COM>[CXB] Caralyn Brown <cbrown%wellfleet.com@talcott.harvard.edu>[CXD] Chuck Davin <jrd@ptt.lcs.mit.edu>[CXG] Chris Gunner <gunner@dsmail.lkg.dec.com>[Dean Throop][DXM5] Donna McMaster <mcmaster@synoptics.com>[DXP1] David Perkins <dperkins@synoptics.com>Reynolds & Postel [Page 131]
RFC 1700 Assigned Numbers October 1994[EXD] Eric Decker <cire@cisco.com>[FB77] Fred Baker <fbaker@acc.com>[FJK2][GS2] Greg Satz <satz@CISCO.COM>[IANA] IANA <iana@isi.edu>[JDC20] Jeffrey Case <case@UTKUX1.UTK.EDU>[JKR1] Joyce K. Reynolds <jkrey@isi.edu>[JXC] John Cook <cook@chipcom.com>[JXG1] Jim Greuel <jimg%hpcndpc@hplabs.hp.com>[JXS2] Jon Saperia <saperia@tcpjon.enet.dec.com>[Jeff Hilgeman][Johannsen][KZM] Keith McCloghrie <KZM@HLS.COM>[LS8] Louis Steinberg <lou@ARAMIS.RUTGERS.EDU>[MXA1] Masuma Ahmed <mxa@mail.bellcore.com>[MTR] Marshall Rose <mrose@dbc.mtview.ca.us>[RAW44] Robert A. Woodburn <WOODY@SPARTA.COM>[JXC4] John Chu <jychu@watson.ibm.com>[Ned Freed][Deirdre Kostick][Joel Gyllenskog] Joel Gyllenskog <jgyllens@hpdmd48.boi.hp.com>[Robert Purvey] Robert Purvey <bpurvy@us.oracle.com>[RXF] Richard Fox <rfox@synoptics.com>[Jon Saperia] Jon Saperia <saperia@tcpjon.enet.dec.com>Reynolds & Postel [Page 132]
RFC 1700 Assigned Numbers October 1994[SW159] Steven Willis <swillis@WELLFLEET.COM>[SXW] Steve Waldbusser <sw01+@andrew.cmu.edu>[TXB] Tracy Brown <tacox@mail.bellcore.com>[TXK] Teemu Kurki <grus@funet.fi>[Hartmut Wittig][]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbersReynolds & Postel [Page 133]
RFC 1700 Assigned Numbers October 1994PRIVATE ENTERPRISE NUMBERSSMI Network Management Private Enterprise Codes:Prefix: iso.org.dod.internet.private.enterprise (1.3.6.1.4.1)This file isftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbersDecimal Name References------- ---- ---------- 0 Reserved Joyce K. Reynolds <jkrey@isi.edu> 1 Proteon John A. Shriver <jas@PROTEON.COM> 2 IBM Vik Chandra <vc@ralvm6.vnet.ibm.com> 3 CMU Steve Waldbusser <sw01+@andrew.cmu.edu> 4 Unix Keith Sklower <sklower@okeeffe.berkeley.edu> 5 ACC Art Berggreen <art@SALT.ACC.COM> 6 TWG John Lunny <jlunny@eco.twg.com> (703) 847-4500 7 CAYMAN Beth Miaoulis beth@cayman.com 8 PSI Marty Schoffstahl schoff@NISC.NYSER.NET 9 cisco Greg Satz satz@CISCO.COM 10 NSC Geof Stone geof@NETWORK.COM 11 HP R. Dwight Schettler rds%hpcndm@HPLABS.HP.COM 12 Epilogue Karl Auerbac karl@empirical.com 13 U of Tennessee Jeffrey Case case@UTKUX1.UTK.EDU 14 BBN Robert Hinden <hinden@ENG.SUN.COM> 15 Xylogics, Inc. John R. LoVerso loverso@westford.ccur.com 16 Timeplex Laura Bridge laura@uunet.UU.NET 17 Canstar Sanand Patel sanand@HUB.TORONTO.EDU 18 Wellfleet Caralyn Brown cbrown@wellfleet.com 19 TRW Jay Frederking jayf@blackhole.ind.TRW.COM 20 MIT Jon Rochlis jon@ATHENA.MIT.EDU 21 EON Michael Waters ---none--- 22 Spartacus Yoav Kluger ykluger@HAWK.ULOWELL.EDU 23 Novell Steve Bostock steveb@novell.com 24 Spider Systems Peter Reid peter@spider.co.uk 25 NSFNET Hans-Werner Braun HWB@MCR.UMICH.EDU 26 Hughes LAN Systems Keith McCloghrie KZM@HLS.COM 27 Intergraph Guy Streeter guy@guy.bll.ingr.com 28 Interlan Bruce Taber taber@europa.InterLan.COM 29 Vitalink Communications 30 Ulana Bill Anderson wda@MITRE-BEDFORD.ORG 31 NSWC Stephen Northcutt SNORTHC@RELAY-NSWC.NAVY.MIL 32 Santa Cruz Operation Keith Reynolds keithr@SCO.COM 33 Xyplex Bob Stewart STEWART@XYPLEX.COM 34 Cray Hunaid Engineer hunaid@OPUS.CRAY.COM 35 Bell Northern Research Glenn Waters gwaters@BNR.CAReynolds & Postel [Page 134]
RFC 1700 Assigned Numbers October 1994 36 DEC Ron Bhanukitsiri rbhank@DECVAX.DEC.COM 37 Touch Brad Benson ---none--- 38 Network Research Corp. Bill Versteeg bvs@NCR.COM 39 Baylor College of Medicine Stan Barber SOB@BCM.TMC.EDU 40 NMFECC-LLNL Steven Hunter hunter@CCC.MFECC.LLNL.GOV 41 SRI David Wolfe ctabka@TSCA.ISTC.SRI.COM 42 Sun Microsystems Dennis Yaro yaro@SUN.COM 43 3Com Jeremy Siegel jzs@NSD.3Com.COM 44 CMC Dave Preston ---none--- 45 SynOptics David Perkins dperkins@synoptics.com 46 Cheyenne Software Reijane Huai sibal@CSD2.NYU.EDU 47 Prime Computer Mike Spina WIZARD%enr.prime.com@RELAY.CS.NET 48 MCNC/North Carolina Data Network Ken Whitfield ken@MCNC.ORG 49 Chipcom John Cook cook@chipcom.com 50 Optical Data Systems Josh Fielk ---none--- 51 gated Jeffrey C. Honig jch@gated.cornell.edu 52 Cabletron Systems Roger Dev ---none--- 53 Apollo Computers Jeffrey Buffun jbuffum@APOLLO.COM 54 DeskTalk Systems, Inc. David Kaufman ---none--- 55 SSDS Ron Strich ---none--- 56 Castle Rock Computing John Sancho ---none--- 57 MIPS Computer Systems Charles Marker II marker@MIPS.COM 58 TGV, Inc. Ken Adelman Adelman@TGV.COM 59 Silicon Graphics, Inc. Ronald Jacoby rj@SGI.COM 60 University of British Columbia Don McWilliam mcwillm@CC.UBC.CA 61 Merit Bill Norton wbn@MERIT.EDU 62 FiberCom Eric Rubin err@FIBERCOM.COM 63 Apple Computer Inc Jim Hayes Hayes@APPLE.COM 64 Gandalf Henry Kaijak ---none--- 65 Dartmouth Philip Koch Philip.Koch@DARTMOUTH.EDU 66 David Systems Kathryn de Graaf degraaf@davidsys.com 67 Reuter Bob Zaniolo ---none--- 68 Cornell Laurie Collinsworth ljc1@cornell.edu 69 LMS L. Michael Sabo Sabo@DOCKMASTER.NCSC.MIL 70 Locus Computing Corp. Arthur Salazar lcc.arthur@SEAS.UCLA.EDU 71 NASA Steve Schoch SCHOCH@AMES.ARC.NASA.GOV 72 Retix Alex Martin ---none--- 73 Boeing Jerry Geisler ---none--- 74 AT&T Rich Bantel rgb@mtung.att.com 75 Ungermann-Bass Didier Moretti ---none--- 76 Digital Analysis Corporation Skip Koppenhaver stubby!skip@uunet.UU.NET 77 LAN Manager Doug Karl KARL-D@OSU-20.IRCC.OHIO-STATE.EDU 78 Netlabs Jonathan Biggar jon@netlabs.com 79 ICL Jon Infante ---none--- 80 Auspex Systems Brian A. Ehrmantraut bae@auspex.com 81 Lannet Company Efrat Ramati ---none--- 82 Network Computing Devices Dave Mackie lupine!djm@UUNET.UU.NETReynolds & Postel [Page 135]
RFC 1700 Assigned Numbers October 1994 83 Raycom Systems Bruce Willins ---none--- 84 Pirelli Focom Ltd. Sam Lau ---none--- 85 Datability Software Systems Larry Fischer lfischer@dss.com 86 Network Application Technology Y.C. Wang ---none--- 87 LINK (Lokales Informatik-Netz Karlsruhe) Guenther Schreiner snmp-admin@ira.uka.de 88 NYU Bill Russell russell@cmcl2.NYU.EDU 89 RND Rina Nethaniel ---none--- 90 InterCon Systems Corporation Amanda Walker AMANDA@INTERCON.COM 91 Coral Network Corporation Jason Perreault jason@coral.com 92 Webster Computer Corporation Robert R. Elz kre@munnari.oz.au 93 Frontier Technologies Corporation Prakash Ambegaonkar ---none--- 94 Nokia Data Communications Douglas Egan ---none--- 95 Allen-Bradely Company Bill King abvax!calvin.icd.ab.com!wrk@uunet.UU.NET 96 CERN Jens T. Rasmussen jenst%cernvax.cern.ch@CUNYVM.CUNY.EDU 97 Sigma Network Systems, Inc. Ken Virgile signet!ken@xylogics.COM 98 Emerging Technologies, Inc. Dennis E. Baasch etinc!dennis@uu.psi.com 99 SNMP Research Jeffrey Case case@UTKUX1.UTK.EDU 100 Ohio State University Shamim Ahmed ahmed@nisca.ircc.ohio-state.edu 101 Ultra Network Technologies Julie Dmytryk Julie_Dmytryk.MKT@usun.ultra.com 102 Microcom Annmarie Freitas ---none--- 103 Martin Marietta Astronautic Group David Rageth DAVE@MMC.COM 104 Micro Technology Mike Erlinger mike@lexcel.com 105 Process Software Corporation Bernie Volz VOLZ@PROCESS.COM 106 Data General Corporation Joanna Karwowska karwowska@dg-rtp.dg.com 107 Bull Company Anthony Berent berent@rdgeng.enet.dec.com 108 Emulex Corporation Jeff Freeman ---none--- 109 Warwick University Computing Services Israel Drori raanan@techunix.technion.ac.il 110 Network General Corporation James Davidson ngc!james@uunet.UU.NET 111 Oracle John Hanley jhanley@oracle.com 112 Control Data Corporation Nelluri L. Reddy reddy@uc.msc.umn.edu 113 Hughes Aircraft Company Keith McCloghrie KZM@HLS.COM 114 Synernetics, Inc. Jas Parmar jas@synnet.com 115 Mitre Bede McCall bede@mitre.org 116 Hitachi, Ltd. Hirotaka Usuda ---none--- 117 Telebit Mark S. Lewis mlewis@telebit.com 118 Salomon Technology Services Paul Maurer II ---none--- 119 NEC Corporation Yoshiyuki AkiyamaReynolds & Postel [Page 136]
RFC 1700 Assigned Numbers October 1994 kddlab!ccs.mt.nec.co.jp!y-akiyam@uunet.uu.net 120 Fibermux Michael Sung msung@ccrelay.fibermux.com 121 FTP Software Inc. Stev Knowles stev@vax.ftp.com 122 Sony Takashi Hagiwara Hagiwara@Sm.Sony.Co.Jp 123 Newbridge Networks Corporation James Watt ---none--- 124 Racal-Milgo Information Systems Maurice R. Turcotte mailrus!uflorida!rm1!dnmrt%rmatl@uunet.UU.NET 125 CR SYSTEMS Soren H. Sorensen ---none--- 126 DSET Corporation Dan Shia dset!shia@uunet.UU.NET 127 Computone Bill Versteeg bvs@NCR.COM 128 Tektronix, Inc. Dennis Thomas dennist@tektronix.TEK.COM 129 Interactive Systems Corporation Steve Alexander stevea@i88.isc.com 130 Banyan Systems Inc. Deepak Taneja eepak=Taneja%Eng%Banyan@Thing.banyan.com 131 Sintrom Datanet Limited 132 Bell Canada Mark Fabbi markf@gpu.utcs.utoronto.ca 133 Crosscomm Corporation Reuben Sivan crossc!rsivan@uunet.UU.NET 134 Rice University Catherine Foulston cathyf@rice.edu 135 T3Plus Networking, Inc. Harley Frazee harley@io.t3plus.com 136 Concurrent Computer Corporation John R. LoVerso loverso@westford.ccur.com 137 Basser Paul O'Donnell paulod@cs.su.oz.au 138 Luxcom 139 Artel Jon Ziegler Ziegler@Artel.com 140 Independence Technologies, Inc. (ITI) Gerard Berthet gerard@indetech.com 141 Frontier Software Development Narendra Popat ---none--- 142 Digital Computer Limited Osamu Fujiki ---none--- 143 Eyring, Inc. Ron Holt ron@Eyring.COM 144 Case Communications Peter Kumik ---none--- 145 Penril DataComm, Inc. Keith Hogan keith%penril@uunet.uu.net 146 American Airlines Bill Keatley ---none--- 147 Sequent Computer Systems Scott Hahn sdh@sequent.com 148 Bellcore Kaj Tesink kaj@nvuxr.cc.bellcore.com 149 Konkord Communications Ken Jones konkord!ksj@uunet.uu.net 150 University of Washington Christopher Wheeler cwheeler@cac.washignton.edu 151 Develcon Sheri Mayhew zaphod!sherim@herald.usask.ca 152 Solarix Systems Paul Afshar paul@solar1.portal.com 153 Unifi Communications Corp. Yigal Hochberg yigal@unifi.com 154 Roadnet Dale Shelton ---none--- 155 Network Systems Corp. Nadya K. El-Afandi nadya@khara.network.com 156 ENE (European Network Engineering) Peter Cox ---none--- 157 Dansk Data Elektronik A/S Per Bech Hansen pbh@dde.dk 158 Morning Star Technologies Karl Fox karl@MorningStar.Com 159 Dupont EOP Oscar Rodriguez ---none---Reynolds & Postel [Page 137]
RFC 1700 Assigned Numbers October 1994 160 Legato Systems, Inc. Jon Kepecs kepecs@Legato.COM 161 Motorola SPS Vince Enriquez enriquez@sps.mot.com 162 European Space Agency (ESA) Eduardo EDUATO%ESOC.BITNET@CUNYVM.CUNY.EDU 163 BIM Bernard Lemercier bl@sunbim.be 164 Rad Data Communications Ltd. Oft Israel ---none--- 165 Intellicom Paul Singh ---none--- 166 Shiva Corporation Phil Budne phil@Shiva.COM 167 Fujikura America Debbie Reed ---none--- 168 Xlnt Designs INC (XDI) Mike Anello mike@xlnt.com 169 Tandem Computers Rex Davis ---none--- 170 BICC David A. Brown fzbicdb@uk.ac.ucl 171 D-Link Systems, Inc. Henry P. Nagai ---none--- 172 AMP, Inc. Rick Downs ---none--- 173 Netlink Mauro Zallocco ---none--- 174 C. Itoh Electronics Larry Davis ---none--- 175 Sumitomo Electric Industries (SEI) Kent Tsuno tsuno@sumitomo.com 176 DHL Systems, Inc. David B. Gurevich dgurevic@rhubarb.ssf-sys.dhl.com 177 Network Equipment Technologies Mark Tom marktom@tom.net.com 178 APTEC Computer Systems Larry Burton ssds!larryb@uunet.UU.NET 179 Schneider & Koch & Co, Datensysteme GmbH Thomas Ruf tom@rsp.de 180 Hill Air Force Base Russell G. Wilson rwilson@oodis01.af.mil 181 ADC Kentrox Bruce Kropp ktxc8!bruce@uunet.UU.NET 182 Japan Radio Co. Nagayuki Kojima nkojima@lab.nihonmusen.co.jp 183 Versitron Matt Harris ---none--- 184 Telecommunication Systems Hugh Lockhart ---none--- 185 Interphase Gil Widdowson ---none--- 186 Toshiba Corporation Mike Asagami toshiba@mothra.nts.uci.edu 187 Clearpoint Research Corp. 188 Ascom Andrew Smith andrew@hasler.ascom.ch 189 Fujitsu America Chung Lam ---none--- 190 NetCom Solutions, Inc. Dale Cabell---none--- 191 NCR Cheryl Krupczak clefor@secola.columbia.ncr.com 192 Dr. Materna GmbH Torsten Beyer tb@Materna.de 193 Ericsson Business Communications Gunnar Nilsson ---none--- 194 Metaphor Computer Systems Paul Rodwick ---none--- 195 Patriot Partners Paul Rodwick ---none--- 196 The Software Group Limited (TSG) Ragnar Paulson tsgfred!ragnar@uunet.UU.NET 197 Kalpana, Inc. Anil Bhavnani ---none--- 198 University of Waterloo R. J. White snmp-tech@watmath.waterloo.edu 199 CCL/ITRI Ming-Perng Chen N100CMP0%TWNITRI1.BITNET@CUNYVM.CUNY.EDU 200 Coeur Postel Professor Kynikos Special Consultant 201 Mitsubish Cable Industries, Ltd. Masahiko Hori ---none---Reynolds & Postel [Page 138]
RFC 1700 Assigned Numbers October 1994 202 SMC Lance Sprung ---none--- 203 Crescendo Communication, Inc. Prem Jain prem@cres.com 204 Goodall Software Engineering Doug Goodall goodall@crl.com 205 Intecom Brad Parke ---none--- 206 Victoria University of Wellington Jonathan Stone jonathan@isor.vuw.ac.nz 207 Allied Telesis, Inc. Scott Holley SCOTT_CLINTON_HOLLEY@cup.portal.com 208 Dowty Network Systems A/S Hartvig Ekner hj@dowtyns.dk 209 Protools Glen Arp ---none--- 210 Nippon Telegraph and Telephone Corp. Toshiharu Sugawara sugawara%wink.ntt.jp@RELAY.CS.NET 211 Fujitsu Limited Ippei Hayashi hayashi@sysrap.cs.fujitsu.co.jp 212 Network Peripherals Inc. Creighton Chong cchong@fastnet.com 213 Netronix, Inc. Jacques Roth ---none--- 214 University of Wisconsin - Madison Dave Windorski DAVID.WINDORSKI@MAIL.ADMIN.WISC.EDU 215 NetWorth, Inc. Craig Scott ---none--- 216 Tandberg Data A/S Harald Hoeg haho%huldra.uucp@nac.no 217 Technically Elite Concepts, Inc. Russell S. Dietz Russell_Dietz@Mcimail.com 218 Labtam Australia Pty. Ltd. Michael Podhorodecki michael@labtam.oz.au 219 Republic Telcom Systems, Inc. Steve Harris rtsc!harris@boulder.Colorado.edu 220 ADI Systems, Inc. Paul Liu ---none--- 221 Microwave Bypass Systems, Inc. Tad Artis ---none--- 222 Pyramid Technology Corp. Richard Rein rein@pyramid.com 223 Unisys_Corp Lawrence Brow ---none--- 224 LANOPTICS LTD., Israel Israel Drori raanan@techunix.technion.ac.il 225 NKK Corporation J. Yoshida ---none--- 226 MTrade UK Ltd. Peter Delchiappo ---none--- 227 Acals Patrick Cheng pcheng@dill.ind.trw.com 228 ASTEC, Inc. Hiroshi Fujii fujii@astec.co.jp 229 Delmarva Power John K. Scoggin, Jr. scoggin@delmarva.com 230 Telematics International, Inc. Kevin Smith ---none--- 231 Siemens Nixdorf Informations Syteme AG Gunther Kroenert ---none--- 232 Compaq 233 NetManage, Inc. William Dunn netmanage@cup.portal.com 234 NCSU Computing Center David Joyner david@unity.ncsu.edu 235 Empirical Tools and Technologies Karl Auerbach karl@empirical.com 236 Samsung Group Hong K. Paik paik@samsung.com 237 Takaoka Electric Mfg. Co., Ltd. Hidekazu Hagiwara hagiwara@takaoka.takaoka-electric.co.jp 238 Netrix Systems Corporation Eldon S. Mast esm@netrix.comReynolds & Postel [Page 139]
RFC 1700 Assigned Numbers October 1994 239 WINDATA Bob Rosenbaum ---none--- 240 RC International A/S Carl H. Dreyer chd@rci.dk 241 Netexp Research Henk Boetzkes ---none--- 242 Internode Systems Pty Ltd Simon Hackett simon@ucs.adelaide.edu.au 243 netCS Informationstechnik GmbH Oliver Korfmacher okorf@bunt.netcs.com 244 Lantronix Rich Lyman rich@alecto.gordian.com 245 Avatar Consultants Kory Hamzeh ames!avatar.com!kory@harvard.harvard.edu 246 Furukawa Electoric Co. Ltd. Shoji Fukutomi kddlab!polo.furukawa.co.jp!fuku@uunet.UU.NET 247 AEG Electrcom R. Nurnberg ---none--- 248 Richard Hirschmann GmbH & Co. Heinz Nisi mia@intsun.rus.uni-stuttgart.de 249 G2R Inc. Khalid Hireche ---none--- 250 University of Michigan Tim Howes Tim.Howes@terminator.cc.umich.edu 251 Netcomm, Ltd. W.R. Maynard-Smith ---none--- 252 Sable Technology Corporation Rodney Thayer ---none--- 253 Xerox Edwards E. Reed ipcontact.cin_ops@xerox.com 254 Conware Computer Consulting GmbH Michael Sapich sapich@conware.de 255 Compatible Systems Corp. John Gawf gawf@compatible.com 256 Scitec Communications Systems Ltd. Stephen Lewis ---none--- 257 Transarc Corporation Pat Barron Pat_Barron@TRANSARC.COM 258 Matsushita Electric Industrial Co., Ltd. Nob Mizuno mizuno@isl.mei.co.jp 259 ACCTON Technology Don Rooney ---none--- 260 Star-Tek, Inc. Carl Madison carl@startek.com 261 Codenoll Tech. Corp. Dan Willie ---none--- 262 Formation, Inc. Carl Marcinik ---none--- 263 Seiko Instruments, Inc. (SII) Yasuyoshi Watanabe ---none--- 264 RCE (Reseaux de Communication d'Entreprise S.A.) Etienne Baudras-Chardigny ---none--- 265 Xenocom, Inc. Sean Welch welch@raven.ulowell.edu 266 KABELRHEYDT Hubert Theissen ---none--- 267 Systech Computer Corporation Brian Petry systech!bpetry@uunet.UU.NET 268 Visual Brian O'Shea bos@visual.com 269 SDD (Scandinavian Airlines Data Denmark A/S) Per Futtrup ---none--- 270 Zenith Electronics Corporation David Lin ---none--- 271 TELECOM FINLAND Petri Jokela ---none--- 272 BinTec Computersystems Marc Sheldon ms@BinTec.DE 273 EUnet Germany Marc Sheldon ms@Germany.EU.net 274 PictureTel Corporation Oliver Jones oj@pictel.com 275 Michigan State University Lih-Er Wey WEYLE@msu.eduReynolds & Postel [Page 140]
RFC 1700 Assigned Numbers October 1994 276 GTE Telecom Incorporated Grant Gifford ---none--- 277 Cascade Communications Corp. Chikong Shue alpo!chi@uunet.uu.net 278 Hitachi Cable, Ltd. Takahiro Asai ---none--- 279 Olivetti Marco Framba framba@orc.olivetti.com 280 Vitacom Corporation Parag Rastogi parag@cup.portal.com 281 INMOS Graham Hudspith gwh@inmos.co.uk 282 AIC Systems Laboratories Ltd. Glenn Mansfield glenn@aic.co.jp 283 Cameo Communications, Inc. Alan Brind ---none--- 284 Diab Data AB Mats Lindstrom mli@diab.se 285 Olicom A/S Lars Povlsen krus@olicom.dk 286 Digital-Kienzle Computersystems Hans Jurgen Dorr ---none--- 287 CSELT(Centro Studi E Laboratori Telecomunicazioni) Paolo Coppo coppo@cz8700.cselt.stet.it 288 Electronic Data Systems Mark Holobach holobach@tis.eds.com 289 McData Corporation Glenn Levitt gpl0363@mcmail.mcdata.com 290 Harris Corporation David Rhein davidr@ssd.csd.harris.com 291 Technology Dynamics, Inc. Chip Standifer TDYNAMICS@MCIMAIL.COM 292 DATAHOUSE Information Systems Ltd. Kim Le ---none--- 293 DSIR Network Group Tony van der Peet srghtvp@grv.dsir.govt.nz 294 Texas Instruments Blair Sanders Blair_Sanders@mcimail.com 295 PlainTree Systems Inc. Paul Chefurka chefurka@plntree.UUCP 296 Hedemann Software Development Stefan Hedemann 100015.2504@compuserve.com 297 Fuji Xerox Co., Ltd. Hiroshi Kume Kume%KSPB%Fuji_Xerox@tcpgw.netg.ksp.fujixerox.co.jp 298 Asante Technology Hsiang Ming Ma ---none--- 299 Stanford University RL "Bob" Morgan morgan@jessica.stanford.edu 300 Digital Link Jimmy Tu jimmy@dl.com 301 Raylan Corporation Mark S. Lewis mlewis@telebit.com 302 Datacraft Alan Lloyd alan@datacraft.oz 303 Hughes Keith McCloghrie KZM@HLS.COM 304 Farallon Computing, Inc. Steven Sweeney ---none--- 305 GE Information Services Steve Bush sfb@ncoast.org 306 Gambit Computer Communications Zohar Seigal ---none--- 307 Livingston Enterprises, Inc. Steve Willens steve@livingston.com 308 Star Technologies Jim Miner miner@star.com 309 Micronics Computers Inc. Darren Croke dc@micronics.com 310 Basis, Inc. Heidi Stettner heidi@mtxinu.COM 311 Microsoft John M. Ballard jballard@microsoft.com 312 US West Advance Technologies Donna Hopkins dmhopki@uswat.uswest.com 313 University College London Shaw C. Chuang S.Chuang@cs.ucl.ac.uk 314 Eastman Kodak Company W. James Colosky wjc@tornado.kodak.com 315 Network Resources Corporation Kathy Weninger ---none--- 316 Atlas Telecom Bruce Kropp ktxc8!bruce@uunet.UU.NETReynolds & Postel [Page 141]
RFC 1700 Assigned Numbers October 1994 317 Bridgeway Umberto Vizcaino ---none--- 318 American Power Conversion Corp. Peter C. Yoest apc!yoest@uunet.uu.net 319 DOE Atmospheric Radiation Measurement Project Paul Krystosek krystosk@eid.anl.gov 320 VerSteeg CodeWorks Bill Versteeg bvs@NCR.COM 321 Verilink Corp Bill Versteeg bvs@NCR.COM 322 Sybus Corportation Mark T. Dauscher mdauscher@sybus.com 323 Tekelec Bob Grady ---none--- 324 NASA Ames Research Cente Nick Cuccia cuccia@nas.nasa.gov 325 Simon Fraser University Robert Urquhart quipu@sfu.ca 326 Fore Systems, Inc. Eric Cooper ecc@fore.com 327 Centrum Communications, Inc. Vince Liu ---none--- 328 NeXT Computer, Inc. Lennart Lovstrand Lennart_Lovstrand@NeXT.COM 329 Netcore, Inc. Skip Morton ---none--- 330 Northwest Digital Systems Brian Dockter ---none--- 331 Andrew Corporation Ted Tran ---none--- 332 DigiBoard Dror Kessler dror@digibd.com 333 Computer Network Technology Corp. Bob Meierhofer ---none--- 334 Lotus Development Corp. Bill Flanagan bflanagan@lotus.com 335 MICOM Communication Corporation Donna Beatty SYSAD@prime.micom.com 336 ASCII Corporation Toshiharu Ohno tony-o@ascii.co.jp 337 PUREDATA Research Tony Baxter tony@puredata.com 338 NTT DATA Yasuhiro Kohata kohata@rd.nttdata.jp 339 Empros Systems International David Taylor dtaylor@ems.cdc.ca 340 Kendall Square Research (KSR) Dave Hudson tdh@uunet.UU.NET 341 Martin Marietta Energy Systems Gary Haney haneyg@ornl.gov 342 Network Innovations Pete Grillo pl0143@mail.psi.net 343 Intel Corporation Brady Orand borand@pcocd2.intel.com 344 Proxar Ching-Fa Hwang cfh@proxar.com 345 Epson Research Center Richard Schneider rschneid@epson.com 346 Fibernet George Sandoval ---none--- 347 Box Hill Systems Corporation Tim Jones tim@boxhill.com 348 American Express Travel Related Services Jeff Carton jcarton@amex-trs.com 349 Compu-Shack Tomas Vocetka OPLER%CSEARN.bitnet@CUNYVM.CUNY.EDU 350 Parallan Computer, Inc. Charles Dulin ---none--- 351 Stratacom Clyde Iwamoto cki@strata.com 352 Open Networks Engineering, Inc. Russ Blaesing rrb@one.com 353 ATM Forum Keith McCloghrie KZM@HLS.COM 354 SSD Management, Inc. Bill Rose ---none--- 355 Automated Network Management, Inc. Carl Vanderbeek ---none-- 356 Magnalink Communications Corporation David E. Kaufman ---none--- 357 TIL Systems, Ltd. Garry McCracken ---none--- 358 Skyline Technology, Inc. Don Weir ---none---Reynolds & Postel [Page 142]
RFC 1700 Assigned Numbers October 1994 359 Nu-Mega Technologies, Inc. Dirk Smith ---none--- 360 Morgan Stanley & Co. Inc. Victor Kazdoba vsk@katana.is.morgan.com 361 Integrated Business Network Michael Bell ---none--- 362 L & N Technologies, Ltd. Steve Loring ---none--- 363 Cincinnati Bell Information Systems, Inc. Deron Meranda dmeranda@cbis.COM 364 OSCOM International Farhad Fozdar f_fozdar@fennel.cc.uwa.edu.au 365 MICROGNOSIS Paul Andon pandon@micrognosis.co.uk 366 Datapoint Corporation Lee Ziegenhals lcz@sat.datapoint.com 367 RICOH Co. Ltd. Toshio Watanabe watanabe@godzilla.rsc.spdd.ricoh.co.jp 368 Axis Communications AB Martin Gren martin@axis.se 369 Pacer Software Wayne Tackabury wft@pacersoft.com 370 Axon Networks Inc. Robin Iddon axon@cix.clink.co.uk 371 Brixton Systems, Inc. Peter S. Easton easton@brixton.com 372 GSI Etienne Demailly etienne.demailly@gsi.fr 373 Tatung Co., Ltd. Chih-Yi Chen TCCISM1%TWNTTIT.BITNET@pucc.Princeton.EDU 374 DIS Research LTD. Ray Compton rayc@command.com 375 Quotron Systems, Inc. Richard P. Stubbs richard@atd.quotron.com 376 Dassault Electronique Olivier J. Caleff caleff@dassault-elec.fr 377 Corollary, Inc. James L. Gula gula@corollary.com 378 SEEL, Ltd. Ken Ritchie ---none--- 379 Lexcel Mike Erlinger mike@lexcel.com 380 Sophisticated Technologies, Inc. Bill Parducci 70262.1267@compuserve.com 381 OST A. Pele ---none--- 382 Megadata Pty Ltd. Andrew McRae andrew@megadata.mega.oz.au 383 LLNL Livermore Computer Center Dan Nessett nessett@ocfmail.ocf.llnl.gov 384 Dynatech Communications Graham Welling s8000!gcw@uunet.uu.net 385 Symplex Communications Corp. Cyrus Azar ---none--- 386 Tribe Computer Works Ken Fujimoto fuji@tribe.com 387 Taligent, Inc. Lorenzo Aguilar lorenzo@taligent.com 388 Symbol Technologies, Inc. John Kramer +1-408-369-2679 jkramer@psd.symbol.com 389 Lancert Mark Hankin ---none--- 390 Alantec Paul V. Fries pvf@alantec.com 391 Ridgeback Solutions Errol Ginsberg bacchus!zulu!errol@uu2.psi.com 392 Metrix, Inc. D. Venkatrangan venkat@metrix.com 393 Excutive Systems/XTree Company Dale Cabell cabell@smtp.xtree.com 394 NRL Communication Systems BranchReynolds & Postel [Page 143]
RFC 1700 Assigned Numbers October 1994 R. K. Nair nair@itd.nrl.navy.mil 395 I.D.E. Corporation Rob Spade ---none--- 396 Matsushita Electric Works, Ltd. Claude Huss claude@trc.mew.mei.co.jp 397 MegaPAC Ian George ---none--- 398 Pilkington Communication Systems Dave Atkinson ---none--- 399 Hitachi Computer Products (America), Inc. Masha Golosovker masha@hicomb.hi.com 400 METEO FRANCE Remy Giraud Remy.Giraud@meteo.fr 401 PRC Inc. Jim Noble noble_jim@prc.com 402 Wal*Mart Stores, Inc. Mike Fitzgerel mlfitzg@wal-mart.com 403 Nissin Electric Company, Ltd. Aki Komatsuzaki (408) 737-0274 404 Distributed Support Information Standard Mike Migliano <mike@uwm.edu> 405 SMDS Interest Group (SIG) Elysia C. Tan <ecmt1@sword.bellcore.com> 406 SolCom Systems Ltd. Hugh Evans 0506 873855 407 Bell Atlantic Colin deSa socrates!bm5ld15@bagout.BELL-ATL.COM 408 Advanced Multiuser Technologies Corporation 409 Mitsubishi Electric Corporation Yoshitaka Ogawa <ogawa@nkai.cow.melco.co.jp> 410 C.O.L. Systems, Inc. Frank Castellucci (914) 277-4312 411 University of Auckland Nevil Brownlee < n.brownlee@aukuni.ac.nz> 412 Desktop Management Task Force (DMTF) Dave Perkins <dperkins@synoptics.com> 413 Klever Computers, Inc. Tom Su 408-735-7723 kci@netcom.com 414 Amdahl Corporation Steve Young sy@uts.admahl.com 415 JTEC Pty, Ltd. Jan Bartel (02) 809 6933 416 Matra Communcation Hong-Loc Nguyen (33.1) 34.60.85.25 417 HAL Computer Systems Michael A. Petonic petonic@hal.com 418 Lawrence Berkeley Laboratory Russ Wright wright@lbl.gov 419 Dale Computer Corporation Dean Craven 1-800-336-7483 420 IPTC, Universitaet of Tuebingen Andreas J. Haug <ahaug@mailserv.zdv.uni-tuebingen.de> 421 Bytex Corporation Mary Ann Burt <bytex!ws054!maryann@uunet.UU.NET> 422 Cogwheel, Inc. Brian Ellis bri@Cogwheel.COM 423 Lanwan Technologies Thomas Liu (408) 986-8899 424 Thomas-Conrad Corporation Karen Boyd 512-836-1935 425 TxPort Bill VerSteeg bvs@ver.com 426 Compex, Inc. Andrew Corlett BDA@ORION.OAC.UCI.EDU 427 Evergreen Systems, Inc. Bill Grace (415) 897-8888 428 HNV, Inc. James R. Simons jrs@denver.ssds.COM 429 U.S. Robotics, Inc. Chris Rozman chrisr@usr.com 430 Canada Post Corporation Walter Brown +1 613 722-8843 431 Open Systems Solutions, Inc. David Ko davidk@ossi.com 432 Toronto Stock Exchange Paul Kwan (416) 947-4284Reynolds & Postel [Page 144]
RFC 1700 Assigned Numbers October 1994 433 MamakosTransSys Consulting Louis A. Mamakos louie@transsys.com 434 EICON Vartan Narikian vartan@eicon.qc.ca 435 Jupiter Systems Russell Leefer rml@jupiter.com 436 SSTI Philip Calas (33) 61 44 19 51 437 Grand Junction Networks Randy Ryals randyr@grandjunction.com 438 Anasazi, Inc. Chad Larson (chad@anasazi.com) 439 Edward D. Jones and Company John Caruso (314) 851-3422 440 Amnet, Inc. Richard Mak mak@amnet.COM 441 Chase Research Kevin Gage ---none--- 442 PEER Networks Randy Presuhn randy@peer.com 443 Gateway Communications, Inc. Ed Fudurich ---none--- 444 Peregrine Systems Eric Olinger eric@peregrine.com 445 Daewoo Telecom SeeYoung Oh oco@scorpio.dwt.co.kr 446 Norwegian Telecom Research Paul Hoff paalh@brage.nta.no 447 WilTel Anil Prasad anil_prasad@wiltel.com 448 Ericsson-Camtec Satish Popat ---none--- 449 Codex Thomas McGinty ---none--- 450 Basis Heidi Stettner heidi@mtxinu.COM 451 AGE Logic Syd Logan syd@age.com 452 INDE Electronics Gordon Day gday@inde.ubc.ca 453 ISODE Consortium Steve Kille S.Kille@isode.com 454 J.I. Case Mike Oswald mike@helios.uwsp.edu 455 Trillium Jeff Lawrence j_lawrence@trillium.com 456 Bacchus Inc. Errol Ginsberg bacchus!zulu!errol@uu2.psi.com 457 MCC Doug Rosenthal rosenthal@mcc.com 458 Stratus Computer Dave Snay dks@sw.stratus.com 459 Quotron Richard P. Stubbs richard@atd.quotron.com 460 Beame & Whiteside Carl Beame beame@ns.bws.com 461 Cellular Technical Services Greg Hummel ---none--- 462 Shore Microsystems, Inc. Gordon Elam (309) 229-3009 463 Telecommunications Techniques Corp. Tom Nisbet nisbet@tt.com 464 DNPAP (Technical University Delft) Jan van Oorschot <bJan.vOorschot@dnpap.et.tudelft.nl> 465 Plexcom, Inc. Bruce Miller (805) 522-3333 466 Tylink Stavros Mohlulis (508) 285-0033 467 Brookhaven National Laboratory Dave Stampf drs@bach.ccd.bnl.gov 468 Computer Communication Systems Gerard Laborde <Gerard.Laborde@sp1.y-net.fr> 469 Norand Corp. Rose Gorrell 319-269-3100 470 MUX-LAP Philippe Labrosse 514-735-2741 471 Premisys Communications, Inc Mike MacFaden <premisys!mike@fernwood.mpk.ca.us> 472 Bell South Telecommunications Johnny Walker 205-988-7105 473 J. Stainsbury PLC Steve Parker 44-71-921-7550 474 Ki Research Inc Toni Barckley 410-290-0355x220 475 Wandel and Goltermann TechnologiesReynolds & Postel [Page 145]
RFC 1700 Assigned Numbers October 1994 David Walters 919-941-5730x4203 <walter@wg.com> 476 Emerson Computer Power Roger Draper 714-457-3638 rdraper@cerf.net 477 Network Software Associates Jeffery Chiao 714-768-4013 478 Procter and Gamble Peter Marshall 513-983-1100x5988 479 Meridian Technology Corporation Kenneth B. Denson <kdenson@magic.meridiantc.com> 480 QMS, Inc. Bill Lott lott@imagen.com 481 Network Express Tom Jarema 313-761-5051 ITOH@MSEN.COM 482 LANcity Corporation Pam Yassini pam@lancity.com 483 Dayna Communications, Inc. Sanchaita Datta datta@signus.utah.edu 484 kn-X Ltd. Sam Lau 44 943 467007 485 Sync Research, Inc. Alan Bartky (714) 588-2070 486 PremNet Ken Huang HuangK@rimail.interlan.com 487 SIAC Peter Ripp (212) 383-9061 488 New York Stock Exchange Peter Ripp (212) 383-9061 489 American Stock Exchange Peter Ripp (212) 383-9061 490 FCR Software, Inc. Brad Parker brad@fcr.com 491 National Medical Care, Inc. Robert Phelan (617) 466-9850 492 Dialogue Communication Systemes, S.A. Klaus Handke +(49) 30 802 24 97 493 NorTele Bjorn Kvile +47 2 48 89 90 494 Madge Networks, Inc. Duncan Greatwood dgreatwo@madge.mhs.compuserve.com 495 Memotec Communications Graham Higgins ghiggins@teleglobe.com 496 CTON Nick Hennenfent nicholas@cton.com 497 Leap Technology, Inc. George Economou george@leap.com 498 General DataComm, Inc. William Meltzer meltzer@gdc.com 499 ACE Communications, Ltd. Danny On 972-3-570-1423 500 Automatic Data Processing (ADP) Alex Rosin (201) 714-3982 501 Programa SPRITEL Alberto Martinez Martinez_Alberto_SPRITEL@euskom.spritel.es 502 Adacom Aial Haorch 972-4-899-899 503 Metrodata Ltd Nick Brown 100022.767@compuserve.com 504 Ellemtel Telecommunication Systems Laboratories Richard G Bruvik Richard.Bruvik@eua.ericsson.se 505 Arizona Public Service Duane Booher DBOOHER@APSC.COM 506 NETWIZ, Ltd., Emanuel Wind eumzvir@techunix.technion.ac.il 507 Science and Engineering Research Council (SERC) Paul Kummer P.Kummer@daresbury.ac.uk 508 The First Boston Corporation Kevin Chou csfb1!dbadmin4!kchou@uunet.UU.NET 509 Hadax Electronics Inc. Marian Kramarczyk 73477.2731@compuserve.com 510 VTKK Markku Lamminluoto lamminluoto@vtkes1.vtkk.fi 511 North Hills Israel Ltd. Carmi Cohen carmi@north.hellnet.org 512 TECSIEL R. Burlon sr@teculx.tecsiel.itReynolds & Postel [Page 146]
RFC 1700 Assigned Numbers October 1994 513 Bayerische Motoren Werke (BMW) AG Michael Connolly mconnolly@net.bmw.de 514 CNET Technologies Nelson Su 408-954-8000 515 MCI Kurt Robohm krobohm@mcimail.com 516 Human Engineering AG (HEAG) Urs Brunner ubrunner@clients.switch.ch 517 FileNet Corporation Joe Raby raby@filenet.com 518 NFT-Ericsson Kjetil Donasen +47 2 84 24 00 519 Dun & Bradstreet Vic Smagovic 908-464-2079 520 Intercomputer Communications Brian Kean 513-745-0500x244 521 Defense Intelligence Agency Barry Atkinson DIA-DMS@DDN-CONUS.DDN.MIL 522 Telesystems SLW Inc. Joe Magony 416-441-9966 523 APT Communications David Kloper 301-831-1182 524 Delta Airlines Jim Guy 404-715-2948 525 California Microwave Kevin Braun 408-720-6520 526 Avid Technology Inc Steve Olynyk 508-640-3328 527 Integro Advanced Computer Systems Pascal Turbiez +33-20-08-00-40 528 RPTI Chris Shin 886-2-918-3006 529 Ascend Communications Inc. Marc Hyman 510-769-6001 530 Eden Computer Systems Inc. Louis Brando 305-591-7752 531 Kawasaki-Steel Corp Tomoo Watanabe nrd@info.kawasaki-steel.co.jp 532 Barclays Malcolm Houghton +44 202 671 212 533 B.U.G., Inc. Isao Tateishi tateishi@bug.co.jp 534 Exide Electronics Brian Hammill hamill@dolphin.exide.com 535 Superconducting Supercollider Lab. Carl W. Kalbfleisch cwk@irrational.ssc.gov 536 Triticom Jim Bales (612) 937-0772 537 Universal Instruments Corp. Tom Dinnel BA06791%BINGVAXA.bitnet@CUNYVM.CUNY.EDU 538 Information Resources, Inc. Jeff Gear jjg@infores.com 539 Applied Innovation, Inc. Dean Dayton dean@aicorp.cmhnet.org 540 Crypto AG Roland Luthi luthi@iis.ethz.ch 541 Infinite Networks, Ltd. Sean Harding +44 923 710 277 542 Rabbit Software Bill Kwan kwan@rabbit.com 543 Apertus Technologies Stuart Stanley stuarts@apertus.com 544 Equinox Systems, Inc. Monty Norwood 1-800-275-3500 x293 545 Hayes Microcomputer Products Chris Roussel hayes!hayes.com!croussel@uunet.UU.NET 546 Empire Technologies Inc. Cheryl Krupczak cheryl@cc.gatech.edu 547 Glaxochem, Ltd. Andy Wilson 0229 52261547 548 KPY Network Partners, Corp. Gordon Vickers sccs@pizza.netcom.com 549 Agent Technology, Inc. Ibi Dhilla idhilla@genesis.nred.ma.us 550 Dornier GMBH Arens Heinrech 49-7545-8 ext 9337 551 Telxon Corporation Frank Ciotti frankc@teleng.telxon.comReynolds & Postel [Page 147]
RFC 1700 Assigned Numbers October 1994 552 Entergy Corporation Louis Cureau 504-364-7630 553 Garrett Communications Inc. Igor Khasin (408) 980-9752 554 Agile Networks, Inc. Dave Donegan ddonegan@agile.com 555 Larscom Sameer Jayakar 415-969-7572 556 Stock Equipment Karl Klebenow 216-543-6000 557 ITT Corporation Kevin M. McCauley kmm@vaxf.acdnj.itt.com 558 Universal Data Systems, Inc. Howard Cunningham 70400.3671@compuserve.com 559 Sonix Communications, Ltd. David Webster +44 285 641 651 560 Paul Freeman Associates, Inc. Pete Wilson pwilson@world.std.com 561 John S. Barnes, Corp. Michael Lynch 704-878-4107 562 Northern Telecom, Ltd. Glenn Waters 613-763-3933 <gwaters@bnr.ca> 563 CAP Debris Patrick Preuss ppr@lfs.hamburg.cap-debris.de 564 Telco Systems NAC Harry Hirani Harry@telco-nac.com 565 Tosco Refining Co Fred Sanderson 510-602-4358 566 Russell Info Sys Atul Desai 714-362-4040 567 University of Salford Richard Letts R.J.Letts@salford.ac.uk 568 NetQuest Corp. Jerry Jacobus netquest@tigger.jvnc.net 569 Armon Networking Ltd. Yigal Jacoby yigal@armon.hellnet.org 570 IA Corporation Didier Fort Didier.Fort@lia.com 571 AU-System Communicaton AB Torbjorn Ryding 8-7267572 572 GoldStar Information & Communications, Ltd. Soo N. Kim ksn@giconet.gsic.co.kr 573 SECTRA AB Tommy Pedersen tcp@sectra.se 574 ONEAC Corporation Bill Elliot ONEACWRE@AOL.COM 575 Tree Technologies Michael Demjanenko (716) 688-4640 576 GTE Government Systems Henry Hernandez (617) 455-2942 577 Denmac Systems, Inc. Andy Denenberg (708) 291-7760 578 Interlink Computer Sciences, Inc. Mike Mazurek mfm@interlink.com 579 Bridge Information Systems, Inc. Stephen Harvey (314) 567-8482 580 Leeds and Northrup Australia (LNA) Nigel Cook nigelc@lna.oz.au 581 BHA Computer David Hislop rob@bha.oz.au 582 Newport Systems Solutions, Inc. Pauline Chen paulinec@netcom.com 583 Atrium Technologies Narender Reddy Vangati vnr@atrium.com 584 ROBOTIKER Maribel Narganes maribel@teletek.es 585 PeerLogic Inc. Ratinder Ahuja ratinder@peerlogic.com 586 Digital Transmittion Systems Bill VerSteeg bvs@ver.com 587 Far Point Communications Bill VerSteeg bvs@ver.com 588 Xircom Bill VerSteeg bvs@ver.com 589 Mead Data Central Stephanie Bowman steph@meaddata.com 590 Royal Bank of Canada N. Lim (416) 348-5197 591 Advantis, Inc. Janet Brehm 813 878-4298 592 Chemical Banking Corp. Paul McDonnell pmcdonnl@world.std.com 593 Eagle Technology Ted Haynes (408) 441-4043Reynolds & Postel [Page 148]
RFC 1700 Assigned Numbers October 1994 594 British Telecom Ray Smyth rsmyth@bfsec.bt.co.uk 595 Radix BV P. Groenendaal project2@radix.nl 596 TAINET Communication System Corp. Joseph Chen +886-2-6583000 (R.O.C.) 597 Comtek Services Inc. Steve Harris (703) 506-9556 598 Fair Issac Steve Pasadis apple.com!fico!sxp (415) 472-2211 599 AST Research Inc. Bob Beard bobb@ast.com 600 Soft*Star s.r.l. Ing. Enrico Badella softstar@pol88a.polito.it 601 Bancomm Joe Fontes jwf@bancomm.com 602 Trusted Information Systems, Inc. James M. Galvin galvin@tis.com 603 Harris & Jeffries, Inc. Deepak Shahane hjinc@CERF.NET 604 Axel Technology Corp. Henry Ngai (714) 455-1688 605 GN Navtel, Inc. Joe Magony 416-479-8090 606 CAP debis Patrick Preuss +49 40 527 28 366 607 Lachman Technology, Inc. Steve Alexander stevea@lachman.com 608 Galcom Networking Ltd. Zeev Greenblatt galnet@vax.trendline.co.il 609 BAZIS M. van Luijt martin@bazis.nl 610 SYNAPTEL Eric Remond remond@synaptel.fr 611 Investment Management Services, Inc. J. Laurens Troost rens@stimpys.imsi.com 612 Taiwan Telecommunication Lab Dennis Tseng LOUIS%TWNMOCTL.BITNET@pucc.Princeton.EDU 613 Anagram Corporation Michael Demjanenko (716) 688-4640 614 Univel John Nunneley jnunnele@univel.com 615 University of California, San Diego Arthur Bierer abierer@ucsd.edu 616 CompuServe Ed Isaacs, Brian Biggs SYSADM@csi.compuserve.com 617 Telstra - OTC Australia Peter Hanselmann peterhan@turin.research.otc.com.au 618 Westinghouse Electric Corp. Ananth Kupanna ananth@access.digex.com 619 DGA Ltd. Tom L. Willis twillis@pintu.demon.co.uk 620 Elegant Communications Inc. Robert Story Robert.Story@Elegant.COM 621 Experdata Claude Lubin clubin@expdat.gna.org 622 Unisource Business Networks Sweden AB Goran Sterner gsr@tip.net 623 Molex, Inc. Steven Joffe molex@mcimail.com 624 Quay Financial Software Mick Fleming mickf@quay.ie 625 VMX Inc. Joga Ryali joga@vmxi.cerfnet.com 626 Hypercom, Inc. Noor Chowdhury (602) 548-2113 627 University of Guelph Kent Percival Percival@CCS.UoGuelph.CA 628 DIaLOGIKa Juergen Jungfleisch 0 68 97 9 35-0 629 NBASE Switch Communication Sergiu Rotenstein 75250.1477@compuserve.com 630 Anchor Datacomm B.V. Erik Snoek sdrierik@diamond.sara.nlReynolds & Postel [Page 149]
RFC 1700 Assigned Numbers October 1994 631 PACDATA John Reed johnr@hagar.pacdata.com 632 University of Colorado Evi Nemeth evi@cs.colorado.edu 633 Tricom Communications Limited Robert Barrett 0005114429@mcimail.com 634 Santix Software GmbH Michael Santifaller santi%mozart@santix.guug.de 635 FastComm Communications Corp. Bill Flanagan 70632.1446@compuserve.com 636 The Georgia Institute of Technology Michael Mealling michael.mealling@oit.gatech.edu 637 Alcatel Data Networks Douglas E. Johnson doug.e.johnson@adn.sprint.com 638 GTECH Brian Ruptash bar@gtech.com 639 UNOCAL Corporation Peter Ho ho@unocal.com 640 First Pacific Network Randy Hamilton 408-703-2763 641 Lexmark International Don Wright don@lexmark.com 642 Qnix Computer Sang Weon, Yoo swyoo@qns.qnix.co.kr 643 Jigsaw Software Concepts (Pty) Ltd. Willem van Biljon wvb@itu2.sun.ac.za 644 VIR, Inc. Mark Cotton (215) 364-7955 645 SFA Datacomm Inc. Don Lechthaler lech@world.std.com 646 SEIKO Telecommunication Systems, Inc. Lyn T. Robertson (503) 526-5638 647 Unified Management Andy Barnhouse (612) 561-4944 648 RADLINX Ltd. Ady Lifshes ady%rndi@uunet.uu.net 649 Microplex Systems Ltd. Henry Lee hyl@microplex.com 650 Objecta Elektronik & Data AB Johan Finnved jf@objecta.se 651 Phoenix Microsystems Bill VerSteeg bvs@ver.com 652 Distributed Systems International, Inc. Ron Mackey rem@dsiinc.com 653 Evolving Systems, Inc. Judith C. Bettinger judy@evolving.com 654 SAT GmbH Walter Eichelburg 100063.74@compuserve.com 655 CeLAN Technology, Inc. Mark Liu 886--35-772780 656 Landmark Systems Corp. Steve Sonnenberg steves@socrates.umd.edu 657 Netone Systems Co., Ltd. YongKui Shao syk@new-news.netone.co.jp 658 Loral Data Systems Jeff Price jprice@cps070.lds.loral.com 659 Cellware Broadband Technology Michael Roth mike@cellware.de 660 Mu-Systems Gaylord Miyata miyata@world.std.com 661 IMC Networks Corp. Jerry Roby (714) 724-1070 662 Octel Communications Corp. Alan Newman (408) 321-5182 663 RIT Technologies LTD. Ghiora Drori drori@dcl.hellnet.org 664 Adtran Jeff Wells 205-971-8000 665 PowerPlay Technologies, Inc. Ray Caruso rayman@csn.org 666 Oki Electric Industry Co., Ltd. Shigeru Urushibara uru@cs1.cs.oki.co.jp 667 Specialix International Jeremy Rolls jeremyr@specialix.co.ukReynolds & Postel [Page 150]
RFC 1700 Assigned Numbers October 1994 668 INESC (Instituto de Engenharia de Sistemas e Computadores) Pedro Ramalho Carlos prc@inesc.pt 669 Globalnet Communications Real Barriere (514) 651-6164 670 Product Line Engineer SVEC Computer Corp. Rich Huang msumgr@enya.cc.fcu.edu.tw 671 Printer Systems Corp. Bill Babson bill@prsys.com 672 Contec Micro Electronics USA David Sheih (408) 434-6767 673 Unix Integration Services Chris Howard chris@uis.com 674 Dell Computer Corporation Steven Blair sblair@dell.com 675 Whittaker Electronic Systems Michael McCune mccune@cerf.net 676 QPSX Communications David Pascoe davidp@qpsx.oz.au 677 Loral WDl Mike Aronson Mike_Aronson@msgate.wdl.loral.com 678 Federal Express Corp. Randy Hale (901) 369-2152 679 E-COMMS Inc. Harvey Teale (206) 857-3399 680 Software Clearing House Tom Caris ca@sch.com 681 Antlow Computers LTD. C. R. Bates 44-635-871829 682 Emcom Corp. Mike Swartz emcom@cerf.net 683 Extended Systems, Inc. Al Youngwerth alberty@tommy.extendsys.com 684 Sola Electric Mike Paulsen (708) 439-2800 685 Esix Systems, Inc. Anthony Chung esix@esix.tony.com 686 3M/MMM Chris Amley ccamley@mmm.com 687 Cylink Corp. Ed Chou ed@cylink.com 688 Znyx Advanced Systems Division, Inc. Alan Deikman aland@netcom.com 689 Texaco, Inc. Jeff Lin linj@Texaco.com 690 McCaw Cellular Communication Corp. Tri Phan tri.phan@mccaw.com 691 ASP Computer Product Inc. Elise Moss 71053.1066@compuserve.com 692 HiPerformance Systems Mike Brien +27-11-806-1000 693 Regionales Rechenzentrum Sibylle Schweizer unrz54@daphne.rrze.uni-erlangen.de 694 SAP AG Dr. Uwe Hommel +49 62 27 34 0 695 ElectroSpace System Inc. Dr. Joseph Cleveland e03353@esitx.esi.org 696 ( Unassigned ) 697 MultiPort Software Reuben Sivan 72302.3262@compuserve.com 698 Combinet, Inc. Samir Sawhney samir@combinet.com 699 TSCC Carl Wist carlw@tscc.com 700 Teleos Communications Inc. Bill Nayavich wln@teleoscom.com 701 Alta Research Amy Saperstein (305) 428-8535 702 Independence Blue Cross Bill Eshbach esh@ibx.com 703 ADACOM Station Interconnectivity LTD. Itay Kariv +9 72 48 99 89 9 704 MIROR Systems Frank Kloes +27 12 911 0003 705 Merlin Gerin Adam Stolinski (714) 557-1637 x249 706 Owen-Corning Fiberglas Tom Mann mann.td@ocf.compuserve.com 707 Talking Networks Inc. Terry Braun tab@lwt.mtxinu.com 708 Cubix Corporation Rebekah Marshall (702) 883-7611Reynolds & Postel [Page 151]
RFC 1700 Assigned Numbers October 1994 709 Formation Inc. Bob Millis bobm@formail.formation.com 710 Lannair Ltd. Pablo Brenner pablo@lannet.com 711 LightStream Corp. Chris Chiotasso chris@lightstream.com 712 LANart Corp. Doron I. Gartner doron@lanart.com 713 University of Stellenbosch Graham Phillips phil@cs.sun.ac.za 714 Wyse Technology Bill Rainey bill@wyse.com 715 DSC Communications Corp. Colm Bergin cbergin@cpdsc.com 716 NetEc Thomas Krichel netec@uts.mcc.ac.uk 717 Breltenbach Software Engineering Hilmar Tuneke +02 92 49 70 00 718 Victor Company of Japan,Limited Atsushi Sakamoto 101176.2703@compuserve.com 719 Japan Direx Corporation Teruo Tomiyama +81 3 3498 5050 720 NECSY Network Control Systems S.p.A. Piero Fiozzo fip@necsy.it 721 ISDN Systems Corp. Jeff Milloy p00633@psilink.com 722 Zero-One Technologies, LTD. Curt Chen + 88 62 56 52 32 33 723 Radix Technologies, Inc. Steve Giles giless@delphi.com 724 National Institute of Standards and Technology Jim West west@mgmt3.ncsl.nist.gov 725 Digital Technology Inc. Chris Gianattasio gto@lanhawk.com 726 Castelle Corp. Waiming Mok wmm@castelle.com 727 Presticom Inc. Martin Dube 76270.2672@compuserve.com 728 Showa Electric Wire & Cable Co., Ltd. Robert O'Grady kfn@tanuki.twics.co.jp 729 SpectraGraphics Jack Hinkle hinkle@spectra.com 730 Connectware Inc. Rick Downs rxd4@acsysinc.com 731 Wind River Systems Emily Hipp hipp@wrs.com 732 RADWAY International Ltd. Doron Kolton 0005367977@mcimail.com 733 System Management ARTS, Inc. Alexander Dupuy dupuy@smarts.com 734 Persoft, Inc. Steven M. Entine entine@pervax.persoft.com 735 Xnet Technology Inc. Esther Chung estchung@xnet-tech.com 736 Unison-Tymlabs Dean Andrews ada@unison.com 737 Micro-Matic Research Patrick Lemli 73677.2373@compuserve.com 738 B.A.T.M. Advance Technologies Nahum Killim bcrystal@actcom.co.il 739 University of Copenhagen Kim H|glund shotokan@diku.dk 740 Network Security Systems, Inc. Carleton Smith rpitt@nic.cerf.net 741 JNA Telecommunications Sean Cody seanc@jna.com.au 742 Encore Computer Corporation Tony Shafer tshafer@encore.com 743 Central Intelligent Agency Carol Jobusch 703 242-2485 744 ISC (GB) Limited Mike Townsend miket@cix.compulink.co.uk 745 Digital Communication Associates Ravi Shankar shankarr@dca.com 746 CyberMedia Inc. Unni Warrier unni@cs.ucla.edu 747 Distributed Systems International, Inc. Ron Mackey rem@dsiinc.com 748 Peter Radig EDP-Consulting Peter Radig +49 69 9757 6100 749 Vicorp Interactive Systems Phil Romine phil@vis.com 750 Inet Inc. Bennie Lopez brl@inetinc.comReynolds & Postel [Page 152]
RFC 1700 Assigned Numbers October 1994 751 Argonne National Laboratory Michael Shaffer mashaffer@anl.gov 752 Tek Logix Peter Palsall 905 625-4121 753 North Western University Phil Draughon jpd@nwu.edu 754 Astarte Fiber Networks James Garnett garnett@catbelly.com 755 Diederich & Associates, Inc. Douglas Capitano dlcapitano@delphi.com 756 Florida Power Corporation Bob England rengland@fpc.com 757 ASK/INGRES Howard Dernehl howard@ingres.com 758 Open Network Enterprise Spada Stefano +39 39 245-8101 759 The Home Depot Keith Porter ktp01@homedepot.com 760 Pan Dacom Telekommunikations Jens Andresen +49 40 644 09 71 761 NetTek Steve Kennedy steve@gbnet.com 762 Karlnet Corp. Doug Kall kbridge@osu.edu 763 Efficient Networks, Inc. Thirl Johnson (214) 991-3884 764 Fiberdata Jan Fernquist +46 828 8383 765 Lanser Emil Smilovici (514) 485-7104 766 Telebit Communications A/S Peder Chr. Norgaard pcn@tbit.dk 767 HILAN GmbH Markus Pestinger markus@lahar.ka.sub.org 768 Network Computing Inc. Fredrik Noon fnoon@ncimail.mhs.compuserve.com 769 Walgreens Company Denis Renaud (708) 818-4662 770 Internet Initiative Japan Inc. Toshiharu Ohno tony-o@iij.ad.jp 771 GP van Niekerk Ondernemings Gerrit van Niekerk gvanniek@dos-lan.cs.up.ac.za 772 DSP & Telecoms Research Group Patrick McGleenon p.mcgleenon@ee.queens-belfast.ac.uk 773 Securities Industry Automation Corporation Chiu Szeto cszeto@prism.poly.edu 774 SYNaPTICS David Gray david@synaptics.ie 775 Data Switch Corporation Joe Welfeld jwelfeld@dasw.com 776 Telindus Distribution Karel Van den Bogaert kava@telindus.be 777 MAXM Systems Corporation Gary Greathouse ggreathouse@maxm.com 778 Fraunhofer Gesellschaft Jan Gottschick jan.gottschick@isst.fhg.de 779 EQS Business Services Ken Roberts kroberts@esq.com 780 CNet Technology Inc. Repus Hsiung idps17@shts.seed.net.tw 781 Datentechnik GmbH Thomas Pischinger +43 1 50100 266 782 Network Solutions Inc. Dave Putman davep@netsol.com 783 Viaman Software Vikram Duvvoori info@viman.com 784 Schweizerische Bankgesellschaft Zuerich Roland Bernet Roland.Bernet@zh014.ubs.ubs.ch 785 University of Twente - TIOS Aiko Pras pras@cs.utwente.nl 786 Simplesoft Inc. Sudhir Pendse sudhir@netcom.com 787 Stony Brook, Inc. Ken Packert p01006@psilink.com 788 Unified Systems Solutions, Inc. Steven Morgenthal smorgenthal@attmail.com 789 Network Appliance Corporation Varun Mehta varun@butch.netapp.comReynolds & Postel [Page 153]
RFC 1700 Assigned Numbers October 1994 790 Ornet Data Communication Technologies Ltd. Haim Kurz haim@ornet.co.il 791 Computer Associates International Glenn Gianino giagl01@usildaca.cai.com 792 Multipoint Network Inc. Michael Nguyen mike@multipoint.com 793 NYNEX Science & Technology Lily Lau llau@nynexst.com 794 Commercial Link Systems Wiljo Heinen wiljo@freeside.cls.de 795 Adaptec Inc. Tom Battle tab@lwt.mtxinu.com 796 Softswitch Charles Springer cjs@ssw.com 797 Link Technologies, Inc. Roy Chu royc@wyse.com 798 IIS Olry Rappaport iishaifa@attmail.com 799 Mobile Solutions Inc. Dale Shelton dshelton@srg.srg.af.mil 800 Xylan Corp. Burt Cyr burt@xylan.com 801 Airtech Software Forge Limited Callum Paterson tsf@cix.compulink.co.uk 802 National Semiconductor Maurice Turcotte mturc@atlanta.nsc.com 803 Video Lottery Technologies Angelo Lovisa ange@awd.cdc.com 804 National Semiconductor Corp Waychi Doo wcd@berlioz.nsc.com 805 Applications Management Corp Terril (Terry) Steichen tjs@washington.ssds.com 806 Travelers Insurance Company Eric Miner ustrv67v@ibmmail.com 807 Taiwan International Standard Electronics Ltd. B. J. Chen bjchen@taisel.com.tw 808 US Patent and Trademark Office Rick Randall randall@uspto.gov 809 Hynet, LTD. Amir Fuhrmann amf@teleop.co.il 810 Aydin, Corp. Rick Veher (215) 657-8600 811 ADDTRON Technology Co., LTD. Tommy Tasi +8 86-2-4514507 812 Fannie Mae David King s4ujdk@fnma.com 813 MultiNET Services Hubert Martens martens@multinet.de 814 GECKO mbH Holger Dopp hdo@gecko.de 815 Memorex Telex Mike Hill hill@raleng.mtc.com 816 Advanced Communications Networks (ACN) SA Antoine Boss +41 38 247434 817 Telekurs AG Jeremy Brookfield bkj@iris.F2.telekurs.ch 818 Victron bv Jack Stiekema jack@victron.nl 819 CF6 Company Francois Caron +331 4696 0060 820 Walker Richer and Quinn Inc. Rebecca Higgins rebecca@elmer.wrq.com 821 Saturn Systems Paul Parker paul_parker@parker.fac.cs.cmu.edu 822 Mitsui Marine and Fire Insurance Co. LTD. Kijuro Ikeda +813 5389 8111 823 Loop Telecommunication International, Inc. Charng-Show Li +886 35 787 696 824 Telenex Corporation James Krug (609) 866-1100 825 Bus-Tech, Inc. Charlie Zhang chun@eecs.cory.berkley.edu 826 ATRIE Fred B.R. Tuang cmp@fddi3.ccl.itri.org.tw 827 Gallagher & Robertson A/S Arild Braathen arild@gar.no 828 Networks Northwest, Inc. John J. Hansen jhansen@networksnw.comReynolds & Postel [Page 154]
RFC 1700 Assigned Numbers October 1994 829 Conner Peripherials Richard Boyd rboyd@mailserver.conner.com 830 Elf Antar France P. Noblanc +33 1 47 44 45 46 831 Lloyd Internetworking Glenn McGregor glenn@lloyd.com 832 Datatec Industries, Inc. Chris Wiener cwiener@datatec.com 833 TAICOM Scott Tseng cmp@fddi3.ccl.itri.org.tw 834 Brown's Operating System Services Ltd. Alistair Bell alistair@ichthya.demon.co.uk 835 MiLAN Technology Corp. Gopal Hegde gopal@milan.com 836 NetEdge Systems, Inc. Dave Minnich Dave_Minnich@netedge.com 837 NetFrame Systems George Mathew george_mathew@netframe.com 838 Xedia Corporation Colin Kincaid colin%madway.uucp@dmc.com 839 Pepsi Niraj Katwala niraj@netcom.com 840 Tricord Systems, Inc. Mark Dillon mdillon@tricord.mn.org 841 Proxim Inc. Russ Reynolds proxim@netcom.com 842 Applications Plus, Inc. Joel Estes joele@hp827.applus.com 843 Pacific Bell Aijaz Asif saasif@srv.PacBell.COM 844 Supernet Sharon Barkai sharon@supernet.com 845 TPS-Teleprocessing Systems Manfred Gorr gorr@tpscad.tps.de 846 Technology Solutions Company Niraj Katwala niraj@netcom.com 847 Computer Site Technologies Tim Hayes (805) 967-3494 848 NetPort Software John Bartas jbartas@sunlight.com 849 Alon Systems Menachem Szus 70571.1350@compuserve.com 850 Tripp Lite Lawren Markle 72170.460@compuserve.com 851 NetComm Limited Paul Ripamonti paulri@msmail.netcomm.pronet.com 852 Precision Systems, Inc. (PSI) Fred Griffin cheryl@empiretech.com 853 Objective Systems Integrators Ed Reeder Ed.Reeder@osi.com 854 Simpact Associates Inc. Robert Patterson bpatterson@dcs.simpact.com 855 Systems Enhancement Corporation Steve Held 71165.2156@compuserve.com 856 Information Integration, Inc. Gina Sun iiii@netcom.com 857 CETREL S.C. Louis Reinard ssc-re@cetrel.lu 858 ViaTech Development Theodore J. Collins III ted.collins@vtdev.mn.org 859 Olivetti North America Tom Purcell tomp@mail.spk.olivetti.com 860 WILMA Nikolaus Schaller hns@ldv.e-technik.tu-muenchen.de 861 ILX Systems Inc. Peter Mezey peterm@ilx.com 862 Total Peripherals Inc. Mark Ustik (508) 393-1777 863 SunNetworks Consultant John Brady jbrady@fedeast.east.sun.com 864 Arkhon Technologies, Inc. Joe Wang rkhon@nic.cerf.net 865 Computer Sciences Corporation George M. Dands dands@sed.csc.com 866 Philips.TRT Thibault Muchery +33 14128 7000 867 Katron Technologies Inc. Robert Kao +88 627 991 064 868 Transition Engineering Inc. Hemant Trivedi hemant@transition.comReynolds & Postel [Page 155]
RFC 1700 Assigned Numbers October 1994 869 Altos Engineering Applications, Inc. Wes Weber or Dave Erhart altoseng@netcom.com 870 Nicecom Ltd. Arik Ramon arik@nicecom.nice.com 871 Fiskars/Deltec Carl Smith (619) 291-2973 872 AVM GmbH Andreas Stockmeier stocki@avm-berlin.de 873 Comm Vision Richard Havens (408) 923 0301 x22 874 Institute for Information Industry Peter Pan peterpan@pdd.iii.org.tw 875 Legent Corporation Gary Strohm gstrohm@legent.com 876 Network Automation Doug Jackson +64 6 285 1711 877 NetTech Marshall Sprague marshall@nettech.com 878 Coman Data Communications Ltd. Zvi Sasson coman@nms.cc.huji.ac.il 879 Skattedirektoratet Karl Olav Wroldsen +47 2207 7162 880 Client-Server Technologies Timo Metsaportti timo@itf.fi 881 Societe Internationale de Telecommunications Aeronautiques Chuck Noren chuck.noren@es.atl.sita.int 882 Maximum Strategy Inc. Paul Stolle pstolle@maxstrat.com 883 Integrated Systems, Inc. Michael Zheng mz@isi.com 884 E-Systems, Melpar Rick Silton rsilton@melpar.esys.com 885 Reliance Comm/Tec Mark Scott 73422.1740@compuserve.com 886 Summa Four Inc. Paul Nelson (603) 625-4050 887 J & L Information Systems Rex Jackson (818) 709-1778 888 Forest Computer Inc. Dave Black dave@forest.com 889 Palindrome Corp. Jim Gast jgast@palindro.mhs.compuserve.com 890 ZyXEL Communications Corp. Harry Chou howie@csie.nctu.edu.tw 891 Network Managers (UK) Ltd, Mark D Dooley mark@netmgrs.co.uk 892 Sensible Office Systems Inc. Pat Townsend (712) 276-0034 893 Informix Software Anthony Daniel anthony@informix.com 894 Dynatek Communications Howard Linton (703) 490-7205 895 Versalynx Corp. Dave Fisler (619) 536-8023 896 Potomac Scheduling Communications Company David Labovitz del@access.digex.net 897 Sybase Inc. Dave Meldrum meldrum@sybase.com 898 DiviCom Inc. Eyal Opher eyal@divi.com 899 Datus elektronische Informationssysteme GmbH Hubert Mertens marcus@datus.uucp 900 Matrox Electronic Systems Limited Marc-Andre Joyal marc-andre.joyal@matrox.com 901 Digital Products, Inc. Ross Dreyer rdreyer@digprod.com 902 Scitex Corp. Ltd. Yoav Chalfon yoav_h@ird.scitex.com 903 RAD Vision Oleg Pogorelik radvis@vax.trendline.co.il 904 Tran Network Systems Paul Winkeler paulw@revco.com 905 Scorpion Logic Sean Harding +09 2324 5672 906 Inotech Inc. Eric Jacobs (703) 641-0469 907 Controlled Power Co. Yu Chin 76500,3160@compuserve.com 908 Elsag Bailey Incorporate Derek McKearney mckearney@bailey.com 909 J.P. Morgan Chung Szeto szeto_chung@jpmorgan.comReynolds & Postel [Page 156]
RFC 1700 Assigned Numbers October 1994 910 Clear Communications Corp. Kurt Hall khall@clear.com 911 General Technology Inc. Perry Rockwell (407) 242-2733 912 Adax Inc. Jory Gessow jory@adax.com 913 Mtel Technologies, Inc. Jon Robinson 552-3355@mcimail.com 914 Underscore, Inc. Jeff Schnitzer jds@underscore.com 915 SerComm Corp. Ben Lin +8 862-577-5400 916 Baxter Healthcare Corporation Joseph Sturonas sturonaj@mpg.mcgawpark.baxter.com 917 Tellus Technology Ron Cimorelli (510) 498-8500 918 Continuous Electron Beam Accelerator Facility Paul Banta banta@cebaf.gov 919 Canoga Perkins Margret Siska (818) 718-6300 920 R.I.S Technologies Fabrice Lacroix +33 7884 6400 921 INFONEX Corp. Kazuhiro Watanabe kazu@infonex.co.jp 922 WordPerfect Corp. Douglas Eddy eddy@wordperfect.com 923 NRaD Russ Carleton roccor@netcom.com 924 Hong Kong Telecommunications Ltd. K. S. Luk +8 52 883 3183 925 Signature Systems Doug Goodall goodall@crl.com 926 Alpha Technologies LTD. Guy Pothiboon (604) 430-8908 927 PairGain Technologies, Inc. Ken Huang kenh@pairgain.com 928 Sonic Systems Sudhakar Ravi sudhakar@sonicsys.com 929 Steinbrecher Corp. Kary Robertson krobertson@delphi.com 930 Centillion Networks, Inc. Derek Pitcher derek@lanspd.com 931 Network Communication Corp. Tracy Clark ncc!central!tracyc@netcomm.attmail.com 932 Sysnet A.S. Carstein Seeberg case@sysnet.no 933 Telecommunication Systems Lab Gerald Maguire maguire@it.kth.se 934 QMI Scott Brickner (410) 573-0013 935 Phoenixtec Power Co., LTD. An-Hsiang Tu +8 862 646 3311 936 Hirakawa Hewtech Corp. H. Ukaji lde02513@niftyserve.or.jp 937 No Wires Needed B.V. Arnoud Zwemmer roana@cs.utwente.nl 938 Primary Access Kerstin Lodman lodman@priacc.com 939 Enterprises.FDSW Dag Framstad dag.framstad@fdsw.no 940 Grabner & Kapfer GnbR Vinzenz Grabner zen@wsr.ac.att 941 Nemesys Research Ltd. Michael Dixon mjd@nemesys.co.uk 942 Pacific Communication Sciences, Inc. (PSCI) Yvonne Kammer mib-contact@pcsi.com 943 Level One Communications, Inc. Moshe Kochinski moshek@level1.com 944 Fast Track, Inc. Andrew H. Dimmick adimmick@world.std.com 945 Andersen Consulting, OM/NI Practice Greg Tilford p00919@psilink.com 946 Bay Technologies Pty Ltd. Paul Simpson pauls@baytech.com.au 947 Integrated Network Corp. Daniel Joffe wandan@integnet.com 948 Epoch, Inc. David Haskell deh@epoch.com 949 Wang Laboratories Inc. Pete Reilley pvr@wiis.wang.com 950 Polaroid Corp. Sari Germanos sari@temerity.polaroid.com 951 Sunrise Sierra Gerald Olson (510) 443-1133Reynolds & Postel [Page 157]
RFC 1700 Assigned Numbers October 1994 952 Silcon Group Bjarne Bonvang +45 75 54 22 55 953 Coastcom Donald Pickerel dpickere@netcom.com 954 4th DIMENSION SOFTWARE LTD. Thomas Segev/Ely Hofner autumn@zeus.datasrv.co.il 955 SEIKO SYSTEMS Inc. Kiyoshi Ishida ishi@ssi.co.jp 956 PERFORM Jean-Hugues Robert +33 42 27 29 32 957 TV/COM International Jean Tellier (619) 675-1376 958 Network Integration, Inc. Scott C. Lemon slemon@nii.mhs.compuserve.com 959 Sola Electric, A Unit of General Signal Bruce Rhodes 72360,2436@compuserve.com 960 Gradient Technologies, Inc. Geoff Charron geoff@gradient.com 961 Tokyo Electric Co., Ltd. A. Akiyama +81 558 76 9606 962 Codonics, Inc. Joe Kulig jjk@codonics.com 963 Delft Technical University Mark Schenk m.schenk@ced.tudelft.nl 964 Carrier Access Corp. Roger Koenig tomquick@carrier.com 965 eoncorp Barb Wilson wilsonb@eon.com 966 Naval Undersea Warfare Center Mark Lovelace lovelace@mp34.nl.nuwc.navy.mil 967 AWA Limited Mike Williams +61 28 87 71 11 968 Distinct Corp. Tarcisio Pedrotti tarci@distinct.com 969 National Technical University of Athens Theodoros Karounos karounos@phgasos.ntua.gr 970 BGS Systems, Inc. Amr Hafez amr@bgs.com 971 McCaw Wireless Data Inc. Brian Bailey bbailey@airdata.com 972 Bekaert Koen De Vleeschauwer kdv@bekaert.com 973 Epic Data Inc. Vincent Lim vincent_lim@epic.wimsey.com 974 Prodigy Services Co. Ed Ravin elr@wp.prodigy.com 975 First Pacific Networks (FPN) Randy Hamilton randy@fpn.com 976 Xylink Ltd. Bahman Rafatjoo 100117.665@compuserve.com 977 Relia Technologies Corp. Fred Chen fredc@relia1.relia.com.tw 978 Legacy Storage Systems Inc. James Hayes james@lss-chq.mhs.compuserve.com 979 Digicom, SPA Claudio Biotti +39 3312 0 0122 980 Ark Telecom Alan DeMars alan@arktel.com 981 National Security Agency (NSA) Cynthia Stewart maedeen@romulus.ncsc.mil 982 Southwestern Bell Corporation Brian Bearden bb8840@swuts.sbc.com 983 Virtual Design Group, Inc. Chip Standifer 70650.3316@compuserve.com 984 Rhone Poulenc Olivier Pignault +33 1348 2 4053 985 Swiss Bank Corporation Neil Todd toddn@gb.swissbank.com 986 ATEA N.V. Walter van Brussel p81710@banyan.atea.be 987 Computer Communications Specialists, Inc. Carolyn Zimmer cczimmer@crl.com 988 Object Quest, Inc. Michael L. Kornegay mlk@bir.com 989 DCL System International, Ltd. Gady Amit gady-a@dcl-see.co.ilReynolds & Postel [Page 158]
RFC 1700 Assigned Numbers October 1994 990 SOLITON SYSTEMS K.K. Masayuki Yamai +81 33356 6091 991 U S Software Don Dunstan ussw@netcom.com 992 Systems Research and Applications Corporation Todd Herr herrt@smtplink.sra.com 993 University of Florida Todd Hester todd@circa.ufl.edu 994 Dantel, Inc. John Litster (209) 292-1111 995 Multi-Tech Systems, Inc. Dale Martenson (612) 785-3500 x519 996 Softlink Ltd. Moshe Leibovitch softlink@zeus.datasrv.co.il 997 ProSum Christian Bucari +33.1.4590.6231 998 March Systems Consultancy, Ltd. Ross Wakelin r.wakelin@march.co.uk 999 Hong Technology, Inc. Walt Milnor brent@oceania.com 1000 Internet Assigned Numbers Authority iana@isi.edu 1001 PECO Energy Co. Rick Rioboli u002rdr@peco.com 1002 United Parcel Service Steve Pollini nrd1sjp@nrd.ups.com 1003 Storage Dimensions, Inc. Michael Torhan miketorh@xstor.com 1004 ITV Technologies, Inc. Jacob Chen itv@netcom.com 1005 TCPSI Victor San Jose Victor.Sanjose@sp1.y-net.es 1006 Promptus Communications, Inc. Paul Fredette (401) 683-6100 1007 Norman Data Defense Systems Kristian A. Bognaes norman@norman.no 1008 Pilot Network Services, Inc. Rob Carrade carrade@pilot.net 1009 Integrated Systems Solutions Corporation Chris Cowan cc@austin.ibm.com 1010 SISRO Kamp Alexandre 100074.344@compuserve.com 1011 NetVantage Kevin Bailey speed@kaiwan.com 1012 Marconi S.p.A. Giuseppe Grasso gg@relay.marconi.it 1013 SURECOM Mike S. T. Hsieh +886.25.92232 1014 Royal Hong Kong Jockey Club Edmond Lee 100267.3660@compuserve.com 1015 Gupta Howard Cohen hcohen@gupta.com 1016 Tone Software Corporation Neil P. Harkins (714) 991-9460 1017 Opus Telecom Pace Willisson pace@blitz.com 1018 Cogsys Ltd. Niall Teasdale niall@hedgehog.demon.co.uk 1019 Komatsu, Ltd. Akifumi Katsushima +81 463.22.84.30 1020 ROI Systems, Inc Michael Wong (801) 942-1752 1021 Lightning Instrumentation SA Mike O'Dowd odowd@lightning.ch 1022 TimeStep Corp. Stephane Lacelle slacelle@newbridge.com 1023 INTELSAT Ivan Giron i.giron@intelsat.int 1024 Network Research Corporation Japan, Ltd. Tsukasa Ueda 100156.2712@compuserve.com 1025 Relational Development, Inc. Steven Smith rdi@ins.infonet.net 1026 Emerald Systems, Corp. Robert A. Evans Jr. (619) 673-2161 x5120 1027 Mitel, Corp. Tom Quan tq@software.mitel.com 1028 Software AG Peter Cohen sagpc@sagus.com 1029 MillenNet, Inc. Manh Do (510) 770-9390 1030 NK-EXA Corp. Ken'ichi Hayami hayami@dst.nk-exa.co.jp 1031 BMC Software Chris Sharp csharp@patrol.comReynolds & Postel [Page 159]
RFC 1700 Assigned Numbers October 1994 1032 StarFire Enterprises, Inc. Lew Gaiter lg@starfire.com 1033 Hybrid Networks, Inc. Doug Muirhead dougm@hybrid.com 1034 Quantum Software GmbH Thomas Omerzu omerzu@quantum.de 1035 Openvision Technologies Limited Andrew Lockhart alockhart@openvision.co.uk 1036 Healthcare Communications, Inc. (HCI) Larry Streepy streepy@healthcare.com 1037 SAIT Systems Hai Dotu +3223.7053.11 1038 SAT Mleczko Alain +33.1.4077.1156 1039 CompuSci Inc., Bob Berry bberry@compusci.com 1040 Aim Technology Ganesh Rajappan ganeshr@aim.com 1041 CIESIN Kalpesh Unadkat kalpesh@ciesin.org 1042 Systems & Technologies International Howard Smith ghamex@aol.com 1043 Israeli Electric Company (IEC) Yoram Harlev yoram@yor.iec.co.il 1044 Phoenix Wireless Group, Inc. Gregory M. Buchanan buchanan@pwgi.com 1045 SWL Bill Kight wkightgrci.com (410) 290.7245 1046 nCUBE Greg Thompson gregt@ncube.com 1047 Cerner, Corp. Dennis Avondet (816) 221.1024 X2432 1048 Andersen Consulting Mark Lindberg mlindber@andersen.com 1049 Lincoln Telephone Company Bob Morrill root@si6000.ltec.com 1050 Acer Jay Tao jtao@Altos.COM 1051 Cedros Juergen Haakert +49.2241.9701.80 1052 AirAccess Ido Ophir 100274.365@compuserve.com 1053 Expersoft Corporation David Curtis curtis@expersoft.com 1054 Eskom Sanjay Lakhani h00161@duvi.eskom.co.za 1055 SBE, Inc. Vimal Vaidya vimal@sbei.com 1056 EBS, Inc. Emre Gundogan baroque@ebs.com 1057 American Computer and Electronics, Corp. Tom Abraham tha@acec.com 1058 Syndesis Limited Wil Macaulay wil@syndesis.com 1059 Isis Distributed Systems, Inc. Ken Chapman kchapman@isis.com 1060 Priority Call Management Greg Schumacher gregs@world.std.com 1061 Koelsch & Altmann GmbH Christian Schreyer 100142.154@compuserve.com 1062 WIPRO INFOTECH LTD. Chandrashekar Kapse kapse@wipinfo.soft.net 1063 Controlware Uli Blatz ublatz@cware.de 1064 Mosaic Software W.van Biljon willem@mosaic.co.za 1065 Canon Information Systems Victor Villalpando vvillalp@cisoc.canon.com 1066 AmericaOnline Andrew R. Scholnick andrew@aol.net 1067 Whitetree Network Technologies, Inc. Carl Yang cyang@whitetree.com 1068 Xetron Corp. Dave Alverson davea@xetron.com 1069 Target Concepts, Inc. Bill Price bprice@tamu.edu 1070 DMH Software Yigal Hochberg 72144.3704@compuserve.com 1071 Innosoft International, Inc. Jeff Allison jeff@innosoft.comReynolds & Postel [Page 160]
RFC 1700 Assigned Numbers October 1994 1072 Controlware GmbH Uli Blatz ublatz@cware.de 1073 Telecommunications Industry Association (TIA) Mike Youngberg mikey@synacom.com 1074 Boole & Babbage Rami Rubin rami@boole.com 1075 System Engineering Support, Ltd. Vince Taylor +44 454.614.638 1076 SURFnet Ton Verschuren Ton.Verschuren@surfnet.nl 1077 OpenConnect Systems, Inc. Mark Rensmeyer mrensme@oc.com 1078 PDTS (Process Data Technology and Systems) Martin Gutenbrunner GUT@pdts.mhs.compuserve.com 1079 Cornet, Inc. Nat Kumar (703) 658-3400 1080 NetStar, Inc. John K. Renwick jkr@netstar.com 1081 Semaphore Communications, Corp. Jimmy Soetarman (408) 980-7766 1082 Casio Computer Co., Ltd. Shouzo Ohdate ohdate@casio.co.jp 1083 CSIR Frikkie Strecker fstreck@marge.mikom.csir.co.za 1084 APOGEE Communications Olivier Caleff caleff@apogee-com.fr 1085 Information Management Company Michael D. Liss mliss@imc.com 1086 Wordlink, Inc. Mike Aleckson (314) 878-1422 1087 PEER Avinash S. Rao arao@cranel.com 1088 Telstra Corp. Michael Scollay michaels@ind.tansu.com.au 1089 Net X, Inc. Sridhar Kodela techsupp@netx.unicomp.net 1090 PNC PLC Gordon Tees +44 716.061.200To request an assignment of an Enterprise Number send the completecompany name, address, and phone number; and the contact's personcomplete name, address, phone number, and email mailbox in an emailmessage to <iana-mib@isi.edu>.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbersReynolds & Postel [Page 161]
RFC 1700 Assigned Numbers October 1994SGMP Vendor Specific Codes: [obsolete]Prefix: 1,255,Decimal Name References------- ---- ---------- 0 Reserved [JKR1] 1 Proteon [JS18] 2 IBM [JXR] 3 CMU [SXW] 4 Unix [MS9] 5 ACC [AB20] 6 TWG [MTR] 7 CAYMAN [BXM2] 8 NYSERNET [MS9] 9 cisco [GS2] 10 BBN [RH6] 11 Unassigned [JKR1] 12 MIT [JR35] 13-254 Unassigned [JKR1] 255 Reserved [JKR1][]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/sgmp-vendor-specific-codesReynolds & Postel [Page 162]
RFC 1700 Assigned Numbers October 1994ADDRESS RESOLUTION PROTOCOL PARAMETERSThe Address Resolution Protocol (ARP) specified in [RFC826] hasseveral parameters. The assigned values for these parameters arelisted here.REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODESThe Reverse Address Resolution Protocol (RARP) specified in [RFC903]uses the "Reverse" codes below.DYNAMIC REVERSE ARPThe Dynamic Reverse Address Resolution Protocol (DRARP) uses the"DRARP" codes below. For further information, contact: David Brownell(suneast!helium!db@Sun.COM).INVERSE ADDRESS RESOULUTION PROTOCOLThe Inverse Address Resolution Protocol (IARP) specified in [RFC1293]uses the "InARP" codes below.Assignments:Number Operation Code (op) Reference------ -------------------------- --------- 1 REQUEST [RFC826] 2 REPLY [RFC826] 3 request Reverse [RFC903] 4 reply Reverse [RFC903] 5 DRARP-Request [David Brownell] 6 DRARP-Reply [David Brownell] 7 DRARP-Error [David Brownell] 8 InARP-Request [RFC1293] 9 InARP-Reply [RFC1293] 10 ARP-NAK [Mark Laubach]Number Hardware Type (hrd) References------ ----------------------------------- ---------- 1 Ethernet (10Mb) [JBP] 2 Experimental Ethernet (3Mb) [JBP] 3 Amateur Radio AX.25 [PXK] 4 Proteon ProNET Token Ring [JBP] 5 Chaos [GXP] 6 IEEE 802 Networks [JBP] 7 ARCNET [JBP] 8 Hyperchannel [JBP] 9 Lanstar [TU]Reynolds & Postel [Page 163]
RFC 1700 Assigned Numbers October 1994 10 Autonet Short Address [MXB1] 11 LocalTalk [JKR1] 12 LocalNet (IBM PCNet or SYTEK LocalNET) [JXM] 13 Ultra link [RXD2] 14 SMDS [GXC1] 15 Frame Relay [AGM] 16 Asynchronous Transmission Mode (ATM) [JXB2] 17 HDLC [JBP] 18 Fibre Channel [Yakov Rekhter] 19 Asynchronous Transmission Mode (ATM) [Mark Laubach] 20 Serial Line [JBP] 21 Asynchronous Transmission Mode (ATM) [MXB1]Protocol Type (pro)Use the same codes as listed in the section called "Ethernet Numbersof Interest" (all hardware types use this code set for the protocoltype).REFERENCES[RFC826] Plummer, D., "An Ethernet Address Resolution Protocol or Converting Network Protocol Addresses to 48-bit Ethernet Addresses for Transmission on Ethernet Hardware", STD 37,RFC826, MIT-LCS, November 1982.[RFC903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A Reverse Address Resolution Protocol", STD 38,RFC 903, Stanford University, June 1984.[RFC1293] Bradley, T., and C. Brown, "Inverse Address Resolution Protocol",RFC 1293, Wellfleet Communications, Inc., January 1992.PEOPLE[AGM] Andy Malis <malis_a@timeplex.com>[GXC1] George Clapp <meritec!clapp@bellcore.bellcore.com>[GXP] Gill Pratt <gill%mit-ccc@MC.LCS.MIT.EDU>[JBP] Jon Postel <postel@isi.edu>[JKR1] Joyce K. Reynolds <jkrey@isi.edu>Reynolds & Postel [Page 164]
RFC 1700 Assigned Numbers October 1994[JXM] Joseph Murdock <---none--->[MXB1] Mike Burrows <burrows@SRC.DEC.COM>[PXK] Philip Koch <Philip.Koch@DARTMOUTH.EDU>[RXD2] Rajiv Dhingra <rajiv@ULTRA.COM>[TU] Tom Unger <tom@CITI.UMICH>[David Brownell][Mark Laubach][Yakov Rekhter] <Yakov@IBM.COM>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/arp-parametersReynolds & Postel [Page 165]
RFC 1700 Assigned Numbers October 1994IEEE 802 NUMBERS OF INTERESTSome of the networks of all classes are IEEE 802 Networks. Thesesystems may use a Link Service Access Point (LSAP) field in much thesame way the MILNET uses the "link" field. Further, there is anextension of the LSAP header called the Sub-Network Access Protocol(SNAP).The IEEE likes to describe numbers in binary in bit transmissionorder, which is the opposite of the big-endian order used throughoutthe Internet protocol documentation.Assignments: Link Service Access Point Description References ------------------------- ----------- ---------- IEEE Internet binary binary decimal 00000000 00000000 0 Null LSAP [IEEE] 01000000 00000010 2 Indiv LLC Sublayer Mgt [IEEE] 11000000 00000011 3 Group LLC Sublayer Mgt [IEEE] 00100000 00000100 4 SNA Path Control [IEEE] 01100000 00000110 6 Reserved (DOD IP) [RFC768,JBP] 01110000 00001110 14 PROWAY-LAN [IEEE] 01110010 01001110 78 EIA-RS 511 [IEEE] 01111010 01011110 94 ISI IP [JBP] 01110001 10001110 142 PROWAY-LAN [IEEE] 01010101 10101010 170 SNAP [IEEE] 01111111 11111110 254 ISO CLNS IS 8473 [RFC926,JXJ] 11111111 11111111 255 Global DSAP [IEEE]These numbers (and others) are assigned by the IEEE Standards Office.The address is:IEEE Registration Authorityc/o Iris RingelIEEE Standards Dept445 Hoes Lane, P.O. Box 1331Piscataway, NJ 08855-1331Phone +1 908 562 3813Fax: +1 908 562 1571The fee is $1000 and it takes 10 working days after receipt of therequest form and fee. They will not do anything via fax or phone.At an ad hoc special session on "IEEE 802 Networks and ARP", heldduring the TCP Vendors Workshop (August 1986), an approach to aReynolds & Postel [Page 166]
RFC 1700 Assigned Numbers October 1994consistent way to send DoD-IP datagrams and other IP related protocols(such as the Address Resolution Protocol (ARP)) on 802 networks wasdeveloped, using the SNAP extension (see [RFC1042]).REFERENCES[RFC768] Postel, J., "User Datagram Protocol", STD 6,RFC 768, USC/Information Sciences Institute, August 1980.[RFC926] International Standards Organization, "Protocol for Providing the Connectionless-Mode Network Services",RFC 926, ISO, December 1984.[RFC1042] Postel, J., and J. Reynolds, "A Standard for the Transmission of IP Datagrams over IEEE 802 Networks", STD 43,RFC 1042, USC/Information Sciences Institute, February 1988.PEOPLE[JBP] Jon Postel <postel@isi.edu>[JXJ] <mystery contact>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ieee-802-numbersReynolds & Postel [Page 167]
RFC 1700 Assigned Numbers October 1994ETHER TYPESMany of the networks of all classes are Ethernets (10Mb) orExperimental Ethernets (3Mb). These systems use a message "type"field in much the same way the ARPANET uses the "link" field.If you need an Ether Type, contact:Xerox Systems Institute3400 Hillview Ave.PO BOX 10034Palo Alto, CA 94303Phone: 415-813-7164Contact: Fonda Lix PalloneThe following list of EtherTypes is contributed unverified informationfrom various sources.Assignments:Ethernet Exp. Ethernet Description References------------- ------------- ----------- ----------decimal Hex decimal octal 000 0000-05DC - - IEEE802.3 Length Field [XEROX] 257 0101-01FF - - Experimental [XEROX] 512 0200 512 1000 XEROX PUP (see 0A00) [8,XEROX] 513 0201 - - PUP Addr Trans (see 0A01)[XEROX] 0400 Nixdorf [XEROX] 1536 0600 1536 3000 XEROX NS IDP [133,XEROX] 0660 DLOG [XEROX] 0661 DLOG [XEROX] 2048 0800 513 1001 Internet IP (IPv4) [105,JBP] 2049 0801 - - X.75 Internet [XEROX] 2050 0802 - - NBS Internet [XEROX] 2051 0803 - - ECMA Internet [XEROX] 2052 0804 - - Chaosnet [XEROX] 2053 0805 - - X.25 Level 3 [XEROX] 2054 0806 - - ARP [88,JBP] 2055 0807 - - XNS Compatability [XEROX] 2076 081C - - Symbolics Private [DCP1] 2184 0888-088A - - Xyplex [XEROX] 2304 0900 - - Ungermann-Bass net debugr[XEROX] 2560 0A00 - - Xerox IEEE802.3 PUP [XEROX] 2561 0A01 - - PUP Addr Trans [XEROX] 2989 0BAD - - Banyan Systems [XEROX] 4096 1000 - - Berkeley Trailer nego [XEROX] 4097 1001-100F - - Berkeley Trailer encap/IP[XEROX]Reynolds & Postel [Page 168]
RFC 1700 Assigned Numbers October 1994 5632 1600 - - Valid Systems [XEROX] 16962 4242 - - PCS Basic Block Protocol [XEROX] 21000 5208 - - BBN Simnet [XEROX] 24576 6000 - - DEC Unassigned (Exp.) [XEROX] 24577 6001 - - DEC MOP Dump/Load [XEROX] 24578 6002 - - DEC MOP Remote Console [XEROX] 24579 6003 - - DEC DECNET Phase IV Route[XEROX] 24580 6004 - - DEC LAT [XEROX] 24581 6005 - - DEC Diagnostic Protocol [XEROX] 24582 6006 - - DEC Customer Protocol [XEROX] 24583 6007 - - DEC LAVC, SCA [XEROX] 24584 6008-6009 - - DEC Unassigned [XEROX] 24586 6010-6014 - - 3Com Corporation [XEROX] 28672 7000 - - Ungermann-Bass download [XEROX] 28674 7002 - - Ungermann-Bass dia/loop [XEROX] 28704 7020-7029 - - LRT [XEROX] 28720 7030 - - Proteon [XEROX] 28724 7034 - - Cabletron [XEROX] 32771 8003 - - Cronus VLN [131,DT15] 32772 8004 - - Cronus Direct [131,DT15] 32773 8005 - - HP Probe [XEROX] 32774 8006 - - Nestar [XEROX] 32776 8008 - - AT&T [XEROX] 32784 8010 - - Excelan [XEROX] 32787 8013 - - SGI diagnostics [AXC] 32788 8014 - - SGI network games [AXC] 32789 8015 - - SGI reserved [AXC] 32790 8016 - - SGI bounce server [AXC] 32793 8019 - - Apollo Computers [XEROX] 32815 802E - - Tymshare [XEROX] 32816 802F - - Tigan, Inc. [XEROX] 32821 8035 - - Reverse ARP [48,JXM] 32822 8036 - - Aeonic Systems [XEROX] 32824 8038 - - DEC LANBridge [XEROX] 32825 8039-803C - - DEC Unassigned [XEROX] 32829 803D - - DEC Ethernet Encryption [XEROX] 32830 803E - - DEC Unassigned [XEROX] 32831 803F - - DEC LAN Traffic Monitor [XEROX] 32832 8040-8042 - - DEC Unassigned [XEROX] 32836 8044 - - Planning Research Corp. [XEROX] 32838 8046 - - AT&T [XEROX] 32839 8047 - - AT&T [XEROX] 32841 8049 - - ExperData [XEROX] 32859 805B - - Stanford V Kernel exp. [XEROX] 32860 805C - - Stanford V Kernel prod. [XEROX] 32861 805D - - Evans & Sutherland [XEROX] 32864 8060 - - Little Machines [XEROX] 32866 8062 - - Counterpoint Computers [XEROX]Reynolds & Postel [Page 169]
RFC 1700 Assigned Numbers October 1994 32869 8065 - - Univ. of Mass. @ Amherst [XEROX] 32870 8066 - - Univ. of Mass. @ Amherst [XEROX] 32871 8067 - - Veeco Integrated Auto. [XEROX] 32872 8068 - - General Dynamics [XEROX] 32873 8069 - - AT&T [XEROX] 32874 806A - - Autophon [XEROX] 32876 806C - - ComDesign [XEROX] 32877 806D - - Computgraphic Corp. [XEROX] 32878 806E-8077 - - Landmark Graphics Corp. [XEROX] 32890 807A - - Matra [XEROX] 32891 807B - - Dansk Data Elektronik [XEROX] 32892 807C - - Merit Internodal [HWB] 32893 807D-807F - - Vitalink Communications [XEROX] 32896 8080 - - Vitalink TransLAN III [XEROX] 32897 8081-8083 - - Counterpoint Computers [XEROX] 32923 809B - - Appletalk [XEROX] 32924 809C-809E - - Datability [XEROX] 32927 809F - - Spider Systems Ltd. [XEROX] 32931 80A3 - - Nixdorf Computers [XEROX] 32932 80A4-80B3 - - Siemens Gammasonics Inc. [XEROX] 32960 80C0-80C3 - - DCA Data Exchange Cluster[XEROX] 80C4 Banyan Systems [XEROX] 80C5 Banyan Systems [XEROX] 32966 80C6 - - Pacer Software [XEROX] 32967 80C7 - - Applitek Corporation [XEROX] 32968 80C8-80CC - - Intergraph Corporation [XEROX] 32973 80CD-80CE - - Harris Corporation [XEROX] 32975 80CF-80D2 - - Taylor Instrument [XEROX] 32979 80D3-80D4 - - Rosemount Corporation [XEROX] 32981 80D5 - - IBM SNA Service on Ether [XEROX] 32989 80DD - - Varian Associates [XEROX] 32990 80DE-80DF - - Integrated Solutions TRFS[XEROX] 32992 80E0-80E3 - - Allen-Bradley [XEROX] 32996 80E4-80F0 - - Datability [XEROX] 33010 80F2 - - Retix [XEROX] 33011 80F3 - - AppleTalk AARP (Kinetics)[XEROX] 33012 80F4-80F5 - - Kinetics [XEROX] 33015 80F7 - - Apollo Computer [XEROX] 33023 80FF-8103 - - Wellfleet Communications [XEROX] 33031 8107-8109 - - Symbolics Private [XEROX] 33072 8130 - - Hayes Microcomputers [XEROX] 33073 8131 - - VG Laboratory Systems [XEROX] 8132-8136 Bridge Communications [XEROX] 33079 8137-8138 - - Novell, Inc. [XEROX] 33081 8139-813D - - KTI [XEROX] 8148 Logicraft [XEROX] 8149 Network Computing Devices[XEROX] 814A Alpha Micro [XEROX]Reynolds & Postel [Page 170]
RFC 1700 Assigned Numbers October 1994 33100 814C - - SNMP [JKR1] 814D BIIN [XEROX] 814E BIIN [XEROX] 814F Technically Elite Concept[XEROX] 8150 Rational Corp [XEROX] 8151-8153 Qualcomm [XEROX] 815C-815E Computer Protocol Pty Ltd[XEROX] 8164-8166 Charles River Data System[XEROX] 817D-818C Protocol Engines [XEROX] 818D Motorola Computer [XEROX] 819A-81A3 Qualcomm [XEROX] 81A4 ARAI Bunkichi [XEROX] 81A5-81AE RAD Network Devices [XEROX] 81B7-81B9 Xyplex [XEROX] 81CC-81D5 Apricot Computers [XEROX] 81D6-81DD Artisoft [XEROX] 81E6-81EF Polygon [XEROX] 81F0-81F2 Comsat Labs [XEROX] 81F3-81F5 SAIC [XEROX] 81F6-81F8 VG Analytical [XEROX] 8203-8205 Quantum Software [XEROX] 8221-8222 Ascom Banking Systems [XEROX] 823E-8240 Advanced Encryption Syste[XEROX] 827F-8282 Athena Programming [XEROX] 8263-826A Charles River Data System[XEROX] 829A-829B Inst Ind Info Tech [XEROX] 829C-82AB Taurus Controls [XEROX] 82AC-8693 Walker Richer & Quinn [XEROX] 8694-869D Idea Courier [XEROX] 869E-86A1 Computer Network Tech [XEROX] 86A3-86AC Gateway Communications [XEROX] 86DB SECTRA [XEROX] 86DE Delta Controls [XEROX] 34543 86DF - - ATOMIC [JBP] 86E0-86EF Landis & Gyr Powers [XEROX] 8700-8710 Motorola [XEROX] 8A96-8A97 Invisible Software [XEROX] 36864 9000 - - Loopback [XEROX] 36865 9001 - - 3Com(Bridge) XNS Sys Mgmt[XEROX] 36866 9002 - - 3Com(Bridge) TCP-IP Sys [XEROX] 36867 9003 - - 3Com(Bridge) loop detect [XEROX] 65280 FF00 - - BBN VITAL-LanBridge cache[XEROX] FF00-FF0F ISC Bunker Ramo [XEROX]The standard for transmission of IP datagrams over Ethernets andExperimental Ethernets is specified in [RFC894] and [RFC895]respectively.Reynolds & Postel [Page 171]
RFC 1700 Assigned Numbers October 1994NOTE: Ethernet 48-bit address blocks are assigned by the IEEE.IEEE Registration Authorityc/o Iris RingelIEEE Standards Department445 Hoes Lane, P.O. Box 1331Piscataway, NJ 08855-1331Phone +1 908 562 3813Fax: +1 908 562 1571IANA ETHERNET ADDRESS BLOCKThe IANA owns an Ethernet address block which may be used formulticast address asignments or other special purposes.The address block in IEEE binary is: 0000 0000 0000 0000 0111 1010In the normal Internet dotted decimal notation this is 0.0.94 sincethe bytes are transmitted higher order first and bits within bytes aretransmitted lower order first (see "Data Notation" in theIntroduction).IEEE CSMA/CD and Token Bus bit transmission order: 00 00 5EIEEE Token Ring bit transmission order: 00 00 7AAppearance on the wire (bits transmitted from left to right): 0 23 47 | | | 1000 0000 0000 0000 0111 1010 xxxx xxx0 xxxx xxxx xxxx xxxx | | Multicast Bit 0 = Internet Multicast 1 = Assigned by IANA for other usesAppearance in memory (bits transmitted right-to-left within octets,octets transmitted left-to-right): 0 23 47 | | | 0000 0001 0000 0000 0101 1110 0xxx xxxx xxxx xxxx xxxx xxxx | | Multicast Bit 0 = Internet MulticastReynolds & Postel [Page 172]
RFC 1700 Assigned Numbers October 1994 1 = Assigned by IANA for other usesThe latter representation corresponds to the Internet standardbit-order, and is the format that most programmers have to deal with.Using this representation, the range of Internet Multicast addressesis: 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 decimalETHERNET VENDOR ADDRESS COMPONENTSEthernet hardware addresses are 48 bits, expressed as 12 hexadecimaldigits (0-9, plus A-F, capitalized). These 12 hex digits consist ofthe first/left 6 digits (which should match the vendor of the Ethernetinterface within the station) and the last/right 6 digits whichspecify 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 writtenhyphenated by octets (e.g., 12-34-56-78-9A-BC).These addresses are physical station addresses, not multicast norbroadcast, so the second hex digit (reading from the left) will beeven, not odd.At present, it is not clear how the IEEE assigns Ethernet blockaddresses. Whether in blocks of 2**24 or 2**25, and whethermulticasts are assigned with that block or separately. A portion ofthe vendor block address is reportedly assigned serially, with theother portion intentionally assigned randomly. If there is a globalalgorithm for which addresses are designated to be physical (in achipset) versus logical (assigned in software), or globally-assignedversus locally-assigned addresses, some of the known addresses do notfollow the scheme (e.g., AA0003; 02xxxx).00000C Cisco00000E Fujitsu00000F NeXT000010 Sytek00001D Cabletron000020 DIAB (Data Intdustrier AB)000022 Visual Technology00002A TRWReynolds & Postel [Page 173]
RFC 1700 Assigned Numbers October 1994000032 GPT Limited (reassigned from GEC Computers Ltd)00005A S & Koch00005E IANA000065 Network General00006B MIPS000077 MIPS00007A Ardent000089 Cayman SystemsGatorbox000093 Proteon00009F Ameristar Technology0000A2 Wellfleet0000A3 Network Application Technology0000A6 Network General (internal assignment, not for products)0000A7 NCD X-terminals0000A9 Network Systems0000AA Xerox Xerox machines0000B3 CIMLinc0000B7 Dove Fastnet0000BC Allen-Bradley0000C0 Western Digital0000C5 Farallon phone net card0000C6 HP Intelligent Networks Operation (formerly Eon Systems)0000C8 Altos0000C9 Emulex Terminal Servers0000D7 Dartmouth College (NED Router)0000D8 3Com? Novell? PS/20000DD Gould0000DE Unigraph0000E2 Acer Counterpoint0000EF Alantec0000FD High Level Hardvare (Orion, UK)000102 BBN BBN internal usage (not registered)0020AF 3COM ???001700 Kabel008064 Wyse Technology / Link Technologies00802B IMAC ???00802D Xylogics, Inc. Annex terminal servers00808C Frontier Software Development0080C2 IEEE 802.1 Committee0080D3 Shiva00AA00 Intel00DD00 Ungermann-Bass00DD01 Ungermann-Bass020701 Racal InterLan020406 BBN BBN internal usage (not registered)026086 Satelcom MegaPac (UK)02608C 3Com IBM PC; Imagen; Valid; Cisco02CF1F CMC Masscomp; Silicon Graphics; Prime EXLReynolds & Postel [Page 174]
RFC 1700 Assigned Numbers October 1994080002 3Com (Formerly Bridge)080003 ACC (Advanced Computer Communications)080005 Symbolics Symbolics LISP machines080008 BBN080009 Hewlett-Packard08000A Nestar Systems08000B Unisys080011 Tektronix, Inc.080014 Excelan BBN Butterfly, Masscomp, Silicon Graphics080017 NSC08001A Data General08001B Data General08001E Apollo080020 Sun Sun machines080022 NBI080025 CDC080026 Norsk Data (Nord)080027 PCS Computer Systems GmbH080028 TI Explorer08002B DEC08002E Metaphor08002F Prime Computer Prime 50-Series LHC300080036 Intergraph CAE stations080037 Fujitsu-Xerox080038 Bull080039 Spider Systems080041 DCA Digital Comm. Assoc.080045 ???? (maybe Xylogics, but they claim not to know this number)080046 Sony080047 Sequent080049 Univation08004C Encore08004E BICC080056 Stanford University080058 ??? DECsystem-2008005A IBM080067 Comdesign080068 Ridge080069 Silicon Graphics08006E Concurrent Masscomp080075 DDE (Danish Data Elektronik A/S)08007C Vitalink TransLAN III080080 XIOS080086 Imagen/QMS080087 Xyplex terminal servers080089 Kinetics AppleTalk-Ethernet interface08008B Pyramid08008D XyVision XyVision machinesReynolds & Postel [Page 175]
RFC 1700 Assigned Numbers October 1994080090 Retix Inc Bridges484453 HDS ???800010 AT&TAA0000 DEC obsoleteAA0001 DEC obsoleteAA0002 DEC obsoleteAA0003 DEC Global physical address for some DEC machinesAA0004 DEC Local logical address for systems running DECNETETHERNET MULTICAST ADDRESSESAn Ethernet multicast address consists of the multicast bit, the23-bit vendor component, and the 24-bit group identifier assigned bythe vendor. For example, DEC is assigned the vendor component08-00-2B, so multicast addresses assigned by DEC have the first24-bits 09-00-2B (since the multicast bit is the low-order bit of thefirst byte, which is "the first bit on the wire").Ethernet TypeAddress Field UsageMulticast Addresses:01-00-5E-00-00-00- 0800 Internet Multicast [RFC1112]01-00-5E-7F-FF-FF01-00-5E-80-00-00- ???? Internet reserved by IANA01-00-5E-FF-FF-FF01-80-C2-00-00-00 -802- Spanning tree (for bridges)09-00-02-04-00-01? 8080? Vitalink printer09-00-02-04-00-02? 8080? Vitalink management09-00-09-00-00-01 8005 HP Probe09-00-09-00-00-01 -802- HP Probe09-00-09-00-00-04 8005? HP DTC09-00-1E-00-00-00 8019? Apollo DOMAIN09-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 Hello09-00-2B-00-00-05 ???? DEC MAP Intermediate System Hello09-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 Experimental09-00-2B-01-00-00 8038 DEC LanBridge Copy packetsReynolds & Postel [Page 176]
RFC 1700 Assigned Numbers October 1994 (All bridges)09-00-2B-01-00-01 8038 DEC LanBridge Hello packets (All local bridges) 1 packet per second, sent by the designated LanBridge09-00-2B-02-00-00 ???? DEC DNA Lev. 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 Sys. Transport (LAST)?09-00-2B-23-00-00 803A? DEC Argonaut Console?09-00-4E-00-00-02? 8137? Novell IPX09-00-56-00-00-00- ???? Stanford reserved09-00-56-FE-FF-FF09-00-56-FF-00-00- 805C Stanford V Kernel, version 6.009-00-56-FF-FF-FF09-00-77-00-00-01 ???? Retix spanning tree bridges09-00-7C-02-00-05 8080? Vitalink diagnostics09-00-7C-05-00-01 8080? Vitalink gateway?0D-1E-15-BA-DD-06 ???? HPAB-00-00-01-00-00 6001 DEC Maintenance Operation Protocol (MOP) Dump/Load AssistanceAB-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 hostAB-00-00-04-00-00 6003 DECNET Phase IV Router Hello packets 1 packet every 15 seconds, sent by the DECNET routerAB-00-00-05-00-00 ???? Reserved DEC throughAB-00-03-FF-FF-FFAB-00-03-00-00-00 6004 DEC Local Area Transport (LAT) - oldAB-00-04-00-xx-xx ???? Reserved DEC customer private useAB-00-04-01-xx-yy 6007 DEC Local Area VAX Cluster groups Sys. Communication Architecture (SCA)CF-00-00-00-00-00 9000 Ethernet Configuration Test protocol (Loopback)Broadcast Address:Reynolds & Postel [Page 177]
RFC 1700 Assigned Numbers October 1994FF-FF-FF-FF-FF-FF 0600 XNS packets, Hello or gateway search? 6 packets every 15 seconds, per XNS stationFF-FF-FF-FF-FF-FF 0800 IP (e.g. RWHOD via UDP) as neededFF-FF-FF-FF-FF-FF 0804 CHAOSFF-FF-FF-FF-FF-FF 0806 ARP (for IP and CHAOS) as neededFF-FF-FF-FF-FF-FF 0BAD BanyanFF-FF-FF-FF-FF-FF 1600 VALID packets, Hello or gateway search? 1 packets every 30 seconds, per VALID stationFF-FF-FF-FF-FF-FF 8035 Reverse ARPFF-FF-FF-FF-FF-FF 807C Merit Internodal (INP)FF-FF-FF-FF-FF-FF 809B EtherTalkREFERENCES[RFC894] Hornig, C., "A Standard for the Transmission of IP Datagrams over Ethernet Networks, STD 41,RFC 894, Symbolics, April 1984.[RFC895] Postel, J., "A Standard for the Transmission of IP Datagrams over Experimental Ethernet Networks, STD 42,RFC 895, USC/Information Sciences Institute, April 1984.[RFC1112] Deeering, S., "Host Extensions for IP Multicasting", STD 5,RFC 1112, Stanford University, August 1989.PEOPLE[AXC] Andrew Cherenson <arc@SGI.COM>[DCP1] David Plummer <DCP@SCRC-QUABBIN.ARPA>[DT15] Daniel Tappan <Tappan@BBN.COM>[HWB] Hans-Werner Braun <HWB@MCR.UMICH.EDU>[JBP] Jon Postel <postel@isi.edu>[JKR1] Joyce K. Reynolds <jkrey@isi.edu>[JXM] Joseph Murdock <---none--->[XEROX] Fonda Pallone (415-813-7164)Reynolds & Postel [Page 178]
RFC 1700 Assigned Numbers October 1994[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ethernet-numbersReynolds & Postel [Page 179]
RFC 1700 Assigned Numbers October 1994X.25 TYPE NUMBERSCCITT defines the high order two bits of the first octet of call userdata as follows:00 - Used for other CCITT recomendations (such as X.29)01 - Reserved for use by "national" administrative authorities10 - Reserved for use by international administrative authoorities11 - Reserved for arbitrary use between consenting DTEsCall User Data (hex) Protocol Reference------------------- -------- ---------01 PAD [GS2]C5 Blacker front-end descr dev [AGM]CC IP [RFC877,AGM]*CD ISO-IP [AGM]CF PPP [RFC1598]DD Network Monitoring [AGM]*NOTE: ISO SC6/WG2 approved assignment in ISO 9577 (January 1990).REFERENCES[RFC877] Korb, J., "A Standard for the Transmission of IP Datagrams Over Public Data Networks",RFC 877, Purdue University, September 1983.[RFC1598] Simpson, W., "PPPin X.25",RFC 1598, Daydreamer, March 1994.PEOPLE[AGM] Andy Malis <malis_a@timeplex.com>[GS2] Greg Satz <satz@CISCO.COM>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/x25-type-numbersReynolds & Postel [Page 180]
RFC 1700 Assigned Numbers October 1994PUBLIC DATA NETWORK NUMBERSOne of the Internet Class A Networks is the international system ofPublic Data Networks. This section lists the mapping between theInternet Addresses and the Public Data Network Addresses (X.121).Assignments: Internet Public Data Net Description References -------------- ----------------- ----------- ---------- 014.000.000.000 Reserved [JBP] 014.000.000.001 3110-317-00035 00 PURDUE-TN [TN] 014.000.000.002 3110-608-00027 00 UWISC-TN [TN] 014.000.000.003 3110-302-00024 00 UDEL-TN [TN] 014.000.000.004 2342-192-00149 23 UCL-VTEST [PK] 014.000.000.005 2342-192-00300 23 UCL-TG [PK] 014.000.000.006 2342-192-00300 25 UK-SATNET [PK] 014.000.000.007 3110-608-00024 00 UWISC-IBM [MS56] 014.000.000.008 3110-213-00045 00 RAND-TN [MO2] 014.000.000.009 2342-192-00300 23 UCL-CS [PK] 014.000.000.010 3110-617-00025 00 BBN-VAN-GW [JD21] 014.000.000.011 2405-015-50300 00 CHALMERS [UXB] 014.000.000.012 3110-713-00165 00 RICE [PAM6] 014.000.000.013 3110-415-00261 00 DECWRL [PAM6] 014.000.000.014 3110-408-00051 00 IBM-SJ [SXA3] 014.000.000.015 2041-117-01000 00 SHAPE [JFW] 014.000.000.016 2628-153-90075 00 DFVLR4-X25 [GB7] 014.000.000.017 3110-213-00032 00 ISI-VAN-GW [JD21] 014.000.000.018 2624-522-80900 52 FGAN-SIEMENS-X25 [GB7] 014.000.000.019 2041-170-10000 00 SHAPE-X25 [JFW] 014.000.000.020 5052-737-20000 50 UQNET [AXH] 014.000.000.021 3020-801-00057 50 DMC-CRC1 [VXT] 014.000.000.022 2624-522-80329 02 FGAN-FGANFFMVAX-X25 [GB7] 014.000.000.023 2624-589-00908 01 ECRC-X25 [PXD] 014.000.000.024 2342-905-24242 83 UK-MOD-RSRE [JXE2] 014.000.000.025 2342-905-24242 82 UK-VAN-RSRE [AXM] 014.000.000.026 2624-522-80329 05 DFVLRSUN-X25 [GB7] 014.000.000.027 2624-457-11015 90 SELETFMSUN-X25 [BXD] 014.000.000.028 3110-408-00146 00 CDC-SVL [RAM57] 014.000.000.029 2222-551-04400 00 SUN-CNUCE [ABB2] 014.000.000.030 2222-551-04500 00 ICNUCEVM-CNUCE [ABB2] 014.000.000.031 2222-551-04600 00 SPARE-CNUCE [ABB2] 014.000.000.032 2222-551-04700 00 ICNUCEVX-CNUCE [ABB2] 014.000.000.033 2222-551-04524 00 CISCO-CNUCE [ABB2] 014.000.000.034 2342-313-00260 90 SPIDER-GW [AD67]Reynolds & Postel [Page 181]
RFC 1700 Assigned Numbers October 1994 014.000.000.035 2342-313-00260 91 SPIDER-EXP [AD67] 014.000.000.036 2342-225-00101 22 PRAXIS-X25A [TXR] 014.000.000.037 2342-225-00101 23 PRAXIS-X25B [TXR] 014.000.000.038 2403-712-30250 00 DIAB-TABY-GW [FXB] 014.000.000.039 2403-715-30100 00 DIAB-LKP-GW [FXB] 014.000.000.040 2401-881-24038 00 DIAB-TABY1-GW [FXB] 014.000.000.041 2041-170-10060 00 STC [TC27] 014.000.000.042 2222-551-00652 60 CNUCE [TC27] 014.000.000.043 2422-510-05900 00 Tollpost-Globe AS [OXG] 014.000.000.044 2422-670-08900 00 Tollpost-Globe AS [OXG] 014.000.000.045 2422-516-01000 00 Tollpost-Globe AS [OXG] 014.000.000.046 2422-450-00800 00 Tollpost-Globe AS [OXG] 014.000.000.047 2422-610-00200 00 Tollpost-Globe AS [OXG] 014.000.000.048 2422-310-00300 00 Tollpost-Globe AS [OXG] 014.000.000.049 2422-470-08800 00 Tollpost-Globe AS [OXG] 014.000.000.050 2422-210-04600 00 Tollpost-Globe AS [OXG] 014.000.000.051 2422-130-28900 00 Tollpost-Globe AS [OXG] 014.000.000.052 2422-310-27200 00 Tollpost-Globe AS [OXG] 014.000.000.053 2422-250-05800 00 Tollpost-Globe AS [OXG] 014.000.000.054 2422-634-05900 00 Tollpost-Globe AS [OXG] 014.000.000.055 2422-670-08800 00 Tollpost-Globe AS [OXG] 014.000.000.056 2422-430-07400 00 Tollpost-Globe AS [OXG] 014.000.000.057 2422-674-07800 00 Tollpost-Globe AS [OXG] 014.000.000.058 2422-230-16900 00 Tollpost-Globe AS [OXG] 014.000.000.059 2422-518-02900 00 Tollpost-Globe AS [OXG] 014.000.000.060 2422-370-03100 00 Tollpost-Globe AS [OXG] 014.000.000.061 2422-516-03400 00 Tollpost-Globe AS [OXG] 014.000.000.062 2422-616-04400 00 Tollpost-Globe AS [OXG] 014.000.000.063 2422-650-23500 00 Tollpost-Globe AS [OXG] 014.000.000.064 2422-330-02500 00 Tollpost-Globe AS [OXG] 014.000.000.065 2422-350-01900 00 Tollpost-Globe AS [OXG] 014.000.000.066 2422-410-00700 00 Tollpost-Globe AS [OXG] 014.000.000.067 2422-539-06200 00 Tollpost-Globe AS [OXG] 014.000.000.068 2422-630-07200 00 Tollpost-Globe AS [OXG] 014.000.000.069 2422-470-12300 00 Tollpost-Globe AS [OXG] 014.000.000.070 2422-470-13000 00 Tollpost-Globe AS [OXG] 014.000.000.071 2422-170-04600 00 Tollpost-Globe AS [OXG] 014.000.000.072 2422-516-04300 00 Tollpost-Globe AS [OXG] 014.000.000.073 2422-530-00700 00 Tollpost-Globe AS [OXG] 014.000.000.074 2422-650-18800 00 Tollpost-Globe AS [OXG] 014.000.000.075 2422-450-24500 00 Tollpost-Globe AS [OXG] 014.000.000.076 2062-243-15631 00 DPT-BXL-DDC [LZ15] 014.000.000.077 2062-243-15651 00 DPT-BXL-DDC2 [LZ15] 014.000.000.078 3110-312-00431 00 DPT-CHI [LZ15] 014.000.000.079 3110-512-00135 00 DPT-SAT-ENG [LZ15] 014.000.000.080 2080-941-90550 00 DPT-PAR [LZ15] 014.000.000.081 4545-511-30600 00 DPT-PBSC [LZ15] 014.000.000.082 4545-513-30900 00 DPT-HONGKONG [LZ15]Reynolds & Postel [Page 182]
RFC 1700 Assigned Numbers October 1994 014.000.000.083 4872-203-55000 00 UECI-TAIPEI [LZ15] 014.000.000.084 2624-551-10400 20 DPT-HANOVR [LZ15] 014.000.000.085 2624-569-00401 99 DPT-FNKFRT [LZ15] 014.000.000.086 3110-512-00134 00 DPT-SAT-SUPT [LZ15] 014.000.000.087 4602-3010-0103 20 DU-X25A [JK64] 014.000.000.088 4602-3010-0103 21 FDU-X25B [JK64] 014.000.000.089 2422-150-33700 00 Tollpost-Globe AS [OXG] 014.000.000.090 2422-271-07100 00 Tollpost-Globe AS [OXG] 014.000.000.091 2422-516-00100 00 Tollpost-Globe AS [OXG] 014.000.000.092 2422-650-18800 00 Norsk Informas. [OXG] 014.000.000.093 2422-250-30400 00 Tollpost-Globe AS [OXG] 014.000.000.094 Leissner Data AB [PXF1] 014.000.000.095 Leissner Data AB [PXF1] 014.000.000.096 Leissner Data AB [PXF1] 014.000.000.097 Leissner Data AB [PXF1] 014.000.000.098 Leissner Data AB [PXF1] 014.000.000.099 Leissner Data AB [PXF1] 014.000.000.100 Leissner Data AB [PXF1] 014.000.000.101 Leissner Data AB [PXF1] 014.000.000.102 Leissner Data AB [PXF1] 014.000.000.103 Leissner Data AB [PXF1] 014.000.000.104 Leissner Data AB [PXF1] 014.000.000.105 Leissner Data AB [PXF1] 014.000.000.106 Leissner Data AB [PXF1] 014.000.000.107 Leissner Data AB [PXF1] 014.000.000.108 Leissner Data AB [PXF1] 014.000.000.109 Leissner Data AB [PXF1] 014.000.000.110 Leissner Data AB [PXF1] 014.000.000.111 Leissner Data AB [PXF1] 014.000.000.112 Leissner Data AB [PXF1] 014.000.000.113 Leissner Data AB [PXF1] 014.000.000.114 Leissner Data AB [PXF1] 014.000.000.115 Leissner Data AB [PXF1] 014.000.000.116 Leissner Data AB [PXF1] 014.000.000.117 Leissner Data AB [PXF1] 014.000.000.118 Leissner Data AB [PXF1] 014.000.000.119 Leissner Data AB [PXF1] 014.000.000.120 Leissner Data AB [PXF1] 014.000.000.121 Leissner Data AB [PXF1] 014.000.000.122 Leissner Data AB [PXF1] 014.000.000.123 Leissner Data AB [PXF1] 014.000.000.124 Leissner Data AB [PXF1] 014.000.000.125 Leissner Data AB [PXF1] 014.000.000.126 Leissner Data AB [PXF1] 014.000.000.127 Leissner Data AB [PXF1] 014.000.000.128 Leissner Data AB [PXF1] 014.000.000.129 2422-150-17900 00 Tollpost-Globe AS [OXG] 014.000.000.130 2422-150-42700 00 Tollpost-Globe AS [OXG]Reynolds & Postel [Page 183]
RFC 1700 Assigned Numbers October 1994 014.000.000.131 2422-190-41900 00 T-G Airfreight AS [OXG] 014.000.000.132 2422-616-16100 00 Tollpost-Globe AS [OXG] 014.000.000.133 2422-150-50700-00 Tollpost-Globe Int. [OXG] 014.000.000.134 2422-190-28100-00 Intersped AS [OXG] 014.000.000.135-014.255.255.254 Unassigned [JBP] 014.255.255.255 Reserved [JBP]The standard for transmission of IP datagrams over the Public DataNetwork is specified inRFC-1356 [69].REFERENCES[RFC877] Korb, J., "A Standard for the Transmission of IP Datagrams Over Public Data Networks",RFC 877, Purdue University, September 1983.PEOPLE[ABB2] A. Blasco Bonito <blasco@ICNUCEVM.CNUCE.CNR.IT>[AD67] Andy Davis <andy@SPIDER.CO.UK>[AXH] Arthur Harvey <harvey@gah.enet.dec.com>[AXM] Alex Martin <---none--->[BXD] Brian Dockter <---none--->[FXB] <mystery contact>[GB7] Gerd Beling <GBELING@ISI.EDU>[JBP] Jon Postel <postel@isi.edu.[JD21] Jonathan Dreyer <Dreyer@CCV.BBN.COM>[JFW] Jon F. Wilkes <Wilkes@CCINT1.RSRE.MOD.UK>[JK64] mystery contact![JXE2] Jeanne Evans <JME%RSRE.MOD.UK@CS.UCL.AC.UK>[LZ15] Lee Ziegenhals <lcz@sat.datapoint.com>[MS56] Marvin Solomon <solomon@CS.WISC.EDU>Reynolds & Postel [Page 184]
RFC 1700 Assigned Numbers October 1994[MO2] Michael O'Brien <obrien@AEROSPACE.AERO.ORG>[OXG] Oyvind Gjerstad <ogj%tglobe2.UUCP@nac.no>[PAM6] Paul McNabb <pam@PURDUE.EDU>[PK] Peter Kirstein <Kirstein@NSS.CS.UCL.AC.UK>[PXD] Peter Delchiappo <---none--->[PXF1] Per Futtrup <---none--->[RAM57] Rex Mann <---none--->[SXA3] Sten Andler <---none--->[TN] Thomas Narten <narten@PURDUE.EDU>[TC27] Thomas Calderwood <TCALDERW@BBN.COM>[TXR] Tim Rylance <praxis!tkr@UUNET.UU.NET>[UXB] <mystery contact>[VXT] V. Taylor <vktaylor@NCS.DND.CA>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/public-data-network-numbersReynolds & Postel [Page 185]
RFC 1700 Assigned Numbers October 1994MILNET LINK NUMBERSThe word "link" here refers to a field in the original MILNET Host/IMPinterface leader. The link was originally defined as an 8-bit field.Later specifications defined this field as the "message-id" with alength of 12 bits. The name link now refers to the high order 8 bits ofthis 12-bit message-id field. The Host/IMP interface is defined in BBNReport 1822 [BBN1822].The low-order 4 bits of the message-id field are called the sub-link.Unless explicitly specified otherwise for a particular protocol, thereis no sender to receiver significance to the sub-link. The sender mayuse the sub-link in any way he chooses (it is returned in the RFNM bythe destination IMP), the receiver should ignore the sub-link.Link Assignments:Decimal Description References------- ----------- ----------0-63 BBNCC Monitoring [MB]64-149 Unassigned [JBP]150 Xerox NS IDP [ETHERNET,XEROX]151 Unassigned [JBP]152 PARC Universal Protocol [PUP,XEROX]153 TIP Status Reporting [JGH]154 TIP Accounting [JGH]155 Internet Protocol [regular] [RFC791,JBP]156-158 Internet Protocol [experimental] [RFC791,JBP]159 Figleaf Link [JBW1]160 Blacker Local Network Protocol [DM28]161-194 Unassigned [JBP]195 ISO-IP [RFC926,RXM]196-247 Experimental Protocols [JBP]248-255 Network Maintenance [JGH]MILNET LOGICAL ADDRESSESThe MILNET facility for "logical addressing" is described in [RFC878]and [RFC1005]. A portion of the possible logical addresses arereserved for standard uses.There are 49,152 possible logical host addresses. Of these, 256 arereserved for assignment to well-known functions. Assignments forwell-known functions are made by the IANA. Assignments for otherReynolds & Postel [Page 186]
RFC 1700 Assigned Numbers October 1994logical host addresses are made by the NIC.Logical Address Assignments:Decimal Description References------- ----------- ----------0 Reserved [JBP]1 The BBN Core Gateways [MB]2-254 Unassigned [JBP]255 Reserved [JBP]MILNET X.25 ADDRESS MAPPINGSAll MILNET hosts are assigned addresses by the Defense Data Network(DDN). The address of a MILNET host may be obtained from the NetworkInformation Center (NIC), represented as an ASCII text string in whatis called "host table format". This section describes the process bywhich MILNET X.25 addresses may be derived from addresses in the NIChost table format.A NIC host table address consists of the ASCII text stringrepresentations of four decimal numbers separated by periods,corresponding to the four octeted of a thirty-two bit Internetaddress. The four decimal numbers are referred to in this section as"n", "h' "l", and "i". Thus, a host table address may be representedas: "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.25physical 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 leadingReynolds & Postel [Page 187]
RFC 1700 Assigned Numbers October 1994 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 optionalIn the example given above, the host table address 10.2.0.124corresponds to the X.25 physical address 000001240200.2. If h > 64 or h = 64, the host table address corresponds to theX.25 logical addressZZZZ F RRRRRZZ (SS)where: ZZZZ = 0000 as required F = 1 because the address is a logical address; RRRRR is a five decimal digit representation of the result "r" of the calculation r = h * 256 + i (Note that the decimal representation of "r" will always require five digits); ZZ = 00 and (SS) is optionalThus, the host table address 10.83.0.207 corresponds to the X.25logical address 000012145500.In both cases, the "n" and "l" fields of the host table address arenot used.REFERENCES[BBN1822] BBN, "Specifications for the Interconnection of a Host andReynolds & Postel [Page 188]
RFC 1700 Assigned Numbers October 1994 an IMP", Report 1822, Bolt Beranek and Newman, Cambridge, Massachusetts, revised, December 1981.[ETHERNET] "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.[PUP] 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.[RFC791] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", STD 5,RFC 791, USC/Information Sciences Institute, September 1981.[RFC878] Malis, Andrew, "The ARPANET 1822L Host Access Protocol",RFC 878, BBN Communications Corp., December 1983.[RFC926] International Standards Organization, "Protocol for Providing the Connectionless-Mode Network Services",RFC 926, ISO, December 1984.[RFC1005] Khanna, A., and A. Malis, "The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)",RFC 1005, BBN Communications Corp., May 1987.PEOPLE[DM28] Dennis Morris <Morrisd@IMO-UVAX.DCA.MIL>[JBP] Jon Postel <postel@isi.edu>[JBW1] Joseph Walters, Jr. <JWalters@BBN.COM>[JGH] Jim Herman <Herman@CCJ.BBN.COM>[MB] Michael Brescia <Brescia@CCV.BBN.COM>Reynolds & Postel [Page 189]
RFC 1700 Assigned Numbers October 1994[RXM] Robert Myhill <Myhill@CCS.BBN.COM>[XEROX] Fonda Pallone <---none--->[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/milnet-parametersReynolds & Postel [Page 190]
RFC 1700 Assigned Numbers October 1994XNS PROTOCOL TYPESAssigned well-known socket numbers Routing Information 1 Echo 2 Router Error 3 Experimental 40-77Assigned internet packet types Routing Information 1 Echo 2 Error 3 Packet Exchange 4 Sequenced Packet 5 PUP 12 DoD IP 13 Experimental 20-37[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/xns-protocol-typesReynolds & Postel [Page 191]
RFC 1700 Assigned Numbers October 1994INTERNET / XNS PROTOCOL MAPPINGSBelow are two tables describing the arrangement of protocol fields ortype field assignments so that one could send XNS Datagrams on theMILNET or Internet Datagrams on 10Mb Ethernet, and also protocol andtype fields so one could encapsulate each kind of Datagram in theother. 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 |MILNET | 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 192]
RFC 1700 Assigned Numbers October 1994URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ip-xns-mappingReynolds & Postel [Page 193]
RFC 1700 Assigned Numbers October 1994PRONET 80 TYPE NUMBERSBelow is the current list of PRONET 80 Type Numbers. Note: a protocolthat is on this list does not necessarily mean that there is anyimplementation of it on ProNET.Of these, protocols 1, 14, and 20 are the only ones that have everbeen 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 JohnShriver (jas@proteon.com).1 IP2 IP with trailing headers3 Address Resolution Protocol4 Proteon HDLC5 VAX Debugging Protocol (MIT)10 Novell NetWare (IPX and pre-IPX) (old format, 3 byte trailer)11 Vianetix12 PUP13 Watstar protocol (University of Waterloo)14 XNS15 Diganostics16 Echo protocol (link level)17 Banyan Vines20 DECnet (DEUNA Emulation)21 Chaosnet23 IEEE 802.2 or ISO 8802/2 Data Link24 Reverse Address Resolution Protocol29 TokenVIEW-1031 AppleTalk LAP Data Packet33 Cornell Boot Server Location Protocol34 Novell NetWare IPX (new format, no trailer, new XOR checksum)Reynolds & Postel [Page 194]
RFC 1700 Assigned Numbers October 1994[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/pronet80-type-numbersReynolds & Postel [Page 195]
RFC 1700 Assigned Numbers October 1994NOVELL SAP NUMBERS OF INTERESTFor the convenience of the Internet community the IANA maitains a listof Novell Service Access Point (SAP) numbers. This list is keptup-to-date- by contributions from the community. Please sendcorrections and additions to IANA@ISI.EDU.Novell SAPs====== ====Decimal Hex SAP Description======= ==== ===============0 0000 Unknown1 0001 User2 0002 User Group3 0003 Print Queue or Print Group4 0004 File Server (SLIST source)5 0005 Job Server6 0006 Gateway7 0007 Print Server or Silent Print Server8 0008 Archive Queue9 0009 Archive Server10 000a Job Queue11 000b Administration15 000F Novell TI-RPC23 0017 Diagnostics32 0020 NetBIOS33 0021 NAS SNA Gateway35 0023 NACS Async Gateway or Asynchronous Gateway36 0024 Remote Bridge or Routing Service38 0026 Bridge Server or Asynchronous Bridge Server39 0027 TCP/IP Gateway Server40 0028 Point to Point (Eicon) X.25 Bridge Server41 0029 Eicon 3270 Gateway42 002a CHI Corp ???44 002c PC Chalkboard45 002d Time Synchronization Server or Asynchronous Timer46 002e SAP Archive Server or SMS Target Service Agent69 0045 DI3270 Gateway71 0047 Advertising Print Server75 004b Btrieve VAP/NLM 5.076 004c Netware SQL VAP/NLM Server77 004d Xtree Network Version Netware XTree80 0050 Btrieve VAP 4.1182 0052 QuickLink (Cubix)83 0053 Print Queue User88 0058 Multipoint X.25 Eicon RouterReynolds & Postel [Page 196]
RFC 1700 Assigned Numbers October 199496 0060 STLB/NLM ???100 0064 ARCserve102 0066 ARCserve 3.0114 0072 WAN Copy Utility122 007a TES-Netware for VMS146 0092 WATCOM Debugger or Emerald Tape Backup Server149 0095 DDA OBGYN ???152 0098 Netware Access Server (Asynchronous gateway)154 009a Netware for VMS II or Named Pipe Server155 009b Netware Access Server158 009e Portable Netware Server or SunLink NVT161 00a1 Powerchute APC UPS NLM170 00aa LAWserve ???172 00ac Compaq IDA Status Monitor256 0100 PIPE STAIL ???258 0102 LAN Protect Bindery259 0103 Oracle DataBase Server263 0107 Netware 386 or RSPX Remote Console271 010f Novell SNA Gateway274 0112 Print Server (HP)276 0114 CSA MUX (f/Communications Executive)277 0115 CSA LCA (f/Communications Executive)278 0116 CSA CM (f/Communications Executive)279 0117 CSA SMA (f/Communications Executive)280 0118 CSA DBA (f/Communications Executive)281 0119 CSA NMA (f/Communications Executive)282 011a CSA SSA (f/Communications Executive)283 011b CSA STATUS (f/Communications Executive)286 011e CSA APPC (f/Communications Executive)294 0126 SNA TEST SSA Profile298 012a CSA TRACE (f/Communications Executive)304 0130 Communications Executive307 0133 NNS Domain Server or Netware Naming Services Domain309 0135 Netware Naming Services Profile311 0137 Netware 386 Print Queue or NNS Print Queue321 0141 LAN Spool Server (Vap, Intel)338 0152 IRMALAN Gateway340 0154 Named Pipe Server360 0168 Intel PICKIT Comm Server or Intel CAS Talk Server369 171 UNKNOWN???371 0173 Compaq372 0174 Compaq SNMP Agent373 0175 Compaq384 0180 XTree Server or XTree Tools394 18A UNKNOWN??? Running on a Novell Server432 01b0 GARP Gateway (net research)433 01b1 Binfview (Lan Support Group)447 01bf Intel LanDesk ManagerReynolds & Postel [Page 197]
RFC 1700 Assigned Numbers October 1994458 01ca AXTEC ???459 01cb Netmode ???460 1CC UNKNOWN??? Sheva netmodem???472 01d8 Castelle FAXPress Server474 01da Castelle LANPress Print Server476 1DC Castille FAX/Xerox 7033 Fax Server/Excel Lan Fax496 01f0 LEGATO ???501 01f5 LEGATO ???563 0233 NMS Agent or Netware Management Agent567 0237 NMS IPX Discovery or LANtern Read/Write Channel568 0238 NMS IP Discovery or LANtern Trap/Alarm Channel570 023a LABtern572 023c MAVERICK ???574 23E UNKNOWN??? Running on a Novell Server575 023f Used by eleven various Novell Servers590 024e Remote Something ???618 026a Network Management (NMS) Service Console619 026b Time Synchronization Server (Netware 4.x)632 0278 Directory Server (Netware 4.x)772 0304 Novell SAA Gateway776 0308 COM or VERMED 1 ???778 030a Gallacticom BBS780 030c Intel Netport 2 or HP JetDirect or HP Quicksilver800 0320 Attachmate Gateway807 0327 Microsoft Diagnostiocs ???821 0335 MultiTech Systems Multisynch Comm Server853 0355 Arcada Backup Exec858 0358 MSLCD1 ???865 0361 NETINELO ???894 037e Twelve Novell file servers in the PC3M family895 037f ViruSafe Notify902 0386 HP Bridge903 0387 HP Hub916 0394 NetWare SAA Gateway923 039b Lotus Notes951 03b7 Certus Anti Virus NLM964 03c4 ARCserve 4.0 (Cheyenne)967 03c7 LANspool 3.5 (Intel)990 03de Gupta Sequel Base Server or NetWare SQL993 03e1 Univel Unixware996 03e4 Univel Unixware1020 03fc Intel Netport1021 03fd Print SErver Queue ???1034 40A ipnServer??? Running on a Novell Server1035 40B UNKNOWN???1037 40D LVERRMAN??? Running on a Novell Server1038 40E LVLIC??? Running on a Novell Server1040 410 UNKNOWN??? Running on a Novell ServerReynolds & Postel [Page 198]
RFC 1700 Assigned Numbers October 19941044 0414 Kyocera1065 0429 Site Lock Virus (Brightworks)1074 0432 UFHELP R ???1075 433 Sunoptics SNMP Agent???1100 044c Backup ???1111 457 Canon GP55??? Running on a Canon GP55 network printer1115 045b Dell SCSI Array (DSA) Monitor1200 04b0 CD-Net (Meridian)1217 4C1 UNKNOWN???1299 513 Emulux NQA??? Something from Emulex1312 0520 Site Lock Checks1321 0529 Site Lock Checks (Brightworks)1325 052d Citrix OS/2 App Server1344 536 Milan ???1408 0580 McAfee's NetShield anti-virus1569 621 ?? Something from Emulex1571 623 UNKNOWN??? Running on a Novell Server1900 076C Xerox2857 0b29 Site Lock3113 0c29 Site Lock Applications3116 0c2c Licensing Server9088 2380 LAI Site Lock9100 238c Meeting Maker18440 4808 Site Lock Server or Site Lock Metering VAP/NLM21845 5555 Site Lock User25362 6312 Tapeware28416 6f00 Rabbit Gateway (3270)30467 7703 MODEM??32770 8002 NetPort Printers (Intel) or LANport32776 8008 WordPerfect Network Version34238 85BE Cisco Enhanced Interior Routing Protocol (EIGRP)34952 8888 WordPerfect Network Version or Quick Network Management36864 9000 McAfee's NetShield anti-virus38404 9604 ?? CSA-NT_MON61727 f11f Site Lock Metering VAP/NLM61951 f1ff Site Lock62723 F503 ?? SCA-NT65535 ffff Any Service or WildcardThis file isftp://ftp.isi.edu/in-notes/iana/assignments/novell-sap-numbers[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/novell-sap-numbersReynolds & Postel [Page 199]
RFC 1700 Assigned Numbers October 1994POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTSPPP DLL PROTOCOL NUMBERSThe Point-to-Point Protocol (PPP) Data Link Layer [146,147,175]contains a 16 bit Protocol field to identify the the encapsulatedprotocol. The Protocol field is consistent with the ISO 3309 (HDLC)extension mechanism for Address fields. All Protocols MUST beassigned such that the least significant bit of the most significantoctet equals "0", and the least significant bit of the leastsignificant octet equals "1".Assigned PPP DLL Protocol NumbersValue (in hex) Protocol Name0001 Padding Protocol0003 to 001f reserved (transparency inefficient)0021 Internet Protocol0023 OSI Network Layer0025 Xerox NS IDP0027 DECnet Phase IV0029 Appletalk002b Novell IPX002d Van Jacobson Compressed TCP/IP002f Van Jacobson Uncompressed TCP/IP0031 Bridging PDU0033 Stream Protocol (ST-II)0035 Banyan Vines0037 reserved (until 1993)0039 AppleTalk EDDP003b AppleTalk SmartBuffered003d Multi-Link003f NETBIOS Framing0041 Cisco Systems0043 Ascom Timeplex0045 Fujitsu Link Backup and Load Balancing (LBLB)0047 DCA Remote Lan0049 Serial Data Transport Protocol (PPP-SDTP)004b SNA over 802.2004d SNA004f IP6 Header Compression006f Stampede Bridging007d reserved (Control Escape) [RFC1661]007f reserved (compression inefficient) [RFC1662]00cf reserved (PPP NLPID)00fb compression on single link in multilink group00fd 1st choice compressionReynolds & Postel [Page 200]
RFC 1700 Assigned Numbers October 199400ff reserved (compression inefficient)0201 802.1d Hello Packets0203 IBM Source Routing BPDU0205 DEC LANBridge100 Spanning Tree0231 Luxcom0233 Sigma Network Systems8001-801f Not Used - reserved [RFC1661]8021 Internet Protocol Control Protocol8023 OSI Network Layer Control Protocol8025 Xerox NS IDP Control Protocol8027 DECnet Phase IV Control Protocol8029 Appletalk Control Protocol802b Novell IPX Control Protocol802d reserved802f reserved8031 Bridging NCP8033 Stream Protocol Control Protocol8035 Banyan Vines Control Protocol8037 reserved till 19938039 reserved803b reserved803d Multi-Link Control Protocol803f NETBIOS Framing Control Protocol807d Not Used - reserved [RFC1661]8041 Cisco Systems Control Protocol8043 Ascom Timeplex8045 Fujitsu LBLB Control Protocol8047 DCA Remote Lan Network Control Protocol (RLNCP)8049 Serial Data Control Protocol (PPP-SDCP)804b SNA over 802.2 Control Protocol804d SNA Control Protocol804f IP6 Header Compression Control Protocol006f Stampede Bridging Control Protocol80cf Not Used - reserved [RFC1661]80fb compression on single link in multilink group control80fd Compression Control Protocol80ff Not Used - reserved [RFC1661]c021 Link Control Protocolc023 Password Authentication Protocolc025 Link Quality Reportc027 Shiva Password Authentication Protocolc029 CallBack Control Protocol (CBCP)c081 Container Control Protocol [KEN]c223 Challenge Handshake Authentication Protocolc281 Proprietary Authentication Protocol [KEN]Reynolds & Postel [Page 201]
RFC 1700 Assigned Numbers October 1994c26f Stampede Bridging Authorization Protocolc481 Proprietary Node ID Authentication Protocol [KEN]Protocol field values in the "0xxx" to "3xxx" range identify thenetwork-layer protocol of specific datagrams, and values in the "8xxx"to "bxxx" range identify datagrams belonging to the associated NetworkControl Protocol (NCP), if any.It is recommended that values in the "02xx" to "1exx" and "xx01" to"xx1f" ranges not be assigned, as they are compression inefficient.Protocol field values in the "4xxx" to "7xxx" range are used forprotocols with low volume traffic which have no associated NCP.Protocol field values in the "cxxx" to "exxx" range identify datagramsas Control Protocols (such as LCP).PPP LCP AND IPCP CODESThe Point-to-Point Protocol (PPP) Link Control Protocol (LCP), [146]the Compression Control Protocol (CCP), Internet Protocol ControlProtocol (IPCP), [147] and other control protocols, contain an 8 bitCode field which identifies the type of packet. These Codes areassigned as follows:Code Packet Type---- ----------- 1 Configure-Request 2 Configure-Ack 3 Configure-Nak 4 Configure-Reject 5 Terminate-Request 6 Terminate-Ack 7 Code-Reject 8 * Protocol-Reject 9 * Echo-Request 10 * Echo-Reply 11 * Discard-Request 12 * Identification 13 * Time-Remaining 14 + Reset-Request 15 + Reset-Reply* LCP Only+ CCP OnlyPPP LCP CONFIGURATION OPTION TYPESReynolds & Postel [Page 202]
RFC 1700 Assigned Numbers October 1994The Point-to-Point Protocol (PPP) Link Control Protocol (LCP)specifies a number of Configuration Options [146] which aredistinguished by an 8 bit Type field. These Types are assigned asfollows:Type Configuration Option---- -------------------- 1 Maximum-Receive-Unit 2 Async-Control-Character-Map 3 Authentication-Protocol 4 Quality-Protocol 5 Magic-Number 6 RESERVED 7 Protocol-Field-Compression 8 Address-and-Control-Field-Compression 9 FCS-Alternatives 10 Self-Describing-Pad 11 Numbered-Mode 12 Multi-Link-Procedure 13 Callback 14 Connect-Time 15 Compound-Frames 16 Nominal-Data-Encapsulation 17 Multilink-MRRU 18 Multilink-Short-Sequence-Number-Header-Format 19 Multilink-Endpoint-Discriminator 20 Proprietary [KEN] 21 DCE-Identifier [SCHNEIDER]PPP LCP FCS-ALTERNATIVESThe Point-to-Point Protocol (PPP) Link Control Protocol (LCP)FCS-Alternatives Configuration Option contains an 8-bit Options fieldwhich identifies the FCS used. These are assigned as follows:Bit FCS---- ---------- 1 Null FCS 2 CCITT 16-Bit FCS 4 CCITT 32-bit FCSPPP LCP CALLBACK OPERATION FIELDSThe Point-to-Point Protocol (PPP) Link Control Protocol (LCP) CallbackConfiguration Option contains an 8-bit Operations field whichidentifies the format of the Message. These are assigned as follows:Reynolds & Postel [Page 203]
RFC 1700 Assigned Numbers October 1994Operation Description--------- --------------------------- 0 Location determined by user authentication. 1 Dialing string. 2 Location identifier. 3 E.164 number. 4 X.500 distinguished name. 5 unassigned 6 Location is determined during CBCP negotiation.PPP IPCP CONFIGURATION OPTION TYPESThe Point-to-Point Protocol (PPP) Internet Protocol Control Protocol(IPCP) specifies a number of Configuration Options [147] which aredistinguished by an 8 bit Type field. These Types are assigned asfollows:Type Configuration Option---- -------------------- 1 IP-Addresses (deprecated) 2 IP-Compression-Protocol 3 IP-AddressPPP ATCP CONFIGURATION OPTION TYPESThe Point-to-Point Protocol (PPP) Apple Talk Control Protocol (ATCP)specifies a number of Configuration Options [RFC-1378] which aredistinguished by an 8 bit Type field. These Types are assigned asfollows:Type Configuration Option---- -------------------- 1 AppleTalk-Address 2 Routing-Protocol 3 Suppress-Broadcasts 4 AT-Compression-Protocol 5 Reserved 6 Server-information 7 Zone-information 8 Default-Router-AddressPPP OSINLCP CONFIGURATION OPTION TYPESThe Point-to-Point Protocol (PPP) OSI Network Layer Control Protocol(OSINLCP) specifies a number of Configuration Options [RFC-1377] whichare distinguished by an 8 bit Type field. These Types are assigned asfollows:Reynolds & Postel [Page 204]
RFC 1700 Assigned Numbers October 1994Type Configuration Option---- -------------------- 1 Align-NPDUPPP BRIDGING CONFIGURATION OPTION TYPESThe Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)specifies a number of Configuration Options which are distinguished byan 8 bit Type field. These Types are assigned as follows:Type Configuration Option---- -------------------- 1 Bridge-Identification 2 Line-Identification 3 MAC-Support 4 Tinygram-Compression 5 LAN-Identification 6 MAC-Address 7 Spanning-Tree-ProtocolPPP BRIDGING MAC TYPESThe Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)contains an 8 bit MAC Type field which identifies the MACencapsulated. These Types are assigned as follows:Type MAC---- ----------- 0 Reserved 1 IEEE 802.3/Ethernet with cannonical addresses 2 IEEE 802.4 with cannonical addresses 3 IEEE 802.5 with non-cannonical addresses 4 FDDI with non-cannonical addresses 5-10 reserved 11 IEEE 802.5 with cannonical addresses 12 FDDI with cannonical addressesPPP BRIDGING SPANNING TREEThe Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)Spanning Tree Configuration Option contains an 8-bit Protocol fieldwhich identifies the spanning tree used. These are assigned asfollows:Protocol Spanning Tree-------- --------------- 0 Null - no spanning tree protocol supported 1 IEEE 802.1D spanning tree protocolReynolds & Postel [Page 205]
RFC 1700 Assigned Numbers October 1994 2 IEEE 802.1G extended spanning tree protocol 3 IBM source route spanning tree protocol 4 DEC LANbridge 100 spanning tree protocolREFERENCES[RFC1661] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD 51,RFC 1661, Daydreamer, July 1994.[RFC1662] Simpson, W., Editor, "PPP in HDLC-like Framing", STD 51,RFC1662, Daydreamer, July 1994.PEOPLE[KEN] <ken@funk.com>[SCHNEIDER] Kevin Schneider <kevin@adtran.com>[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbersReynolds & Postel [Page 206]
RFC 1700 Assigned Numbers October 1994MACHINE NAMESThese are the Official Machine Names as they appear in the Domain NameSystem HINFO records and the NIC Host Table. Their use is describedin [RFC952].A machine name or CPU type may be up to 40 characters taken from theset of uppercase letters, digits, and the two punctuation charactershyphen and slash. It must start with a letter, and end with a letteror digit.AMIGA-500AMIGA-500/010AMIGA-500/020AMIGA-500/EC030AMIGA-500/030AMIGA-600AMIGA-1000AMIGA-1000/010AMIGA-1000/020AMIGA-1000/EC030AMIGA-1000/030AMIGA-1200AMIGA-1200/EC030AMIGA-1200/030AMIGA-1200/EC040AMIGA-1200/LC040AMIGA-1200/040AMIGA-2000AMIGA-2000/010AMIGA-2000/020AMIGA-2000/EC030AMIGA-2000/030AMIGA-2000/LC040AMIGA-2000/EC040AMIGA-2000/040AMIGA-3000AMIGA-3000/EC040AMIGA-3000/LC040AMIGA-3000/040AMIGA-3000/060AMIGA-4000/EC030AMIGA-4000/030AMIGA-4000/LC040AMIGA-4000/040AMIGA-4000/060ALTOReynolds & Postel [Page 207]
RFC 1700 Assigned Numbers October 1994ALTOS-6800AMDAHL-V7APOLLOAPPLE-MACINTOSHAPPLE-POWERBOOKATARI-104STATT-3B1ATT-3B2ATT-3B20ATT-7300AXPBBN-C/60BURROUGHS-B/29BURROUGHS-B/4800BUTTERFLYC/30C/70CADLINCCADRCDC-170CDC-170/750CDC-173CDTVCDTV/060CD32CELERITY-1200CLUB-386COMPAQ-386/20COMTEN-3690CP8040CRAY-1CRAY-X/MPCRAY-2CTIWS-117DANDELIONDEC-10DEC-1050DEC-1077DEC-1080DEC-1090DEC-1090BDEC-1090TDEC-2020TDEC-2040DEC-2040TDEC-2050TDEC-2060DEC-2060TReynolds & Postel [Page 208]
RFC 1700 Assigned Numbers October 1994DEC-2065DEC-AXPDEC-FALCONDEC-KS10DECSTATIONDEC-VAXDEC-VAXCLUSTERDEC-VAXSTATIONDEC-VAX-11730DORADODPS8/70MELXSI-6400EVEREX-386FOONLY-F2FOONLY-F3FOONLY-F4GOULDGOULD-6050GOULD-6080GOULD-9050GOULD-9080H-316H-60/68H-68H-68/80H-89HONEYWELL-DPS-6HONEYWELL-DPS-8/70HP3000HP3000/64IBM-158IBM-360/67IBM-370/3033IBM-3081IBM-3084QXIBM-3101IBM-4331IBM-4341IBM-4361IBM-4381IBM-4956IBM-6152IBM-PCIBM-PC/ATIBM-PC/RTIBM-PC/XTIBM-RS/6000IBM-SERIES/1Reynolds & Postel [Page 209]
RFC 1700 Assigned Numbers October 1994IMAGENIMAGEN-8/300IMSAIINTEGRATED-SOLUTIONSINTEGRATED-SOLUTIONS-68KINTEGRATED-SOLUTIONS-CREATORINTEGRATED-SOLUTIONS-CREATOR-8INTEL-386INTEL-IPSCIS-1IS-68010LMILSI-11LSI-11/2LSI-11/23LSI-11/73M68000MAC-IIMAC-POWERBOOKMACINTOSHMASSCOMPMC500MC68000MICROPORTMICROVAXMICROVAX-IMV/8000NAS3-5NCR-COMTEN-3690NEXT/N1000-316NOWONYX-Z8000PDP-11PDP-11/3PDP-11/23PDP-11/24PDP-11/34PDP-11/40PDP-11/44PDP-11/45PDP-11/50PDP-11/70PDP-11/73PE-7/32PE-3205PERQPLEXUS-P/60PLIReynolds & Postel [Page 210]
RFC 1700 Assigned Numbers October 1994PLURIBUSPRIME-2350PRIME-2450PRIME-2755PRIME-9655PRIME-9755PRIME-9955IIPRIME-2250PRIME-2655PRIME-9955PRIME-9950PRIME-9650PRIME-9750PRIME-2250PRIME-750PRIME-850PRIME-550IIPYRAMID-90PYRAMID-90MXPYRAMID-90XRIDGERIDGE-32RIDGE-32CROLM-1666RS/6000S1-MKIIASMISEQUENT-BALANCE-8000SIEMENSSILICON-GRAPHICSSILICON-GRAPHICS-IRISSGI-IRIS-2400SGI-IRIS-2500SGI-IRIS-3010SGI-IRIS-3020SGI-IRIS-3030SGI-IRIS-3110SGI-IRIS-3115SGI-IRIS-3120SGI-IRIS-3130SGI-IRIS-4D/20SGI-IRIS-4D/20GSGI-IRIS-4D/25SGI-IRIS-4D/25GSGI-IRIS-4D/25SSGI-IRIS-4D/50SGI-IRIS-4D/50GSGI-IRIS-4D/50GTReynolds & Postel [Page 211]
RFC 1700 Assigned Numbers October 1994SGI-IRIS-4D/60SGI-IRIS-4D/60GSGI-IRIS-4D/60TSGI-IRIS-4D/60GTSGI-IRIS-4D/70SGI-IRIS-4D/70GSGI-IRIS-4D/70GTSGI-IRIS-4D/80GTSGI-IRIS-4D/80SSGI-IRIS-4D/120GTXSGI-IRIS-4D/120SSGI-IRIS-4D/210GTXSGI-IRIS-4D/210SSGI-IRIS-4D/220GTXSGI-IRIS-4D/220SSGI-IRIS-4D/240GTXSGI-IRIS-4D/240SSGI-IRIS-4D/280GTXSGI-IRIS-4D/280SSGI-IRIS-CS/12SGI-IRIS-4SERVER-8SPERRY-DCP/10SUNSUN-2SUN-2/50SUN-2/100SUN-2/120SUN-2/130SUN-2/140SUN-2/150SUN-2/160SUN-2/170SUN-3/50SUN-3/60SUN-3/75SUN-3/80SUN-3/110SUN-3/140SUN-3/150SUN-3/160SUN-3/180SUN-3/200SUN-3/260SUN-3/280SUN-3/470SUN-3/480SUN-4/60SUN-4/110Reynolds & Postel [Page 212]
RFC 1700 Assigned Numbers October 1994SUN-4/150SUN-4/200SUN-4/260SUN-4/280SUN-4/330SUN-4/370SUN-4/390SUN-50SUN-100SUN-120SUN-130SUN-150SUN-170SUN-386i/250SUN-68000SYMBOLICS-3600SYMBOLICS-3670SYMMETRIC-375SYMULTTANDEM-TXPTANDY-6000TEK-6130TI-EXPLORERTP-4000TRS-80UNIVAC-1100UNIVAC-1100/60UNIVAC-1100/62UNIVAC-1100/63UNIVAC-1100/64UNIVAC-1100/70UNIVAC-1160UNKNOWNVAXVAX-11/725VAX-11/730VAX-11/750VAX-11/780VAX-11/785VAX-11/790VAX-11/8600VAX-8600VAXCLUSTERVAXSTATIONWANG-PC002WANG-VS100WANG-VS400WYSE-386Reynolds & Postel [Page 213]
RFC 1700 Assigned Numbers October 1994WYSE-WN5004WYSE-WN5008WYSE-WN5104WYSE-WN5108WYSE-WX15CWYSE-WX17CWYSE-WX17MWYSE-WX19CWYSE-WX19MWYSE-WYX14MWYSE-WYX5XEROX-1108XEROX-8010ZENITH-148REFERENCES[RFC952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet Host Table Specification",RFC 952, SRI, October 1985.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/machine-namesReynolds & Postel [Page 214]
RFC 1700 Assigned Numbers October 1994OPERATING SYSTEM NAMESThese are the Official System Names as they appear in the Domain NameSystem HINFO records and the NIC Host Table. Their use is described in[RFC952].A system name may be up to 40 characters taken from the set ofuppercase letters, digits, and the three punctuation charactershyphen, period, and slash. It must start with a letter, and end witha letter or digit.AEGISAMIGA-OS-1.2AMIGA-OS-1.3AMIGA-OS-2.0AMIGA-OS-2.1AMIGA-OS-3.0AMIGA-OS-3.1APOLLOAIX/370AIX-PS/2BS-2000CEDARCGWCHORUSCHRYSALISCMOSCMSCOSCPIXCTOSCTSSDCNDDNOSDOMAINDOSEDXELFEMBOSEMMOSEPOSFOONEXFORTHFUZZGCOSGPOSReynolds & Postel [Page 215]
RFC 1700 Assigned Numbers October 1994HDOSIMAGENINTERCOMIMPRESSINTERLISPIOSIRIXISI-68020ITSLISPLISPMLOCUSMACOSMINOSMOSMPE5MPE/VMPE/IXMSDOSMULTICSMUSICMUSIC/SPMVSMVS/SPNEXUSNMSNONSTOPNOS-2NTOSOPENVMSOS/DDPOS/2OS4OS86OSXPCDOSPERQ/OSPLIPSDOS/MITPRIMOSRMX/RDOSROSRSX11MRTE-ASATOPSSCO-OPEN-DESKTOP-1.0SCO-OPEN-DESKTOP-1.1SCO-OPEN-DESKTOP-2.0Reynolds & Postel [Page 216]
RFC 1700 Assigned Numbers October 1994SCO-OPEN-DESKTOP-3.0SCO-OPEN-DESKTOP-LITE-3.0SCO-OPEN-SERVER-3.0SCO-UNIX-3.2.0SCO-UNIX-3.2V2.0SCO-UNIX-3.2V2.1SCO-UNIX-3.2V4.0SCO-UNIX-3.2V4.1SCO-UNIX-3.2V4.2SCO-XENIX-386-2.3.2SCO-XENIX-386-2.3.3SCO-XENIX-386-2.3.4SCSSIMPSUNSUN-OS-3.5SUN-OS-4.0SWIFTTACTANDEMTENEXTHE-MAJOR-BBSTOPS10TOPS20TOSTP3010TRSDOSULTRIXUNIXUNIX-BSDUNIX-V1ATUNIX-VUNIX-V.1UNIX-V.2UNIX-V.3UNIX-PCUNKNOWNUT2DVVMVM/370VM/CMSVM/SPVMSVMS/EUNICEVRTXWAITSWANGReynolds & Postel [Page 217]
RFC 1700 Assigned Numbers October 1994WIN32WYSE-WYXWAREX11R3XDEXENIXREFERENCES[RFC952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet Host Table Specification",RFC 952, SRI, October 1985.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/operating-system-namesReynolds & Postel [Page 218]
RFC 1700 Assigned Numbers October 1994TERMINAL TYPE NAMESThese are the Official Terminal Type Names. Their use is described in[RFC930]. The maximum length of a name is 40 characters.A terminal names may be up to 40 characters taken from the set ofuppercase letters, digits, and the two punctuation characters hyphenand slash. It must start with a letter, and end with a letter ordigit.ADDS-CONSUL-980ADDS-REGENT-100ADDS-REGENT-20ADDS-REGENT-200ADDS-REGENT-25ADDS-REGENT-40ADDS-REGENT-60ADDS-VIEWPOINTADDS-VIEWPOINT-60AED-512AMPEX-DIALOGUE-210AMPEX-DIALOGUE-80AMPEX-210AMPEX-230ANDERSON-JACOBSON-510ANDERSON-JACOBSON-630ANDERSON-JACOBSON-832ANDERSON-JACOBSON-841ANN-ARBOR-AMBASSADORANSIARDSBITGRAPHBUSSIPLEXERCALCOMP-565CDC-456CDI-1030CDI-1203C-ITOH-101C-ITOH-50C-ITOH-80CLNZCOMPUCOLOR-IICONCEPT-100CONCEPT-104CONCEPT-108DATA-100Reynolds & Postel [Page 219]
RFC 1700 Assigned Numbers October 1994DATA-GENERAL-6053DATAGRAPHIX-132ADATAMEDIA-1520DATAMEDIA-1521DATAMEDIA-2500DATAMEDIA-3025DATAMEDIA-3025ADATAMEDIA-3045DATAMEDIA-3045ADATAMEDIA-DT80/1DATAPOINT-2200DATAPOINT-3000DATAPOINT-3300DATAPOINT-3360DEC-DECWRITER-IDEC-DECWRITER-IIDEC-GIGIDEC-GT40DEC-GT40ADEC-GT42DEC-LA120DEC-LA30DEC-LA36DEC-LA38DEC-VT05DEC-VT100DEC-VT101DEC-VT102DEC-VT125DEC-VT131DEC-VT132DEC-VT200DEC-VT220DEC-VT240DEC-VT241DEC-VT300DEC-VT320DEC-VT340DEC-VT50DEC-VT50HDEC-VT52DEC-VT55DEC-VT61DEC-VT62DELTA-DATA-5000DELTA-DATA-NIH-7000DELTA-TELTERM-2DIABLO-1620Reynolds & Postel [Page 220]
RFC 1700 Assigned Numbers October 1994DIABLO-1640DIGILOG-333DTC-300SDTC-382EDT-1200ETOS52-APLETOS52-CRTETOS52-FDWETOS52-FUPETOS52-GFMETOS52-SPREXECUPORT-4000EXECUPORT-4080FACIT-TWIST-4440FREEDOM-100FREEDOM-110FREEDOM-200GENERAL-TERMINAL-100AGENERAL-TERMINAL-101GIPSI-TX-MGIPSI-TX-MEGIPSI-TX-C4GIPSI-TX-C8GSIHAZELTINE-1420HAZELTINE-1500HAZELTINE-1510HAZELTINE-1520HAZELTINE-1552HAZELTINE-2000HAZELTINE-ESPRITHITACHI-5601HITACHI-5603HITACHI-5603EHITACHI-5603EAHITACHI-560XHITACHI-560XEHITACHI-560XEAHITACHI-560PRHITACHI-HOAP1HITACHI-HOAP2HITACHI-HOAP3HITACHI-HOAP4HP-2392HP-2621HP-2621AHP-2621PHP-2623Reynolds & Postel [Page 221]
RFC 1700 Assigned Numbers October 1994HP-2626HP-2626AHP-2626PHP-2627HP-2640HP-2640AHP-2640BHP-2645HP-2645AHP-2648HP-2648AHP-2649HP-2649AIBM-1050IBM-2741IBM-3101IBM-3101-10IBM-3151IBM-3179-2IBM-3180-2IBM-3196-A1IBM-3275-2IBM-3276-2IBM-3276-3IBM-3276-4IBM-3277-2IBM-3278-2IBM-3278-3IBM-3278-4IBM-3278-5IBM-3279-2IBM-3279-3IBM-3477-FCIBM-3477-FGIBM-5081IBM-5151IBM-5154IBM-5251-11IBM-5291-1IBM-5292-2IBM-5555-B01IBM-5555-C01IBM-6153IBM-6154IBM-6155IBM-AEDIBM-3278-2-EIBM-3278-3-EReynolds & Postel [Page 222]
RFC 1700 Assigned Numbers October 1994IBM-3278-4-EIBM-3278-5-EIBM-3279-2-EIBM-3279-3-EIMLACINFOTON-100INFOTON-400INFOTONKASISC-8001LSI-ADM-1LSI-ADM-11LSI-ADM-12LSI-ADM-2LSI-ADM-20LSI-ADM-22LSI-ADM-220LSI-ADM-3LSI-ADM-31LSI-ADM-3ALSI-ADM-42LSI-ADM-5MEMOREX-1240MICROBEEMICROTERM-ACT-IVMICROTERM-ACT-VMICROTERM-ERGO-301MICROTERM-MIME-1MICROTERM-MIME-2MICROTERM-ACT-5AMICROTERM-TWISTNEC-5520NETRONICSNETWORK-VIRTUAL-TERMINALOMRON-8025AGPERKIN-ELMER-550PERKIN-ELMER-1100PERKIN-ELMER-1200PERQPLASMA-PANELQUME-SPRINT-5QUME-101QUME-102SOROCSOROC-120SOUTHWEST-TECHNICAL-PRODUCTS-CT82SUNSUPERBEESUPERBEE-III-MReynolds & Postel [Page 223]
RFC 1700 Assigned Numbers October 1994TECTEKTRONIX-4006TEKTRONIX-4010TEKTRONIX-4012TEKTRONIX-4013TEKTRONIX-4014TEKTRONIX-4023TEKTRONIX-4024TEKTRONIX-4025TEKTRONIX-4027TEKTRONIX-4105TEKTRONIX-4107TEKTRONIX-4110TEKTRONIX-4112TEKTRONIX-4113TEKTRONIX-4114TEKTRONIX-4115TEKTRONIX-4125TEKTRONIX-4404TELERAY-1061TELERAY-3700TELERAY-3800TELETEC-DATASCREENTELETERM-1030TELETYPE-33TELETYPE-35TELETYPE-37TELETYPE-38TELETYPE-40TELETYPE-43TELEVIDEO-910TELEVIDEO-912TELEVIDEO-920TELEVIDEO-920BTELEVIDEO-920CTELEVIDEO-925TELEVIDEO-955TELEVIDEO-950TELEVIDEO-970TELEVIDEO-975TERMINET-1200TERMINET-300TI-700TI-733TI-735TI-743TI-745TI-800Reynolds & Postel [Page 224]
RFC 1700 Assigned Numbers October 1994TYCOMUNIVAC-DCT-500VIDEO-SYSTEMS-1200VIDEO-SYSTEMS-5000VOLKER-CRAIG-303VOLKER-CRAIG-303AVOLKER-CRAIG-404VISUAL-200VISUAL-55WYSE-30WYSE-50WYSE-60WYSE-75WYSE-85WYSE-99GTWYSE-100WYSE-120WYSE-120ESWYSE-150WYSE-150ESWYSE-160WYSE-160ESWYSE-185WYSE-185ESWYSE-285WYSE-285ESWYSE-325WYSE-325ESWYSE-350WYSE-370XEROX-1720XTERMZENITH-H19ZENITH-Z29ZENTEC-30REFERENCES[RFC930] Solomon, M., and E. Wimmers, "Telnet Terminal Type Option",RFC 930, University of Wisconsin, Madison, January 1985.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/terminal-type-namesReynolds & Postel [Page 225]
RFC 1700 Assigned Numbers October 1994PROTOCOL AND SERVICE NAMESThese are the Official Protocol Names as they appear in the DomainName System WKS records and the NIC Host Table. Their use isdescribed in [RFC952].A protocol or service may be up to 40 characters taken from the set ofuppercase letters, digits, and the punctuation character hyphen. Itmust start with a letter, and end with a letter or digit.ARGUS - ARGUS ProtocolARP - Address Resolution ProtocolAUTH - Authentication ServiceBBN-RCC-MON - BBN RCC MonitoringBL-IDM - Britton Lee Intelligent Database MachineBOOTP - Bootstrap ProtocolBOOTPC - Bootstrap Protocol ClientBOOTPS - Bootstrap Protocol ServerBR-SAT-MON - Backroom SATNET MonitoringCFTP - CFTPCHAOS - CHAOS ProtocolCHARGEN - Character Generator ProtocolCISCO-FNA - CISCO FNATIVECISCO-TNA - CISCO TNATIVECISCO-SYS - CISCO SYSMAINTCLOCK - DCNET Time Server ProtocolCMOT - Common Mgmnt Info Ser and Prot over TCP/IPCOOKIE-JAR - Authentication SchemeCSNET-NS - CSNET Mailbox Nameserver ProtocolDAYTIME - Daytime ProtocolDCN-MEAS - DCN Measurement Subsystems ProtocolDCP - Device Control ProtocolDGP - Dissimilar Gateway ProtocolDISCARD - Discard ProtocolDMF-MAIL - Digest Message Format for MailDOMAIN - Domain Name SystemECHO - Echo ProtocolEGP - Exterior Gateway ProtocolEHF-MAIL - Encoding Header Field for MailEMCON - Emission Control ProtocolEMFIS-CNTL - EMFIS Control ServiceEMFIS-DATA - EMFIS Data ServiceFCONFIG - Fujitsu Config ProtocolFINGER - Finger ProtocolFTP - File Transfer ProtocolFTP-DATA - File Transfer Protocol DataReynolds & Postel [Page 226]
RFC 1700 Assigned Numbers October 1994GGP - Gateway Gateway ProtocolGRAPHICS - Graphics ProtocolHMP - Host Monitoring ProtocolHOST2-NS - Host2 Name ServerHOSTNAME - Hostname ProtocolICMP - Internet Control Message ProtocolIGMP - Internet Group Management ProtocolIGP - Interior Gateway ProtocolIMAP2 - Interim Mail Access Protocol version 2INGRES-NET - INGRES-NET ServiceIP - Internet ProtocolIPCU - Internet Packet Core UtilityIPPC - Internet Pluribus Packet CoreIP-ARC - Internet Protocol on ARCNETIP-ARPA - Internet Protocol on ARPANETIP-CMPRS - Compressing TCP/IP HeadersIP-DC - Internet Protocol on DC NetworksIP-DVMRP - Distance Vector Multicast Routing ProtocolIP-E - Internet Protocol on Ethernet NetworksIP-EE - Internet Protocol on Exp. Ethernet NetsIP-FDDI - Transmission of IP over FDDIIP-HC - Internet Protocol on HyperchannnelIP-IEEE - Internet Protocol on IEEE 802IP-IPX - Transmission of 802.2 over IPX NetworksIP-MTU - IP MTU Discovery OptionsIP-NETBIOS - Internet Protocol over NetBIOS NetworksIP-SLIP - Transmission of IP over Serial LinesIP-WB - Internet Protocol on Wideband NetworkIP-X25 - Internet Protocol on X.25 NetworksIRTP - Internet Reliable Transaction ProtocolISI-GL - ISI Graphics Language ProtocolISO-TP4 - ISO Transport Protocol Class 4ISO-TSAP - ISO TSAPLA-MAINT - IMP Logical Address MaintenanceLARP - Locus Address Resoultion ProtocolLDP - Loader Debugger ProtocolLEAF-1 - Leaf-1 ProtocolLEAF-2 - Leaf-2 ProtocolLINK - Link ProtocolLOC-SRV - Location ServiceLOGIN - Login Host ProtocolMAIL - Format of Electronic Mail MessagesMERIT-INP - MERIT Internodal ProtocolMETAGRAM - Metagram RelayMIB - Management Information BaseMIT-ML-DEV - MIT ML DeviceMFE-NSP - MFE Network Services ProtocolMIT-SUBNET - MIT Subnet SupportReynolds & Postel [Page 227]
RFC 1700 Assigned Numbers October 1994MIT-DOV - MIT Dover SpoolerMPM - Internet Message Protocol (Multimedia Mail)MPM-FLAGS - MPM Flags ProtocolMPM-SND - MPM Send ProtocolMSG-AUTH - MSG Authentication ProtocolMSG-ICP - MSG ICP ProtocolMUX - Multiplexing ProtocolNAMESERVER - Host Name ServerNETBIOS-DGM - NETBIOS Datagram ServiceNETBIOS-NS - NETBIOS Name ServiceNETBIOS-SSN - NETBIOS Session ServiceNETBLT - Bulk Data Transfer ProtocolNETED - Network Standard Text EditorNETRJS - Remote Job ServiceNI-FTP - NI File Transfer ProtocolNI-MAIL - NI Mail ProtocolNICNAME - Who Is ProtocolNFILE - A File Access ProtocolNNTP - Network News Transfer ProtocolNSW-FE - NSW User System Front EndNTP - Network Time ProtocolNVP-II - Network Voice ProtocolOSPF - Open Shortest Path First Interior GW ProtocolPCMAIL - Pcmail Transport ProtocolPOP2 - Post Office Protocol - Version 2POP3 - Post Office Protocol - Version 3PPP - Point-to-Point ProtocolPRM - Packet Radio MeasurementPUP - PUP ProtocolPWDGEN - Password Generator ProtocolQUOTE - Quote of the Day ProtocolRARP - A Reverse Address Resolution ProtocolRATP - Reliable Asynchronous Transfer ProtocolRE-MAIL-CK - Remote Mail Checking ProtocolRDP - Reliable Data ProtocolRIP - Routing Information ProtocolRJE - Remote Job EntryRLP - Resource Location ProtocolRTELNET - Remote Telnet ServiceRVD - Remote Virtual Disk ProtocolSAT-EXPAK - Satnet and Backroom EXPAKSAT-MON - SATNET MonitoringSEP - Sequential Exchange ProtocolSFTP - Simple File Transfer ProtocolSGMP - Simple Gateway Monitoring ProtocolSNMP - Simple Network Management ProtocolSMI - Structure of Management InformationSMTP - Simple Mail Transfer ProtocolReynolds & Postel [Page 228]
RFC 1700 Assigned Numbers October 1994SQLSRV - SQL ServiceST - Stream ProtocolSTATSRV - Statistics ServiceSU-MIT-TG - SU/MIT Telnet Gateway ProtocolSUN-RPC - SUN Remote Procedure CallSUPDUP - SUPDUP ProtocolSUR-MEAS - Survey MeasurementSWIFT-RVF - Remote Virtual File ProtocolTACACS-DS - TACACS-Database ServiceTACNEWS - TAC NewsTCP - Transmission Control ProtocolTCP-ACO - TCP Alternate Checksum OptionTELNET - Telnet ProtocolTFTP - Trivial File Transfer ProtocolTHINWIRE - Thinwire ProtocolTIME - Time Server ProtocolTP-TCP - ISO Transport Service on top of the TCPTRUNK-1 - Trunk-1 ProtocolTRUNK-2 - Trunk-2 ProtocolUCL - University College London ProtocolUDP - User Datagram ProtocolNNTP - Network News Transfer ProtocolUSERS - Active Users ProtocolUUCP-PATH - UUCP Path ServiceVIA-FTP - VIA Systems-File Transfer ProtocolVISA - VISA ProtocolVMTP - Versatile Message Transaction ProtocolWB-EXPAK - Wideband EXPAKWB-MON - Wideband MonitoringXNET - Cross Net DebuggerXNS-IDP - Xerox NS IDPREFERENCES[RFC952] Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet Host Table Specification",RFC 952, SRI, October 1985.[]URL =ftp://ftp.isi.edu/in-notes/iana/assignments/service-namesReynolds & Postel [Page 229]
RFC 1700 Assigned Numbers October 1994Security Considerations Security issues are not discussed in this memo.Authors' Addresses Joyce K. Reynolds USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Phone: +1 310-822-1511 EMail: jkrey@isi.edu Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Phone: +1 310-822-1511 EMail: postel@isi.edu []Reynolds & Postel [Page 230]
[8]ページ先頭