Re: IPV6 RFC3542 compliance [PATCH]

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

In article 
<OF2D6866A4.ACD65B11-ON88257019.0027E8B0-88257019.002A2862@xxxxxxxxxx> (at Tue, 
7 Jun 2005 00:40:28 -0700), David Stevens <dlstevens@xxxxxxxxxx> says:

> > We can still keep old binaries if we renumber.
> > This is important point.
> > e.g. people, including myself, can keep using old binaries on new 
> kernels.
:
> But old binaries won't work with just that change
> (and making them work is independent of changing
> the numbers).
> 
> For example, old binary:
> 
> IPV6_RTHDR is value 5
> 
> it does:
>         on=1; setsockopt(s, SOL_IPV6, 5, &on);
> and later a recvmsg() where it looks for
> cmsg_type == IPV6_RTHDR (5).
> 
> In the new API, the equivalent:
> 
> IPV6_RTHDR 728
> IPV6_RECVRTHDR 729
> 
>         old binary calls with "5", which you want
> to work, but returns cmsg_type "728" (app doesn't
> find a "5").

No, kernel should send 5, if application use old API, of course.

--yoshfuji