@techreport{huston-nopeer-00,
    number =    {draft-huston-nopeer-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-huston-nopeer/00/},
    author =    {Geoff Huston},
    title =     {{NOPEER community for BGP route scope control}},
    pagetotal = 6,
    year =      2001,
    month =     aug,
    day =       13,
    abstract =  {This document proposes the use of a scope control BGP community. This new well-known advisory transitive community is intended to allow an origin AS to specify the extent to which a specific route should be externally propagated. In particular this community, termed here as NOPEER, allows the origin AS to specify that a route with this attribute need not be advertised across bilateral peer connections.},
}