ICMP Locator Update Message for the Identifier-Locator Network Protocol for IPv6 (ILNPv6)
Note: This ballot was opened for revision 02 and is now closed.
(Brian Haberman) Yes
(Ron Bonica) No Objection
(Stewart Bryant) (was Discuss) No Objection
(Gonzalo Camarillo) No Objection
(Benoît Claise) No Objection
(Wesley Eddy) No Objection
(Adrian Farrel) (was Discuss) No Objection
Comment (2012-05-24 for -03)
The IESG failed to convince me that this work needs to be conducted other than on experimental code points. However, I will not stand against the IESG consensus, and will allow the IESG to make its decision to allocate a code point. --- The LISP documents (currently in the RFC Editor Queue for publication as Experimental RFCs in the IETF Stream) have clear and unambiguous text to caution the user about the unknown side-effects of conducting the experiment on the Internet. For example, draft-ietf-lisp-23 says: This experimental specification has areas that require additional experience and measurement. It is NOT RECOMMENDED for deployment beyond experimental situations. Results of experimentation may lead to modifications and enhancements of protocol mechanisms defined in this document. See Section 15 for specific, known issues that are in need of further work during development, implementation, and experimentation. An examination of the implications of LISP on Internet traffic, applications, routers, and security is for future study. This analysis will explain what role LISP can play in scalable routing and will also look at scalability and levels of state required for encapsulation, decapsulation, liveness, and so on. It seems to me highly desirable that similar caveats be applied to this work and added to the front of all ILNP documents. I strongly urge the authors and IRSG to apply such text.