Re: Protocol Drafts - What's different.
"James Kempf" <[email protected]>
| Newsgroups | gmane.ietf.mobike |
|---|---|
| Message-ID | <[email protected]> |
> mobike-protocol, addrmgmt: Do not work with NATs.
>
> => and nothing will be done to change this if the WG still believes
> interoperability with NATs is not useful.
>
Is that really what the WG believes? Given that the base IKEv2 protocol
includes NAT support, it seems a little strange to exclude it in MOBIKE.
(Please, no comments about the immorality of NATs. Living in America, I have
to suffer enough of that kind of stuff from the current USG.).
> Scope of address updates:
>
> addrmgmt: Updating individual child SAs is possible.
>
> => IMHO this is the main difference: the idea is to manage all the IPsec
> SAs between two multi-homed peers using different peer addresses from
> one IKE SA.
>
Actually, I like this. It might be very useful for multihoming. The only
issue is if updating individual child SAs is always necessary, or if they
can be updated en masse.
jak