Host Multihoming with the Host Identity Protocol
draft-ietf-hip-multihoming-10

Document Type Active Internet-Draft (hip WG)
Last updated 2016-08-25 (latest revision 2016-07-24)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Gonzalo Camarillo
Shepherd write-up Show (last changed 2016-06-14)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date
Responsible AD Terry Manderson
Send notices to "Gonzalo Camarillo" <gonzalo.camarillo@ericsson.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                  T. Henderson, Ed.
Internet-Draft                                  University of Washington
Intended status: Standards Track                                 C. Vogt
Expires: January 25, 2017                                    Independent
                                                                J. Arkko
                                                                Ericsson
                                                           July 24, 2016

            Host Multihoming with the Host Identity Protocol
                     draft-ietf-hip-multihoming-10

Abstract

   This document defines host multihoming extensions to the Host
   Identity Protocol (HIP), by leveraging protocol components defined
   for host mobility.

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 January 25, 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
   (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

Henderson, et al.       Expires January 25, 2017                [Page 1]
Internet-Draft               HIP Multihoming                   July 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction and Scope  . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and Conventions . . . . . . . . . . . . . . . . .   3
   3.  Protocol Model  . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Multiple Addresses  . . . . . . . . . . . . . . . . . . .   5
     4.3.  Multiple Security Associations  . . . . . . . . . . . . .   6
     4.4.  Host Multihoming for Fault Tolerance  . . . . . . . . . .   7
     4.5.  Host Multihoming for Load Balancing . . . . . . . . . . .   8
     4.6.  Site Multihoming  . . . . . . . . . . . . . . . . . . . .   9
     4.7.  Dual Host Multihoming . . . . . . . . . . . . . . . . . .  10
     4.8.  Combined Mobility and Multihoming . . . . . . . . . . . .  10
     4.9.  Initiating the Protocol in R1, I2, or R2  . . . . . . . .  11
     4.10. Using LOCATOR_SETs across Addressing Realms . . . . . . .  12
     4.11. Interaction with Security Associations  . . . . . . . . .  13
   5.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  Sending LOCATOR_SETs  . . . . . . . . . . . . . . . . . .  13
     5.2.  Handling Received LOCATOR_SETs  . . . . . . . . . . . . .  15
     5.3.  Verifying Address Reachability  . . . . . . . . . . . . .  17
     5.4.  Changing the Preferred Locator  . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   8.  Authors and Acknowledgments . . . . . . . . . . . . . . . . .  20
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Normative references  . . . . . . . . . . . . . . . . . .  20
     9.2.  Informative references  . . . . . . . . . . . . . . . . .  21
   Appendix A.  Document Revision History  . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction and Scope

   The Host Identity Protocol [RFC7401] (HIP) supports an architecture
   that decouples the transport layer (TCP, UDP, etc.) from the
   internetworking layer (IPv4 and IPv6) by using public/private key
   pairs, instead of IP addresses, as host identities.  When a host uses
   HIP, the overlying protocol sublayers (e.g., transport layer sockets
   and Encapsulating Security Payload (ESP) Security Associations (SAs))
Show full document text