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] RPKI Invalid == Reject policies on the AS 3333 EBGP border
- Previous message (by thread): [routing-wg] RPKI Invalid == Reject policies on the AS 3333 EBGP border
- Next message (by thread): [routing-wg] RPKI Invalid == Reject policies on the AS 3333 EBGP border
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
W. Boot
w.boot at navice.eu
Thu Apr 1 12:38:27 CEST 2021
Would "invalid" also include unsigned space? If it does, that might lead to legacy space or networks getting space through certain NIRs to be accidentally being blocked by whomever relying on this, unless these blocks can be exempt from inclusion? On 2021-03-26 16:46, Paul Hoogsteder wrote: > Dear RIPE Routing WG and RIPE NCC, > > after having gone through all responses on the mailing list there seems > to > be unanimous support for RIPE NCC to proceed with the deployment of > "RPKI > Invalid == Reject" policies on the AS 3333 EBGP border. > > Kind regards, > > Job Snijders & Paul Hoogsteder
- Previous message (by thread): [routing-wg] RPKI Invalid == Reject policies on the AS 3333 EBGP border
- Next message (by thread): [routing-wg] RPKI Invalid == Reject policies on the AS 3333 EBGP border
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]