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]/
[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 ]
Tore Anderson
tore at fud.no
Mon Oct 7 11:40:57 CEST 2013
* Elvis Velea > On 10/7/13 1:18 AM, Sander Steffann wrote: >> 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. > > I think they still reserve 3 bits, even with the sparse allocation > algorithm. This is easy to find out, since delegations are public data. AFAICT: - Allocations (at least up to and including /29s): reserve a /26 (for some reason the allocated /32 isn't the first one in the /26) - Assignments (at least /48s): reserve a /46 $ grep 'ipv6.*201310' delegated-ripencc-extended-latest ripencc|AT|ipv6|2a00:f020::|32|20131001|allocated ripencc|SE|ipv6|2a00:f060::|32|20131001|allocated ripencc|NO|ipv6|2a00:f0a0::|32|20131001|allocated ripencc|QA|ipv6|2a00:f0e0::|32|20131001|allocated ripencc|AT|ipv6|2a00:f120::|32|20131002|allocated ripencc|RU|ipv6|2a00:f160::|32|20131002|allocated ripencc|BE|ipv6|2a00:f1a0::|32|20131002|allocated ripencc|SE|ipv6|2a00:f1e0::|32|20131002|allocated ripencc|ME|ipv6|2a00:f220::|32|20131002|allocated ripencc|AZ|ipv6|2a00:f260::|32|20131003|allocated ripencc|RU|ipv6|2a00:f2a0::|32|20131003|allocated ripencc|GE|ipv6|2a00:f2e0::|32|20131003|allocated ripencc|NL|ipv6|2a00:f320::|32|20131003|allocated ripencc|NL|ipv6|2a00:f360::|32|20131003|allocated ripencc|IT|ipv6|2a00:f3a0::|32|20131004|allocated ripencc|RU|ipv6|2a00:f3e0::|32|20131004|allocated ripencc|DE|ipv6|2a00:f420::|32|20131004|allocated ripencc|RU|ipv6|2a00:f460::|32|20131004|allocated ripencc|GG|ipv6|2a04:6b40::|29|20131001|allocated ripencc|NO|ipv6|2a04:6b80::|29|20131001|allocated ripencc|NL|ipv6|2a04:6bc0::|29|20131002|allocated ripencc|ES|ipv6|2a04:6c00::|29|20131002|allocated ripencc|BE|ipv6|2a04:6c40::|29|20131003|allocated ripencc|RO|ipv6|2a04:6c80::|29|20131003|allocated ripencc|SE|ipv6|2a04:6cc0::|29|20131003|allocated ripencc|SE|ipv6|2a04:6d00::|29|20131003|allocated ripencc|CH|ipv6|2a04:6d40::|29|20131004|allocated ripencc|PT|ipv6|2a04:6d80::|29|20131004|allocated ripencc|NL|ipv6|2a04:6dc0::|29|20131004|allocated ripencc|RU|ipv6|2001:67c:2be0::|48|20131001|assigned ripencc|PL|ipv6|2001:67c:2be4::|48|20131003|assigned ripencc|NL|ipv6|2001:67c:2be8::|48|20131004|assigned ripencc|PL|ipv6|2001:67c:2bec::|48|20131004|assigned Tore
- 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 ]