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] 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
Thu Jul 16 16:26:32 CEST 2009
* Gert Doering: > 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, although usually not RFC-conforming (just like IPv4, where we've learnt not to enable certain protocol features). > and none of them support the modifications necessary to "help the NAT > gateway", I can't see how this would be a step forward. > > But this is far out of scope for RIPE APWG anyway Is it? RIPE could promote 6to4 adoption (similary to what is done for ENUM). Perhaps it's more of a topic for the IPv6 WG, but I don't think this is IETF or ICANN material. -- 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 ]