Mobile IPv6 Experimental Messages
RFC 5096

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    mip6 mailing list <mip6@ietf.org>, 
    mip6 chair <mip6-chairs@tools.ietf.org>
Subject: Protocol Action: 'Mobile IPv6 Experimental Messages' to 
         Proposed Standard 

The IESG has approved the following document:

- 'Mobile IPv6 Experimental Messages '
   <draft-ietf-mip6-experimental-messages-04.txt> as a Proposed Standard

This document is the product of the Mobility for IPv6 Working Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-experimental-messages-04.txt

Technical Summary
 
  This document defines a new experimental Mobility header message and
  a mobility option that can be used for experimental extensions to the
  Mobile IPv6 protocol.

Working Group Summary

  No controversy has been raised or identified with this document. The
  I-D is fairly simple and the extension useful for the MIP6 protocol.

Document Quality

  No known implementations of the extensions being proposed here
  exist. 

  Jari Arkko has reviewed this specification for the IESG.

Note to RFC Editor
 
   Add to the end of last paragraph of Section 1:

   Experimental mechanisms should only be used for
   actual experimentation. By design, only a single code
   point is allocated for the message and another one for the
   option. This limits the number of experiments among
   a set of peers to one at a time. When experimental
   mechanisms are shown to be useful and there is
   a desire to deploy them beyond the experiment they
   should be standardized and given new code points.