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/routing-wg@ripe.net/
[routing-wg] DT/AS3320 is enabling Resource Public Key Infrastructure (RPKI) based filtering policies
- Previous message (by thread): [routing-wg] Downtime for RPKI dashboard/API on 20-2-2024 and 21-2-2024
- Next message (by thread): [routing-wg] [ripe-list] DT/AS3320 is enabling Resource Public Key Infrastructure (RPKI) based filtering policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at sobornost.net
Thu Feb 8 19:51:15 CET 2024
Dear Sebastian and Deutsche Telekom colleagues, Congratulations on this milestone! Kind regards, Job On Thu, 8 Feb 2024 at 18:42, <Sebastian-Becker at telekom.de> wrote: > Dear community, > > > > The Deutsche Telekom/AS3320 network is continuously evolving to provide > best-in-class IP services, connectivity, and stability to its eBGP peers. > As part of this evolution, DT will enable Resource Public Key > Infrastructure (RPKI) based filtering policies within the AS3320 network. > This means that in the future we won't accept any prefixes that are > advertised with an incorrect matching RPKI ROA record. Prefixes validated > as "unknown" will still be accepted. > > > > This implementation will discard RPKI invalid prefixes. > > All advertisements received by the DT network are verified against an > encrypted Route Origin Authorization (ROA) registered with the appropriate > Regional Internet Registry (RIR). This will help ensure the authenticity of > routing information received and distributed within DT's network and > prevent accidental or malicious route hijacking. > > The RPKI validation functionality will be fully functional during Q1 2024. > > > > Please note that after RPKI-based filtering is enabled, RPKI invalid > prefix(es) received by the AS3320 will be discarded. To correct INVALID > prefixes, please use the Regional Internet Registry's record of IP > resources to correct or create the appropriate ROAs. Or encourage your > customers to correct the entries. > > For additional questions or needed information, please contact me and I > will loop in the necessary teams from DT. > > > > -- > > Kind Regards > > > *Sebastian Becker * > *DEUTSCHE TELEKOM GLOBAL CARRIER * > *Internet, Content and Security Solutions (ICS) * > > *Sebastian Becker Global Peering Manager (AS3320) **globalcarrier.telekom.com > <https://globalcarrier.telekom.com>* > > *LIFE IS FOR SHARING. * > > *You can find the obligatory information on **www.telekom.de/compulsory-statement > <https://www.telekom.de/compulsory-statement>* > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/ripe-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20240208/29ecf8ee/attachment.html>
- Previous message (by thread): [routing-wg] Downtime for RPKI dashboard/API on 20-2-2024 and 21-2-2024
- Next message (by thread): [routing-wg] [ripe-list] DT/AS3320 is enabling Resource Public Key Infrastructure (RPKI) based filtering policies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]