RE: Issue: NAT-T interaction (#3)
"Jing Xiang" <[email protected]>
| Newsgroups | gmane.ietf.mobike |
|---|---|
| Message-ID | <6204FDDE129D364D8040A98BCCB290EF0EA17D62@zbl6c004.corpeast.baynetworks.com> |
Tero, I don't see why we have to make MOBIKE & NAT-T mutually exclusive. e.g. In your just updated draft-ietf-mobike-design-00.txt, it says: "If NAT is detected in the IKE SA creation, that should automatically disable the MOBIKE extensions and use NAT-T." However, currently NAT-T does not provide mechanism for signalling address change. Does that mean we limit MOBIKE to non-NAT environment? If a connection is established using NAT-T, doesn't IKEv2 already specify that "Any authenticated IKE packet or any authenticated UDP encapsulated ESP packet can be used to detect that the IP address or the port has changed."? Since ADDRESS_UPDATE message is authenticated why it can't be used for roaming from NAT cases? Best Regards! /Jing _______________________________________________ Mobike mailing list [email protected] https://www.machshav.com/mailman/listinfo.cgi/mobike