Host Mobility with the Host Identity Protocol
draft-ietf-hip-rfc5206-bis-14

Document Type Active Internet-Draft (hip WG)
Last updated 2016-11-23 (latest revision 2016-10-10)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html 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 Ed Queue
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
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                  T. Henderson, Ed.
Internet-Draft                                  University of Washington
Obsoletes: 5206 (if approved)                                    C. Vogt
Intended status: Standards Track                             Independent
Expires: April 13, 2017                                         J. Arkko
                                                                Ericsson
                                                        October 10, 2016

             Host Mobility with the Host Identity Protocol
                     draft-ietf-hip-rfc5206-bis-14

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 (specified in RFC[Replace with the RFC number for draft-
   ietf-hip-multihoming]).  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 April 13, 2017.

Copyright Notice

   Copyright (c) 2016 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 April 13, 2017                 [Page 1]
Internet-Draft              HIP Host Mobility               October 2016

   (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.

Table of Contents

   1.  Introduction and Scope  . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology and Conventions . . . . . . . . . . . . . . . . .   4
   3.  Protocol Model  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Operating Environment . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Locator . . . . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  Mobility Overview . . . . . . . . . . . . . . . . . .   7
     3.2.  Protocol Overview . . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  Mobility with a Single SA Pair (No Rekeying)  . . . .   9
       3.2.2.  Mobility with a Single SA Pair (Mobile-Initiated
               Rekey)  . . . . . . . . . . . . . . . . . . . . . . .  10
       3.2.3.  Mobility messaging through rendezvous server  . . . .  11
       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
   4.  LOCATOR_SET Parameter Format  . . . . . . . . . . . . . . . .  15
     4.1.  Traffic Type and Preferred Locator  . . . . . . . . . . .  16
     4.2.  Locator Type and Locator  . . . . . . . . . . . . . . . .  17
     4.3.  UPDATE Packet with Included LOCATOR_SET . . . . . . . . .  17
   5.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  Locator Data Structure and Status . . . . . . . . . . . .  18
     5.2.  Sending the LOCATOR_SET . . . . . . . . . . . . . . . . .  19
     5.3.  Handling Received LOCATOR_SETs  . . . . . . . . . . . . .  20
     5.4.  Verifying Address Reachability  . . . . . . . . . . . . .  22
     5.5.  Changing the Preferred Locator  . . . . . . . . . . . . .  23
     5.6.  Credit-Based Authorization  . . . . . . . . . . . . . . .  24
       5.6.1.  Handling Payload Packets  . . . . . . . . . . . . . .  24
Show full document text