> > now we have couple of new transport protocols coming, such as SCTP and
> > DCCP. how can we support service name lookup for those? i.e.
> > how can we tell getnameinfo(3) to use "sctp" or "dccp" for the 2nd
> > argument of getservbyport(3)?
> >
> > my proposal:
> > define NI_UDP as replacement of NI_DGRAM. deprecate NI_DGRAM (keep
> > it as an alias to NI_UDP is okay). define NI_SCTP, NI_DCCP and such.
> > these three are mutually exclusive, and if more than one is specified
> > it would cause EAI_FAIL.
>
> Since getnameinfo in theory should apply to non-Inet protocols
> I think it would be useful to try to abstract from NI_SCTP and NI_DCCP
> to something which captures the flavors/attributes of those transports.
> I don't know if NI_SEQPACKET is descriptive for SCTP and protocols
> of that flavor.
> I have no idea what a more abstract name would be descriptive for DCCP.
SCTP supports both SOCK_DGRAM, SOCK_STREAM as well as SOCK_SEQPACKET.
DCCP should be SOCK_DGRAM only, if i understand correctly.
therefore, there's no 1-by-1 mapping from SOCK_xx to IPPROTO_xx.
itojun
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
