This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] NTT/AS2914 enabled RPKI OV 'invalid = reject' EBGP policies
- Previous message (by thread): [routing-wg] NTT/AS2914 enabled RPKI OV 'invalid = reject' EBGP policies
- Next message (by thread): [routing-wg] NTT/AS2914 enabled RPKI OV 'invalid = reject' EBGP policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Sat Apr 4 13:55:09 CEST 2020
On Sat, Apr 04, 2020 at 10:20:38AM +0200, Tijn Buijs wrote: > On 2020-03-26 02:09, Job Snijders wrote: > > Exciting news! Today NTT's Global IP Network (AS 2914) enabled RPKI > > based BGP Origin Validation on virtually all EBGP sessions, both > > customer and peering edge. This change positively impacts the > > Internet routing system. > > It is the word "virtually" that triggers me :), because in my mind it > translates to "not all of them". Why haven't you enabled it on all our > EBGP sessions? Currently, a number of technical caveats affects our ability for 100% deployment. As a result a limited number of RPKI invalid route announcements are still propagated to EBGP peers. We are developing technical workarounds and engaging vendors in order to enable us to gradually decrease this number in the coming months. We remain committed to global RPKI deployment, and we will provide updates on our progress from time to time as we work to reduce this number to zero. Kind regards, Job
- Previous message (by thread): [routing-wg] NTT/AS2914 enabled RPKI OV 'invalid = reject' EBGP policies
- Next message (by thread): [routing-wg] NTT/AS2914 enabled RPKI OV 'invalid = reject' EBGP policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]