ASSIGNED PORT NUMBERS
Ports are used in the TCP [46,102] to name the ends of logical
connections which carry long term conversations. For the purpose of
providing services to unknown callers, a service contact port is
defined. This list specifies the port used by the server process as
its contact port. The contact port is sometimes called the
"well-known port".
To the extent possible, these same port assignments are used with the
UDP [46,100].
To the extent possible, these same port assignments are used with the
ISO-TP4 [64].
The assigned ports use a small portion of the possible port numbers.
The assigned ports have all except the low order eight bits cleared
to zero. The low order eight bits are specified here.
Port Assignments:
Decimal Keyword Description References
------- ------- ----------- ----------
0 Reserved [JBP]
1-4 Unassigned [JBP]
5 RJE Remote Job Entry [17,JBP]
7 ECHO Echo [90,JBP]
9 DISCARD Discard [88,JBP]
11 USERS Active Users [84,JBP]
13 DAYTIME Daytime [87,JBP]
15 NETSTAT Who is up or NETSTAT [JBP]
17 QUOTE Quote of the Day [95,JBP]
19 CHARGEN Character Generator [86,JBP]
20 FTP-DATA File Transfer [Default Data] [91,JBP]
21 FTP File Transfer [Control] [91,JBP]
23 TELNET Telnet [108,JBP]
25 SMTP Simple Mail Transfer [97,JBP]
27 NSW-FE NSW User System FE [29,RHT]
29 MSG-ICP MSG ICP [82,RHT]
31 MSG-AUTH MSG Authentication [82,RHT]
33 DSP Display Support Protocol [MLC]
35 any private printer server [JBP]
37 TIME Time [104,JBP]
39 RLP Resource Location Protocol [1,MA]
41 GRAPHICS Graphics [125,JBP]
42 NAMESERVER Host Name Server [94,JBP]
43 NICNAME Who Is [56,JAKE]
DOMAIN SYSTEM PARAMETERS
The Internet Domain Naming System (DOMAIN) includes several
parameters. These are documented in RFC 883 [80]. The CLASS
parameter is listed here. The per CLASS parameters are defined in
separate RFCs as indicated.
Domain System Parameters:
Decimal Name References
------- ---- ----------
0 Reserved [PM1]
1 Internet [80,PM1]
2 Unassigned [PM1]
3 Chaos [PM1]
4-65534 Unassigned [PM1]
65535 Reserved [PM1]
ASSIGNED ARPANET LOGICAL ADDRESSES
The ARPANET facility for "logical addressing" is described in
RFC 878 [74]. A portion of the possible logical addresses are
reserved for standard uses.
There are 49,152 possible logical host addresses. Of these, 256 are
reserved for assignment to well-known functions. Assignments for
well-known functions are made by Joyce Reynolds. Assignments for
other logical host addresses are made by the NIC.
Logical Address Assignments:
Decimal Description References
------- ----------- ----------
0 Reserved [JBP]
1 The BBN Core Gateways [MB]
2-254 Unassigned [JBP]
255 Reserved [JBP]
ASSIGNED ARPANET LINK NUMBERS
The word "link" here refers to a field in the original ARPANET
Host/IMP interface leader. The link was originally defined as an
8-bit field. Later specifications defined this field as the
"message-id" with a length of 12 bits. The name link now refers to
the high order 8 bits of this 12-bit message-id field. The Host/IMP
interface is defined in BBN Report 1822 [10].
The low-order 4 bits of the message-id field are called the sub-link.
Unless explicitly specified otherwise for a particular protocol,
there is no sender to receiver significance to the sub-link. The
sender may use the sub-link in any way he chooses (it is returned in
the RFNM by the destination IMP), the receiver should ignore the
sub-link.
Link Assignments:
Decimal Description References
------- ----------- ----------
0 Reserved [JBP]
1-149 Unassigned [JBP]
150 Xerox NS IDP [139,HGM]
151 Unassigned [JBP]
152 PARC Universal Protocol [15,HGM]
153 TIP Status Reporting [JGH]
154 TIP Accounting [JGH]
155 Internet Protocol [regular] [101,JBP]
156-158 Internet Protocol [experimental] [101,JBP]
159 Figleaf Link [JBW1]
160-194 Unassigned [JBP]
195 ISO-IP [65,RXM]
196-247 Experimental Protocols [JBP]
248-255 Network Maintenance [JGH]
IEEE 802 NUMBERS OF INTEREST
Some of the networks of all classes are IEEE 802 Networks. These
systems may use a Link Service Access Point (LSAP) field in much the
same way the ARPANET uses the "link" field, further, there is a
extension of the LSAP header called the Sub-Network Access Protocol
(SNAP).
The IEEE likes to describe numbers in binary in bit transmission
order, which is the opposite of the big-endian order used throughout
the Internet protocol documentation.
Assignments:
Link Service Access Point Description References
-------------------------- ----------- ----------
IEEE Internet
binary binary decimal
00000000 00000000 0 Null LSAP [IEEE]
11000000 00000011 3 Group LLC Sublayer Mgt [IEEE]
01000000 00000010 4 Indiv LLC Sublayer Mgt [IEEE]
01100000 00000110 6 DOD IP [101,JBP]
01110000 00001110 14 PROWAY-LAN [IEEE]
01110010 01001110 78 EIA-RS 511 [IEEE]
01110001 10001110 142 PROWAY-LAN [IEEE]
01010101 10101010 170 SNAP [IEEE]
01111111 11111110 254 ISO DIS 8473 [65,JXJ]
11111111 11111111 255 Global DSAP [IEEE]
These numbers (and others) are assigned by the IEEE Standards Office.
The address is: IEEE Standards Office, 345 East 47th Street, New
York, N.Y. 10017, Attn: Vince Condello. Phone: (212) 705-7092.
At an ad hoc special session on "IEEE 802 Networks and ARP" held
during the TCP Vendors Workshop (August 1986), an approach to a
consistent way to sent DOD-IP datagrams and other IP related
protocols on 802 networks was developed.
Due to some evolution of the IEEE 802.2 standards and the need to
provide for a standard way to do additional DOD-IP related protocols
(such as Address Resolution Protocol (ARP)) on IEEE 802 networks, the
following new policy is established, which will replace the old
policy (see RFC-960 and RFC-948 [138]).
The new policy is for DDN and ARPA-Internet community to use IEEE
802.2 encapsulation on 802.3, 802.4, and 802.5 networks by using the
SNAP with an organization code indicating that the following 16 bits
specify the Ethertype code (where IP = 2048 (0800 hex), see Ethernet
Numbers of Interest).
Header
...--------+--------+--------+
MAC Header| Length | 802.{3/4/5} MAC
...--------+--------+--------+
+--------+--------+--------+
| Dsap=K1| Ssap=K1| control| 802.2 SAP
+--------+--------+--------+
+--------+--------+---------+--------+--------+
|protocol id or org code =K2| Ether Type | 802.2 SNAP
+--------+--------+---------+--------+--------+
The values of K1 and K2 must be assigned by the IEEE. There is
already assigned a value of K1 that indicates that the 5-octet SNAP
header follows. There may be a value of K2 that is already assigned
that indicates that the last two octets of the SNAP header holds the
EtherType.
The total length of the SAP Header and the SNAP header is 8-octets,
making the 802.2 protocol overhead come out on a nice octet boundary.
K1 is 170. The IEEE like to talk about things in bit transmission
order and specifies this value as 01010101. In big-endian order, as
used in Internet specifications, this becomes 10101010 binary, or
AA hex, or 170 decimal.
We believe that K2 is 0 (zero). This must be further investigated.
As an interim measure use K2 = 0.
The use of the IP LSAP (K1 = 6) is to be phased out as quickly as
possible.
ETHERNET NUMBERS OF INTEREST
Many of the networks of all classes are Ethernets (10Mb) or
Experimental Ethernets (3Mb). These systems use a message "type"
field in much the same way the ARPANET uses the "link" field.
If you need an Ethernet type number, contact the XEROX Corporation,
2300 Geng Road, Palo Alto, California 94303, ATTN: Ms. Pam Cance
[PXC].
Assignments:
Ethernet Exp. Ethernet Description References
------------- ------------- ----------- ----------
decimal Hex decimal octal
512 0200 512 1000 XEROX PUP [15,HGM]
513 0201 - - PUP Addr. Trans. [HGM]
1536 0600 1536 3000 XEROX NS IDP [139,HGM]
2048 0800 513 1001 DOD IP [101,JBP]
2049 0801 - - X.75 Internet [HGM]
2050 0802 - - NBS Internet [HGM]
2051 0803 - - ECMA Internet [HGM]
2052 0804 - - Chaosnet [HGM]
2053 0805 - - X.25 Level 3 [HGM]
2054 0806 - - ARP [83,JBP]
2055 0807 - - XNS Compatability [HGM]
2076 081C - - Symbolics Private [DCP1]
32771 8003 - - Cronus VLN [127,DT15]
32772 8004 - - Cronus Direct [127,DT15]
32774 8006 - - Nestar [HGM]
32784 8010 - - Excelan [HGM]
32821 8035 - - Reverse ARP [50,JCM]
36864 9000 - - Loopback [HGM]
The standard for transmission of IP datagrams over Ethernets and
Experimental Ethernets is specified in RFC 894 [99] and RFC 895 [85]
respectively.
NOTE: Ethernet 48-bit address blocks are now assigned by the IEEE
Standards Office (see section "IEEE 802 Numbers of Interest").
ASSIGNED ADDRESS RESOLUTION PROTOCOL PARAMETERS
The Address Resolution Protocol (ARP) specified in RFC 826 [83] has
several parameters. The assigned values for these parameters are
listed here.
Assignments:
Operation Code (op)
1 REQUEST
2 REPLY
Hardware Type (hrd)
Type Description 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]
Protocol Type (pro)
Use the same codes as listed in the section "Ethernet Numbers
of Interest" (all hardware types use this code set for the
protocol type).
ASSIGNED PUBLIC DATA NETWORK NUMBERS
One of the Internet Class A Networks is the international system of
Public Data Networks. This section lists the mapping between the
Internet Addresses and the Public Data Network Addresses (X.121).
The numbers below are assigned for networks that are connected to the
ARPA-Internet and DDN-Internet, and for independent networks. These
independent networks are marked with an asterisk preceding the
number.
Assignments:
* Internet Public Data Net Description References
- -------------- ----------------- ----------- ----------
014.000.000.000 Reserved [JBP]
014.000.000.001 3110-317-00035 00 PURDUE-TN [CAK]
014.000.000.002 3110-608-00027 00 UWISC-TN [CAK]
014.000.000.003 3110-302-00024 00 UDEL-TN [CAK]
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 [MHS1]
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 [SA1]
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 DFVLR5-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 [JR17]
014.000.000.022 2624-522-80902 77 DFVLRVAX-X25 [GB7]
* 014.000.000.023 2624-589-00908 01 ECRC-X25 [PXD]
014.000.000.024-014.255.255.254 Unassigned [JBP]
014.255.255.255 Reserved [JBP]
The standard for transmission of IP datagrams over the Public Data
Network is specified in RFC 877 [68].
OFFICIAL MACHINE NAMES
These are the Official Machine Names as they appear in the NIC Host
Table. Their use is described in RFC 952 [49].
An Official Machine Name or CPU Type may be up to 40 characters taken
from the set of uppercase letters, digits, and the two punctuation
characters hyphen and slash. It must start with a letter, and end
with a letter or digit.
ALTO
AMDAHL-V7
APOLLO
ATT-3B20
BBN-C/60
BURROUGHS-B/29
BURROUGHS-B/4800
BUTTERFLY
C/30
C/70
CADLINC
CADR
CDC-170
CDC-170/750
CDC-173
CELERITY-1200
COMTEN-3690
CP8040
CTIWS-117
DANDELION
DEC-10
DEC-1050
DEC-1077
DEC-1080
DEC-1090
DEC-1090B
DEC-1090T
DEC-2020T
DEC-2040
DEC-2040T
DEC-2050T
DEC-2060
DEC-2060T
DEC-2065
DEC-FALCON
DEC-KS10
DORADO
OFFICIAL SYSTEM NAMES
These are the Official System Names as they appear in the NIC Host
Table. Their use is described in RFC 952 [49].
An Official System Names or Operating System Type may be up to 40
characters taken from the set of uppercase letters, digits, and the
two punctuation characters hyphen and slash. It must start with a
letter, and end with a letter or digit.
AEGIS
APOLLO
BS-2000
CEDAR
CGW
CHRYSALIS
CMOS
CMS
COS
CPIX
CTOS
DCN
DDNOS
DOMAIN
EDX
ELF
EMBOS
EMMOS
EPOS
FOONEX
FUZZ
GCOS
GPOS
HDOS
IMAGEN
INTERCOM
IMPRESS
INTERLISP
IOS
ITS
LISP
LISPM
LOCUS
MINOS
MOS
MPE5
MSDOS
OFFICIAL PROTOCOL AND SERVICE NAMES
These are the Official Protocol Names. Their use is described in
greater detail in RFC 952 [49].
An Official Protocol Name or Service Type may be up to 20 characters
taken from the set of uppercase letters, digits, and the punctuation
character hyphen. It must start with a letter, and end with a letter
or digit.
ARGUS - ARGUS Protocol
AUTH - Authentication Service
BBN-RCC-MON - BBN RCC Monitoring
BOOTPC - Bootstrap Protocol Client
BOOTPS - Bootstrap Protocol Server
BR-SAT-MON - Backroom SATNET Monitoring
CFTP - CFTP
CHAOS - CHAOS Protocol
CHARGEN - Character Generator Protocol
CISCO-FNA - CISCO FNATIVE
CISCO-TNA - CISCO TNATIVE
CISCO-SYS - CISCO SYSMAINT
CLOCK - DCNET Time Server Protocol
CSNET-NS - CSNET Mailbox Nameserver Protocol
DAYTIME - Daytime Protocol
DCN-MEAS - DCN Measurement Subsystems Protocol
DCP - Device Control Protocol
DISCARD - Discard Protocol
DOMAIN - Domain Name Server
ECHO - Echo Protocol
EGP - Exterior Gateway Protocol
EMCON - Emission Control Protocol
FINGER - Finger Protocol
FTP - File Transfer Protocol
FTP-DATA - File Transfer Protocol Data
GGP - Gateway Gateway Protocol
GRAPHICS - Graphics Protocol
HMP - Host Monitoring Protocol
HOST2-NS - Host2 Name Server
HOSTNAME - Hostname Protocol
ICMP - Internet Control Message Protocol
IGMP - Internet Group Multicast Protocol
IGP - Interior Gateway Protocol
IP - Internet Protocol
IPCU - Internet Packet Core Utility
IPPC - Internet Pluribus Packet Core
IRTP - Internet Reliable Transaction Protocol
