@techreport{mlevy-v6ops-auto-v6-allocation-per-asn-00,
    number =    {draft-mlevy-v6ops-auto-v6-allocation-per-asn-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mlevy-v6ops-auto-v6-allocation-per-asn/00/},
    author =    {Martin J. Levy and Matthew Pounsett},
    title =     {{A mechanism to allocate IPv6 blocks for BGP networks based on the networks AS Number}},
    pagetotal = 7,
    year =      2013,
    month =     jan,
    day =       24,
    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.},
}