RFC2100 The Naming of Hosts

2100 The Naming of Hosts. J. Ashworth. April 1 1997. (Format: TXT=4077 bytes) (Status: INFORMATIONAL)

日本語訳
RFC一覧

参照

Network Working Group                                       J. Ashworth
Request for Comments: 2100                        Ashworth & Associates
Category: Informational                                    1 April 1997


                          The Naming of Hosts

Status of this Memo

   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.

Introduction

   This RFC is a commentary on the difficulty of deciding upon an
   acceptably distinctive hostname for one's computer, a problem which
   grows in direct proportion to the logarithmically increasing size of
   the Internet.

   Distribution of this memo is unlimited.

   Except to TS Eliot.

   And, for that matter, to David Addison, who hates iambic pentameter.

Poetry

    The Naming of Hosts is a difficult matter,
        It isn't just one of your holiday games;
    You may think at first I'm as mad as a hatter
        When I tell you, a host must have THREE DIFFERENT NAMES.

    First of all, there's the name that the users use daily,
        Such as venus, athena, and cisco, and ames,
    Such as titan or sirius, hobbes or europa--
        All of them sensible everyday names.

    There are fancier names if you think they sound sweeter,
        Some for the web pages, some for the flames:
    Such as mercury, phoenix, orion, and charon--
        But all of them sensible everyday names.

    But I tell you, a host needs a name that's particular,
        A name that's peculiar, and more dignified,
    Else how can it keep its home page perpendicular,
        And spread out its data, send pages world wide?




Ashworth                     Informational                      [Page 1]

RFC 2100                  The Naming of Hosts               1 April 1997


    Of names of this kind, I can give you a quorum,
        Like lothlorien, pothole, or kobyashi-maru,
    Such as pearly-gates.vatican, or else diplomatic-
        Names that never belong to more than one host.

    But above and beyond there's still one name left over,
        And that is the name that you never will guess;
    The name that no human research can discover--
        But THE NAMESERVER KNOWS, and will us'ually confess.

    When you notice a client in rapt meditation,
        The reason, I tell you, is always the same:
    The code is engaged in a deep consultation
        On the address, the address, the address of its name:

                It's ineffable,
                effable,
                Effanineffable,
                Deep and inscrutable,
                singular
                Name.

Credits

   Thanks to Don Libes, Mark Lottor, and a host of twisted
   individuals^W^Wcreative sysadmins for providing source material for
   this memo, to Andrew Lloyd-Webber, Cameron Mackintosh, and a cast of
   thousands (particularly including Terrance Mann) who drew my
   attention to the necessity, and of course, to Thomas Stearns Eliot,
   for making this all necessary.

References

   [1]  Libes, D., "Choosing a Name for Your Computer", Communications
        of the ACM, Vol. 32, No. 11, Pg. 1289, November 1989.

   [2]  Lottor, M. et al., "Domain Name Survey, Jan 1997",
        namedroppers@internic.net

   [3]  Wong, M. et. al., "Cool Hostnames",
        http://www.seas.upenn.edu/~mengwong/coolhosts.html

   [4]  Stearns, TS, _Old Possum's Book of Practical Cats_.








Ashworth                     Informational                      [Page 2]

RFC 2100                  The Naming of Hosts               1 April 1997


Security Considerations

   Security issues are not discussed in this memo.

   Particularly the cardiac security of certain famous poets.

Author's Address

   Jay R. Ashworth
   Ashworth & Associates
   Advanced Technology Consulting
   St. Petersburg FL 33709-4819

   Phone: +1 813 790 7592

   EMail:  jra@scfn.thpl.lib.fl.us



































Ashworth                     Informational                      [Page 3]

一覧

 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 

スポンサーリンク

CHR関数 ASCIIコードから文字に変換する

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

上に戻る