RFC relevance of internet

As per Relevance of the word internet, we have this rfc below:

Network Working Group J.
Request for Comments: 770
September 1980

Obsoletes RFCs: 762, 758, 755,
750, 739, 604, 503, 433, 349
Obsoletes IENs: 127, 117, 93

ASSIGNED

This Network Working Group Request for Comments documents the
assigned values from several series of numbers used in network
implementations. This RFC will be updated periodically, and in any
current information can be obtained from Jon Postel. The assignment
numbers is also handled by Jon. If you are developing a protocol
application that will require the use of a link, socket, etc.
contact Jon to receive a number assignment

Jon
USC - Information Sciences
4676 Admiralty
Marina del Rey, California 90291

phone: (213) 822-1511

ARPANET mail: POSTEL@

Most of the protocols mentioned here are documented in the RFC series
notes. The more prominent and more generally used are documented in
Protocol Handbook [1] prepared by the Network Information Center (NIC).
In the lists that follow a bracketed number, e.g. [1], off to the
of the page indicates a reference for the listed protocol

Postel [Page 1]

RFC 770 September 1980
Assigned
Network

ASSIGNED NETWORK

This list of network numbers is used in the internet, the field
8 bits in size

Assigned Network

Decimal Octal Name Network
------- ----- ---- ------- ----------
0 0
1 1 BBN-PR BBN Packet Radio
2 2 SF-PR-1 SF Bay Area Packet Radio Network (1)
3 3 BBN-RCC BBN RCC
4 4 SATNET Atlantic Satellite
5 5 SILL-PR Ft. Sill Packet Radio
6 6 SF-PR-2 SF Bay Area Packet Radio Network (2)
7 7 CHAOS MIT CHAOS
8 10 CLARKNET SATNET subnet for
9 11 BRAGG-PR Ft. Bragg Packet Radio
10 12 ARPANET ARPANET [1,2]
11 13 UCLNET University College London
12 14 CYCLADES
13 15 NPLNET National Physical
14 16 TELENET
15 17 EPSS British Post Office
16 20 DATAPAC
17 21 TRANSPAC
18 22 LCSNET MIT LCS Network [37,38]
19 23 TYMNET
20 24 DC-PR Washington D.C. Packet Radio
21 25 EDN DCEC
22 26 DIALNET DIALNET [47,48]
23 27 MITRE MITRE Cablenet [23]
24 30 BBN-LOCAL BBN Local
25 31 RSRE-PPSN RSRE /
26 32 AUTODIN-II AUTODIN
27 33 NOSC-LCCN NOSC /
28 34 WIDEBAND Wide Band Satellite
29 35 DCN-COMSAT COMSAT Distributed Computing
30 36 DCN-UCL UCL Distributed Computing
31 37 BBN-SAT-TEST BBN SATNET Test
32 40 UCL-CR1 UCL Cambridge Ring 1
33 41 UCL-CR2 UCL Cambridge Ring 2
34 42 MATNET Mobile Access Terminal
35 43 NULL UCL/RSRE Null
36 44 SU-NET Stanford University

Postel [Page 2]

RFC 770 September 1980
Assigned
Network

37 45 DECNET Digital Equipment
38 46 DECNET-TEST Test Digital Equipment
39-254 47-376
255 377

Postel [Page 3]

RFC 770 September 1980
Assigned
Internet Protocol

ASSIGNED INTERNET PROTOCOL

In the Internet Protocol (IP) there is a field to identify
version of the internetwork general protocol. This field is 4
in size

Assigned Internet Protocol

Decimal Octal Version
------- ----- ------- ----------
0 0 March 1977 version [35]
1-3 1-3
4 4 January 1980 version [44]
5 5 ST Datagram Mode [45]
6-14 6-16
15 17

Postel [Page 4]

RFC 770 September 1980
Assigned
Internet Protocol

ASSIGNED INTERNET PROTOCOL

In the Internet Protocol (IP) [44] there is a field to identify
the next level protocol. This field is 8 bits in size. This
is called Protocol in the IP header

Assigned Internet Protocol

Decimal Octal Protocol Numbers
------- ----- ---------------- ----------
0 0
1 1 raw internet datagrams [44]
2 2 TCP-3 [36]
3 3 Gateway-to-Gateway [49]
4 4 Gateway Monitoring Message [41]
5 5 ST [45]
6 6 TCP-4 [46]
7 7
8 10 DSP [37,38]
9 11
10 12 TCP-2 [35]
11 13 NVP [39]
12 14 PUP [55]
13 15
14 16
15 17
16 20
17 21 User Datagram [50]
18 22 Multiplexing [51]
19 23
20-62 24-76
63 77 any local
64 100 EXPAK
65 101 EXPAK PC
66 102
67 103 Gateway
68 104
69 105 SIMP
70 106 SIMP
71 107 SIMP packet core/
72-76 110-114
77 115 backroom SIMP
78 116 backroom SIMP
79 117 SIMP message
80-254 120-376
255 377

Postel [Page 5]

RFC 770 September 1980
Assigned
Port or Socket

ASSIGNED PORT or SOCKET

Ports are used in the TCP [46] and sockets are used in the AHHP [1,3]
to name the ends of logical connections which carry long
conversations. For the purpose of providing services to
callers a service contact socket is defined. This list specifies
port or socket used by the server process as its contact socket.
the AHHP an Initial Connection Procedure ICP [1,34] is used
the user process and the server process to make the initial
and establish the long term connections leaving the contact
free to handle other callers. In the TCP no ICP is necessary since
port may engage in many simultaneous connections

The assigned ports/sockets use a small part of the
port/socket numbers. The ports/assigned sockets have all except
low order eight bits cleared to zero. The low order eigth bits
specified here

Socket Assignments

General Assignments

Decimal Octal
------- ----- -----------
0-63 0-77 Network Wide Standard
64-127 100-177 Hosts Specific
128-223 200-337 Reserved for Future
224-255 340-377 Any Experimental

Postel [Page 6]

RFC 770 September 1980
Assigned
Port or Socket

Specific Assignments

Network Standard

Decimal Octal Description
------- ----- ----------- ----------
1 1 Old Telnet [6]
3 3 Old File Transfer [7,8,9]
5 5 Remote Job Entry [1,10]
7 7 Echo [11]
9 11 Discard [12]
11 13 Who is on or
13 15 Date and
15 17 Who is up or
17 21 Short Text
19 23 Character generator or TTYTST [13]
21 25 New File Transfer [1,14,15]
23 27 New Telnet [1,16,17]
25 31 Distributed Programming System [18,19]
27 33 NSW User System w/COMPASS FE [20]
29 35 MSG-3 ICP [21]
31 37 MSG-3 Authentication [21]
33 41 DPS ICP [18,19]
35 43 IO Station
37 45 Time Server [1,22]
39 47 NSW User System w/SRI FE [20]
41 51 Graphics [1,26]
42 52 Name Server [52]
43 53
45 55 Internet Message Processing Module [53]
47 57 NI FTP [54]
49 61 RAND Network Graphics Conference [56]
51 63 Simple Internet
53 65 AUTODIN II FTP [57]
55 67 ISI Graphics Language [58]
57 71 Mail Transfer [43]
59-63 73-77

Postel [Page 7]

RFC 770 September 1980
Assigned
Port or Socket

Host Specific

Decimal Octal Description
------- ----- ----------- ----------
65 101
67 103 Datacomputer at CCA [24]
69 105
69 105 Trivial File Transfer [42]
71 107 NETRJS (EBCDIC) at UCLA-CCN [1,25]
73 111 NETRJS (ASCII-68) at UCLA-CCN [1,25]
75 113 NETRJS (ASCII-63) at UCLA-CCN [1,25]
77 115 any private RJE
79 117 Name or Finger [1,40]
81 121 Network
83 123 MIT ML
85 125 MIT ML
87 127 any terminal
89 131 SU/MIT Telnet
91-94 133-136
95 137 SUPDUP [33]
97 141 Datacomputer
99 143 CADC - NIFTP via
101 145 NPL - NIFTP via
103 147 BNPL - NIFTP via
105 151 CAMBRIDGE - NIFTP via
107 153 HARWELL - NIFTP via
109 155 SWURCC - NIFTP via
111 157 ESSEX - NIFTP via
113 161 RUTHERFORD - NIFTP via
115-127 163-177

Reserved for Future

Decimal Octal Description
------- ----- ----------- ----------
128-223 200-337

Postel [Page 8]

RFC 770 September 1980
Assigned
Port or Socket

Experimental

Decimal Octal Description
------- ----- ----------- ----------
224-231 340-347
232-237 350-355 Authorized Mailer at
239 357
241 361 NCP Measurement [27,28]
243 363 Survey Measurement [28,29,30]
245 365 LINK [31]
247 367
249-255 371-377 RSEXEC [31,32]

Postel [Page 9]

RFC 770 September 1980
Assigned
Link

ASSIGNED LINK

The word "link" here refers to a field in the original
Host/IMP interface leader. The link was originally defined as an 8
bit field. Some time after the ARPANET Host-to-Host (AHHP)
was defined and, by now, some time ago the definition of this
was changed to "Message-ID" and the length to 12 bits. The name
now refers to the high order 8 bits of this 12 bit message-id field
The low order 4 bits of the message-id field are to be zero
specifically specified otherwise for the particular protocol used
that link. The Host/IMP interface is defined in BBN report 1822 [2].

Link Assignments

Decimal Octal Description
------- ----- ----------- ----------
0 0 AHHP Control Messages [1,3]
1 1
2-71 2-107 AHHP Regular Messages [1,3]
72-150 110-226
151 227 CHAOS
152 230 PARC Universal
153 231 TIP Status
154 232 TIP
155 233 Internet Protocol (regular traffic) [44]
156-158 234-236 Internet Protocol (experimental traffic) [44]
159-191 237-277 Measurements [28]
192-195 300-303 Message Switching Protocol [4,5]
196-255 304-377 Experimental
224-255 340-377 NVP [1,39]
248-255 370-377 Network

Postel [Page 10]

RFC 770 September 1980
Assigned

[1] Feinler, E. and J. Postel, eds., "ARPANET Protocol Handbook,"
NIC 7104, for the Defense Communications Agency by
International, Menlo Park, California, Revised January 1978.

[2] BBN, "Specifications for the Interconnection of a Host and
IMP," Report 1822, Bolt Beranek and Newman, Cambridge
Massachusetts, May 1978.

[3] McKenzie,A. "Host/Host Protocol for the ARPA Network,"
NIC 8246, January 1972. Also in [1].

[4] Walden, D. " A System for Interprocess Communication in
Resource Sharing Network," RFC 62, NIC 4962, 3 August 1970.
Also published in Communications of the ACM, volume 15,
number 4, April 1972.

[5] Bressler, B. "A Proposed Experiment with a Message
Protocol," RFC 333, NIC 9926, 15 May 72.

[6] Postel, J. "Telnet Protocol," RFC 318, NIC 9348, 3 April 1972.

[7] McKenzie, A. "File Transfer Protocol," RFC 454, NIC 14333,
16 February 1973.

[8] Clements, R. "FTPSRV -- Extensions for Tenex Paged Files,"
RFC 683, NIC 32251, 3 April 1975. Also in [1].

[9] Harvey, B. "One More Try on the FTP," RFC 691, NIC 32700,
6 June 1975.

[10] Bressler, B. "Remote Job Entry Protocol," RFC 407, NIC 12112,
16 October 72. Also in [1].

[11] Postel, J. "Echo Process," RFC 347, NIC 10426, 30 May 1972.

[12] Postel, J. "Discard Process," RFC 348, NIC 10427,
30 May 1972.

[13] Postel, J. "Character Generator Process," RFC 429, NIC 13281,
12 December 1972.

[14] Neigus, N. "File Transfer Protocol," RFC 542, NIC 17759,
12 July 1973. Also in [1].

Postel [Page 11]

RFC 770 September 1980
Assigned

[15] Postel, J. "Revised FTP Reply Codes," RFC 640, NIC 30843,
5 June 1974. Also in [1].

[16] McKenzie, A. "Telnet Protocol Specification," NIC 18639,
August 1973. Also in [1].

[17] McKenzie, A. "Telnet Option Specification," NIC 18640,
August 1973. Also in [1].

[18] White, J. "A High Level Framework for Network-Based
Sharing," RFC 707, NIC 34263, 14 January 1976. Also in
Proceedings, AFIPS, June 1976.

[19] White, J. "Elements of a Distributed Programming System,"
RFC 708, NIC 34353, 28 January 1976.

[20] 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. "
Semi-Annual Report," CADD-7608-1611, Massachusetts
Associates, 16 August 1976.

[21] NSW Protocol Committee, "MSG: The Interprocess
Facility for the National Software Works," CADD-7612-2411,
Massachusetts Computer Associates, BBN 3237, Bolt Beranek
Newman, Revised 24 December 1976.

[22] Harrenstien, K. "Time Server," RFC 738, NIC 42218,
31 October 1977. Also in [1].

[23] Skelton, A., S. Holmgren, and D. Wood, "The MITRE
Project," IEN 96, April 1979.

[24] CCA, "Datacomputer Version 5/4 User Manual,"
Corporation of America, August 1979.

[25] Braden, R. "NETRJS Protocol," RFC 740, NIC 42423,
22 November 1977. Also in [1].

[26] Sproull, R, and E. Thomas. "A Networks Graphics Protocol,"
NIC 24308, 16 August 1974. Also in [1].

[27] Cerf, V., "NCP Statistics," RFC 388, NIC 11360,
23 August 1972.

Postel [Page 12]

RFC 770 September 1980
Assigned

[28] Cerf, V., "Formation of a Network Measurement Group (NMG),"
RFC 323, NIC 9630, 23 March 1972.

[29] Bhushan, A., "A Report on the Survey Project," RFC 530,
NIC 17375, 22 June 1973.

[30] Cantor, D., "Storing Network Survey Data at the Datacomputer,"
RFC 565, NIC 18777, 28 August 1973.

[31] Bressler, R., "Inter-Entity Communication -- An Experiment,"
RFC 441, NIC 13773, 19 January 1973.

[32] Thomas, R. "A Resource Sharing Executive for the ARPANET,"
AFIPS Conference Proceedings, 42:155-163, NCC, 1973.

[33] Crispin, M. "SUPDUP Protocol," RFC 734, NIC 41953,
7 October 1977. Also in [1].

[34] Postel, J. "Official Initial Connection Protocol," NIC 7101,
11 June 1971. Also in [1].

[35] Cerf, V. "Specification of Internet Transmission
Program -- TCP (version 2)," March 1977.

[36] Cerf, V. and J. Postel, "Specification of
Transmission Control Program -- TCP Version 3,"
USC/Information Sciences Institute, January 1978.

[37] Reed, D. "Protocols for the LCS Network," Local Network
3, Laboratory for Computer Science, MIT, 29 November 1976.

[38] Clark, D. "Revision of DSP Specification," Local Network
9, Laboratory for Computer Science, MIT, 17 June 1977.

[39] Cohen, D. "Specifications for the Network Voice
(NVP)," NSC Note 68, 29 January 1976. Also as USC/
Sciences Institute RR-75-39, March 1976, and as RFC 741,
NIC 42444, 22 November 1977. Also in [1].

[40] Harrenstien, K. "Name/Finger," RFC 742, NIC 42758,
30 December 1977. Also in [1].

[41] Cole, J. "Gateway Monitoring Messages," BBN, 1 February 1978.

[42] Sollins, K. "The TFTP Protocol," IEN 133, MIT/LCS
January 1980.

Postel [Page 13]

RFC 770 September 1980
Assigned

[43] Sluizer, S., and J. Postel, "Mail Transfer Protocol," RFC 772,
USC/Information Sciences Institute, September 1980.

[44] Postel, J. "DOD Standard Internet Protocol," IEN 128, RFC 760,
USC/Information Sciences Institute, January 1980.

[45] Forgie, J. "ST - A Proposed Internet Stream Protocol,"
IEN 119, M.I.T. Lincoln Laboratory, September 1979.

[46] Postel, J., "DOD Standard Transmission Control Protocol,"
IEN 129, RFC 761, USC/Information Sciences Institute
January 1980.

[47] McCarthy, J. and L. Earnest, "DIALNET," Stanford
Artificial Intelligence Laboratory, Undated

[48] Crispin, M. and I. Zabala, "DIALNET Protocols,"
University Artificial Intelligence Laboratory, July 1978.

[49] Strazisar, V., "How to Build a Gateway," IEN 109, Bolt
and Newman, August 1979.

[50] Postel, J., "User Datagram Protocol," IEN 88, USC/
Sciences Institute, May 1979.

[51] Cohen, D. and J. Postel, "Multiplexing Protocol," IEN 90,
USC/Information Sciences Institute, May 1979.

[52] Postel, J., "Name Server," IEN 116, USC/Information
Institute, August 1979.

[53] Postel, J., "Internet Message Protocol," RFC 759, IEN 113,
USC/Information Sciences Institute, August 1980.

[54] The High Level Protocol Group, "A Network Independent
Transfer Protocol," INWG Protocol Note 86, December 1977.

[55] Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP:
Internetwork Architecture," XEROX Palo Alto Research Center
CSL-79-10, July 1979.

[56] O'Brien, M., "A Network Graphical Conferencing System,"
Corporation, N-1250-ARPA, August 1979.

[57] Forsdick, H., and A. McKenzie, "FTP Functional Specification,"
Bolt Beranek and Newman, Report 4051, August 1979.

Postel [Page 14]

RFC 770 September 1980
Assigned

[58] Bisbey, R., D. Hollingworth, B. Britt, and G. Mellstrom
"Graphics Language (version 2)," USC/Information
Institute, June 1979.

Postel [Page 15]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX