Skip to main content

ICMP Locator Update Message for the Identifier-Locator Network Protocol for IPv6 (ILNPv6)
draft-irtf-rrg-ilnp-icmpv6-06

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "Lars Eggert" <lars@netapp.com>, "Internet Research Steering Group" <irsg@irtf.org>
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, <ietf-announce@ietf.org>, tony.li@tony.li
Subject: Results of IETF-conflict review for <draft-irtf-rrg-ilnp-icmpv6-03.txt>

The IESG has completed a review of <draft-irtf-rrg-ilnp-icmpv6>
consistent with RFC5742.  This review is applied to all non-IETF streams.

The IESG has no problem with the publication of 'ICMP Locator Update
message for ILNPv6' <draft-irtf-rrg-ilnp-icmpv6-03.txt> as an
Experimental RFC.

The IESG would also like the IRSG to review the comments in
the datatracker
(http://datatracker.ietf.org/doc/draft-irtf-rrg-ilnp-icmpv6/) related to
this document and determine whether or not they merit incorporation into
the document. Comments may exist in both the ballot and the history log.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-irtf-rrg-ilnp-icmpv6/

The process for such documents is described at
http://www.rfc-editor.org/indsubs.html

Thank you,

The IESG Secretary


Ballot Text

Technical Summary

   This note specifies an experimental ICMPv6 message type used with
   the Identifier-Locator Network Protocol (ILNP).  The
   Identifier-Locator Network Protocol (ILNP) is an experimental,
   evolutionary enhancement to IP.  This message is used to
   dynamically update Identifier/Locator bindings for an existing
   ILNP session.
   
Working Group Summary

   This is a product of the IRTF Routing RG.
   
Document Quality

   Brian Haberman reviewed the document and concluded that the IESG
   note included below is appropriate.

Personnel

   Brian Haberman is the responsible AD for the IESG review of
   this document.
   
IESG Note

     The IESG has concluded that this work is related to IETF work done
      in the LISP WG and the HIP WG, but this relationship does not prevent
      publishing.

RFC Editor Note