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 ]

Elvis Velea elvis at velea.eu
Mon Oct 7 12:24:10 CEST 2013

Hi Andrea,

On 10/7/13 12:21 PM, Andrea Cima wrote:
[...]
> The RIPE NCC reserves three bits for each allocation. This is due to
> historical reasons as, according to policy, the RIPE NCC had to reserve
> a /29 for each LIR. /32s (and their reservations) are made using the
> sparse allocation method.
[...]
>
> We currently reserve two bits for IPv6 assignments, which is done on the
> basis of availability. According to the policy: "When possible, these
> further assignments will be made from an adjacent address block."
>
> http://www.ripe.net/ripe/docs/ripe-589#IPv6_PI_Assignments

Thanks for clarifying these procedures.

>
> Best regards,
> Andrea Cima
> RIPE NCC
>

Regards,
Elvis

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 ]

[ address-policy-wg Archives ]