IPv6 ND Vendor-Specific Information Option
draft-gundavelli-6man-ipv6-nd-vendor-spec-options-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sri Gundavelli , Ole Trøan , Wojciech Dec , Suresh Krishnan | ||
| Last updated | 2010-02-13 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The current IPv6 Neighbor Discovery specification does not provide semantics for carrying vendor-specific options in the IPv6 Neighbor Discovery messages. With the anticipated wide scale deployment of IPv6 networks, it is useful for organizations and vendors to have the ability to carry organization/vendor specific information in the IPv6 Neighbor Discovery messages. This will facilitate the vendors and organizations to make deployment specific extensions as needed in system deployment. This document defines a new vendor-specific information option that can be carried in IPv6 Neighbor Discovery messages exchanged between IPv6 nodes on a link.
Authors
Sri Gundavelli
Ole Trøan
Wojciech Dec
Suresh Krishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)