draft-ietf-hip-rfc5206-bis-11.txt   draft-ietf-hip-rfc5206-bis-12.txt 
Network Working Group T. Henderson, Ed. Network Working Group T. Henderson, Ed.
Internet-Draft University of Washington Internet-Draft University of Washington
Obsoletes: 5206 (if approved) C. Vogt Obsoletes: 5206 (if approved) C. Vogt
Intended status: Standards Track J. Arkko Intended status: Standards Track Independent
Expires: November 6, 2016 Ericsson Research NomadicLab Expires: December 2, 2016 J. Arkko
May 5, 2016 Ericsson
May 31, 2016
Host Mobility with the Host Identity Protocol Host Mobility with the Host Identity Protocol
draft-ietf-hip-rfc5206-bis-11 draft-ietf-hip-rfc5206-bis-12
Abstract Abstract
This document defines mobility extensions to the Host Identity This document defines mobility extensions to the Host Identity
Protocol (HIP). Specifically, this document defines a general Protocol (HIP). Specifically, this document defines a general
"LOCATOR_SET" parameter for HIP messages that allows for a HIP host "LOCATOR_SET" parameter for HIP messages that allows for a HIP host
to notify peers about alternate addresses at which it may be reached. to notify peers about alternate addresses at which it may be reached.
This document also defines elements of procedure for mobility of a This document also defines elements of procedure for mobility of a
HIP host -- the process by which a host dynamically changes the HIP host -- the process by which a host dynamically changes the
primary locator that it uses to receive packets. While the same primary locator that it uses to receive packets. While the same
skipping to change at page 1, line 41 skipping to change at page 1, line 42
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 November 6, 2016. This Internet-Draft will expire on December 2, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 3 1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4 2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4
3. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . 5 3. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Operating Environment . . . . . . . . . . . . . . . . . . 5 3.1. Operating Environment . . . . . . . . . . . . . . . . . . 5
3.1.1. Locator . . . . . . . . . . . . . . . . . . . . . . . 8 3.1.1. Locator . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2. Mobility Overview . . . . . . . . . . . . . . . . . . 8 3.1.2. Mobility Overview . . . . . . . . . . . . . . . . . . 7
3.2. Protocol Overview . . . . . . . . . . . . . . . . . . . . 9 3.2. Protocol Overview . . . . . . . . . . . . . . . . . . . . 8
3.2.1. Mobility with a Single SA Pair (No Rekeying) . . . . 9 3.2.1. Mobility with a Single SA Pair (No Rekeying) . . . . 8
3.2.2. Mobility with a Single SA Pair (Mobile-Initiated 3.2.2. Mobility with a Single SA Pair (Mobile-Initiated
Rekey) . . . . . . . . . . . . . . . . . . . . . . . 11 Rekey) . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.3. Mobility messaging through rendezvous server . . . . 11 3.2.3. Mobility messaging through rendezvous server . . . . 10
3.2.4. Network Renumbering . . . . . . . . . . . . . . . . . 13 3.2.4. Network Renumbering . . . . . . . . . . . . . . . . . 12
3.3. Other Considerations . . . . . . . . . . . . . . . . . . 13 3.3. Other Considerations . . . . . . . . . . . . . . . . . . 12
3.3.1. Address Verification . . . . . . . . . . . . . . . . 13 3.3.1. Address Verification . . . . . . . . . . . . . . . . 12
3.3.2. Credit-Based Authorization . . . . . . . . . . . . . 13 3.3.2. Credit-Based Authorization . . . . . . . . . . . . . 12
3.3.3. Preferred Locator . . . . . . . . . . . . . . . . . . 15 3.3.3. Preferred Locator . . . . . . . . . . . . . . . . . . 14
4. LOCATOR_SET Parameter Format . . . . . . . . . . . . . . . . 15 4. LOCATOR_SET Parameter Format . . . . . . . . . . . . . . . . 14
4.1. Traffic Type and Preferred Locator . . . . . . . . . . . 16 4.1. Traffic Type and Preferred Locator . . . . . . . . . . . 16
4.2. Locator Type and Locator . . . . . . . . . . . . . . . . 17 4.2. Locator Type and Locator . . . . . . . . . . . . . . . . 16
4.3. UPDATE Packet with Included LOCATOR_SET . . . . . . . . . 17 4.3. UPDATE Packet with Included LOCATOR_SET . . . . . . . . . 17
5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 17 5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 17
5.1. Locator Data Structure and Status . . . . . . . . . . . . 18 5.1. Locator Data Structure and Status . . . . . . . . . . . . 17
5.2. Sending LOCATOR_SETs . . . . . . . . . . . . . . . . . . 19 5.2. Sending LOCATOR_SETs . . . . . . . . . . . . . . . . . . 19
5.3. Handling Received LOCATOR_SETs . . . . . . . . . . . . . 20 5.3. Handling Received LOCATOR_SETs . . . . . . . . . . . . . 19
5.4. Verifying Address Reachability . . . . . . . . . . . . . 22 5.4. Verifying Address Reachability . . . . . . . . . . . . . 22
5.5. Changing the Preferred Locator . . . . . . . . . . . . . 23 5.5. Changing the Preferred Locator . . . . . . . . . . . . . 23
5.6. Credit-Based Authorization . . . . . . . . . . . . . . . 24 5.6. Credit-Based Authorization . . . . . . . . . . . . . . . 23
5.6.1. Handling Payload Packets . . . . . . . . . . . . . . 24 5.6.1. Handling Payload Packets . . . . . . . . . . . . . . 24
5.6.2. Credit Aging . . . . . . . . . . . . . . . . . . . . 26 5.6.2. Credit Aging . . . . . . . . . . . . . . . . . . . . 25
6. Security Considerations . . . . . . . . . . . . . . . . . . . 27 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26
6.1. Impersonation Attacks . . . . . . . . . . . . . . . . . . 28 6.1. Impersonation Attacks . . . . . . . . . . . . . . . . . . 27
6.2. Denial-of-Service Attacks . . . . . . . . . . . . . . . . 29 6.2. Denial-of-Service Attacks . . . . . . . . . . . . . . . . 28
6.2.1. Flooding Attacks . . . . . . . . . . . . . . . . . . 29 6.2.1. Flooding Attacks . . . . . . . . . . . . . . . . . . 28
6.2.2. Memory/Computational-Exhaustion DoS Attacks . . . . . 29 6.2.2. Memory/Computational-Exhaustion DoS Attacks . . . . . 28
6.3. Mixed Deployment Environment . . . . . . . . . . . . . . 30 6.3. Mixed Deployment Environment . . . . . . . . . . . . . . 29
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
8. Authors and Acknowledgments . . . . . . . . . . . . . . . . . 31 8. Authors and Acknowledgments . . . . . . . . . . . . . . . . . 30
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.1. Normative references . . . . . . . . . . . . . . . . . . 31 9.1. Normative references . . . . . . . . . . . . . . . . . . 30
9.2. Informative references . . . . . . . . . . . . . . . . . 32 9.2. Informative references . . . . . . . . . . . . . . . . . 31
Appendix A. Document Revision History . . . . . . . . . . . . . 33 Appendix A. Document Revision History . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction and Scope 1. Introduction and Scope
The Host Identity Protocol [RFC7401] (HIP) supports an architecture The Host Identity Protocol [RFC7401] (HIP) supports an architecture
that decouples the transport layer (TCP, UDP, etc.) from the that decouples the transport layer (TCP, UDP, etc.) from the
internetworking layer (IPv4 and IPv6) by using public/private key internetworking layer (IPv4 and IPv6) by using public/private key
pairs, instead of IP addresses, as host identities. When a host uses pairs, instead of IP addresses, as host identities. When a host uses
HIP, the overlying protocol sublayers (e.g., transport layer sockets HIP, the overlying protocol sublayers (e.g., transport layer sockets
and Encapsulating Security Payload (ESP) Security Associations (SAs)) and Encapsulating Security Payload (ESP) Security Associations (SAs))
are instead bound to representations of these host identities, and are instead bound to representations of these host identities, and
skipping to change at page 34, line 13 skipping to change at page 33, line 13
| | | | | |
| | removed discussion about possible multiple LOCATOR_SET | | | removed discussion about possible multiple LOCATOR_SET |
| | and ESP_INFO parameters in an UPDATE (per previous | | | and ESP_INFO parameters in an UPDATE (per previous |
| | mailing list discussion) | | | mailing list discussion) |
| | | | | |
| | removed discussion about handling LOCATOR_SET | | | removed discussion about handling LOCATOR_SET |
| | parameters in packets other than UPDATE (per previous | | | parameters in packets other than UPDATE (per previous |
| | mailing list discussion) | | | mailing list discussion) |
| | | | | |
| draft-11 | Editorial improvements from WGLC | | draft-11 | Editorial improvements from WGLC |
| | |
| draft-12 | Update author affiliations and IPR boilerplate to |
| | trust200902 |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
Authors' Addresses Authors' Addresses
Thomas R. Henderson (editor) Thomas R. Henderson (editor)
University of Washington University of Washington
Campus Box 352500 Campus Box 352500
Seattle, WA Seattle, WA
USA USA
EMail: tomhend@u.washington.edu EMail: tomhend@u.washington.edu
Christian Vogt Christian Vogt
Ericsson Research NomadicLab Independent
Hirsalantie 11 3473 North First Street
JORVAS FIN-02420 San Jose, CA 95134
FINLAND USA
EMail: christian.vogt@ericsson.com EMail: mail@christianvogt.net
Jari Arkko Jari Arkko
Ericsson Research NomadicLab Ericsson
JORVAS FIN-02420 JORVAS FIN-02420
FINLAND FINLAND
Phone: +358 40 5079256 Phone: +358 40 5079256
EMail: jari.arkko@ericsson.com EMail: jari.arkko@piuha.net
 End of changes. 16 change blocks. 
53 lines changed or deleted 45 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/