[address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yannis Nikolopoulos
dez at otenet.gr
Tue Jul 19 10:43:05 CEST 2011
Hello again, On 07/19/2011 10:56 AM, Jan Zorz @ go6.si wrote: > On 7/19/11 9:38 AM, Jasper Jans wrote: >> The RIPE currently reserves a /29 for every initial /32. >> So as long as there is a policy that allows expansion of the initial >> assignment based upon a sound network design there should not be >> any issue to bump it up to a bigger block. > Hi, > > As presented, discussed and suggested at RIPE62 in Amsterdam, we are > currently working on policy change proposal, that would rise the > minimum IPv6 allocation size to /29 and automatically made of use that > "reserved" /29 space for each legacy /32 allocation (that would almost > never be used otherwise). > would this mean that all LIRs that got an initial /32 will get "upgraded" to a /29 ? If not, it doesn't really solve the issue at hand. cheers, Yannis > Primary reason for that proposal was wasteful transition mechanisms > (like 6RD...), but this change also solves some of issues, rised in > this thread. > > Stay tuned :) > > Cheers, Jan Zorz > Go6 Slovenia >
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]