> On Nov 21, 2023, at 7:42 AM, Dale W. Carder wrote:
>
> Thus spake Tom Samplonius (t...@samplonius.org) on Mon, Nov 20, 2023 at
> 07:02:52PM -0800:
>>> On Nov 17, 2023, at 6:58 AM, Christopher Morrow
>>> wrote:
>>> IRR filters provide control over whom is provided reachability through
>>>
Thus spake Tom Samplonius (t...@samplonius.org) on Mon, Nov 20, 2023 at
07:02:52PM -0800:
> > On Nov 17, 2023, at 6:58 AM, Christopher Morrow
> > wrote:
> > IRR filters provide control over whom is provided reachability through
> > a particular peering/path.
>
> How does that work? IRR
> On Nov 17, 2023, at 6:58 AM, Christopher Morrow
> wrote:
>
>> On Thu, Nov 16, 2023 at 9:31 PM Tom Samplonius wrote:
>
>>> The most surprising thing in the DE-DIX flow chart, was that they check
>>> that the origin AS exists in the IRR as-set, before doing RPKI, and if the
>>> set
To: nanog@nanog.org
Sent: Thursday, November 16, 2023 6:54:17 PM
Subject: Generally accepted BGP acceptance criteria?
In the world of IRR and RPKI, BGP route acceptance criteria is important to get
right.
DE-CIX has published a detailed flow chart documenting their acceptance
criteria: http
> On Thu, Nov 16, 2023 at 9:31 PM Tom Samplonius wrote:
>> The most surprising thing in the DE-DIX flow chart, was that they check
>> that the origin AS exists in the IRR as-set, before doing RPKI, and if the
>> set existence fails, they reject the route. I don’t see a problem with
>>
Thus spake Tom Samplonius (t...@samplonius.org) on Thu, Nov 16, 2023 at
04:54:17PM -0800:
>
> In the world of IRR and RPKI, BGP route acceptance criteria is important to
> get right.
>
> DE-CIX has published a detailed flow chart documenting their acceptance
> criteria:
Also, you don't want to accept Google prefixes from your customer, even
if they are ROV valid.
i.e. you want to restrict what you accept to customer and customer's
customer prefixes...
Frank
On 17/11/2023 08:38, Pierfrancesco Caci wrote:
If you need to support RTBH you need to check prefix
If you need to support RTBH you need to check prefix list (thus IRR) first,
then the RTBH , then RPKI. Otherwise blackhole route gets dropped before
executing.
>
> I imagine there is a some sort of coalescing industry standard out there,
> but so far I can’t find it.
>
There is not, and won't be for a long time, if ever.
There isn't a one size fits all solution.
On Thu, Nov 16, 2023 at 9:31 PM Tom Samplonius wrote:
>
> In the world of IRR and
In the world of IRR and RPKI, BGP route acceptance criteria is important to
get right.
DE-CIX has published a detailed flow chart documenting their acceptance
criteria: https://www.de-cix.net/en/locations/frankfurt/route-server-guide
But I don’t see a lot of operators publishing their
10 matches
Mail list logo
