@techreport{ymbk-grow-bgp-collector-communities-02,
    number =    {draft-ymbk-grow-bgp-collector-communities-02},
    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/02/},
    author =    {Randy Bush and Emile Aben},
    title =     {{Marking Announcements to BGP Collectors}},
    pagetotal = 5,
    year =      2022,
    month =     feb,
    day =       17,
    abstract =  {When BGP route collectors such as RIPE RIS and Route Views are used by operators and researchers, currently one can not tell if the collection of paths announced to a collector represents the ISP's customer cone, includes internal routes, includes paths learned from peerings or transits. 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.},
}