Mobile IPv6 Vendor Specific Option
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, mip6 mailing list <email@example.com>, mip6 chair <firstname.lastname@example.org> Subject: Protocol Action: 'Mobile IPv6 Vendor Specific Option' to Proposed Standard The IESG has approved the following document: - 'Mobile IPv6 Vendor Specific Option ' <draft-ietf-mip6-vsm-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-vsm-04.txt
Technical Summary There is a need for vendor specific extensions to Mobility Header messages so that Mobile IPv6 vendors are able to extend the protocol for research or deployment purposes. This document defines a new vendor specific mobility option. Working Group Summary No controversy has been raised or identified with this spec. 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.