Title : IP Version 6 Addressing Architecture
Author(s) : R. Hinden, S. Deering
Filename : draft-ietf-ipv6-addr-arch-v4-01.txt
Two high-level comments:
1) The use of compatible addresses does not belong to the revised addr arch specification, especially if we want to move it to Draft Standard. I suggest removing it right now to avoid fuss in the future.
2.5.5 IPv6 Addresses with Embedded IPv4 Addresses
The IPv6 transition mechanisms [TRAN] include a technique for hosts and routers to dynamically tunnel IPv6 packets over IPv4 routing infrastructure. IPv6 nodes that use this technique are assigned special IPv6 unicast addresses that carry a global IPv4 address in the low-order 32 bits. This type of address is termed an "IPv4-compatible IPv6 address" and has the format:
| 80 bits | 16 | 32 bits | +--------------------------------------+--------------------------+ |0000..............................0000|0000| IPv4 address | +--------------------------------------+----+---------------------+
Note: The IPv4 address used in the "IPv4-compatible IPv6 address" must be a globally-unique IPv4 unicast address.
2) Site local deprecation document is Proposed Standard (it should have been published as BCP, sigh..), so it cannot be a normative reference if we want to move this to Draft Standard (unless SLDEP is also moved to DS). Luckily enough, I think this only provides additional information, so it should be OK to move it over to Informative references.
5.1 Normative References
[SLDEP] C. Huitema, B. Carpenter, "Deprecating Site Local
Addresses", RFC3879, September 2004.-- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
