[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AT&T/as7018 now drops invalid prefixes from peers

Subject: AT&T/as7018 now drops invalid prefixes from peers
From: job at instituut.net (Job Snijders)
Date: Tue, 12 Feb 2019 18:48:01 +0000
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <CAP5r2cs0vwpu6HwRSG44eZuwz5veehdG-7AS9oBBpJP2Kcfhtg@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>

On Tue, Feb 12, 2019 at 6:40 PM Owen DeLong <owen at delong.com> wrote:
>
> To be clear, I donâ??t believe they are dropping all routes which donâ??t validate (have no ROAs), only routes where the prefix matches an existing ROA and the origin AS in the AS PATH does not match.

Small addition: routes are not only rejected when the BGP Origin ASN
doesn't match with any of the ROAs, but also if the Prefix Length
doesn't match up. RFC 6811 describes the procedure.

Kind regards,

Job

References:
- AT&T/as7018 now drops invalid prefixes from peers
  - From: jayb at braeburn.org (Jay Borkenhagen)
- AT&T/as7018 now drops invalid prefixes from peers
  - From: valdis.kletnieks at vt.edu (valdis.kletnieks at vt.edu)
- AT&T/as7018 now drops invalid prefixes from peers
  - From: jsweeting at arin.net (John Sweeting)
- AT&T/as7018 now drops invalid prefixes from peers
  - From: owen at delong.com (Owen DeLong)

Prev by Date: AT&T/as7018 now drops invalid prefixes from peers
Next by Date: AT&T/as7018 now drops invalid prefixes from peers
Previous by thread: AT&T/as7018 now drops invalid prefixes from peers
Next by thread: AT&T/as7018 now drops invalid prefixes from peers
Index(es):
- Date
- Thread