Jun-ichiro itojun Hagino wrote: > > > And define NI_TCP, which is also the default if none is specified? > > I'd also propose deprecating the default, to get everyone in the habit > > of specifying something. > > deprecating the default would break source-code level backward > compatibility (code written for RFC2553 would have problem) so we > need to keep NI_TCP to 0 and make it a default, unfortunately. > if you have any solution please let me know.
Techically, deprecating would break nothing, since it changes the status to "supported but discouraged". The goal is to get programmers into the habit of specifying something, not to actually remove the functionality. The intent is not to actually take the 2nd step of removing the deprecation, just discourage the usage. -- Andrew White -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
