Regarding the "Transit inbound IPv4 filters" section it is only a matter of making the text a bit clearer. Just mention that you should only accept back your own prefixes/address space if you have AS customers bellow you that might be advertising more specifics of your own address space. And maybe have a section clarifying this SWIP/LOA agreement between provider and customer.
When that happens you should also be careful with what you accept on your peering sessions or you will end up giving free transit traffic to your customers if they advertise more specifics on those peerings (IXPs are a good example). In theory your customer should not be able to deagreggate the announcement but you cannot enforce that. All you can do is have exact matches on your peerings. Luis On Mon, Nov 3, 2014 at 3:18 AM, Courtney Smith <mr.courtney.smith+...@gmail.com> wrote: > I'm not sure if we should a have separate document for service providers or > address the differences in a single bcop. I always imagined this bcop to > have the most value to the enterprise network engineer. Except for those in > large environments, BGP is probably not part of their daily activities. > > On Nov 2, 2014 10:23 PM, "Barry Greene" <bgre...@senki.org> wrote: >> >> >> >> >> On Nov 2, 2014, at 10:49 AM, Luis Balbinot <l...@luisbalbinot.com> wrote: >> >> > This is not something we see a lot in the LACNIC region. This might be >> > a perfect example of a BCOP that is only good inside it's own region. >> >> I think these difference support the argument that one BCP document will >> not cover all the models for eBGP interconnection. If the goal is to >> influence behavior, then we need BCPs that focus on specific groups. >> Multi-homing enterprises are different from an ISP in Asia or a >> multi-service provider in Asia or an SP in Europe. >> >> >> >> >> _______________________________________________ >> BCOP mailing list >> BCOP@nanog.org >> http://mailman.nanog.org/mailman/listinfo/bcop >> > > _______________________________________________ > BCOP mailing list > BCOP@nanog.org > http://mailman.nanog.org/mailman/listinfo/bcop > _______________________________________________ BCOP mailing list BCOP@nanog.org http://mailman.nanog.org/mailman/listinfo/bcop
