Host behavior to short prefix length
draft-akimichi-6man-ra-prefixlen-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Akimichi Ogawa , Kaname Nishizuka , Yoshifumi Atarashi , Akira Kanai | ||
| Last updated | 2022-04-08 (Latest revision 2021-10-05) | ||
| 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 Prefix Information Option in the IPv6 Neighbor Discovery Router Advertisement message defines an 8-bit prefix length field. Prefix List entries are created using the prefix length in the Prefix Information Option. The Conceptual Model of a Host described in RFC 4861[RFC4861] does not clarify behavior of a host, when a short prefix length is received. This document updates RFC 4861(if approved), and clarifies that hosts SHOULD NOT accept prefix length shorter than /64.
Authors
Akimichi Ogawa
Kaname Nishizuka
Yoshifumi Atarashi
Akira Kanai
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)