Controlled IPv6 deaggregation by large organizations
draft-van-beijnum-grow-controlled-deagg-00

Document Type Expired Internet-Draft (individual)
Author Iljitsch van Beijnum 
Last updated 2015-04-25 (latest revision 2014-10-22)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-van-beijnum-grow-controlled-deagg-00.txt

Abstract

The use of IPv6 addresses by large organizations doesn't fit the commonly used PA/PI dichotomy. Such organizations may hold a large address block which is deaggregated into subprefixes that are advertised by subunits of the organization. This document proposes a set of best practices to allow this deaggregation to be controlled through filtering so that on the one hand, the size of the IPv6 global routing table isn't unduly inflated, while on the other hand organizations that seek to deaggregate a large IPv6 address block don't see their reachability limited by remote filters.

Authors

Iljitsch van Beijnum (iljitsch@muada.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)