[address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Oct 13 11:58:48 CEST 2014
Hi Daniel, Some comments to clarify the discussion: > I totally disagree. In other hand, I'll make harder the v6 requeriment to get the /22. For what purpose? When making statements like this please explain what your underlying intentions are. We make policy for a purpose and if the purpose isn't clear then it is impossible to have a reasonable discussion about the solution space. > How? Making the policy not only "to have" the v6 alloc, I'll require also having it with route6 and published in BGP. RIPEstat is a good tool to check if the v6 is publicly visible. IP addresses allocated/assigned do not have to be routed on 'the global internet' (for whatever value of 'global internet' you pick). Routing requirements were explicitly removed from the IPv6 policy with https://www.ripe.net/ripe/policies/proposals/2009-06. Cheers, Sander
- Previous message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
- Next message (by thread): [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]