[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dccp] Re: dccp_service in sockaddr_dccp{}



On Fri, 2005-09-09 at 12:13 +0900, ext YOSHIFUJI Hideaki / åèèæ
wrote:
> I do think sockopt is much better from the point of view of socket API.
> 
>  1. sockaddr_xxx{} and AF_xxx make pair.
>     e.g. sockaddr_in{} is used for AF_INET
>          sockaddr_in6{} is used for AF_INET6
>     Type of sockaddr shall be determined by the sa_family member
>     in sockaddr{} (POSIX).

I tend to share this concern. A separate sockaddr for DCCP doubles the
number of sockaddr combinations that need to be supported. At least both
sockaddr_in_dccp and sockaddr_in6_dccp would be needed. Furthermore, the
shim-layer based schemes like HIP (if they ever materialize) would
possibly require yet another address family.

- Pasi

Attachment: signature.asc
Description: This is a digitally signed message part