%% You should probably cite draft-ietf-idr-tunnel-encaps instead of this I-D.
@techreport{vandevelde-idr-remote-next-hop-00,
    number =    {draft-vandevelde-idr-remote-next-hop-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-vandevelde-idr-remote-next-hop/00/},
    author =    {Gunter Van de Velde and Keyur Patel},
    title =     {{BGP Remote-Next-Hop}},
    pagetotal = 8,
    year =      2012,
    month =     may,
    day =       24,
    abstract =  {The BGP Remote-Next-Hop optional transitive attribute, provides an additional level of recursive route-lookup. The BGP Remote-Next-Hop attribute can be used, both on the public Internet infrastructure and within public or private Autonomous Systems (AS). The usage of BGP Remote-Next-Hop operates as ships-in-the-night and does not require any capability exchange for any BGP Session. BGP Remote-Next-Hop is providing the distribution of one or more Location Identifiers assigned to a particular BGP prefix or an NLRI. To secure the BGP prefix or NLRI entry BGP security mechanisms, either RPKI or other BGP mechanisms can be utilized.},
}