RFC 870
Assigned numbers
💖 ASSIGNED NUMBERS 🎀
Okay bestie, this is RFC 870, "Assigned Numbers" 📋. It comes from the Network Working Group and was written by J. Reynolds and J. Postel at ISI, dated October 1983. It obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604, 503, 433 and 349, plus IENs 127, 117 and 93. So if you still have those old ones saved, it's time to let them go 🥲✨
This RFC is basically the official list of the numbers that network protocol implementations use 🔢. It gets updated every so often, and for the latest info you ask Joyce Reynolds. Joyce also handles the number assignments, so if you're building a protocol or app that needs a link, socket, port, protocol or network number, go talk to Joyce to get one 🫶
Here's Joyce's contact info 📞:
Joyce Reynolds
USC - Information Sciences Institute
4676 Admiralty Way
Marina del Rey, California 90292
phone: (213) 822-1511
ARPA mail: JKREYNOLDS@USC-ISIFMost of the protocols here are documented in the RFC series 📚. The more prominent, widely used ones are in the "Internet Protocol Transition Workbook" [16] or the old "ARPANET Protocol Handbook" [17], which the NIC put together. Some of the items listed are undocumented, so that's just how it is 🙈 For more on protocols, check the memo "Official Protocols" [52].
Every entry names the responsible person and their mailbox. In the lists, a bracketed entry like [16,iii] in the right margin points to a reference for the protocol. The number is the document, and the "iii" is the person 🦋
ASSIGNED NETWORK NUMBERS 🌈
The network numbers listed here are used as internet addresses by the Internet Protocol (IP) [16,47] 💜 IP uses a 32-bit address field and splits it into a network part and a "rest" or local address part. There are 3 forms of this split, which are called classes 👑
Class A is the first type. It has a 7-bit network number and a 24-bit local address, and the highest-order bit is set to 0. That allows 128 class A networks 🌸
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| NETWORK | Local Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Class A AddressClass B is the second type. It has a 14-bit network number and a 16-bit local address, and the two highest-order bits are set to 1-0. That allows 16,384 class B networks 🦄
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 0| NETWORK | Local Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Class B AddressClass C is the third type. It has a 21-bit network number and an 8-bit local address, and the three highest-order bits are set to 1-1-0. That allows 2,097,152 class C networks 🍓
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 1 0| NETWORK | Local Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Class C Address🚫 Note: No addresses are allowed with the three highest-order bits set to 1-1-1. These addresses (sometimes called "class D") are reserved, so hands off!
The usual way to write internet host addresses is dotted decimal 🧚 You split the 32-bit address into four 8-bit fields, write each field as a decimal number, and separate them with periods. For example, the internet address of ISIF in dotted decimal is 010.002.000.052, or 10.2.0.52.
The dotted decimal notation is what the assigned network number listings use. Class A networks show up as nnn.rrr.rrr.rrr, class B networks as nnn.nnn.rrr.rrr, and class C networks as nnn.nnn.nnn.rrr. Here nnn stands for part or all of a network number, and rrr stands for part or all of a local address ✨
There are three categories of Internet Address users: Research, Defense and Commercial 💅 To show how the network identifiers are allocated among these categories, a one-character code goes to the left of the network number (in the column marked by an asterisk). It's R for Research and Development, D for DoD, and C for Commercial.
Numbers assigned for commercial use of IP family protocols, but not for interworking with the ARPA or DoD Internets, get an asterisk in front of the number ⭐
Numbers change sometimes, for various reasons 🙃 To make the transition easier, the old number is listed too. These "old number" entries get a "T" after the number and before the name, and the network name gets the suffix "-TEMP" 🌷
Assigned Network Numbers 🦋
Class A Networks 💖
* Internet Address Name Network References
- ---------------- ---- ------- ----------
000.rrr.rrr.rrr Reserved [JBP]
R 003.rrr.rrr.rrr T RCC-NET-TEMP BBN RCC Network [SGC]
R 004.rrr.rrr.rrr SATNET Atlantic Satellite Network[DM11]
D 005.rrr.rrr.rrr T DEMO-PR-1-TEMPDemo-1 Packet Radio Network[LCS]
D 006.rrr.rrr.rrr T YPG-NET-TEMP Yuma Proving Grounds [2,BXA]
D 007.rrr.rrr.rrr T EDN-TEMP DCEC EDN [EC5]
R 008.rrr.rrr.rrr T BBN-NET-TEMP BBN Network [JSG5]
D 009.rrr.rrr.rrr T BRAGG-PR-TEMP Ft. Bragg Packet Radio Net [JEM]
R 010.rrr.rrr.rrr ARPANET ARPANET [2,17,REK2]
C 012.rrr.rrr.rrr ATT ATT, Bell Labs [MH12]
C 014.rrr.rrr.rrr PDN Public Data Network [REK2]
R 018.rrr.rrr.rrr T MIT-TEMP MIT Network [11,51,DDC2]
R 023.rrr.rrr.rrr MITRE MITRE Cablenet [54,APS]
D 024.rrr.rrr.rrr MINET MINET [2,DHH]
R 025.rrr.rrr.rrr RSRE-EXP RSRE Experimental [NM]
D 026.rrr.rrr.rrr MILNET MILNET [HH6]
R 027.rrr.rrr.rrr T NOSC-LCCN-TEMPNOSC / LCCN [RH6]
R 028.rrr.rrr.rrr WIDEBAND Wide Band Satellite Net [CJW2]
R 032.rrr.rrr.rrr UCL-TAC UCL TAC [PK]
R 035.rrr.rrr.rrr T RSRE-NULL-TEMPRSRE Null Network [NM]
R 036.rrr.rrr.rrr T SU-NET-TEMP Stanford University Network[JCM]
R 039.rrr.rrr.rrr T SRINET-TEMP SRI Local Network [GEOF]
R 041.rrr.rrr.rrr BBN-TEST-A BBN-GATE-TEST-A [RH6]
R 044.rrr.rrr.rrr AMPRNET Amateur Radio Experiment Net[HM]
R 045.rrr.rrr.rrr T C3-PR-TEMP Testbed Development PRNET [BG5]
R 046.rrr.rrr.rrr T Berkeley-TEMP Berkeley Ethernet [DAM1]
R 047.rrr.rrr.rrr T SAC-PR-TEMP SAC Packet Radio Network [BG5]
R 048.rrr.rrr.rrr NDRE-TIU NDRE-TIU [PS3]
R 050.rrr.rrr.rrr NTA-RING NDRE-RING [PS3]
001.rrr.rrr.rrr-002.rrr.rrr.rrr Unassigned [JBP]
011.rrr.rrr.rrr Unassigned [JBP]
013.rrr.rrr.rrr Unassigned [JBP]
015.rrr.rrr.rrr-017.rrr.rrr.rrr Unassigned [JBP]
019.rrr.rrr.rrr-022.rrr.rrr.rrr Unassigned [JBP]
029.rrr.rrr.rrr-031.rrr.rrr.rrr Unassigned [JBP]
033.rrr.rrr.rrr-034.rrr.rrr.rrr Unassigned [JBP]
037.rrr.rrr.rrr-038.rrr.rrr.rrr Unassigned [JBP]
040.rrr.rrr.rrr Unassigned [JBP]
042.rrr.rrr.rrr-043.rrr.rrr.rrr Unassigned [JBP]
049.rrr.rrr.rrr Unassigned [JBP]
051.rrr.rrr.rrr-126.rrr.rrr.rrr Unassigned [JBP]
127.rrr.rrr.rrr Reserved [JBP]Class B Networks 🌸
* Internet Address Name Network References
- ---------------- ---- ------- ----------
128.000.rrr.rrr Reserved [JBP]
R 128.001.rrr.rrr BBN-TEST-B BBN-GATE-TEST-B [RH6]
R 128.002.rrr.rrr CMU-NET CMU-Ethernet [HDW2]
R 128.003.rrr.rrr LBL-CSAM LBL-CSAM-RESEARCH [MO1]<--***
R 128.004.rrr.rrr DCNET LINKABIT DCNET [DLM1]
R 128.005.rrr.rrr FORDNET FORD DCNET [DLM1]
R 128.006.rrr.rrr RUTGERS RUTGERS [CLH3]
R 128.007.rrr.rrr DFVLR DFVLR DCNET Network [HDC1]
R 128.008.rrr.rrr UMDNET Univ of Maryland DCNET [DLM1]
R 128.009.rrr.rrr ISI-NET USC-ISI Local Network [CMR]
R 128.010.rrr.rrr PURDUE-CS Purdue Computer Science [CAK]
R 128.011.rrr.rrr BBN-CRONUS BBN DOS Project [29,WIM]
R 128.012.rrr.rrr SU-NET Stanford University Net [JCM]
D 128.013.rrr.rrr MATNET Mobile Access Terminal Net[DM11]
R 128.014.rrr.rrr BBN-SAT-TEST BBN SATNET Test Net [DM11]
R 128.015.rrr.rrr S1NET LLL-S1-NET [EAK1]
R 128.016.rrr.rrr UCLNET University College London [PK]
D 128.017.rrr.rrr MATNET-ALT Mobile Access Terminal Alt[DM11]
R 128.018.rrr.rrr SRINET SRI Local Network [GEOF]
D 128.019.rrr.rrr EDN DCEC EDN [EC5]
D 128.020.rrr.rrr BRLNET BRLNET [2,MJM2]
R 128.021.rrr.rrr SF-PR-1 SF-1 Packet Radio Network [JEM]
R 128.022.rrr.rrr SF-PR-2 SF-2 Packet Radio Network [JEM]
R 128.023.rrr.rrr BBN-PR BBN Packet Radio Network [JAW3]
R 128.024.rrr.rrr ROCKWELL-PR Rockwell Packet Radio Net [EHP]
D 128.025.rrr.rrr BRAGG-PR Ft. Bragg Packet Radio Net [JEM]
D 128.026.rrr.rrr SAC-PR SAC Packet Radio Network [BG5]
D 128.027.rrr.rrr DEMO-PR-1 Demo-1 Packet Radio Network[LCS]
D 128.028.rrr.rrr C3-PR Testbed Development PR NET [BG5]
128.029.rrr.rrr Unassigned [JBP]
R 128.030.rrr.rrr MIT-NET MIT Local Network [DDC2]
R 128.031.rrr.rrr MIT-RES MIT Research Network [DDC2]
R 128.032.rrr.rrr UCB-ETHER UC Berkeley Ethernet [DAM1]
R 128.033.rrr.rrr BBN-NET BBN Network [JSG5]
R 128.034.rrr.rrr NOSC-LCCN NOSC / LCCN [RH6]
R 128.035.rrr.rrr CISLTESTNET1 Honeywell [25,26,RK1]
R 128.036.rrr.rrr YALE-NET YALE NET [61,JO5]
D 128.037.rrr.rrr YPG-NET Yuma Proving Grounds [2,BXA]
D 128.038.rrr.rrr NSWC-NET NSWC Local Host Net [RLH2]
128.039.rrr.rrr-191.254.rrr.rrr Unassigned [JBP]
191.255.rrr.rrr Reserved [JBP]Class C Networks 🌸
* Internet Address Name Network References
- ---------------- ---- ------- ----------
192.000.000.rrr Reserved [JBP]
R 192.000.001.rrr BBN-TEST-C BBN-GATE-TEST-C [RH6]
192.000.002.rrr-192.000.255.rrr Unassigned [JBP]
R 192.001.000.rrr-192.004.255.rrr BBN local networks [SGC]
R 192.005.001.rrr CISLHYPERNET Honeywell [RK1]
R 192.005.002.rrr WISC Univ of Wisconsin Madison [RS23]
C 192.005.003.rrr HP-DESIGN-AIDS HP Design Aids [NXK]
C 192.005.004.rrr HP-TCG-UNIX Hewlett Packard TCG Unix [NXK]
192.005.005.rrr Unassigned [JBP]
192.005.006.rrr Unassigned [JBP]
R 192.005.007.rrr CIT-CS-NET Caltech-CS-Net [60,DSW]
R 192.005.008.rrr WASHINGTON University of Washington [JAR4]
R 192.005.009.rrr AERONET Aerospace Labnet [1,LCN]
R 192.005.010.rrr ECLNET USC-ECL-CAMPUS-NET [MXB]
R 192.005.011.rrr CSS-RING SEISMIC-RESEARCH-NET [RR2]
R 192.005.012.rrr UTAH-NET UTAH-COMPUTER-SCIENCE-NET [RF1]
R 192.005.013.rrr CCNET Compion Network [61,FAS]
R 192.005.014.rrr RAND-NET RAND Network [61,JDG]
R 192.005.015.rrr NYU-NET NYU Network [EF5]
R 192.005.016.rrr LANL-LAND Los Alamos Dev LAN [61,JC11]
R 192.005.017.rrr NRL-NET Naval Research Lab [AP]
R 192.005.018.rrr IPTO-NET ARPA-IPTO Office Net [REK2]
R 192.005.019.rrr UCIICS UCI-ICS Res Net [MXR]
R 192.005.020.rrr CISLTTYNET Honeywell [RK1]
D 192.005.021.rrr BRLNET1 BRLNET1 [2,MJM2]
D 192.005.022.rrr BRLNET2 BRLNET2 [2,MJM2]
D 192.005.023.rrr BRLNET3 BRLNET3 [2,MJM2]
D 192.005.024.rrr BRLNET4 BRLNET4 [2,MJM2]
D 192.005.025.rrr BRLNET5 BRLNET5 [2,MJM2]
D 192.005.026.rrr NSRDCOA-NET NSRDC Office Auto Net [TC4]
D 192.005.027.rrr DTNSRDC-NET DTNSRDC-NET [TC4]
R 192.005.028.rrr RSRE-NULL RSRE-NULL [NM]
R 192.005.029.rrr RSRE-ACC RSRE-ACC [NM]
R 192.005.030.rrr RSRE-PR RSRE-PR [NM]
R 192.005.031.rrr SIEMENS-NET Siemens Research Network [PXN]
R 192.005.032.rrr CISLTESTNET2 Honeywell [25,26,RK1]
R 192.005.033.rrr CISLTESTNET3 Honeywell [25,26,RK1]
R 192.005.034.rrr CISLTESTNET4 Honeywell [25,26,RK1]
R 192.005.035.rrr RIACS USRA [61,RLB1]
R 192.005.036.rrr CORNELL-CS CORNELL CS Research [61,DK2]
R 192.005.037.rrr UR-CS-NET U of R CS 3Mb Net [31,LB1]
R 192.005.038.rrr SRI-C3ETHER SRI-AITAD C3ETHERNET [61,BG5]
R 192.005.039.rrr UDEL-EECIS Udel EECIS LAN [58,CC2]
R 192.005.040.rrr PUCC-NET-A PURDUE Comp Cntr Net [JXS]
D 192.005.041.rrr WISLAN WIS Research LAN [54,JRM1]
D 192.005.042.rrr AFDSC-HYPER AFDSC Hypernet [MCSJ]
R 192.005.043.rrr CUCSNET Columbia CS Net [61,LH2]
192.005.044.rrr-192.005.255.rrr Unassigned [JBP]
C*192.006.000.rrr-192.006.255.rrr Hewlett Packard [AXG]
C*192.007.000.rrr-192.007.255.rrr Computer Consoles, Inc. [RA11]
C*192.008.000.rrr-192.008.255.rrr Spartacus Computers, Inc. [SXM]
192.009.000.rrr-223.255.254.rrr Unassigned [JBP]
223.255.255.rrr Reserved [JBP]Other Reserved Internet Addresses 💜
* Internet Address Name Network References
- ---------------- ---- ------- ----------
224.000.000.000-255.255.255.255 Reserved [JBP]Network Totals 📊
Okay bestie, these totals are literally the tea ☕ Here's the assigned for the Internet breakdown:
Assigned for the Internet
Class A B C Total
Research 10 27 1055 1092
Defense 2 10 9 21
Commercial 2 0 2 4
Total 14 37 1066 1117
Allocated for Internet and Other Uses
Class A B C Total
Research 10 27 1055 1092
Defense 2 10 9 21
Commercial 2 0 770 772
Total 14 37 1834 1885
Maximum Allowed
Class A B C Total
Research 8 1024 65536 66568
Defense 24 3072 458752 461848
Commercial 94 12286 1572862 1585242
Total 126 16382 2097150 2113658ASSIGNED INTERNET VERSION NUMBERS 🦋
So the Internet Protocol (IP) [16,47] has a version field that tells you which version of the internetwork general protocol you're dealing with, and it's 4 bits big ✨ Lowkey tiny, but iconic.
Assigned Internet Version Numbers
Decimal Octal Version References
------- ----- ------- ----------
0 0 Reserved [JBP]
1-3 1-3 Unassigned [JBP]
4 4 Internet Protocol [16,47,JBP]
5 5 ST Datagram Mode [18,JWF]
6-14 6-16 Unassigned [JBP]
15 17 Reserved [JBP]ASSIGNED INTERNET PROTOCOL NUMBERS 🌈
Now we're getting to the good stuff 💅 The IP [16,47] has a field called Protocol that says which next-level protocol is riding inside, and it's 8 bits wide. Iykyk, it's giving main character energy 👑
Assigned Internet Protocol Numbers 🧚
Okay bestie, the protocol list is up next, and it's a whole lineup 💖 Each number is a protocol, and the bracketed bits tell you where to look for more.
Decimal Octal Protocol References
------- ----- ---------------- ----------
0 0 Reserved [JBP]
1 1 ICMP [16,40,JBP]
2 2 Unassigned [JBP]
3 3 Gateway-to-Gateway [24,MB]
4 4 Unassigned [JBP]
5 5 Stream (ST) [18,JWF]
6 6 Transmission Control (TCP) [16,48,JBP]
7 7 UCL [PK]
8 10 Exterior Gateway Protocol (EGP) [53,RH6]
9 11 Unassigned [JBP]
10 12 BBN RCC Monitoring [SGC]
11 13 NVP [12,SC3]
12 14 PUP [6,EAT3]
13-14 15-16 Unassigned [JBP]
15 17 Cross Net Debugger (XNET) [23,JFH2]
16 20 Chaos Stream [NC3]
17 21 User Datagram (UDP) [16,46,JBP]
18 22 Multiplexing [13,JBP]
19 23 DCN Measurement Subsystems [DLM1]
20 24 Host Monitoring (HMP) [28,RH6]
21 25 Packet Radio Measurement [ZSU]
22 26 XEROX NS IDP [62,LLG]
23 27 Trunk-1 [BML]
24 30 Trunk-2 [BML]
25 31 Leaf-1 [BML]
26 32 Leaf-2 [BML]
27-60 33-74 Unassigned [JBP]
61 75 any host internal protocol [JBP]
62 76 CFTP [19,HCF2]
63 77 any local network [JBP]
64 100 SATNET and Backroom EXPAK [DM11]
65 101 MIT Subnet Support [NC3]
66 102 MIT VAX Remote Disk Protocol [MBG]
67 103 Internet Pluribus Packet Core [DM11]
68 104 Unassigned [JBP]
69 105 SATNET Monitoring [DM11]
70 106 Unassigned [JBP]
71 107 Internet Packet Core Utility [DM11]
72-75 110-113 Unassigned [JBP]
76 114 Backroom SATNET Monitoring [DM11]
77 115 Unassigned [JBP]
78 116 WIDEBAND Monitoring [DM11]
79 117 WIDEBAND EXPAK [DM11]
80-254 120-376 Unassigned [JBP]
255 377 Reserved [JBP]ASSIGNED PORT NUMBERS ✨
Ports are the way TCP [16,48] names the two ends of a logical connection, the pipes that carry those long-term conversations 🦋 To help services answer callers who don't already know them, there's a service contact port. The list below tells you which port a server process uses as its contact port. People also call that the "well-known port" 🎀
The same port assignments get reused with UDP [16,46] wherever that's possible 🌸
Only a tiny slice of the possible port numbers is actually assigned, and the assigned ports have everything except their low order eight bits cleared to zero 🧚 Those low order eight bits are the ones this list is about. Here's the full set:
Port Assignments:
Decimal Octal Description References
------- ----- ----------- ----------
0 0 Reserved [JBP]
1-4 1-4 Unassigned [JBP]
5 5 Remote Job Entry [8,17,JBP]
7 7 Echo [38,JBP]
9 11 Discard [37,JBP]
11 13 Active Users [34,JBP]
13 15 Daytime [36,JBP]
15 17 Who is up or NETSTAT [JBP]
17 21 Quote of the Day [43,JBP]
19 23 Character Generator [35,JBP]
20 24 File Transfer (Default Data) [16,39,JBP]
21 25 File Transfer (Control) [16,39,JBP]
23 27 Telnet [50,JBP]
25 31 SMTP [16,45,JBP]
27 33 NSW User System FE [14,RHT]
29 35 MSG ICP [32,RHT]
31 37 MSG Authentication [32,RHT]
33 41 Unassigned [JBP]
35 43 Any Printer Server [JBP]
37 45 Time [49,JBP]
39 47 Unassigned [JBP]
41 51 Graphics [17,57,JBP]
42 52 Host Name Server [16,42,JBP]
43 53 NICNAME (WhoIs) [16,22,JAKE]
44 54 MPM FLAGS Protocol [JBP]
45 55 Message Processing Module (receive) [41,JBP]
46 56 MPM (default send) [41,JBP]
47 57 NI FTP [59,SK]
49 61 Login Host Protocol [PXD]
51 63 IMP Logical Address Maintenance [30,AGM]
53 65 Domain Name Server [PM1]
55 67 ISI Graphics Language [5,RB6]
57 71 Any Private Terminal Access [JBP]
59 73 Any Private File Service [JBP]
61 75 NIMAIL [3,SK]
63 77 Unassigned [JBP]
65 101 Unassigned [JBP]
67 103 Datacomputer at CCA [10,JZS]
69 105 Trivial File Transfer [16,55,KRS]
71 107 NETRJS [7,17,RTB]
72 110 NETRJS [7,17,RTB]
73 111 NETRJS [7,17,RTB]
74 112 NETRJS [7,17,RTB]
75 113 Any Private Dial Out Service [JBP]
77 115 Any Private RJE Service [JBP]
79 117 Finger (Name) [17,20,KLH]
81 121 HOSTS2 Name Server [EAK1]
83 123 MIT ML Device [DPR]
85 125 MIT ML Device [DPR]
87 127 any terminal link [JBP]
89 131 SU/MIT Telnet Gateway [MRC]
91 133 MIT Dover Spooler [EBM]
93 135 Device Control Protocol [DCT]
95 137 SUPDUP [15,MRC]
97 141 Datacomputer Status [10,JZS]
99 143 Metagram Relay [GEOF]
101 145 NIC Host Name Server [16,21,JAKE]
103 147 Unassigned [JBP]
105 151 CSNET Mailbox Name Server (Program) [56,MHS1]
107 153 Remote Telnet Service [44,JBP]
109-129 155-201 Unassigned [JBP]
131 203 Datacomputer [10,JZS]
132-223 204-337 Reserved [JBP]
224-241 340-361 Unassigned [JBP]
243 363 Survey Measurement [4,AV]
245 365 LINK [9,RDB2]
247-255 367-377 Unassigned [JBP]ASSIGNED AUTONOMOUS SYSTEM NUMBERS ✨
The Exterior Gateway Protocol (EGP) [53] says groups of gateways can form autonomous systems 👑 EGP gives that identifier a 16-bit field, and the values for that field are registered right here 💅
Autonomous System Numbers:
Decimal Description References
------- ----------- ----------
0 Reserved [JBP]
1 The BBN Gateways [MB]
2 The DCN Gateways [DLM1]
3 The MIT Gateways [LM8]
4-65534 Unassigned [JBP]
65535 Reserved [JBP]ASSIGNED ARPANET LINK NUMBERS ✨
Okay so, the word "link" here means a field in the original ARPANET Host/IMP interface leader 🍓 It started life as an 8-bit field. Later specs turned it into a 12-bit field called the "Message-ID", and now the name "link" refers to the high order 8 bits of that 12-bit message-id. The low order 4 bits of the message-id are supposed to be zero, unless a specific protocol running on that link says otherwise 🌈 The whole Host/IMP interface is defined in BBN Report 1822 [2].
Link Assignments:
Decimal Octal Description References
------- ----- ----------- ----------
0 0 Reserved [JBP]
1-149 1-225 Unassigned [JBP]
150 226 Xerox NS IP [62,LLG]
151 227 Unassigned [JBP]
152 230 PARC Universal Protocol [6,EAT3]
153 231 TIP Status Reporting [JGH]
154 232 TIP Accounting [JGH]
155 233 Internet Protocol (regular) [16,47,JBP]
156-158 234-236 Internet Protocol (experimental) [16,47,JBP]
159-195 237-303 Unassigned [JBP]
196-255 304-377 Experimental Protocols [JBP]
248-255 370-377 Network Maintenance [JGH]ETHERNET NUMBERS OF INTEREST ✨
Lots of networks in every class are Ethernets (10Mb) or Experimental Ethernets (3Mb) 🫶 These systems handle a message "type" field in much the same way the ARPANET handles its "link" field 🦋
Assignments:
Ethernet Exp. Ethernet Description References
-------------- -------------- ----------- ----------
decimal Hex decimal octal
512 02,00 512 1000 XEROX PUP [6,EAT3]
1536 06,00 1536 3000 XEROX NS IDP [62,LLG]
2048 08,00 513 1001 DOD IP [16,47,JBP]
2054 08,06 - - Address Res [33,DCP1]ASSIGNED PUBLIC DATA NETWORK NUMBERS ✨
Okay so one of the Internet Class A Networks is the international system of Public Data Networks 🌐 bestie, and this section is where we spill the tea on how Internet Addresses map to Public Data Network Addresses (X.121) 💅. It's giving organised.
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-014.255.255.254 Unassigned [JBP]
014.255.255.255 Reserved [JBP]The rule for sending IP datagrams over the Public Data Network lives in [27] 📮, so go check that one out 🦋.
DOCUMENTS 📚🎀
Here's the full reading list, with every source and its details 🧚
- [1] Aerospace, Internal Report, ATM-83(3920-01)-3, 1982.
- [2] BBN, "Specifications for the Interconnection of a Host and an IMP", Report 1822, Bolt Beranek and Newman, Cambridge, Massachusetts, revised, December 1981.
- [3] Bennett, C., "A Simple NIFTP-Based Mail System", IEN 169, University College, London, January 1981.
- [4] Bhushan, A., "A Report on the Survey Project", RFC 530, NIC 17375, 22 June 1973.
- [5] Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language (version 2.1)", ISI/TM-80-18, USC/Information Sciences Institute, July 1980.
- [6] 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.
- [7] Braden, R., "NETRJS Protocol", RFC 740, NIC 42423, 22 November 1977. Also in [17].
- [8] Bressler, B., "Remote Job Entry Protocol", RFC 407, NIC 12112, 16 October 72. Also in [17].
- [9] Bressler, R., "Inter-Entity Communication -- An Experiment", RFC 441, NIC 13773, 19 January 1973.
- [10] CCA, "Datacomputer Version 5/4 User Manual", Computer Corporation of America, August 1979.
- [11] Clark, D., "Revision of DSP Specification", Local Network Note 9, Laboratory for Computer Science, MIT, 17 June 1977.
- [12] Cohen, D., "Specifications for the Network Voice Protocol", RFC 741, ISI/RR 7539, USC/Information Sciences Institute, March 1976.
- [13] Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90, USC/Information Sciences Institute, May 1979.
- [14] COMPASS, "Semi-Annual Technical Report", CADD-7603-0411, Massachusetts Computer Associates, 4 March 1976. Also as, "National Software Works, Status Report No. 1," RADC-TR-76-276, Volume 1, September 1976. And COMPASS. "Second Semi-Annual Report," CADD-7608-1611, Massachusetts Computer Associates, 16 August 1976.
- [15] Crispin, M., "SUPDUP Protocol", RFC 734, NIC 41953, 7 October 1977. Also in [17].
- [16] Feinler, E., "Internet Protocol Transition Workbook", Network Information Center, SRI International, March 1982.
- [17] Feinler, E. and J. Postel, eds., "ARPANET Protocol Handbook", NIC 7104, for the Defense Communications Agency by SRI International, Menlo Park, California, Revised January 1978.
- [18] Forgie, J., "ST - A Proposed Internet Stream Protocol", IEN 119, M.I.T. Lincoln Laboratory, September 1979.
- [19] Forsdick, H., "CFTP", Network Message, Bolt Berenak and Newman, January 1982.
- [20] Harrenstien, K., "Name/Finger", RFC 742, NIC 42758, 30 December 1977. Also in [17].
- [21] Harrenstien, K., V. White, and E. Feinler, "Hostnames Server", RFC 811, SRI International, March 1982.
- [22] Harrenstien, K., and V. White, "Nicname/Whois", RFC 812, SRI International, March 1982.
- [23] Haverty, J., "XNET Formats for Internet Protocol Version 4", IEN 158, October 1980.
- [24] Hinden, R., A. Sheltzer, "The DARPA Internet Gateway", RFC 823, September 1982.
- [25] Honeywell CISL, Internal Document, "AFSDSC Hyperchannel RPQ Project Plan".
- [26] Honeywell CISL, Internal Document, "Multics MR11 PFS".
- [27] Korb, John T., "A Standard for the Transmission of IP Datagrams Over Public Data Networks", RFC 877, Purdue University, September 1983.
- [28] Littauer, B., "A Host Monitoring Protocol", IEN 197, Bolt Berenak and Newman, September 1981.
- [29] Macgregor, W., and D. Tappan, "The CRONUS Virtual Local Network", RFC 824, Bolt Beranek and Newman, 22 August 1982.
- [30] Malis, A., "Logical Addressing Implementation Specification", BBN Report 5256, pp 31-36, May 1983.
- [31] Metcalfe, R.M. and D.R. Boggs, "Ethernet: Distributed Packet Switching for Local Computer Networks", Communications of the ACM, 19 (7), pp 395-402, July 1976.
- [32] NSW Protocol Committee, "MSG: The Interprocess Communication Facility for the National Software Works", CADD-7612-2411, Massachusetts Computer Associates, BBN 3237, Bolt Beranek and Newman, Revised 24 December 1976.
- [33] Plummer, D., "An Ethernet Address Resolution Protocol or Converting Network Protocol Addresses to 48-bit Ethernet Addresses for Transmission on Ethernet Hardware", RFC 826, MIT LCS, November 1982.
- [34] Postel, J., "Active Users", RFC 866, USC/Information Sciences Institute, May 1983.
- [35] Postel, J., "Character Generator Protocol", RFC 864, USC/Information Sciences Institute, May 1983.
- [36] Postel, J., "Daytime Protocol", RFC 867, USC/Information Sciences Institute, May 1983.
- [37] Postel, J., "Discard Protocol", RFC 863, USC/Information Sciences Institute, May 1983.
- [38] Postel, J., "Echo Protocol", RFC 862, USC/Information Sciences Institute, May 1983.
- [39] Postel, J., "File Transfer Protocol", RFC 765, IEN 149, USC/Information Sciences Institute, June 1980.
- [40] Postel, J., "Internet Control Message Protocol - DARPA Internet Program Protocol Specification", RFC 792, USC/Information Sciences Institute, September 1981.
- [41] Postel, J., "Internet Message Protocol", RFC 759, IEN 113, USC/Information Sciences Institute, August 1980.
- [42] Postel, J., "Name Server", IEN 116, USC/Information Sciences Institute, August 1979.
- [43] Postel, J., "Quote of the Day Protocol", RFC 865, USC/Information Sciences Institute, May 1983.
- [44] Postel, J., "Remote Telnet Service", RFC 818, USC/Information Sciences Institute, November 1982.
- [45] Postel, J., "Simple Mail Transfer Protocol", RFC 821, USC/Information Sciences Institute, August 1982.
- [46] Postel, J., "User Datagram Protocol", RFC 768 USC/Information Sciences Institute, August 1980.
- [47] Postel, J., ed., "Internet Protocol - DARPA Internet Program Protocol Specification", RFC 791, USC/Information Sciences Institute, September 1981.
- [48] Postel, J., ed., "Transmission Control Protocol - DARPA Internet Program Protocol Specification", RFC 793, USC/Information Sciences Institute, September 1981.
- [49] Postel, J., and K. Harrenstien, "Time Protocol", RFC 868, USC/Information Sciences Institute, May 1983.
- [50] Postel, J., and J. Reynolds, "Telnet Protocol Specification", RFC 854, USC/Information Sciences Institute, May 1983.
- [51] Reed, D., "Protocols for the LCS Network", Local Network Note 3, Laboratory for Computer Science, MIT, 29 November 1976.
- [52] Reynolds, J. and J. Postel, "Official Protocols", RFC 880, USC/Information Sciences Institute, October 1983.
- [53] Rosen, E., "Exterior Gateway Protocol" RFC 827, Bolt Berenak and Newman, October 1982.
- [54] Skelton, A., S. Holmgren, and D. Wood, "The MITRE Cablenet Project", IEN 96, April 1979.
- [55] Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, MIT/LCS, June 1981.
- [56] Solomon, M., L. Landweber, and D, Neuhengen, "The CSNET Name Server", Computer Networks, v.6, n.3, pp. 161-172, July 1982.
- [57] Sproull, R., and E. Thomas, "A Networks Graphics Protocol", NIC 24308, 16 August 1974. Also in [17].
- [58] "The Ethernet - A Local Area Network", Version 1.0, Digital Equipment Corporation, Intel Corporation, Xerox Corporation, September 1980.
- [59] The High Level Protocol Group, "A Network Independent File Transfer Protocol", INWG Protocol Note 86, December 1977.
- [60] Whelan, D., "The Caltech Computer Science Department Network", 5052:DF:82, Caltech Computer Science Department, 1982.
- [61] XEROX, "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", X3T51/80-50, Xerox Corporation, Stamford, CT., October 1980.
- [62] XEROX, "Internet Transport Protocols", XSIS 028112, Xerox Corporation, Stamford, Connecticut, December 1981.
Most of the protocols mentioned here are documented in the RFC series of notes 📚✨. The more prominent and more widely used ones are written up in the "Internet Protocol Transition Workbook" [16] or in the old "ARPANET, Protocol Handbook" [17] that the NIC put together 🦋. Some of the items listed are undocumented, so no judgment there, bestie 🙈. For more on protocols, check out the memo "Official Protocols" [52] 💜.
In every case, the name and mailbox of the responsible person is listed 💌. In the lists below, a bracketed entry like [16,iii] in the right margin points to a reference for that protocol. The number is the document, and the "iii" is the person 🧚.
PEOPLE 💖
Here's the whole crew of contacts, in one place 🫶:
PEOPLE
------
[AGM] Andy Malis BBN Malis@BBN-UNIX
[APS] Anita Skelton MITRE skelton@MITRE
[AP] Alan Parker NRL parker@NRL-CSS
[AV] Al Vezza MIT AV@MIT-XX
[AXG] Atul Garg HP ---none---
[BG5] Bob Gilligan SRI Gilligan@SRI-KL
[BML] Barry Leiner ARPA Leiner@USC-ISIA
[BXA] Bobby W. Allen YPG WYMER@OFFICE
[CAK] Chris Kent PURDUE cak@PURDUE
[CC2] Chase Cotton UDEL Cotton@Udel-EE
[CJW2] Cliff Weinstein LL cjw@LL-11
[CLH3] Charles Hedrick RUTGERS Hedrick@RUTGERS
[CMR] Craig Rogers ISI Rogers@USC-ISIB
[DAM1] David A. Mosher UCB Mosher@BERKELEY
[DCP1] David Plummer MIT DCP@MIT-MC
[DCT] Dan Tappan BBN Tappan@BBNG
[DDC2] Dave Clark MIT-LCS Clark@MIT-Multics
[DHH] Doug Hunt BBN DHunt@BBN-Unix
[DK2] Dean B. Krafft CORNELL Dean@CORNELL
[DLM1] David Mills LINKABIT Mills@USC-ISID
[DM11] Dale McNeill BBN mcneill@BBN-Unix
[DPR] David Reed MIT-LCS DPR@MIT-XX
[DSW] Dan Whelan Caltech Dan@CIT-20
[EAK1] Earl Killian LLL EAK@MIT-MC
[EAT3] Ed Taft XEROX Taft.PA@PARC-MAXC
[EBM] Eliot Moss MIT EBM@MIT-XX
[EC5] Ed Cain DCEC cain@EDN-Unix
[EF5] Ed Franceschini NYU Franceschini@NYU
[EHP] Ed Perry SRI Perry@SRI-KL
[FAS] Fred Segovich Compion fred@COMPION-VMS
[GEOF] Geoff Goodfellow SRI Geoff@DARCOM-KA
[HCF2] Harry Forsdick BBN Forsdick@BBNG
[HDC1] Horst Clausen DFVLR Clausen@USC-ISID
[HDW2] Howard Wactlar CMU Wactlar@CMU-10B
[HH6] Heidi Heiden DCA Heiden@BBNC
[HM] Hank Magnuski --- JOSE@PARC-MAXC
[JAKE] Jake Feinler SRI Feinler@SRI-KL
[JAR4] Jim Rees WASHINGTON JIM@WASHINGTON
[JAW3] Jil Westcott BBN Westcott@BBNF
[JBP] Jon Postel ISI Postel@USC-ISIF
[JC11] Jim Clifford LANL jrc@LANL
[JCM] Jeff Mogul STANFORD Mogul@SU-SCORE
[JD21] Jonathan Dreyer BBN JDreyer@BBN-Unix
[JDG] Jim Guyton RAND guyton@RAND-Unix
[JEM] Jim Mathis SRI Mathis@SRI-KL
[JFH2] Jack Haverty BBN Haverty@BBN-Unix
[JGH] Jim Herman BBN Herman@BBN-Unix
[JO5] John O'Donnell YALE ODonnell@YALE
[JRM1] John Mullen MITRE Mullen@MITRE
[JSG5] Jon Goodridge BBN jsg@BBN-UNIX
[JWF] Jim Forgie LL Forgie@BBNC
[JXS] Jeffrey R. Schwab PURDUE jrs@PURDUE
[JZS] Joanne Sattely CCA JZS@CCA
[KLH] Ken Harrenstien SRI KLH@NIC
[KRS] Karen Sollins MIT Sollins@MIT-XX
[LB1] Liudvikas Bukys ROCHESTER Bukys@ROCHESTER
[LCN] Lou Nelson AEROSPACE Lou@AEROSPACE
[LCS] Lou Schreier SRI Schreier@USC-ISID
[LH2] Lincoln Hu COLUMBIA Hu@Columbia-20
[LLG] Larry Garlick XEROX Garlick@PARC-MAXC
[LM8] Liza Martin MIT-LCS Martin@MIT-XX
[MBG] Michael Greenwald MIT-LCS Greenwald@MIT-Multics
[MB] Michael Brescia BBN Brescia@BBN-Unix
[MCSJ] Mike StJohns AFDSC StJohns@MIT-MULTICS
[MH12] Mark Horton ATT mark@BERKELEY
[MHS1] Marvin Solomon WISC Solomon@UWISC
[MJM2] Mike Muuss BRL Mike@BRL
[MO2] Michael O'Brien RAND OBrien@RAND-Unix
[MRC] Mark Crispin Stanford Admin.MRC@SU-SCORE
[MXB] Mark Brown USC Mark@USC-ECLB
[MXR] Marshall Rose Irvine MRose.UCI@RAND-Relay
[NC3] J. Noel Chiappa MIT JNC@MIT-XX
[NM] Neil MacKenzie RSRE T45@USC-ISID
[NXK] Neil Katin HP hpda.neil@BERKELEY
[PK] Peter Kirstein UCL Kirstein@USC-ISIA
[PM1] Paul Mockapetris ISI Mockapetris@USC-ISIF
[PS3] Paal Spilling NDRE Paal@DARCOM-KA
[PXD] Pieter Ditmars BBN pditmars@BBN-UNIX
[PXN] Peter Nellessen SIEMENS crtvax!pn@CMU-CS-SPICE
[RA11] Rick Adams CCI rlgvax!ra@SEISMO
[RB6] Richard Bisbey ISI Bisbey@USC-ISIB
[RDB2] Robert Bressler BBN Bressler@BBN-Unix
[REK2] Robert Kahn ARPA Kahn@USC-ISIA
[RF1] Randy Frank UTAH Frank@UTAH-20
[RH6] Robert Hinden BBN Hinden@BBN-Unix
[RHT] Robert Thomas BBN BThomas@BBNG
[RK1] Richard Kovalcik Honeywell Kovalcik@MIT-MULTICS
[RLB1] Bob Brown USRA rlb@ames-vmsb
[RLH2] Ronald L. Hartung NSWC ron@nswc-wo
[RR2] Raleigh Romine Teledyne romine@SEISMO
[RS23] Russel Sandberg WISC root@UWISC
[RTB] Bob Braden UCLA Braden@USC-ISIA
[SC3] Steve Casner ISI Casner@USC-ISIB
[SGC] Steve Chipman BBN Chipman@BBNA
[SK] Steve Kille UCL UKSAT@USC-ISID
[SXM] Scott Marcus Spartacus ---none---
[TC4] Tony Cincotta DTNSRDC tony@NALCON
[WIM] William Macgregor BBN macg@BBN
[ZSU] Zaw-Sing Su SRI ZSu@SRI-TSCAPPENDIX A 🌈
This appendix sums up what the DDN/PMO and DARPA agreed on at a September 1982 meeting 🗓️. It covers how the numbers tied to DoD Protocol Standards and the DARPA Experimental Standards get allocated and assigned 💅.
Here's the recommended policy for each kind of number assignment we care about 📝.
Network Identifiers used by the Internet Protocol 🌐
The idea is to split the available number spaces for class A, B, and C network addresses across R&D, DoD, and commercial uses. Assignments would then be handled by DARPA, DCA PCCO/DDN, and the National Bureau of Standards, respectively 🎀. The recommended allocations are below 👇.
Class A (highest-order bit 0)
R&D allocation: 8 nets
DoD allocation: 24 nets
Commercial allocation: 94 nets
Reserved Addresses: 0,127
Class B (highest-order bits 1-0)
R&D allocation: 1024 nets
DoD allocation: 3072 nets
Commercial allocation: 12286 nets
Reserved Addresses: 0,16383
Class C (highest-order bits 1-1-0)
R&D allocation: 65536 nets
DoD allocation: 458725 nets
Commercial allocation: 1572862 nets
Reserved Addresses: 0,2097151
Class D (highest-order bits 1-1-1)
All addresses in this class are reserved for future use,
possibly in support of multicast services. They should be
allocated to R&D use for the present.Inside the R&D community, network identifiers will only be granted to applicants who can show evidence that they're acquiring standard Bolt Beranek and Newman gateway software, or that they've implemented or are acquiring a gateway that meets the Exterior Gateway Protocol requirements 🔥. Getting the Berkeley BSD 4.2 UNIX software might count as evidence of the latter 💻.
Experimental networks that become operational don't need renumbering 🙌. Instead, their identifiers can move from R&D to DoD or Commercial status. So network identifiers can change state among R&D, DoD, and commercial, but the number of identifiers allocated to each use should stay within the limits above 💜. To make this fluid assignment possible, the network identifier spaces should not be split up by simple partition, but handed out by specific assignment ✨.
Protocol Identifiers 🧩
Generally, all assignments will be made by the R&D community. But any numbers that become R&D, DoD, national, or international standards will be marked as such in this RFC 🏷️.
Protocol identifiers 0 and 255 are reserved 🚫.
95 protocol identifiers are allocated for assignment to DoD standards, 32 for R&D use, and 127 for Commercial, national, or international standards 📊.
Port Numbers 🚪
A recommendation for allocating and assigning port numbers is still to be developed, jointly by representatives of the ICCB and PSTP 🫶.
ARPANET Link Numbers 🔗
All unnecessary link number usage will be eliminated through joint effort by the ICCB, PSTP, and BBN 🧹.
BBN will look at using link numbers to promote interoperability among the various ARPANET interfaces, and will report back to the ICCB, PSTP, and DDN/PMO 📣. Examples of possible interoperability issues are:
- (i) interoperability of 1822 and X.25 interfaces
- (ii) interoperability of SIP and other interfaces
- (iii) logical addressing or other special services
IP Version Numbers 🌀
These numbers will be assigned only by the R&D community, for exploring alternatives in internet protocol service expansion, such as including stream protocol (ST) services 🧪.
TCP, IP and Telnet Option Identifiers 🎛️
These numbers will be assigned by the R&D community. Any permanent or experimental assignments will be identified in the documents that specify those protocols 📄.
Implementation: 🛠️
This policy recommendation has not been fully implemented yet 😭. For now, Joyce Reynolds is acting coordinator for all number assignments 👑.
📦 where this page comes from
- ietf: rfc870 1983-10
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms