From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc349.txt | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 doc/rfc/rfc349.txt (limited to 'doc/rfc/rfc349.txt') diff --git a/doc/rfc/rfc349.txt b/doc/rfc/rfc349.txt new file mode 100644 index 0000000..f42b2a7 --- /dev/null +++ b/doc/rfc/rfc349.txt @@ -0,0 +1,59 @@ + + + + + + +Network Working Group Jon Postel +Request for Comments : 349 Computer Science + UCLA-NMC +NIC : 10428 30 May 72 + +Categories : Socket Numbers +References : RFC's 322, 204 + + + Proposed Standard Socket Numbers + +I propose that there be a czar (me ?) who hands out official socket +numbers for use by standard protocols. This czar should also keep track +of and publish a list of those socket numbers where host specific +services can be obtained. I further suggest that the initial allocation +be as follows: + Sockets Assignment + 0-63 Network wide standard functions + 64-127 Host specific functions + 128-239 Reserved for future use + 240-255 Any experimental function + +and within the network wide standard functions the following particular +assignment be made: + Socket Assignment + 1 Telnet + 3 File Transfer + 5 Remote Job Entry + 7 Echo + 9 Discard + +these socket numbers (decimal) are to be used for the socket called "L" +in the official Initial Connection protocol (ICP) as specified in NIC +7104 the "Current Network Protocols" notebook. + + + + + + [ This RFC was put into machine readable form for entry ] + [ into the online RFC archives by BBN Corp. under the ] + [ direction of Alex McKenzie. 12/96 ] + + + + + + + + + + [Page 1] + -- cgit v1.2.3