A mechanism to allocate IPv6 blocks for BGP networks based on the networks AS Number
draft-mlevy-v6ops-auto-v6-allocation-per-asn-00

Document Type Expired Internet-Draft (individual)
Authors Martin Levy  , Matthew Pounsett 
Last updated 2013-07-29 (latest revision 2013-01-24)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized 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-mlevy-v6ops-auto-v6-allocation-per-asn-00.txt

Abstract

This document provides a methodology for automatically allocating IPv6 [RFC2460] address blocks for networks that run BGP [RFC4271] and are either single-homed or multi-homed [BARBER2011]. The automatic allocation is taken from a specific /16 block assigned by IANA for this purpose. Networks that require more than this single /48 can still request additional allocations via the existing RIR process. Networks are not forced to use this allocation and can ignore this completely. Availability of the /48 assignment via this mechanism does not change existing mechanisms for obtaining IPv6 assignments through the existing RIR (Regional Internet Registry) or LIR (Local Internet Registry) mechanisms. There is an implicit assumption that it's a good thing to promote networks to enable IPv6 with a near-zero effort.

Authors

Martin Levy (martin@he.net)
Matthew Pounsett (mpounsett@afilias.info)

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