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] Mandating NAT toward the final /8
- Previous message (by thread): [address-policy-wg] Mandating NAT toward the final /8
- Next message (by thread): [address-policy-wg] Mandating NAT toward the final /8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Fri Jul 17 10:06:18 CEST 2009
* Randy Bush: >>> Given that all currently available operating systems fully support IPv6, >> Nit: "Full support" is neither generally available nor necessary. >> IPv6 support levels are typically sufficient > > you're kidding, right? The joke is in RFC 4294 (sections 4.5.4 and 8 in particular). "Full support" of IPv6 requires conformance to RFC 4294, but some of its requirements are quite ridiculous, so real-world implementations typically chose saner defaults. Obviously, I think this is a good thing, but the result is a system which doesn't fully support IPv6 as specified. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [address-policy-wg] Mandating NAT toward the final /8
- Next message (by thread): [address-policy-wg] Mandating NAT toward the final /8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]