SLAAC Prefixes with Variable Interface ID (IID)
draft-mishra-6man-variable-iids-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Gyan Mishra , Dmytro Shytyi , Alexandre Petrescu , Naveen Kottapalli , Dusan Mudric | ||
| Last updated | 2025-05-12 (Latest revision 2024-11-07) | ||
| RFC stream | (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
This draft proposes the use of a longer prefixes in PIO for SLAAC allowing a maximum prefix length of /80 with an IID of 48 bits. This would eliminate the race to the bottom concerns. This implementation uses the RA/PIO bits to carry the variable IID to ensure backwards compatibility. In the past, various IPv6 addressing models have been proposed based on a subnet hierarchy embedding a 64-bit prefix. The last remnant of IPv6 classful addressing is a inflexible interface identifier boundary at /64. This document proposes flexibility to the fixed position of that boundary for interface addressing.
Authors
Gyan Mishra
Dmytro Shytyi
Alexandre Petrescu
Naveen Kottapalli
Dusan Mudric
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)