NIC view of standard host names
The NIC's 1971 recommendations for a standard form of network host name.
Watson, R.W., "NIC view of standard host names", RFC 237, DOI 10.17487/RFC0237, October 1971, <https://www.rfc-editor.org/info/rfc237>.
@misc{rfc237,
series = {Request for Comments},
number = 237,
howpublished = {RFC 237},
publisher = {RFC Editor},
doi = {10.17487/RFC0237},
url = {https://www.rfc-editor.org/info/rfc237},
author = {R.W. Watson},
title = {{NIC view of standard host names}},
pagetotal = 1,
year = 1971,
month = oct,
} RFC text
Network Working Group Richard W. Watson
Request for Comments: 237 October 5, 1971
NIC: 7662
The Nic's View of Standard Host Names
The NIC strongly favors standardization of host names. People will
get used to the names appearing on documents coming from or through
the NIC and so we would like the ones used by NIC and the ones used
in Telnets to agree. In the absence of agreed standard names, we
have chosen some. We are not particularly partial to the ones we are
using, but do feel any standard naming scheme take into account most
of the following considerations.
(1) Names consist of two parts, SITE and HOST, preferably
separated by a delimiter such as a dash.
(2) Site and Host names have some mnemonic value, if possible not
involving the name of the computer as computers will change, but
the organization running it will remain.
(3) We strongly recommend at least 8 characters be allowed,
including one delimiter. The NIC now uses 12 characters maximum.
(4) Assuming 8 character names, we recommend that the site name
be a maximum of 6 characters and that Host names at a given site
be unique in the first six characters. Thus, with the delimiter,
sites desiring to only have 4 characters in their tables can
accept all characters typed by the user and truncate to 6
characters and still achieve uniqueness.
(5) Once the NWG has set a standard syntax and names for present
Hosts, the NIC should be responsible for maintaining the standard
and assigning names to new hosts and other groups involved in
Network dialogue. Besides hosts there are NIC stations and
individuals in organizations not on the Net involved in the
Network dialogue. The NIC needs to assign names to these Network
affiliations and will use the rules set by the NWG.
[This RFC was put into machine readable form for entry]
[into the online RFC archives by H�l�ne Morin, Viag�nie 10/99]
ISO Plain Language
On this page
§1Why Standard Host Names Were Needed
The Network Information Center (NIC) favored standard host names so the names used in NIC documents would agree with names used in Telnet. RFC 237 says users could become confused when the names differed.
The NIC wanted a host's name in its documents to match the name users typed in Telnet. Different names for the same host could cause confusion.
§2The Suggested Name Structure
The NIC recommends two parts, SITE and HOST, preferably separated by a delimiter such as a dash. It prefers mnemonic names that refer to the organization rather than the computer model, because the computer may change while the organization remains. It recommends allowing at least eight characters including the delimiter.
A name should show both the site and the host. The NIC preferred meaningful names that were not tied to a computer model.
§3Maintaining the Names
For an eight-character name, the document recommends a site name of at most six characters and host names unique within a site in their first six characters. It proposes that, after the NWG sets syntax and names, the NIC maintain the standard and assign names to new hosts and other network participants.
The proposal asks the NWG to set the naming rules and the NIC to maintain them. Host names at one site should remain distinguishable even when shortened to six characters.