Introducing draft-denog-v6ops-addresspartnaming

[owen at delong.com (Owen DeLong)]

On Nov 20, 2010, at 9:12 AM, William Herrin wrote:

> On Sat, Nov 20, 2010 at 5:05 AM, Richard Hartmann
> <richih.mailinglist at gmail.com> wrote:
>> On Fri, Nov 19, 2010 at 23:52, William Herrin <bill at herrin.us> wrote:
>> 
>>> I thought about that. Have a "one colon rule" that IPv6 addresses in
>>> hexidecimal format have to include at least one colon somewhere. The
>>> regex which picks that token out versus the other possibilities is
>>> easy enough to write and so is the human rule: "Oh, it's got
>>> hexidecimal digits and a colon in it. IPv6 address."
>> 
>> this would
>> still make it hard for humans to detect an IPv6 address at a glance,
>> makes it impossible to quickly pick out any sections that are more
>> relevant at the moment
> 
> Which is why you wouldn't conventionally remove the colons even though
> the format would allow it. You might, however, move the colons to
> highlight the delineations relevant to a particular address rather
> than the meaningless two-byte separation.
> 
How do you propose to get the router to regurgitate this?

> For example:
> 
> 260:abcde:123456:98::1
> 
> 260 - IANA to ARIN, a /12
> abcde - ARIN to ISP, a /32
> 123456 - ISP to customer, a /56
> 98 - customer subnet
> ::1 - LAN address
> 
> fd:1234567890:abcd::1
> 
> fd - ULA space
> 1234567890 - ULA global ID
> abcd - user subnet
> ::1 - LAN address
>