InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Host Identity Protocol (HIP) Rendezvous Extension (RFC8004)

IP.com Disclosure Number: IPCOM000248003D
Original Publication Date: 2016-Oct-01
Included in the Prior Art Database: 2016-Oct-15
Document File: 28 page(s) / 31K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Laganier: AUTHOR [+2]


"The Host Identity Protocol (HIP) Architecture" [HIP-ARCH] introduces the rendezvous mechanism to help a HIP node to contact a frequently moving HIP node. The rendezvous mechanism involves a third party, the rendezvous server (RVS), which serves as an initial contact point ("rendezvous point") for its clients. The clients of an RVS are HIP nodes that use the HIP Registration Extension [RFC8003] to register their HIT->IP address mappings with the RVS. After this registration, other HIP nodes can initiate a base exchange using the IP address of the RVS instead of the current IP address of the node they attempt to contact. Essentially, the clients of an RVS become reachable at the RVS's IP address. Peers can initiate a HIP base exchange with the IP address of the RVS, which will relay this initial communication such that the base exchange may successfully complete.

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

Internet Engineering Task Force (IETF)                       J. Laganier Request for Comments: 8004                       Luminate Wireless, Inc. Obsoletes: 5204                                                L. Eggert Category: Standards Track                                         NetApp ISSN: 2070-1721                                             October 2016

            Host Identity Protocol (HIP) Rendezvous Extension


   This document defines a rendezvous extension for the Host Identity    Protocol (HIP).  The rendezvous extension extends HIP and the HIP    Registration Extension for initiating communication between HIP nodes    via HIP rendezvous servers.  Rendezvous servers improve reachability    and operation when HIP nodes are multihomed or mobile.  This document    obsoletes RFC 5204.

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

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    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Laganier & Eggert            Standards Track                    [Page 1]
 RFC 8004                HIP Rendezvous Extension            October 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3

   3.  Overview of Rendezvous Server Operation . . . . . . . . . . .   3

     3.1.  Diagram Notation  . . . . . . . . . . . . . . . . . . . .   5

     3.2.  Rendezvous Client Registration  . . . . . . . . . . . . .   5

     3.3.  Relay...