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] working IPv6 requirement for last /22
- 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 ]
Jim Reid
jim at rfc1035.com
Mon Oct 13 19:19:29 CEST 2014
On 13 Oct 2014, at 16:46, Daniel Baeza (Red y Sistemas TVT) <d.baeza at tvt-datos.es> wrote: > If we want to migrate from v4 to v6, some drastic changes should be made. One of them, requiring the v6 to be publicly visible if you want to have the last /22. In your opinion. > That way we ensure that LIR/Network will have, 'at least', ipv6 working on the router. > Its sad we cant check deeper if clients/servers/etc is having v6 conectivity but at least we can check if v6 is public in bgp. This is just silly. An LIR could easily pass your "working IPv6" test without actually deploying or using IPv6 in their network for real. All this protocol policing would do is the equivalent of security theatre at an airport. People get a (bogus) feeling that Something Is Being Done which has little bearing on anything that actually matters. Few, if any, incentives have made a meaningful difference to IPv6 deployment to date. So I doubt the one you are advocating can succeed where other, better ones have failed. >>> 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. > > So please, tell me why someone will require/request public ip space if is not to be publicly routed on "the global internet". > And that is a real question since I saw that "IP addresses allocated/assigned do not have to be routed on 'the global internet" several times and cant understand why. One of the jobs of an RIR is to distribute globally unique IP addresses. It's up to the address holder to decide if they want to route those addresses or not, nobody else. The RIR doesn't get to decide that. FYI many organisations use globally unique addresses so that they do not have to undergo expensive renumbering if/when they sell off parts of their business or acquire another company or interconnect with other corporate nets that aren't directly connected to the Internet
- 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 ]