%% You should probably cite draft-ymbk-grow-bgp-collector-communities-02 instead of this revision.
@techreport{ymbk-grow-bgp-collector-communities-00,
    number =    {draft-ymbk-grow-bgp-collector-communities-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-ymbk-grow-bgp-collector-communities/00/},
    author =    {Randy Bush and Emile Aben},
    title =     {{Marking Announcements to BGP Collectors}},
    pagetotal = 5,
    year =      2015,
    month =     sep,
    day =       4,
    abstract =  {When BGP route collectors such as RIPE RIS and Route Views are used by operators and researchers, currently one can not tell if a path announced to a collector is from the ISP's customer cone, an internal route, or one learned from peering or transit. This greatly reduces the utility of the collected data. This document specifies the use of BGP communities to differentiate the kinds of views being presented to the collectors.},
}