routing-wg  

Messages by Thread

• [routing-wg] RPKI Outage on 16.02.2023 Stella Vouteva
• [routing-wg] RPKI Publication Server v2.0 Bart Bakker
• [routing-wg] Guide to using RIPE NCC's RPKI Publication Service Alex Band
• [routing-wg] RPKI's 2022 Year in Review: growth & innovation Job Snijders via routing-wg
• [routing-wg] Extending the consultation period for service criticality Razvan Oprea
  • Re: [routing-wg] Extending the consultation period for service criticality Razvan Oprea
  • [routing-wg] Service Criticality Ratings Finalised Razvan Oprea
• [routing-wg] Proposed Service Criticality Form Nathalie Trenaman
  • Re: [routing-wg] Proposed Service Criticality Form Job Snijders via routing-wg
  • Re: [routing-wg] Proposed Service Criticality Form Job Snijders via routing-wg
  • Re: [routing-wg] Proposed Service Criticality Form Tijn Buijs
• [routing-wg] RPKI Quarterly Planning Q1 2023 Nathalie Trenaman
• [routing-wg] RPKI ROAs and Monitoring Klaus Darilion via routing-wg
  • Re: [routing-wg] RPKI ROAs and Monitoring Job Snijders via routing-wg
  • Re: [routing-wg] RPKI ROAs and Monitoring Massimo Candela
  • Re: [routing-wg] RPKI ROAs and Monitoring Randy Bush
  • Re: [routing-wg] RPKI ROAs and Monitoring Klaus Darilion via routing-wg
  • Re: [routing-wg] RPKI ROAs and Monitoring Massimo Candela
  • Re: [routing-wg] RPKI ROAs and Monitoring Massimo Candela
  • Re: [routing-wg] RPKI ROAs and Monitoring Randy Bush
  • Re: [routing-wg] RPKI ROAs and Monitoring Tim Bruijnzeels
• [routing-wg] Format change for index pages of RIS MRT data files and RIPE Atlas daily dataset dumps Oleg Muravskiy
• [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB Sasha Romijn
  • Re: [routing-wg] Adding "::" notation to RIPE DB Sander Steffann
  • Re: [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Jared Mauch
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Jared Mauch
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Alexander Zubkov via routing-wg
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Arnold Nipper
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Arnold Nipper
  • Re: [routing-wg] Adding "::" notation to RIPE DB Cynthia Revström via routing-wg
  • Re: [routing-wg] Adding "::" notation to RIPE DB Carlos Friaças via routing-wg
  • Re: [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB Alexander Zubkov via routing-wg
  • Re: [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB Netmaster (exAS286)
  • Re: [routing-wg] Adding "::" notation to RIPE DB Edward Shryane
  • Re: [routing-wg] Adding "::" notation to RIPE DB James Bensley
  • Re: [routing-wg] Adding "::" notation to RIPE DB Radu-Adrian FEURDEAN
  • Re: [routing-wg] Adding "::" notation to RIPE DB Randy Bush
• [routing-wg] Detecting, mitigating, and preventing distributed large-scale prefix de-aggregation attacks Lars Prehn
  • Re: [routing-wg] Detecting, mitigating, and preventing distributed large-scale prefix de-aggregation attacks Nick Hilliard
  • Re: [routing-wg] Detecting, mitigating, and preventing distributed large-scale prefix de-aggregation attacks Lars Prehn
• [routing-wg] European cable cut may impact transoceanic routes Hank Nussbacher
  • Re: [routing-wg] European cable cut may impact transoceanic routes Nick Hilliard
  • Re: [routing-wg] European cable cut may impact transoceanic routes Hank Nussbacher
  • Re: [routing-wg] European cable cut may impact transoceanic routes Stephane Bortzmeyer
• [routing-wg] Publish in Parent - input requested Felipe Victolla Silveira
  • Re: [routing-wg] Publish in Parent - input requested Erik Bais
  • Re: [routing-wg] Publish in Parent - input requested Randy Bush
  • Re: [routing-wg] Publish in Parent - input requested Erik Bais
  • Re: [routing-wg] Publish in Parent - input requested Randy Bush
  • Re: [routing-wg] Publish in Parent - input requested Erik Bais
  • Re: [routing-wg] Publish in Parent - input requested David Farmer via routing-wg
  • Re: [routing-wg] Publish in Parent - input requested Erik Bais
  • Re: [routing-wg] Publish in Parent - input requested David Farmer via routing-wg
  • Re: [routing-wg] Publish in Parent - input requested Jay Borkenhagen
  • Re: [routing-wg] [EXTERNAL] Publish in Parent - input requested Compton, Rich A
  • Re: [routing-wg] Publish in Parent - input requested Tim Bruijnzeels
  • Re: [routing-wg] Publish in Parent - input requested Lukas Tribus
  • Re: [routing-wg] Publish in Parent - input requested Cynthia Revström via routing-wg
  • Re: [routing-wg] Publish in Parent - input requested Ignas Bagdonas
  • Re: [routing-wg] Publish in Parent - input requested Felipe Victolla Silveira
  • Re: [routing-wg] Publish in Parent - input requested Randy Bush
  • Re: [routing-wg] Publish in Parent - input requested Randy Bush
  • Re: [routing-wg] Publish in Parent - input requested Erik Bais
  • Re: [routing-wg] Publish in Parent - input requested Felipe Victolla Silveira
  • Re: [routing-wg] Publish in Parent - input requested Randy Bush
  • Re: [routing-wg] Publish in Parent - input requested Felipe Victolla Silveira
  • [routing-wg] Publish in Parent - input requested Alex Le Heux
• [routing-wg] RPKI Quarterly Planning Q4 2022 Ties de Kock
• [routing-wg] Inconsistent repository state for rrdp.ripe.net Bart Bakker
• [routing-wg] Call for Working Group Participation: MANRS+ Andrei Robachevsky via routing-wg
• [routing-wg] HTTP 404 Errors for rrdp.ripe.net Ties de Kock
• [routing-wg] Call for presentation Routing WG at RIPE85 (Belgrade, Serbia) Job Snijders via routing-wg
  • Re: [routing-wg] Call for presentation Routing WG at RIPE85 (Belgrade, Serbia) Job Snijders via routing-wg
• [routing-wg] (no subject) Hose Fhcnk
• [routing-wg] Notice of Upcoming Test of RPKI Infrastructure Brad Gorman
• [routing-wg] Announcement of new RIS prototype services Oleg Muravskiy
• [routing-wg] New on RIPE Labs: Where Did My Packet Go? Measuring the Impact of RPKI ROV Alun Davies
• [routing-wg] Frequently Asked Questions about 2000::/12 and related routing errors Job Snijders via routing-wg
  • Re: [routing-wg] Frequently Asked Questions about 2000::/12 and related routing errors Niall O'Reilly
• [routing-wg] RPKI Quarterly Planning Q3 2022 Nathalie Trenaman
• [routing-wg] RPKI Service Criticality Questionnaire Job Snijders via routing-wg
  • Re: [routing-wg] RPKI Service Criticality Questionnaire Randy Bush
  • Re: [routing-wg] RPKI Service Criticality Questionnaire Booth, Mike via routing-wg
  • Re: [routing-wg] RPKI Service Criticality Questionnaire Nathalie Trenaman
• [routing-wg] RPKI Outage on 23 June 2022 from 10:50 UTC - 12:00 UTC Stella Vouteva
  • Re: [routing-wg] RPKI Outage on 23 June 2022 from 10:50 UTC - 12:00 UTC Stella Vouteva
• [routing-wg] Join our Open House on BGP Security for Ukrainian Operators Alastair Strachan
• [routing-wg] New on RIPE Labs: An Introduction to IRR Explorer Alun Davies
• [routing-wg] state of RPKI-invalid objects in IRR databases (2022.05.16) Job Snijders via routing-wg
• [routing-wg] RIPE-84 talk about RIPE RPKI core Bart Bakker
• [routing-wg] New on RIPE Labs: Securing the RIPE NCC Trust Anchor Alun Davies
• [routing-wg] Follow up: RIPE NCC Open House - RPKI Data Nathalie Trenaman
• [routing-wg] follow-up on RPKI open house: are CRLs used? Job Snijders via routing-wg
• [routing-wg] HTTP 503 responses for rrdp.ripe.net for locations in the United States Ties de Kock
• [routing-wg] Call for presentation Routing WG at RIPE84 Berlin Paul Hoogsteder
• [routing-wg] Join RIPE NCC Open House on RPKI Data, 4 May at 14 UTC / 16 CEST gpetrova
  • [routing-wg] Join RIPE NCC Open House on RPKI Data: Today at 14 UTC / 16 CEST Gergana Petrova
  • Re: [routing-wg] Join RIPE NCC Open House on RPKI Data: Today at 14 UTC / 16 CEST Sander Steffann
• [routing-wg] New on RIPE Labs: Detecting DNS Root Manipulation Alun Davies
• [routing-wg] Fw: 2749 routes AT RISK - Re: TIMELY/IMPORTANT - Approximately 40 hours until potentially significant routing changes (re: Retirement of ARIN Non-Authenticated IRR scheduled for 4 April 2022) Job Snijders via routing-wg
• [routing-wg] RPKI Quarterly Planning Q2 2022 Nathalie Trenaman
• [routing-wg] CFP for Workshop on Future of Internet Routing & Addressing Randy Bush
• [routing-wg] RFO for RIPE NCC RRDP outage 24 March 2022 Stella Vouteva
  • Re: [routing-wg] RFO for RIPE NCC RRDP outage 24 March 2022 Lukas Tribus
  • Re: [routing-wg] RFO for RIPE NCC RRDP outage 24 March 2022 Stella Vouteva
• [routing-wg] misconceptions about ROV Randy Bush
• [routing-wg] RPKI vulnerable? Hank Nussbacher
  • Re: [routing-wg] RPKI vulnerable? Nick Hilliard
  • Re: [routing-wg] RPKI vulnerable? Nathalie Trenaman
  • Re: [routing-wg] RPKI vulnerable? Job Snijders via routing-wg
  • Re: [routing-wg] RPKI vulnerable? Warren Kumari
  • Re: [routing-wg] RPKI vulnerable? Nick Hilliard
  • Re: [routing-wg] RPKI vulnerable? Warren Kumari
  • Re: [routing-wg] RPKI vulnerable? Randy Bush
  • Re: [routing-wg] RPKI vulnerable? Lukas Tribus
  • Re: [routing-wg] RPKI vulnerable? Rubens Kuhl
  • Re: [routing-wg] RPKI vulnerable? Maria Matejka
  • Re: [routing-wg] RPKI vulnerable? Hank Nussbacher
  • Re: [routing-wg] RPKI vulnerable? Nathalie Trenaman
• [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Ties de Kock
  • Re: [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Gert Doering
  • Re: [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Hank Nussbacher
  • Re: [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Randy Bush
  • Re: [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Job Snijders via routing-wg
  • Re: [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022 Job Snijders via routing-wg
• [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low? Job Snijders via routing-wg
  • Re: [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low? Job Snijders via routing-wg
  • Re: [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low? Ties de Kock
  • Re: [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low? Job Snijders via routing-wg
• Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Cynthia Revström via routing-wg
• [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Bart Bakker
  • Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Job Snijders via routing-wg
  • Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Bart Bakker
  • Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Jeroen Massar via routing-wg
  • Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Shane Kerr
  • Re: [routing-wg] Open-sourcing of the RIPE NCC???s RPKI core software Gert Doering
  • Re: [routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software Cynthia Revström via routing-wg
• [routing-wg] Decommissioning public experimental rsync environment (rpki2.ripe.net) Ties de Kock
• [routing-wg] Issues with RIPE NCC services affecting RPKI Ties de Kock
• [routing-wg] New on RIPE Labs: PeeringDB 2021 Product Report Alun Davies
• [routing-wg] RPKI Quarterly Planning Q1 2022 Nathalie Trenaman
• [routing-wg] Penetration Test Report for RPKI Bart Bakker
  • Re: [routing-wg] Penetration Test Report for RPKI Randy Bush
  • Re: [routing-wg] Penetration Test Report for RPKI Job Snijders via routing-wg
  • Re: [routing-wg] Penetration Test Report for RPKI Ties de Kock
• [routing-wg] RPKI ROA MaxLength - feature or misfeature? (UX/security) Job Snijders via routing-wg
  • Re: [routing-wg] RPKI ROA MaxLength - feature or misfeature? (UX/security) Lukas Tribus
• [routing-wg] Code Audit Report for RPKI Bart Bakker
  • Re: [routing-wg] Code Audit Report for RPKI Job Snijders via routing-wg
  • Re: [routing-wg] Code Audit Report for RPKI Bart Bakker
• [routing-wg] New on RIPE Labs: Should You Update Your Route Flap Damping Parameters? Alun Davies
• [routing-wg] New on RIPE Labs: Improving the Resiliency of RPKI Relying Party Software Alun Davies
• [routing-wg] Changes to RRDP repository postponed - new RPKI rp/validator software releases tomorrow 15:00 CET Ties de Kock
• [routing-wg] Changes to the RRDP repository Ties de Kock
  • Re: [routing-wg] Changes to the RRDP repository Randy Bush
  • Re: [routing-wg] Changes to the RRDP repository Ties de Kock
• [routing-wg] Relative size of IRR registries Rubens Kuhl
  • Re: [routing-wg] Relative size of IRR registries Aliaksei Sheshka
  • Re: [routing-wg] Relative size of IRR registries Rubens Kuhl
• [routing-wg] Too large AS-sets Antti Ristimäki
• [routing-wg] Your opinion on Internet monitoring and measurements - a 10min survey Pavlos Sermpezis
• [routing-wg] New on RIPE Labs: Hunting Routing Resources with IRRHound Alun Davies
• [routing-wg] RPKI Quarterly Planning Q4 2021 Nathalie Trenaman
• [routing-wg] Call for presentation Routing WG at RIPE83 Paul Hoogsteder
• [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?) Job Snijders via routing-wg
  • Re: [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?) Nathalie Trenaman
  • Re: [routing-wg] RPKI planning @ RIPE (Was: Support for "Publish in Parent" [RPKI RFC 8181]?) Job Snijders via routing-wg
• [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Job Snijders via routing-wg
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Nathalie Trenaman
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Randy Bush
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Job Snijders via routing-wg
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Randy Bush
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Rubens Kuhl
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Randy Bush
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Randy Bush
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Tim Bruijnzeels
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Rubens Kuhl
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Job Snijders via routing-wg
  • Re: [routing-wg] Support for "Publish in Parent" [RPKI RFC 8181]? Erik Bais
• [routing-wg] Add BGPsec support to Hosted RPKI? Job Snijders via routing-wg
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Rubens Kuhl
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Job Snijders via routing-wg
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Nick Hilliard
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Job Snijders via routing-wg
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? marco
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Simon Muyal
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Ehsan Ghazizadeh
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Job Snijders via routing-wg
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Randy Bush
  • Re: [routing-wg] Add BGPsec support to Hosted RPKI? Marco Marzetti

• Earlier messages
• Later messages