RFC237 NIC view of standard host names

0237 NIC view of standard host names. R.W. Watson. October 1971. (Format: TXT=2212 bytes) (Obsoleted by RFC0273) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

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駘鈩e Morin, Viag駭ie 10/99]







Watson                                                          [Page 1]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

SetLeftMargin - 左マージン指定

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る