IPv6 Routing and its Relationship to the 64-bit Boundary in the IPv6 Addressing Architecture
draft-farmer-6man-routing-64-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Farmer | ||
| Last updated | 2019-07-22 (Latest revision 2019-01-06) | ||
| 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
There is a common misconception that the IPv6 Addressing Architecture requires the use of only /64 subnet prefixes for subnet routing. This document clarifies the characterization of the relationship between IPv6 routing and the 64 bit boundary, which is that of a recommendation for the use of /64 subnet prefixes for subnet routing in most circumstances, not a requirement for such. To further clarify this relationship, the document also provides operational guidance for the configuration of subnet prefixes and updates RFC 4291 accordingly.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)