Re: about draft-ietf-mobike-protocol-01.txt (issue 40)

 

> In your previous mail you wrote:
> 
>    >=> what is the real difference between MOBIKE multihoming support
>    >and IKEv2 multihoming support, and, more important, is this difference
>    >enough?
> 
>    My understanding of this difference is that in our current
>    proposal, the peers can register their alternative addresses
>    and failover to the other addresses if there's a connectivity
>    problem in the currently used address. (I don't think you
>    can do this in basic IKEv2, and personally, I think its a good
>    tradeoff in terms of functionality vs. effort and configuration.)
>    This is what I call the "failover" multihoming model.
>    
>    In the SCTP multihoming model we can choose more independently
>    where to send data, even if there's still the concept of a
>    primary (default) path.
>    
AFAIK (things may have changed recently in SCTP), you try a new
path only if the primary path fails. But in SCTP, each side can take
the decision independently unlike what we have in MOBIKE today.
But the main reason we did it this way in MOBIKE is to make it
work with NATs.  Also, In MOBIKE, all the IPsec SAs get
updated at the same time. There is no such thing in SCTP - each
side has its own notion of what address set they can use. 
Is there any other difference ?

>    In the load balancing multihoming model we can send even
>    the same stream over multiple paths, and still perform appropriate
>    load balancing, congestion avoidance, and acknowledgement
>    tasks.
>    
> => fine definition. My concern is the SCTP model and SCTP itself
> is in the charter, so according to its own charter the WG doesn't
> provide *yet* a good enough support to multihoming...
> 
I think we should be very careful about keeping the protocol simple.
When the charter was written, i don't think we understood all the details.
So, i don't think we should blindly follow the charter. 

-mohan

> Regards
> 
> [email protected]
> _______________________________________________
> Mobike mailing list
> [email protected]
> https://www.machshav.com/mailman/listinfo.cgi/mobike