[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00288) Re: USAGI IPv6 patches
- To: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Subject: (usagi-users 00288) Re: USAGI IPv6 patches
- From: itojun@xxxxxxxxxx
- Date: Fri, 16 Mar 2001 18:32:40 +0900
- Cc: usagi-users@xxxxxxxxxxxxxx, horape@xxxxxxxxxxxxxxxxxxxxxxxxxx, davem@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, bam@xxxxxxxxxx, pekkas@xxxxxxxxxx, debian-ipv6@xxxxxxxxxxxxxxxx
- In-reply-to: yoshfuji's message of Fri, 16 Mar 2001 18:29:06 JST. <20010316182906T.yoshfuji@linux-ipv6.org>
- List-subscribe: <mailto:usagi-users-ctl@linux-ipv6.org?body=subscribe>
- Reply-to: usagi-users@xxxxxxxxxxxxxx
- Sender: itojun@xxxxxxxxxx
>IMHO, we should enable ipv4-mapped address support by default
>for RFC compliance. And bind(2) with both of ipv4 and ipv6
>should be accepted if IPV6_V6ONLY has been set to ipv6 socket
>for compatibility with application already, wildly being used
>on Linux Systems.
if I were you I'd propose to drop RFC conformance and disable IPv4
mapped address by default, and have IPV6_V6ONLY socket option for
re-enabling it (= kame/netbsd behavior). when default bevhavior is
on insecure side I get worried.
another issue is bind(2) ordering and conflict table... :-P
>I'd like to talk about this issue with itojun, jinmei and others.
>In IETF?
of course. i heard that you will have a linux-usagi unofficial
meeting at th venue, i'll try to show up there.
itojun