nanog mailing list archives
Re: AT&T/as7018 now drops invalid prefixes from peers
From: Job Snijders <job () instituut net>
Date: Tue, 12 Feb 2019 18:48:01 +0000
On Tue, Feb 12, 2019 at 6:40 PM Owen DeLong <owen () 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
Current thread:
- Re: AT&T/as7018 now drops invalid prefixes from peers, (continued)
- Re: AT&T/as7018 now drops invalid prefixes from peers Patrick W. Gilmore (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers Compton, Rich A (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers Jay Borkenhagen (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers Alex Band (Feb 12)
- Re: AT&T/as7018 now drops invalid prefixes from peers Jay Borkenhagen (Feb 14)
- Re: AT&T/as7018 now drops invalid prefixes from peers Jay Borkenhagen (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers Melchior Aelmans (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers valdis . kletnieks (Feb 11)
- Re: AT&T/as7018 now drops invalid prefixes from peers Jay Borkenhagen (Feb 11)
- Message not available
- Message not available
- Re: AT&T/as7018 now drops invalid prefixes from peers John Sweeting (Feb 12)
- Re: AT&T/as7018 now drops invalid prefixes from peers Owen DeLong (Feb 12)
- Re: AT&T/as7018 now drops invalid prefixes from peers Job Snijders (Feb 12)