%% You should probably cite draft-raszuk-idr-bgp-pr-05 instead of this revision.
@techreport{raszuk-idr-bgp-pr-00,
    number =    {draft-raszuk-idr-bgp-pr-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-raszuk-idr-bgp-pr/00/},
    author =    {Robert Raszuk},
    title =     {{BGP Path Record Attribute}},
    pagetotal = 10,
    year =      2014,
    month =     jul,
    day =       23,
    abstract =  {BGP protocol today contains number of build in mechanisms which record critical for its loop free operation data along the path of BGP message propagation. Those are encoded in AS\_PATH, CLUSTER\_LIST or ORIGINATOR\_ID attributes. However in the same time there is no provisioning to record other useful information along the path which can be helpful to the operator in order to enhance end to end visibility of BGP control plane. In order to solve this problem this document proposes a new single BGP attribute designed as an generic and extensible container to carry number of new optional information corresponding to the BGP speakers given BGP advertisement (or withdraw) message traverses.},
}