@techreport{whittle-ivip-etr-addr-forw-01,
    number =    {draft-whittle-ivip-etr-addr-forw-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-whittle-ivip-etr-addr-forw/01/},
    author =    {Robin Whittle},
    title =     {{Ivip4 ETR Address Forwarding}},
    pagetotal = 37,
    year =      2010,
    month =     jul,
    day =       8,
    abstract =  {ETR Address Forwarding (EAF) is a novel method by which an IPv4 Core- Edge Separation solution to the Internet's routing scaling problem can tunnel packets from an ITR to an ETR. EAF involves using 31 bits of the IPv4 header for new purposes: bit 48, the More Fragments flag, the Fragment Offset field and the Header Checksum field - to carry a 30 bit ETR address. Consequently, packets in this format need to be handled by routers with upgraded functionality. EAF is an alternative to encapsulation and has advantages including: simpler ITRs and ETRs, direct support for conventional RFC 1191 PMTUD, no encapsulation overhead and full compatibility with IPsec AH and Traceroute. This I-D also briefly explores an alternative to this approach: a new header, of the same length and different, with a different 4 bit Version, to carry 31 bits of ETR address.},
}