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] Call for Presentations - RIPE 82
- Previous message (by thread): [routing-wg] Call for Presentations - RIPE 82
- Next message (by thread): [routing-wg] Call for Presentations - RIPE 82
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Lothberg
roll at Stupi.SE
Sat Mar 20 00:23:03 CET 2021
Job, Are you saying that the routing WG does not do it's job as you are suggesting that "routing problems" might disrupt the presentations? I suggest that everyone go back to work and fix their networks for everyone benefit, or do we need o have "routing 101? I can redo one of the BGP4 talks from beginning of 1990's if we forgot it all.. Today, any (forwarding) disruption longer than 200ms is unacceptable. (Did you make sure your vendor did the right thing in their HW/SW?) -Peter > > We'll ask presenters to pre-recorded their talk to try to prevent local, > logistcal, and/or routing problems from impacting the meeting. :-) > > Kind regards, > > Job, Paul, Ignas > Routing Working Group Chairs
- Previous message (by thread): [routing-wg] Call for Presentations - RIPE 82
- Next message (by thread): [routing-wg] Call for Presentations - RIPE 82
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]