[92362] in North American Network Operators' Group
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
daemon@ATHENA.MIT.EDU (Bjoern A. Zeeb)
Fri Sep 15 17:42:15 2006
Date: Fri, 15 Sep 2006 21:39:20 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Gert Doering <gert@space.net>
Cc: nanog@merit.edu, IPv6 Ops list <ipv6-ops@lists.cluenet.de>
In-Reply-To: <20060915162530.GC20002@Space.Net>
Errors-To: owner-nanog@merit.edu
On Fri, 15 Sep 2006, Gert Doering wrote:
Hi,
> On Thu, Sep 14, 2006 at 12:05:16AM +0200, Jeroen Massar wrote:
>> It's update your IPv6 filters time:
>>
>> http://www.arin.net/reference/ip_blocks.html
>>
>> 8<-----------------------------------------
>> IPv6 Assignment Blocks CIDR Block
>> 2620:0000:/23
>> ----------------------------------------->8
>> Expect blocks in between /40 and /48 there.
>
> Filter recommendation document updated.
Could you also add blocks like 2800::/23 from LACNIC issued
Nov 2005 by IANA?
> Does the policy really permit /40.../47 assignments?
The only thing I found so far is [1] which really only
defines the <=48 end. It's talking about _at least_ a /44
reserved for future growth and it says "When possible, [subsequent]
assignments will be made from an adjacent address block.".
Considering what we see with v4 PI (direct assignments) today
and had seen with /8 PA and an undefined ("open") other end in
ARIN policy I wouldn't trust any >=40 rule being the maximum
for this block.
I have so far decided to use (also see [2]):
! + ARIN PI (chose whatever one you think is worse)
!ipv6 prefix-list ipv6-ebgp-strict seq 135 deny 2620::/23 le 128
ipv6 prefix-list ipv6-ebgp-strict seq 135 permit 2620::/23 ge 32 le 48
Happy weekend.
/bz
References:
[1] http://www.arin.net/policy/nrpm.html#six582
6.5.8. Direct assignments from ARIN to end-user organizations
6.5.8.2. Initial assignment size
6.5.8.3. Subsequent assignment size
[2] http://sources.zabbadoz.net/ipv6/v6-prefix-filter-20060913-public.cfg
--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
