[address-policy-wg] 2016-04 Review Phase (IPv6 Sub-assignment Clarification)

Dear Sander and Jordi,

On 2018-01-19 11:57:38 CET, Sander Steffann wrote:
> Hi Jordi,
> 
> > 1) Policy text say: "... separate addresses (not prefixes) ...".
> > 2) Max proposal say: "... or anything alike where devices of non-members of the organisation would get assigned an IP out of the organisation’s prefix ..."
> > 3) Max proposal say: "... Explicitly allowing another entity to be provided with addresses from a subnet ..."
> > 4) Max proposal say: "... A subnet in the spirit of this policy is a prefix from the PI/PA assignment with a prefix length of /64 or longer ..."
> > 5) Max proposal say: "... or for housing/hosting for servers in data centres ..."
> > 6) IA say: "... There are cases where a /64 is needed per customer to provide a separate address ..."
> > 7) IA say: "... It is the RIPE NCCs understanding that assignments as described above are dynamic in nature, either by varying the prefix or interface identifier (IID) over time. Any permanent and static assignments of a prefix would still be considered a sub-assignment ..."
> > 8) IA say: "... by using single IPv6 addresses for End User devices and services ..."
> > 
> > [...]
> > 
> > 5 seem to indicate that this is acceptable in data centres, but 7 says permanent and static ... I don't see how a data centre can do temporary addresses?
> 
> Now that is indeed a contradiction that I agree with. Here the NCC's interpretation is more strict than what the policy says, and that should be corrected. Marco, can you look at this again from the NCC's perspective?
> 
> Cheers,
> Sander
> 

I'm happy to provide some clarification here.

If this policy change is accepted, it will be possible to connect a customer server to the IPv6 PI assignment holder's network, provided only a separate address is used. This is clearly specified in the proposed policy text.

Our reference to the dynamic provision of a prefix was referring to configuration mechanisms that are mainly used to provide Internet access to customers. The RIPE NCC's approach aims to support the intent of the proposal to allow IPv6 PI assignments for use cases such as (public) Wi-Fi networks but to discourage the use of IPv6 PI for permanent broadband services.

Kind regards,

Marco Schmidt
Policy Development Officer
RIPE NCC

Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum