Jun-ichiro itojun Hagino wrote: > based on v6ops interim meeting discussion, it seems that there are fair > amount of consensus that IPv4 mapped address on wire is harmful (causes > security drawbacks). > draft-itojun-v6ops-v4mapped-harmful-00.txt > > so, i would like to ask you to update draft-ietf-ipngwg-addr-arch-v3-10 > section 2.5.5, to: > - constrain use of IPv4 mapped address to IEEE Std 1003.1 (RFC2553) API, > and that API only. IPv4 mapped address must not appear on wire, > in any of IPv6 header fields, extension header fields, or payloads
I disagree. First off all, "must not" is way too strong of a requirement. If someone understands all the potential harmfull effects and is prepared to deal with them, then the addresses can be allowed. Secondly, I don't think that the addressing architecture should forbid the use of the address in an extension header. That is for the extension header to define. -vlad -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Vladislav Yasevich Tru64 UNIX - IPv6 Project Lead Hewlett Packard Tel: (603) 884-1079 Nashua, NH 03062 ZKO3-3/T07 -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
