![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I'm sorry, I can't resist:
"Before I can route your packets across this network,
first you must answer these questions three:"
"What is your source address?" "192.197.208.2"
"What is your destination address?" "204.152.167.20"
"What is your preferred solution "errr, I don't know that!"
to the DNS gTLD debate?" <Aaaaiieeeeee...!!!!>
Of course, the good news is someone will eventually answer
the question correctly (ie. "Do you want the technical
solution or the political solution?" "errr, I don't know
that..." <Aaaaiieeee...!!>
The knight beside you will then ask "How do you get to
know so much about DNS?" and you answer "you have to know
these things to be king..."
But I forgot, we reject kings, voting and any suggestions
that this debate is inappropriate for the ietf list.
Sadly, it *is* appropriate for today's ietf list. I only
wish I could really understand why we could build a
network of millions of hosts in such a short time and
without any central planning, yet can't get this
particular problem to the point I can really understand it.
Maybe because it's not really about DNS. That's my current
guess, anyways.
- peterd
--
------------------------------------------------------------------------------
Peter Deutsch, (514) 875-8611 (phone)
Bunyip Information Systems Inc. (514) 875-8134 (fax)
<peterd at bunyip.com> http://www.bunyip.com
"There is a lot to be said for building a model of a traction engine...
....when we want to admire the rhythmic poetry of swinging crank, flashing
rods, and smoothly rotating wheel, all we need to do is to raise steam with
the engine out of gear. Set her ticking over and watch the regular motion of
tumbling eccentrics, the constant round of dipping crank, the gleaming rods
as they beat their steady cycle."
- "Traction Engines Worth Modeling", W.J.Hughes
----------------------------------------------------------------------------
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.