%% You should probably cite rfc6732 instead of this I-D.
@techreport{kuarsingh-v6ops-6to4-provider-managed-tunnel-07,
    number =    {draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-07},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kuarsingh-v6ops-6to4-provider-managed-tunnel/07/},
    author =    {Victor Kuarsingh and Yiu Lee and Olivier Vautrin},
    title =     {{6to4 Provider Managed Tunnels}},
    pagetotal = 12,
    year =      2012,
    month =     jul,
    day =       10,
    abstract =  {6to4 Provider Managed Tunnels (6to4-PMT) provide a framework that can help manage 6to4 tunnels operating in an anycast configuration. The 6to4-PMT framework is intended to serve as an option for operators to help improve the experience of 6to4 operation when conditions of the network may provide sub-optimal performance or break normal 6to4 operation. 6to4-PMT supplies a stable provider prefix and forwarding environment by utilizing existing 6to4 relays with an added function of IPv6 Prefix Translation. This operation may be particularly important in NAT444 infrastructures where a customer endpoint may be assigned a non-RFC1918 address, thus breaking the return path for anycast-based 6to4 operation. 6to4-PMT has been successfully used in a production network, implemented as open source code, and implemented by a major routing vendor. This document is not an Internet Standards Track specification; it is published for informational purposes.},
}