From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: dlstevens@us.ibm.com
Cc: davem@davemloft.net, netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: IPV6 RFC3542 compliance [PATCH]
Date: Tue, 07 Jun 2005 14:19:22 +0900 (JST) [thread overview]
Message-ID: <20050607.141922.65612976.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <OF68DFE8BB.D1DDCA2A-ON88257018.0068C3C7-88257018.006CCE31@us.ibm.com>
In article <OF68DFE8BB.D1DDCA2A-ON88257018.0068C3C7-88257018.006CCE31@us.ibm.com> (at Mon, 6 Jun 2005 13:48:26 -0600), David Stevens <dlstevens@us.ibm.com> says:
> I've been looking at RFC 3542 (Advanced Sockets API) compliance,
> and found the following:
>
> ("x" is one of {PKTINFO, HOPLIMIT, RTHDR, DSTOPTS, TCLASS })
Well, this breaks API.
Please rename old options, say:
IPV6_PKTINFO => IPV6_2292PKTINFO
IPV6_HOPLIMIT => IPV6_2292HOPLIMI
IPV6_RTHDR => IPV6_2292RTHDR
IPV6_DSTOPTS => IPV6_2292DSTOPTS
And, add allocate new values for 2292bis options like:
#define IPV6_RECVPKTINFO 48 /* RFC2292bis */
#define IPV6_PKTINFO 49 /* RFC2292bis */
#define IPV6_RECVHOPLIMIT 50 /* RFC2292bis */
#define IPV6_HOPLIMIT 51 /* RFC2292bis */
#define IPV6_RECVRTHDR 52 /* RFC2292bis */
#define IPV6_RTHDR 53 /* RFC2292bis */
#define IPV6_RECVHOPOPTS 54 /* RFC2292bis */
#define IPV6_HOPOPTS 55 /* RFC2292bis */
#define IPV6_RECVDSTOPTS 56 /* RFC2292bis */
#define IPV6_DSTOPTS 57 /* RFC2292bis */
#define IPV6_RECVRTHDRDSTOPTS 58 /* RFC2292bis */
#define IPV6_RTHDRDSTOPTS 59 /* RFC2292bis */
(This is what KAME people did, and I believe that it is the best way to keep
backward compatibility.)
--
YOSHIFUJI Hideaki @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG-FP : 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2005-06-07 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 19:48 IPV6 RFC3542 compliance [PATCH] David Stevens
2005-06-07 5:19 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2005-06-07 6:25 ` David Stevens
2005-06-07 6:33 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07 6:50 ` David Stevens
2005-06-07 7:05 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07 7:40 ` David Stevens
2005-06-07 7:47 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07 7:55 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-07 8:04 ` David Stevens
2005-06-07 8:01 ` David Stevens
2005-06-07 8:14 ` YOSHIFUJI Hideaki / 吉藤英明
2005-06-08 18:49 ` David Stevens
2005-06-07 6:35 ` David Stevens
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=20050607.141922.65612976.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@oss.sgi.com \
/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