SCTP API should be done in that spec and be congruent to 3493 and new addendum APIs which we need for getnameinfo. I believe Jack McCann is contacting Itojun to work on addendum API spec for getnameinfo. /jim
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Jun-ichiro itojun Hagino > Sent: Monday, December 15, 2003 4:28 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: getnameinfo and various protocol types > > > > > Actualy, RFC2960 explictily states that "All current TCP > ports shall be > > > automatically reserved in the SCTP port address space." > in the IANA > > > considerations section. > > > > That was what I remebered. If this indeed means that there will not > > be any conflicting usage in the future (which the above text doesn't > > explicitly say) then I think we at least don't have the problem > > of getservbyport() returning different results for SCTP and TCP. > > > > Don't know how significant the problem is that a given port > (e.g., 80) > > might not be defined for SCTP, even though the port number is > > reserved, so that getservbyport() for SCTP should > > fail and getservbyport() for TCP would return a service string. > > (it may not be a IPv6 question, but unix API question) > > based on the RFC2960 statement, what should we do about > getservbyport > 2nd argument for SCTP connection, and/or /etc/services entries? > > my guess is that (1) we need to put "foo/sctp" explicitly into > /etc/services and (2) 2nd argument must be "sctp". > this is based on > observation from tcp/udp case (even if there's the same > service - such > as http - on the same port, we put separate entries > into /etc/services) > > itojun > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [EMAIL PROTECTED] > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
