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] IPv6 PI for HOSTING
- Previous message (by thread): [address-policy-wg] IPv6 PI for HOSTING
- Next message (by thread): [address-policy-wg] IPv6 PI for HOSTING
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Fri Dec 25 00:09:15 CET 2009
Max Tulyev wrote: > The problem is IPv6 Internet is still useless. It's not a problem. Use port restricted IPv4. > If it will be when IPv4 > runs out, the world will NOT be moved to IPv6, but will use NATs, trade > the rest of IPv4 blocks and so on. IPv6 will be ignored as working, but > useless thing. IPv6 will be ignored, because IPv6 is, technically, useless, which has nothing to do with IPv6 address allocation policy. Because IPv4 NAT can be fully transparent end to end, it's fine to use port restricted IPv4 with NAT. > I repeat my lovely phrase: If a majority (a half) of web resources will > be reachable via IPv6 when IPv4 will be finished, then MAY BE will be > the migration to IPv6. If not - then it fails. It's impossible because attempts of optional headers, path MTU discovery, stateless autoconfiguration, aggressive introduction of multicast etc. to make IPv6 better than IPv4 have totally failed only to make IPv6 and its operation a lot more complex and a lot less consistent than IPv4. Masataka Ohta
- Previous message (by thread): [address-policy-wg] IPv6 PI for HOSTING
- Next message (by thread): [address-policy-wg] IPv6 PI for HOSTING
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]