itojun@iijlab.net wrote:

> >> 	IPv6 advanced socket API was revised (RFC2292 -> 3542).  there's no
> >> 	backward source compatilibility at all.  i'll work on migration
> >> 	to RFC3542.
> >> 	- binary backward compatibility will be provided (i.e.  old compiled
> >> 	  binary using RFC2292 should work).
> >> 	- source code compatibility to RFC2292 will NOT be provided
> >> 	- coming source code must use RFC3542, not 2292
> >
> >Have any other standards organizations published documents based on 
> >RFC2292?  If so, it would probably make sense to keep the old API 
> >around, as well.
> 
> 	we can't keep both of them, as they use the same #define symbols
> 	(with different behavior).  dunno if any other standards documents
> 	(like POSIX) has copy of RFC2292/3542 in them.

There is no mention of the numbers "2292" or "3542" in the SUSv3
documentation (which is pretty much POSIX plus extensions).  For
the record, here are the RFCs mentioned in SUSv3:

	791 
	819 
	822 
	919 
	920 
	921 
	922 
	1034
	1035
	1123
	1886
	2045
	2373
	2460

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD Support and Service:         http://www.wasabisystems.com/