IPv4 address length technical design
george.herbert at gmail.com
Sat Oct 6 18:06:41 UTC 2012
As I said earlier, names' structure does not map to network or physical location structure.
DNS is who; IP is where. Both are reasonably efficient now as separate entities. Combining them will wreck one. You're choosing to wreck routing (where), which to backbone people sounds frankly stark raving mad.
If you aren't willing to consider where / routing as a problem of equal importance ( not as end-user visible perhaps, but ultimately as important ), then you're just pissing around and not being serious about exploring future options.
George William Herbert
Sent from my iPhone
On Oct 6, 2012, at 10:47 AM, Barry Shein <bzs at world.std.com> wrote:
> It's occured to you that FQDNs contain some structured information,
> On October 5, 2012 at 21:47 bill at herrin.us (William Herrin) wrote:
>> On Fri, Oct 5, 2012 at 8:25 PM, Barry Shein <bzs at world.std.com> wrote:
>>> 5. Bits is bits.
>>> I don't know how to say that more clearly.
>> Hi Barry,
>> Bits is bits and atoms is atoms so lets swap all the iron for helium
>> and see how that works out for us.
>> You can say "bits as bits" as clearly as you like but however you say
>> it you'll be wrong. Bits are defined by the semantics of their use.
>> Any equality or inequality between one bit and another, and in fact
>> whether they can be meaningfully compared at all, is found in those
>> Bits ain't just bits. Bits are information *in context.* Change the
>> context, change the bits.
>> Bill Herrin
>> William D. Herrin ................ herrin at dirtside.com bill at herrin.us
>> 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
>> Falls Church, VA 22042-3004
More information about the NANOG