RFC relevance of internet

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

Elizabeth Feinler RFC 810
Ken Harrenstien 1 March 1982
Zaw-Sing Su References: RFC 811, 796
Vic White Obsoletes: RFC 608
Network Information
SRI

DoD INTERNET HOST TABLE

The ARPANET Official Network Host Table, as outlined in RFC 608,
longer suits the needs of the DoD community, nor does it follow
format suitable for internetting. This paper specifies a new
table format applicable to both ARPANET and Internet needs

In addition to host name to host address translation and
protocol information, we have also included network and gateway
to address correspondence, and host operating system information

This Host Table is utilized by the DoD Host Name Server maintained
the ARPANET Network Information Center (NIC) on behalf of the
Communications Agency (DCA) (RFC 811). It obsoletes the host
described in RFC 608.

LOCATION OF THE STANDARD DoD ONLINE HOST

A machine-translatable ASCII text version of the new DoD Host
is online in the file HOSTS.TXT on the SRI-NIC host. It
be obtained by connecting to host SRI-NIC (10.0.0.73) from your
FTP server, logging in as user=ANONYMOUS, password=GUEST, and doing
'get' on HOSTS.TXT. The same table may also be obtained
the NIC Host Name Server

NOTE: See Appendix A. for timeframe for cutover

1. A "name" (Net, Host, Gateway, or Domain name) is a text string
to 24 characters drawn from the alphabet (A-Z), digits (0-9), and
minus sign (-) and period (.). No blank or space characters
permitted as part of a name. No distinction is made between
and lower case. The first character must be a letter. The
character must not be a minus sign or period. A host which serves
a GATEWAY should have "-GATEWAY" or "-GW" as part of its name.
host which is a TIP or a TAC should have "-TIP" or "-TAC" as part
its host name, if it is an ARPANET or DoD host

2. Internet Addresses are 32-bit addresses (RFC 796). In the
table described herein each address is represented by four
numbers separated by a period. Each decimal number represents 1
octet

[Page 1]

RFC 810 1 March 1982
Host Table

3. If the first bit of the first octet of the address is 0 (zero),
then the next 7 bits of the first octet indicate the network
(Class A Address). If the first two bits are 1,0 (one,zero),
the next 14 bits define the net number (Class B Address). If
first 3 bits are 1,1,0 (one,one,zero), then the next 21 bits
the net number (Class C Address) (RFC 796).

This is depicted in the following diagram

+--------------+-----------------------------------------------+
|0| NET <-7-> | LOCAL ADDRESS <-24-> |
+--------------+-----------------------------------------------+

+---+--------------------------+-------------------------------+
|1 0| NET <-14-> | LOCAL ADDRESS <-16-> |
+---+--------------------------+-------------------------------+

+-----+----------------------------------------+---------------+
|1 1 0| NET <-21-> | LOCAL ADDRESS |
+-----+----------------------------------------+---------------+

4. The LOCAL ADDRESS portion of the internet address identifies
host within the network specified by the NET portion of the address

5. For the ARPANET (a Class A network), the NET address is 10
(decimal) and the LOCAL ADDRESS maps as follows: the second
defines the physical host, the third octet defines the logical host
and the fourth defines the IMP

+-+-------------+---------------+--------------+---------------+
|0| 10 | HOST | LOGICAL HOST | IMP |
+-+-------------+---------------+--------------+---------------+

(NOTE: RFC 796 describes the local address mappings for
other networks.)

6. It is the responsibility of the user using this host table
translate it into whatever format is needed for his or her purposes

7. Names and Addresses for DoD networks, gateways, and hosts will
negotiated and registered with the Network Information
(NIC@SRI-NIC or (415) 859-4775) before being used and before
is passed by a DoD host. For an interim period the NIC will
to keep similar information for non-DoD networks and hosts if
information is provided, and as long as it is needed, i.e.,
intercommunicating network name servers are in place

EXAMPLE OF NEW HOST TABLE

NET : 10.0.0.0 : ARPANET :

[Page 2]

1 March 1982 RFC 810
Host Table

NET : 18.0.0.0 : LCSNET :
GATEWAY : 10.0.0.77, 18.8.0.4 : MIT-GW :: MOS : IP/GW :
HOST : 10.0.0.73 : SRI-NIC,NIC : FOONLY-F3 : TENEX :
NCP/TELNET,NCP/FTP, TCP/TELNET, TCP/FTP :
HOST: 10.2.0.11 : SU-TIP,FELT-TIP :::

SYNTAX AND

; (semicolon) is used to denote the beginning of a comment
Any text on a given line following a ';'
comment, and not part of the host table

NET keyword introducing a network name/address

GATEWAY keyword introducing a gateway name/address

HOST keyword introducing a host name/address

: (colon) is used as a field

:: (2 colons) indicates a null

, (comma) is used as a data element

XXX/YYY indicates protocol information of the
TRANSPORT/SERVICE

where TRANSPORT/SERVICE options are specified

"FOO/BAR" - both transport and service
"FOO" - transport known; services not known or
running,
"BAR" - name is known, what it does is

NOTE: See Appendices B and C for specific options
acronyms

Each host table entry is an ASCII text string comprised of 6 fields

Field 1 = KEYWORD indicating whether this entry
to a NET, GATEWAY, or HOST. NET entries cannot
alternate addresses or nicknames
Field 2 = Internet Address of Network, Gateway, or
followed by alternate
Field 3 = Official Name of Network, Gateway, or
(with optional nicknames
Field 4 = Machine
Field 5 = Operating
Field 6 = Protocol

[Page 3]

RFC 810 1 March 1982
Host Table

Fields 4, 5 and 6 are optional

Fields 3-6, if available, pertain to the first address in Field 2.

'Blanks' (spaces and tabs) are ignored between data elements
fields, but are disallowed within a data element

Each entry ends with a colon

The host table will be sorted by internet address

GRAMMATICAL HOST TABLE

A. Parsing

::= ":" <addresses> ":" [":" []
[":" [] [":" [<protocol list>] ]]] ":"
<addresses> ::=
*[","
]

::= "." "." "." ::= <0 to 255 decimal
::= | | <official hostname> *["," ]
::= ::= <official hostname> ::= <nickname> ::= <protocol list> ::= <protocol spec> *["," <protocol spec>]
<protocol spec> ::= <transport name> "/" |
protocol name

B. Lexical

::= [ ]
::= ::= NET | GATEWAY |
::= [*[]]
::= PDP-11/70 | DEC-1080 | C/30 | CDC-6400...etc
::= ITS | MULTICS | TOPS20 | UNIX...etc
<transport name> ::= TCP | NCP | UDP | IP...etc
::= TELNET | FTP | SMTP | MTP...etc
protocol name> ::= ::= ";" <arbitrary text>
Notes

1. Zero or more 'blanks' between separators " , : " are allowed
'Blanks' are spaces and tabs
2. Continuation lines are lines that begin with at least
blank. They may be used anywhere 'blanks' are legal to split
entry across lines

[Page 4]

1 March 1982 RFC 810
Host Table

1. Feinler, E. and Kudlick, M. Host Names Online, RFC 608,
Network Information Center, SRI International, Jan. 1973.

2. Postel, J. Assigned Numbers, RFC 790, Information
Inst., Univ. of Southern Calif., Marina Del Rey, Sept. 1981.

3. Postel, J. Internet Protocol, RFC 791, Information
Inst., Univ. of Southern Calif., Marina Del Rey, Sept. 1981.

4. Postel, J. Address Mappings, RFC 796, Information
Inst., Univ. of Southern Calif., Marina Del Rey, Sept. 1981.

5. Feinler, E., Harrenstien, K., Su, Z. and White, V.
DoD Internet Host Table Specification, RFC 810,
Information Center, SRI International, March 1, 1982.

[Page 5]

RFC 810 1 March 1982
Host Table

APPENDIX A. CUTOVER

The cutover date for use of the new host table is 1 May 1982.
table below indicates which files will contain the old or the
versions of the host table for what period of time. After 1
1982, the old format for HOSTS.TXT (specified in RFC-608)
will no longer be supported

--------------------------------------------------------------------
May 1982 June-July 1982 August 1982
--------------------------------------------------------------------

HOSTS.TXT HOSTS.TXT HOSTS.
old version new version new

NHOSTS.TXT NHOSTS.TXT old
new version (test) new version

OHOSTS.TXT OHOSTS.
old version old

--------------------------------------------------------------------

These periods of overlap should give implementors time to make
necessary changes to programs accessing this file

[Page 6]

1 March 1982 RFC 810
Host Table

APPENDIX B. TRANSPORT/SERVICE OPTIONS AND

Current TRANSPORT/SERVICE options are

IP TCP/
IP/GW TCP/
NCP TCP/
NCP/FTP TCP/
NCP/RJE TCP/
NCP/SMTP TCP/
NCP/TELNET TCP/
NCP/NNS

Note: "TCP" implies IP is also

Acronym definitions for the above protocol options are

FTP - File Transfer
GW - Gateway
IP - Internet
MTP - Mail Transfer
NCP - Network Control
NNP - NIC Internet Name Server
NVP - Network Voice
RJE - Remote Job Entry
SMTP - Simple Mail Transfer
TELNET - TELNET
TCP - Transmission Control
TFTP - Trivial File Transfer
UDP - User Datagram

[Page 7]

RFC 810 1 March 1982
Host Table

APPENDIX C. OPERATING SYSTEM

Current operating system acronyms are

ASP KRONOS RSX11M
AUGUST MCP RT11
BKY MOS
CCP MPX-RT
DOS/360 MULTICS
ELF MVT
EPOS NOS TOPS10
EXEC-8 NOS/BE TOPS20
GCOS OS/MVS
GPOS OS/MVT
ITS RIG VM/370
INTERCOM RSX11 VM/

[Page 8]

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