%% You should probably cite draft-mishra-6man-variable-slaac-08 instead of this revision.
@techreport{mishra-6man-variable-slaac-02,
    number =    {draft-mishra-6man-variable-slaac-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mishra-6man-variable-slaac/02/},
    author =    {Gyan Mishra and Alexandre Petrescu and Naveen Kottapalli and Dusan Mudric and Dmytro Shytyi},
    title =     {{SLAAC with prefixes of arbitrary length in PIO (Variable SLAAC)}},
    pagetotal = 31,
    year =      2021,
    month =     feb,
    day =       22,
    abstract =  {This draft proposes the use of arbitrary length prefixes in PIO for SLAAC. A prefix of length 63 in PIO, for example, would be permitted to form an address whose interface identifier length is 65, which allows several benefits. A prefix of length 65 would be allowed too, but it SHOULD NOT be used on a large scale, like at a large ISP; this is to avoid a race to the bottom. The implementation uses a parameter in the Host which is off by default. In that case, the Host respects the 64bit boundary. When the parameter is set to on the Host accepts prefixes of lengths different than 64 and forms 128bit addresses. 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.},
}