Re: [multipathtcp] Multipath Address Family

[Pasi Sarolahti <[e-mail]>]

On Nov 24, 2009, at 2:20 AM, Olivier Bonaventure wrote:

> This could be interesting, but if we change de socket API, why don't  
> we
> define a new structure that can handle DNS names in addition to IPv4  
> and
> IPv6 addresses. This would allow some applications to simply call
> connect with a DNS name and let the transport protocol figure out
> whether single path IPv4, single path IPv6, multipath whatever ...
> should be used to reach this DNS name.

I agree that connecting by names would eventually be the right way to  
go for Internet protocols, but am not sure if that fits within the  
authority of this WG anymore. It may be something that needs to be  
discussed by a wider community. My proposal was less ambitious and  
more short-sighted: fix the shortcoming in the API that claims the  
socket is using only one address when it is in fact using many.

Another question is that even if we had an connect-by-name API, would  
we still need to be able express which address(es) are bound to the  
socket in the API?

- Pasi