From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port Number (IPV6_V6ONLY Support)
Date: Thu, 03 Oct 2002 01:29:04 -0700 (PDT) [thread overview]
Message-ID: <20021003.012904.75241727.davem@redhat.com> (raw)
In-Reply-To: <20021003.121350.119660876.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Thu, 03 Oct 2002 12:13:50 +0900 (JST)
Linux IPv6 stack provides the ability for IPv6 applications to
interoperate with IPv4 applications. Port space for TCP (or UDP) is
shared by IPv6 and IPv4. This conforms to RFC2553.
However, some kind of applications may want to restrict their use of
an IPv6 socket to IPv6 communication only. IPV6_V6ONLY socket option is
defined for such applications in RFC2553bis, which is successor of RFC2553.
I really wish BSD socket features did not get standardized
in RFC's, we must live with their mistakes.
For example, this IPV6_V6ONLY socket option is flawed. What we
really need is a generic socket option which says "my family only"
There is nothing ipv6 specific about such a socket attribute.
So please, create instead "SO_ONEFAMILY" or similar generic
socket option.
I still need to review the rest of the patch for functional
correctness. This is probably the most complex area of the
socket identity code in TCP/UDP :-)
next prev parent reply other threads:[~2002-10-03 8:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 3:13 [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port Number (IPV6_V6ONLY Support) YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 3:53 ` acme
2002-10-03 3:55 ` acme
2002-10-03 7:00 ` Pekka Savola
2002-10-03 8:29 ` David S. Miller [this message]
2002-10-03 8:55 ` Brad Hards
2002-10-03 8:58 ` David S. Miller
2002-10-03 13:06 ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same kuznet
2002-10-03 13:02 ` David S. Miller
2002-10-03 13:18 ` Pekka Savola
2002-10-03 13:13 ` David S. Miller
2002-10-03 13:01 ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port kuznet
2002-10-03 14:15 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 14:10 ` David S. Miller
2002-10-03 15:06 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:04 ` David S. Miller
2002-10-03 15:19 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:52 ` kuznet
2002-10-23 7:24 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 7:23 ` David S. Miller
2002-10-23 7:58 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 8:06 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 8:02 ` David S. Miller
2002-10-23 7:36 ` Pekka Savola
2002-10-23 10:01 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 10:15 ` Pekka Savola
2002-10-23 10:12 ` David S. Miller
2002-10-24 16:24 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both kuznet
2002-10-25 7:46 ` Pekka Savola
2002-10-23 15:53 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) Kyle C Quest
2002-10-23 16:06 ` Pekka Savola
2002-10-23 16:09 ` Kyle C Quest
2002-10-24 10:24 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 3:53 [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port Number (IPV6_V6ONLY Support) acme
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021003.012904.75241727.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).