| 1 |
<pre>Network Working Group J. Ashworth |
| 2 |
Request for Comments: 2100 Ashworth & Associates |
| 3 |
Category: Informational 1 April 1997 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">The Naming of Hosts</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Introduction |
| 15 |
|
| 16 |
This RFC is a commentary on the difficulty of deciding upon an |
| 17 |
acceptably distinctive hostname for one's computer, a problem which |
| 18 |
grows in direct proportion to the logarithmically increasing size of |
| 19 |
the Internet. |
| 20 |
|
| 21 |
Distribution of this memo is unlimited. |
| 22 |
|
| 23 |
Except to TS Eliot. |
| 24 |
|
| 25 |
And, for that matter, to David Addison, who hates iambic pentameter. |
| 26 |
|
| 27 |
Poetry |
| 28 |
|
| 29 |
The Naming of Hosts is a difficult matter, |
| 30 |
It isn't just one of your holiday games; |
| 31 |
You may think at first I'm as mad as a hatter |
| 32 |
When I tell you, a host must have THREE DIFFERENT NAMES. |
| 33 |
|
| 34 |
First of all, there's the name that the users use daily, |
| 35 |
Such as venus, athena, and cisco, and ames, |
| 36 |
Such as titan or sirius, hobbes or europa-- |
| 37 |
All of them sensible everyday names. |
| 38 |
|
| 39 |
There are fancier names if you think they sound sweeter, |
| 40 |
Some for the web pages, some for the flames: |
| 41 |
Such as mercury, phoenix, orion, and charon-- |
| 42 |
But all of them sensible everyday names. |
| 43 |
|
| 44 |
But I tell you, a host needs a name that's particular, |
| 45 |
A name that's peculiar, and more dignified, |
| 46 |
Else how can it keep its home page perpendicular, |
| 47 |
And spread out its data, send pages world wide? |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Ashworth Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2100">RFC 2100</a> The Naming of Hosts 1 April 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
Of names of this kind, I can give you a quorum, |
| 58 |
Like lothlorien, pothole, or kobyashi-maru, |
| 59 |
Such as pearly-gates.vatican, or else diplomatic- |
| 60 |
Names that never belong to more than one host. |
| 61 |
|
| 62 |
But above and beyond there's still one name left over, |
| 63 |
And that is the name that you never will guess; |
| 64 |
The name that no human research can discover-- |
| 65 |
But THE NAMESERVER KNOWS, and will us'ually confess. |
| 66 |
|
| 67 |
When you notice a client in rapt meditation, |
| 68 |
The reason, I tell you, is always the same: |
| 69 |
The code is engaged in a deep consultation |
| 70 |
On the address, the address, the address of its name: |
| 71 |
|
| 72 |
It's ineffable, |
| 73 |
effable, |
| 74 |
Effanineffable, |
| 75 |
Deep and inscrutable, |
| 76 |
singular |
| 77 |
Name. |
| 78 |
|
| 79 |
Credits |
| 80 |
|
| 81 |
Thanks to Don Libes, Mark Lottor, and a host of twisted |
| 82 |
individuals^W^Wcreative sysadmins for providing source material for |
| 83 |
this memo, to Andrew Lloyd-Webber, Cameron Mackintosh, and a cast of |
| 84 |
thousands (particularly including Terrance Mann) who drew my |
| 85 |
attention to the necessity, and of course, to Thomas Stearns Eliot, |
| 86 |
for making this all necessary. |
| 87 |
|
| 88 |
References |
| 89 |
|
| 90 |
[<a id="ref-1">1</a>] Libes, D., "Choosing a Name for Your Computer", Communications |
| 91 |
of the ACM, Vol. 32, No. 11, Pg. 1289, November 1989. |
| 92 |
|
| 93 |
[<a id="ref-2">2</a>] Lottor, M. et al., "Domain Name Survey, Jan 1997", |
| 94 |
[email protected] |
| 95 |
|
| 96 |
[<a id="ref-3">3</a>] Wong, M. et. al., "Cool Hostnames", |
| 97 |
<a href="http://www.seas.upenn.edu/~mengwong/coolhosts.html">http://www.seas.upenn.edu/~mengwong/coolhosts.html</a> |
| 98 |
|
| 99 |
[<a id="ref-4">4</a>] Stearns, TS, _Old Possum's Book of Practical Cats_. |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Ashworth Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2100">RFC 2100</a> The Naming of Hosts 1 April 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
Security Considerations |
| 114 |
|
| 115 |
Security issues are not discussed in this memo. |
| 116 |
|
| 117 |
Particularly the cardiac security of certain famous poets. |
| 118 |
|
| 119 |
Author's Address |
| 120 |
|
| 121 |
Jay R. Ashworth |
| 122 |
Ashworth & Associates |
| 123 |
Advanced Technology Consulting |
| 124 |
St. Petersburg FL 33709-4819 |
| 125 |
|
| 126 |
Phone: +1 813 790 7592 |
| 127 |
|
| 128 |
EMail: [email protected] |
| 129 |
|
| 130 |
|
| 131 |
|
| 132 |
|
| 133 |
|
| 134 |
|
| 135 |
|
| 136 |
|
| 137 |
|
| 138 |
|
| 139 |
|
| 140 |
|
| 141 |
|
| 142 |
|
| 143 |
|
| 144 |
|
| 145 |
|
| 146 |
|
| 147 |
|
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
Ashworth Informational [Page 3] |
| 165 |
</pre> |