[132323] in North American Network Operators' Group
Re: Introducing draft-denog-v6ops-addresspartnaming
daemon@ATHENA.MIT.EDU (Joel Jaeggli)
Sat Nov 20 18:05:55 2010
Date: Sat, 20 Nov 2010 15:05:30 -0800
From: Joel Jaeggli <joelja@bogus.com>
To: Owen DeLong <owen@delong.com>
In-Reply-To: <B10AAF98-90FF-480F-9BA4-6654EB176205@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 11/20/10 2:20 PM, Owen DeLong wrote:
>
> On Nov 20, 2010, at 9:12 AM, William Herrin wrote:
>
>> On Sat, Nov 20, 2010 at 5:05 AM, Richard Hartmann
>> <richih.mailinglist@gmail.com> wrote:
>>> On Fri, Nov 19, 2010 at 23:52, William Herrin <bill@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?
>
Since I've been reading old drafts recently I think we can thank mike
o'dell for the term "routing goop". the problem of course is you can't
distinguish which part of the routing goop is signficant (to the humans)
unless you have an apriori mapping. otherwise all you have is some goop
and a mask which together are a route.
