Subject: Last Call: <draft-ietf-hip-rfc5206-bis-12.txt> (Host Mobility with the Host Identity Protocol) to Proposed Standard

From: The IESG <[email-masked]>
Date: Thu, 11 Aug 2016 16:45:21 -0700

The IESG has received a request from the Host Identity Protocol WG (hip)
to consider the following document:
- 'Host Mobility with the Host Identity Protocol'
  <draft-ietf-hip-rfc5206-bis-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
[email-masked] mailing lists by 2016-08-25. Exceptionally, comments may be
sent to [email-masked] instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5206-bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5206-bis/ballot/

No IPR declarations have been submitted directly on this I-D.

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc5206: End-Host Mobility and Multihoming with the Host Identity Protocol (Experimental - IETF stream)
    rfc5204: Host Identity Protocol (HIP) Rendezvous Extension (Experimental - IETF stream)
    rfc5203: Host Identity Protocol (HIP) Registration Extension (Experimental - IETF stream)
Note that some of these references may already be listed in the acceptable Downref Registry.