%% You should probably cite rfc7157 instead of this I-D.
@techreport{ietf-v6ops-ipv6-multihoming-without-ipv6nat-06,
    number =    {draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat/06/},
    author =    {Ole Trøan and David Miles and Satoru Matsushima and Tadahisa Okimoto and Dan Wing},
    title =     {{IPv6 Multihoming without Network Address Translation}},
    pagetotal = 22,
    year =      2014,
    month =     feb,
    day =       14,
    abstract =  {Network Address and Port Translation (NAPT) works well for conserving global addresses and addressing multihoming requirements because an IPv4 NAPT router implements three functions: source address selection, next-hop resolution, and (optionally) DNS resolution. For IPv6 hosts, one approach could be the use of IPv6-to-IPv6 Network Prefix Translation (NPTv6). However, NAT and NPTv6 should be avoided, if at all possible, to permit transparent end-to-end connectivity. In this document, we analyze the use cases of multihoming. We also describe functional requirements and possible solutions for multihoming without the use of NAT in IPv6 for hosts and small IPv6 networks that would otherwise be unable to meet minimum IPv6-allocation criteria. We conclude that DHCPv6-based solutions are suitable to solve the multihoming issues described in this document, but NPTv6 may be required as an intermediate solution.},
}