Browse Prior Art Database

Host Multihoming with the Host Identity Protocol (RFC8047)

IP.com Disclosure Number: IPCOM000249269D
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Feb-15
Document File: 44 page(s) / 57K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Henderson: AUTHOR [+4]

Abstract

The multihoming scenarios can be explained in contrast to the non-multihoming case described in the base protocol specification [RFC7401]. We review the pertinent details here. In the base specification, when used with the ESP transport format, the HIP base exchange will set up a single SA in each direction. The IP addresses associated with the SAs are the same as those used to convey the HIP packets. For data traffic, a security policy database (SPD) and security association database (SAD) will likely exist, following the IPsec architecture. One distinction between HIP and IPsec, however, is that the host IDs, and not the IP addresses, are conceptually used as selectors in the SPD. In the outbound direction, as a result of SPD processing, when an outbound SA is selected, the correct IP destination address for the peer must also be assigned. Therefore, outbound SAs are conceptually associated with the peer IP address that must be used as the destination IP address below the HIP layer. In the inbound direction, the IP addresses may be used as selectors in the SAD to look up the SA, but they are not strictly required; the ESP SPI may be used alone. To summarize, in the non-multihoming case, there is only one source IP address, one destination IP address, one inbound SA, and one outbound SA.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                 T. Henderson, Ed. Request for Comments: 8047                      University of Washington Category: Standards Track                                        C. Vogt ISSN: 2070-1721                                              Independent                                                                 J. Arkko                                                                 Ericsson                                                            February 2017

             Host Multihoming with the Host Identity Protocol

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 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/rfc8047.

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 1]
 RFC 8047                     HIP Multihoming               February 2017

 Table of Contents

   1.  Introduction and Scope  . . . . . . . . . . . . . . . . . . .   3

   2.  Terminology and Conventions . . . . . . . . . . . . . . . . .   4

   3.  Protocol Model  . . . . . . . . . . . . . . . . . . . . . . .   4

   4.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   4

     4.1.  Background  . . . . . . . . . ....