Re: IPV6 RFC3542 compliance [PATCH]

[YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>]

In article 
<OF68DFE8BB.D1DDCA2A-ON88257018.0068C3C7-88257018.006CCE31@xxxxxxxxxx> (at Mon, 
6 Jun 2005 13:48:26 -0600), David Stevens <dlstevens@xxxxxxxxxx> 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@xxxxxxxxxxxxxx>
GPG-FP  : 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA