RFC239 Host mnemonics proposed in RFC 226 (NIC 7625)

0239 Host mnemonics proposed in RFC 226 (NIC 7625). R.T. Braden. September 1971. (Format: TXT=2236 bytes) (Also RFC0226, RFC0229, RFC0236) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                        R. Braden
Request for Comments:  #239                                  UCLA-CCN
NIC 7664                                                     23 September 1971
Categories: D.3
Related:  #226, 229, 236

                  HOST MNEMONICS PROPOSED IN RFC #226

   (Note from NIC: These are comments sent by R.Braden to P. Karp in NIC
   7626, and are now issued as NIC 7664, RFC 239 to include them in the
   dialogue along with RFC 226, 229, 236)

        CCN is in full agreement that a standard set of host mnemonics
   should be selected.  However, your proposed set is not fully
   satisfactory.

   1.  The set you suggest was created, I assume, by the systems
       programmer(s) who wrote TELNET in TENEX.  It is a set of
       historical accidents, and shows it.

   2.  A better source for standard mnemonics might be the NIC site
       codes, since these have been chosen with more care and will
       become familiar as we begin to use the NIC on-line.  Surely
       the NIC is a more reasonable source for a defacto standard
       than a particular system programmer.

   3.  Should mnemonics be limited to 6 characters?

   4.  The most recent list from BBN (NIC #7181, RFC #208,
       August 9, 1971) shows 40 hosts.  You show only 20.  Your
       proposed standard should include known hosts at this time.

   5.  The mnemonic "UCLA36" seems a particularly bad choice; "UCLA91"
       would be much better.

   6.  Also, we at CCN object to the short form "UCLA" for the NMC
       Sigma 7; that also is historical.  We propose the following:

           host 1: UCLAS7 or UCLANM;         host 65: UCLA91.

   7.  "SRIARC" is a poor choice; everybody calls it the NIC.  So we
       suggest "SRINIC" for host 2.

        Please, let's not perpetrate systems programmers' midnight
   decisions on all future Network users!  Standards are vital, and
   deserve a little care.

       [ 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   ]
9


                                                                [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 

スポンサーリンク

テーブル行要素が背景関連プロパティを無視する

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

上に戻る