Network Working Group T. Henderson, Ed.
Internet-Draft The Boeing Company
Obsoletes: 5206 (if approved) C. Vogt
Intended status: Standards Track J. Arkko
Expires: July 19, 2013 Ericsson Research NomadicLab
January 15, 2013
Host Mobility with the Host Identity Protocol
draft-ietf-hip-rfc5206-bis-05
Abstract
This document defines mobility extensions to the Host Identity
Protocol (HIP). Specifically, this document defines a general
"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 elements of procedure for mobility of a
HIP host -- the process by which a host dynamically changes the
primary locator that it uses to receive packets. While the same
LOCATOR_SET parameter can also be used to support end-host
multihoming, detailed procedures are out of scope for this document.
This document obsoletes RFC 5206.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 19, 2013.
Copyright Notice
Copyright (c) 2013 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
Henderson, et al. Expires July 19, 2013 [Page 1]
Internet-Draft HIP Host Mobility January 2013
(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.
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.
Henderson, et al. Expires July 19, 2013 [Page 2]
Internet-Draft HIP Host Mobility January 2013
Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Conventions . . . . . . . . . . . . . . . . . 5
3. Protocol Model . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Operating Environment . . . . . . . . . . . . . . . . . . 6
3.1.1. Locator . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.2. Mobility Overview . . . . . . . . . . . . . . . . . . 8
3.2. Protocol Overview . . . . . . . . . . . . . . . . . . . . 9
3.2.1. Mobility with a Single SA Pair (No Rekeying) . . . . . 10
3.2.2. Mobility with a Single SA Pair (Mobile-Initiated
Rekey) . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.3. Using LOCATOR_SETs across Addressing Realms . . . . . 12
3.2.4. Network Renumbering . . . . . . . . . . . . . . . . . 12
3.3. Other Considerations . . . . . . . . . . . . . . . . . . . 12
3.3.1. Address Verification . . . . . . . . . . . . . . . . . 12
3.3.2. Credit-Based Authorization . . . . . . . . . . . . . . 13
3.3.3. Preferred Locator . . . . . . . . . . . . . . . . . . 14