CIDR for IPv6: Address Aggregation, Allocation, and Assignment Strategy
draft-azinger-cidrv6-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marla Azinger , Tony Li , Jason Weil | ||
| Last updated | 2010-06-29 | ||
| 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
This document discusses strategies for assigning and aggregating IPv6 address space. While CIDR was created to help alleviate this problem in regards to IPv4 addresses with the original [RFC1519] (and updated in [RFC4632]) we are now in need of a similar document to give direction for IPv6 addressing policies. Similarly, [RFC1518] discussed how to use CIDR to allocate address space for IPv4, and [RFC1887] discusses the subject for IPv6. The objective here is to update these documents and provide the best current guidance on how to manage address space in conjunction with managing the growth of routing tables in an IPv6 world.
Authors
Marla Azinger
Tony Li
Jason Weil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)