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/address-policy-wg@ripe.net/
[address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Previous message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Next message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Oct 7 01:18:15 CEST 2013
Hi, > RIPE NCC reserves a /29 for every /32 allocation, right? No, they don't. It used to be like that a long time ago, but these days it is just sparse allocation. The change was announced at RIPE-61 (http://ripe61.ripe.net/presentations/331-Update_RIPE_NCC_R61.pdf) which was in November 2010. However: the current policy for IPv6 PI assignments specifies "Assignments will be made from a separate 'designated block' to facilitate filtering practices.". Is that worth keeping? Cheers, Sander
- Previous message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
- Next message (by thread): [address-policy-wg] 2013-06 New Policy Proposal (PA/PI Unification IPv6 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]