As per Relevance of the word specific, we have this rfc below:
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Network Working Group J.
Request for Comments: 750 USC-
NIC: 45500 26 September 1978
Obsoletes: 739,
604, 503, 433, 349
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
[Page 1]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
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-151 110-227
152 230 PARC Universal
153 231 TIP Status
154 232 TIP
155-158 233-236 Internet Protocol [35,36,42,43,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]
[Page 2]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Socket
ASSIGNED SOCKET
Sockets are used in the AHHP [1,3] to name the ends of
connections which carry long term conversations. For the purpose
providing services to all callers an Initial Connection Procedure
[1,34] is used between the user process and the server process.
list specifies the socket used by the server process as its
socket
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
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-63 52-77
[Page 3]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Socket
Host Specific
Decimal Octal Description
------- ----- ----------- ----------
65 101 Speech Data Base at LL-TX-2 [23]
67 103 Datacomputer at CCA [24]
69 105
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
86-94 126-136
95 137 SUPDUP [33]
97 141 Datacomputer
98-127 142-136
Reserved for Future
Decimal Octal Description
------- ----- ----------- ----------
128-223 200-337
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]
[Page 4]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Network
ASSIGNED NETWORK
This list of network numbers is used in the internetwork
now under development, the field is 8 bits in size
Assigned Network
Decimal Octal Network
------- ----- ------- ----------
0 0
1 1 BBN Packet Radio
2 2 SF Bay Area Packet Radio Network (1)
3 3 BBN RCC
4 4 Atlantic Satellite
5 5 Washington D.C. Packet Radio
6 6 SF Bay Area Packet Radio Network (2)
7 7 CHAOS
8 10 BBN SATNET Test
9 11 Ft. Gordon Packet Radio
10 12 ARPANET [1,2]
11 13 University College London
12 14
13 15 National Physical
14 16
15 17 British Post Office
16 20
17 21
18 22 LCS Network [37,38]
19 23
20 24 Ft. Sill Packet Radio
21 25 DCEC
22-254 26-376
255 377
[Page 5]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Internet Message
ASSIGNED INTERNET MESSAGE
In the internetwork protocols there is a field to identify
version of the internetwork general protocol. This field is 4
in size
Assigned Internet Message
Decimal Octal Version
------- ----- ------- ----------
0 0 March 1977 version [35]
1 1 January 1978 version [36]
2 2 February 1978 version A [42]
3 3 February 1978 version B [43]
4 4 September 1978 version 4 [44]
5-14 5-16
15 17
[Page 6]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Internet Message
ASSIGNED INTERNET MESSAGE
In several of the internetwork protocol versions there is a field
identify the format of the host level specific protocol. This
is 8 bits in size. This field is called either Format or Protocol
Assigned Internet Message
Decimal Octal Format
------- ----- ------ ----------
0 0
1 1 raw internet [42]
2 2 TCP-3 [36]
3 3 DSP [37,38]
4 4 Gateway Monitoring Message [41]
5 5 TCP-3.1 [45]
6 6 TCP-4 [46]
7-254 7-376
255 377
[Page 7]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
Assigned Internet Message
ASSIGNED INTERNET MESSAGE
In the March 1977 internetwork protocol [35] there is a field
identify the type of the message. This field is 4 bits in size
Assigned Internet Message
Decimal Octal Type
------- ----- ---- ----------
0 0 Raw Internet
1 1 TCP-2 [35]
2 2
3 3
4 4
5 5 DSP [37,38]
6 6
7-12 7-14
13 15
14 16
15 17
[Page 8]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
[1] Feinler, E. "ARPANET Protocol Handbook," NIC 7104,
Communications Agency, January 1978.
[2] BBN, "Specifications for the Interconnection of a Host and
IMP," Report 1822, Bolt Beranek and Newman, Cambridge
Massachusetts, January 1976.
[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].
[15] Postel, J. "Revised FTP Reply Codes," RFC 640, NIC 30843,
5 June 1974. Also in [1].
[Page 9]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
[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] Armenti, A., D. Hall, and A. Stone. "Lincoln Speech
Facility," SUR Note 37, NIC 10917, 14 July 1972.
[24] CCA, "Datacomputer Version 1 User Manual,"
Corporation of America, August 1975.
[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.
[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.
[Page 10]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
[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] Postel, J. "Draft Internetwork Protocol Specification --
Version 2," USC-Information Sciences Institute, February 1978.
[43] Cerf, V. "A Proposed New Internet Header Format,"
Research Projects Agency, IEN 26, 14 February 1978.
[44] Postel, J. "Internetwork Protocol Specification -- Version 4,"
IEN-54, USC-Information Sciences Institute, September 1978.
[Page 11]
NWG/RFC 750 JBP 26-Sep-78 18:30 45500
Assigned
[45] Cerf, V. "A Proposal for TCP Version 3.1 Header Format,"
Advanced Research Projects Agency, IEN 26, 14 February 1978.
[46] Postel, J. "Specification of Internetwork Transmission
Protocol -- Version 4," IEN-55, USC-Information
Institute, September 1978.
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
