%% You should probably cite draft-ietf-idr-tunnel-encaps instead of this I-D.
@techreport{rosen-idr-tunnel-encaps-01,
    number =    {draft-rosen-idr-tunnel-encaps-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-rosen-idr-tunnel-encaps/01/},
    author =    {Eric C. Rosen and Keyur Patel and Gunter Van de Velde},
    title =     {{Using the BGP Tunnel Encapsulation Attribute without the BGP Encapsulation SAFI}},
    pagetotal = 28,
    year =      2015,
    month =     jul,
    day =       6,
    abstract =  {RFC 5512 defines a BGP Path Attribute known as the "Tunnel Encapsulation Attribute". This attribute allows one to specify a set of tunnels. For each such tunnel, the attribute can provide additional information used to create a tunnel and the corresponding encapsulation header, and can also provide information that aids in choosing whether a particular packet is to be sent through a particular tunnel. RFC 5512 states that the attribute is only carried in BGP UPDATEs that have the "Encapsulation Subsequent Address Family (Encapsulation SAFI)". This document updates RFC 5512 by removing that restriction, and by specifying semantics for the attribute when it is carried in UPDATEs of certain other SAFIs. This document also extends the attribute by enabling it to carry additional information needed to create the encapsulation headers additional tunnel types not mentioned in RFC 5512. Finally, this document also extends the attribute by allowing it to specify a remote tunnel endpoint address for each tunnel.},
}