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] address-policy-wg
- Previous message (by thread): [address-policy-wg] R: address-policy-wg
- Next message (by thread): [address-policy-wg] New on RIPE Labs: RIPE NCC Membership Statistics Q3 2015
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Oct 30 15:42:12 CET 2015
Hi, > Who writes some sentence, surely knows that today IPv6 addressing in Italy is used only by Facebook, Google, Youtube and some other else, but most of sites are only reachable by IPv4. > So, please, let me know how to migrate all our customers to IPv6 giving them access to the whole internet, as today, and we’ll make it. It's off-topic on this list, but just to give you a sample of the solutions you might deploy: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers https://tools.ietf.org/html/rfc6146 464XLAT: Combination of Stateful and Stateless Translation https://tools.ietf.org/html/rfc6877 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion https://tools.ietf.org/html/rfc6333 Mapping of Address and Port with Encapsulation (MAP-E) https://tools.ietf.org/html/rfc7597 Mapping of Address and Port using Translation (MAP-T) https://tools.ietf.org/html/rfc7599 An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition https://tools.ietf.org/html/rfc6264 As you can see you are not the only one who needs to run a network with a shortage of IPv4 addresses, and solutions have been designed. There are some well-known examples that use these technologies. T-Mobile runs NAT64+464XLAT, UPC runs DS-Lite etc. Implementations are available on the market. Running an ISP on just IPv4 isn't possible anymore (basic math) so you'll have to learn to deal with that, just like everybody else. This mailing list is not the place to argue that point. It is clear that you need *some* IPv4 to be able to talk to others that only talk IPv4, which is why we have the final-/8 policy. Being able to run/expand a network (especially ISP networks) completely on public IPv4 without NAT and/or IPv6 has ended years ago, and no policy change is ever going to be able to change that. People that are still in denial and want to discuss how to run their networks on IPv4-only without having anything to do with IPv6 should start an IPv4 working group... Cheers, Sander
- Previous message (by thread): [address-policy-wg] R: address-policy-wg
- Next message (by thread): [address-policy-wg] New on RIPE Labs: RIPE NCC Membership Statistics Q3 2015
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]