[157143] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv4 address length technical design

daemon@ATHENA.MIT.EDU (Jay Ashworth)
Sun Oct 7 20:09:12 2012

Date: Sun, 7 Oct 2012 20:08:56 -0400 (EDT)
From: Jay Ashworth <jra@baylink.com>
To: NANOG <nanog@nanog.org>
In-Reply-To: <20592.31220.78712.550345@world.std.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

----- Original Message -----
> From: "Barry Shein" <bzs@world.std.com>

> Well, George, you can take a new idea and run with it a bit, or just
> resist it right from the start.
> 
> We can map from host names to ip addresses to routing actions, right?
> 
> So clearly they're not unrelated or independent variables. There's a
> smooth function from hostname->ipaddr->routing.

Ah.  *This* is where you fell off the horse. 

Nope; the first one isn't smooth; it's *completely arbitrary*.

The mapping is, in fact, DNS's raison d'etre.

The second one has a relatively smooth mapping *at any given point in time*,
but you can't fit a function to that; it is prone also to arbitrary changes 
over time.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274


home help back first fref pref prev next nref lref last post