>> 	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.

itojun