[178303] in North American Network Operators' Group
Re: v6 deagg
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Tue Feb 24 17:32:10 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <0E7AFD3D-28E2-4D72-9661-5DFB099ACB28@delong.com>
Date: Tue, 24 Feb 2015 17:32:08 -0500
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: North American Network Operators' Group <nanog@nanog.org>,
manning bill <bmanning@isi.edu>
Errors-To: nanog-bounces@nanog.org
On Tue, Feb 24, 2015 at 12:27 PM, Owen DeLong <owen@delong.com> wrote:
>
>> On Feb 19, 2015, at 21:25 , Christopher Morrow <morrowc.lists@gmail.com> wrote:
>>
>> On Thu, Feb 19, 2015 at 10:16 PM, manning bill <bmanning@isi.edu> wrote:
>>> and then there are the loons who will locally push /64 or longer, some of which may leak.
>>>
>>
>> 2001:2b8:46:bbbb::/64
>> ... a fairly extensive list actually....
>>
>>> show route table inet6.0 | grep ^2 | except /4[876543210] | except /3 | except /2 | count
>> Count: 297 lines
>>
>> Some are likely my local network's interfaces (so skip ~50 or so? to
>> be generous) and some might be my provider's customers? (but they
>> shouldn't send me shorter than a /48, right?)
>>
>> -chris
>> (note on another observation point I don't see this sort of thing so
>> perhaps it's just one upstream in a collection... I'll ask them
>> seperately)
>
> Your regular expression will not only count /49 and longer, it will also count /19 and shorter.
>
> In my routing table, there are at least some examples of such routes.
yup, not very many and I think not enough to matter over all, give
then actual point was I see many smaller (longer?) than /48 in the
table.
