| < draft-smyslov-ipsecme-ikev2-r-mobike-05.txt | draft-smyslov-ipsecme-ikev2-r-mobike-06.txt > | |||
|---|---|---|---|---|
| Network Working Group V. Smyslov | Network Working Group V. Smyslov | |||
| Internet-Draft ELVIS-PLUS | Internet-Draft ELVIS-PLUS | |||
| Updates: 4555 (if approved) November 27, 2019 | Updates: 4555 (if approved) May 30, 2020 | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: May 30, 2020 | Expires: December 1, 2020 | |||
| Responder Initiated IP Addresses Update in MOBIKE | Responder Initiated IP Addresses Update in MOBIKE | |||
| draft-smyslov-ipsecme-ikev2-r-mobike-05 | draft-smyslov-ipsecme-ikev2-r-mobike-06 | |||
| Abstract | Abstract | |||
| IKEv2 Mobility and Multihoming Protocol (MOBIKE), defined in | IKEv2 Mobility and Multihoming Protocol (MOBIKE), defined in | |||
| [RFC4555] allows peers to update their IP addresses without re- | [RFC4555] allows peers to update their IP addresses without re- | |||
| establishing IKE and IPsec Security Associations (SAs). In the | establishing IKE and IPsec Security Associations (SAs). In the | |||
| MOBIKE protocol it is the Initiator of the IKE SA, who is responsible | MOBIKE protocol it is the Initiator of the IKE SA, who is responsible | |||
| for selecting new SA addresses and for initiating the IP addresses | for selecting new SA addresses and for initiating the IP addresses | |||
| update procedure. This document presents an extension to the MOBIKE | update procedure. This document presents an extension to the MOBIKE | |||
| protocol that allows the Responder to initiate IP address update. | protocol that allows the Responder to initiate IP address update. | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 38 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on May 30, 2020. | This Internet-Draft will expire on December 1, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 2, line 25 ¶ | skipping to change at page 2, line 25 ¶ | |||
| 4.1. Capability Advertising . . . . . . . . . . . . . . . . . 4 | 4.1. Capability Advertising . . . . . . . . . . . . . . . . . 4 | |||
| 4.2. Responder Initiated IP Address Update . . . . . . . . . . 5 | 4.2. Responder Initiated IP Address Update . . . . . . . . . . 5 | |||
| 5. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 7 | 5. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 5.1. MOBIKE_SUPPORTED Notification . . . . . . . . . . . . . . 7 | 5.1. MOBIKE_SUPPORTED Notification . . . . . . . . . . . . . . 7 | |||
| 5.2. SWITCH_TO_IP_ADDRESS Notification . . . . . . . . . . . . 7 | 5.2. SWITCH_TO_IP_ADDRESS Notification . . . . . . . . . . . . 7 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 1. Introduction | 1. Introduction | |||
| The Internet Key Exchange protocol version 2 (IKEv2), specified in | The Internet Key Exchange protocol version 2 (IKEv2), specified in | |||
| [RFC7296], is a key part of the IP Security (IPsec) architecture. It | [RFC7296], is a key part of the IP Security (IPsec) architecture. It | |||
| allows peers to perform authenticated key exchange, which results in | allows peers to perform authenticated key exchange, which results in | |||
| establishing IKE Security Association (IKE SA) and to create a data | establishing IKE Security Association (IKE SA) and to create a data | |||
| protection channels called IPsec Security Associations (IPsec SAs). | protection channels called IPsec Security Associations (IPsec SAs). | |||
| In original IKEv2 the IKE and IPsec SAs are established between the | In original IKEv2 the IKE and IPsec SAs are established between the | |||
| IP addresses used in IKEv2 negotiation. The IKEv2 Mobility and | IP addresses used in IKEv2 negotiation. The IKEv2 Mobility and | |||
| skipping to change at page 8, line 29 ¶ | skipping to change at page 8, line 29 ¶ | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| [RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol | [RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol | |||
| (MOBIKE)", RFC 4555, DOI 10.17487/RFC4555, June 2006, | (MOBIKE)", RFC 4555, DOI 10.17487/RFC4555, June 2006, | |||
| <https://www.rfc-editor.org/info/rfc4555>. | <https://www.rfc-editor.org/info/rfc4555>. | |||
| [RFC6311] Singh, R., Ed., Kalyani, G., Nir, Y., Sheffer, Y., and D. | ||||
| Zhang, "Protocol Support for High Availability of IKEv2/ | ||||
| IPsec", RFC 6311, DOI 10.17487/RFC6311, July 2011, | ||||
| <https://www.rfc-editor.org/info/rfc6311>. | ||||
| [RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. | [RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. | |||
| Kivinen, "Internet Key Exchange Protocol Version 2 | Kivinen, "Internet Key Exchange Protocol Version 2 | |||
| (IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October | (IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October | |||
| 2014, <https://www.rfc-editor.org/info/rfc7296>. | 2014, <https://www.rfc-editor.org/info/rfc7296>. | |||
| 8.2. Informative References | 8.2. Informative References | |||
| [RFC5685] Devarapalli, V. and K. Weniger, "Redirect Mechanism for | [RFC5685] Devarapalli, V. and K. Weniger, "Redirect Mechanism for | |||
| the Internet Key Exchange Protocol Version 2 (IKEv2)", | the Internet Key Exchange Protocol Version 2 (IKEv2)", | |||
| RFC 5685, DOI 10.17487/RFC5685, November 2009, | RFC 5685, DOI 10.17487/RFC5685, November 2009, | |||
| End of changes. 7 change blocks. | ||||
| 11 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||