Host Mobility with the Host Identity Protocol
RFC 8046
Document | Type |
RFC - Proposed Standard
(February 2017; No errata)
Obsoletes RFC 5206
|
|
---|---|---|---|
Authors | Thomas Henderson , Christian Vogt , Jari Arkko | ||
Last updated | 2017-02-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Gonzalo Camarillo | ||
Shepherd write-up | Show (last changed 2016-06-14) | ||
IESG | IESG state | RFC 8046 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Terry Manderson | ||
Send notices to | "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) T. Henderson, Ed. Request for Comments: 8046 University of Washington Obsoletes: 5206 C. Vogt Category: Standards Track Independent ISSN: 2070-1721 J. Arkko Ericsson February 2017 Host Mobility with the Host Identity Protocol Abstract This document defines a mobility extension to the Host Identity Protocol (HIP). Specifically, this document defines a "LOCATOR_SET" parameter for HIP messages that allows for a HIP host to notify peers about alternate addresses at which it may be reached. This document also defines how the parameter can be used to preserve communications across a change to the IP address used by one or both peer hosts. The same LOCATOR_SET parameter can also be used to support end-host multihoming (as specified in RFC 8047). This document obsoletes RFC 5206. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8046. Henderson, et al. Standards Track [Page 1] RFC 8046 HIP Host Mobility February 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Henderson, et al. Standards Track [Page 2] RFC 8046 HIP Host Mobility February 2017 Table of Contents 1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 4 2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4 3. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . 7 3.1. Operating Environment . . . . . . . . . . . . . . . . . . 7 3.1.1. Locator . . . . . . . . . . . . . . . . . . . . . . . 9 3.1.2. Mobility Overview . . . . . . . . . . . . . . . . . . 9 3.2. Protocol Overview . . . . . . . . . . . . . . . . . . . . 10 3.2.1. Mobility with a Single SA Pair (No Rekeying) . . . . 10 3.2.2. Mobility with a Single SA Pair (Mobile-Initiated Rekey) . . . . . . . . . . . . . . . . . . . . . . . 12 3.2.3. Mobility Messaging through the Rendezvous Server . . 13 3.2.4. Network Renumbering . . . . . . . . . . . . . . . . . 14 3.3. Other Considerations . . . . . . . . . . . . . . . . . . 14 3.3.1. Address Verification . . . . . . . . . . . . . . . . 14 3.3.2. Credit-Based Authorization . . . . . . . . . . . . . 15 3.3.3. Preferred Locator . . . . . . . . . . . . . . . . . . 16 4. LOCATOR_SET Parameter Format . . . . . . . . . . . . . . . . 16 4.1. Traffic Type and Preferred Locator . . . . . . . . . . . 18 4.2. Locator Type and Locator . . . . . . . . . . . . . . . . 19 4.3. UPDATE Packet with Included LOCATOR_SET . . . . . . . . . 19 5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 19 5.1. Locator Data Structure and Status . . . . . . . . . . . . 19 5.2. Sending the LOCATOR_SET . . . . . . . . . . . . . . . . . 21 5.3. Handling Received LOCATOR_SETs . . . . . . . . . . . . . 22 5.4. Verifying Address Reachability . . . . . . . . . . . . . 24 5.5. Changing the Preferred Locator . . . . . . . . . . . . . 26 5.6. Credit-Based Authorization . . . . . . . . . . . . . . . 26 5.6.1. Handling Payload Packets . . . . . . . . . . . . . . 27 5.6.2. Credit Aging . . . . . . . . . . . . . . . . . . . . 29 6. Security Considerations . . . . . . . . . . . . . . . . . . . 29 6.1. Impersonation Attacks . . . . . . . . . . . . . . . . . . 30Show full document text