This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Previous message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gunter Van de Velde (gvandeve)
gvandeve at cisco.com
Tue Jul 19 11:24:15 CEST 2011
Good :-) G/ -----Original Message----- From: ipv6-wg-admin at ripe.net [mailto:ipv6-wg-admin at ripe.net] On Behalf Of Jan Zorz @ go6.si Sent: 19 July 2011 09:57 To: ipv6-wg at ripe.net; address-policy-wg at ripe.net Subject: Re: [ipv6-wg] additional IPv6 allocation (ripe-512 issues) 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). 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): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
- Next message (by thread): [ipv6-wg] additional IPv6 allocation (ripe-512 issues)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]