@techreport{deering-ipv6-encap-addr-deletion-00,
    number =    {draft-deering-ipv6-encap-addr-deletion-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-deering-ipv6-encap-addr-deletion/00/},
    author =    {Dr. Steve E. Deering and Brian Zill},
    title =     {{Redundant Address Deletion when Encapsulating IPv6 in IPv6}},
    pagetotal = 6,
    year =      2001,
    month =     nov,
    day =       20,
    abstract =  {In some potentially common uses of IPv6-in-IPv6 encapsulation ('tunneling'), a node that is performing an encapsulation or decapsulation will also be the source or destination of the packet being encapsulated. That can result in the same IPv6 address appearing in both the outer (encapsulating) and inner (encapsulated) IPv6 headers. This document specifies a method for deleting such redundant addresses from an inner header when performing an encapsulation, and restoring those addresses when decapsulating, resulting in a 16-octet (128-bit) reduction in header overhead, per address deleted.},
}