IPv6 ND PIO Flags IANA considerations
draft-troan-6man-ndpioiana-01
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ole Trøan | ||
| Last updated | 2017-12-06 (Latest revision 2017-09-19) | ||
| Replaced by | draft-ietf-6man-ndpioiana | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-ndpioiana | |
| Consensus boilerplate | Yes | ||
| 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 Prefix Information Option in the IPv6 Neighbor Discovery Router Advertisement defines an 8-bit flag field with two flags defined and the remaining 6 bits reservered (Reserved1). RFC 6275 has defined a new flag from this field without creating a IANA registry or updating RFC 4861. The purpose of this document is to request IANA to create a new registry for the PIO flags to avoid potential conflict in the use of these flags.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)