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] network failed, was re: Notification of RIPE Database changes
- Previous message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
- Next message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Sun Jun 16 06:57:31 CEST 2013
Randy Bush wrote: > [ discussion about st00pidity omitted ] > > >>Generally (no warranty expressed or implied) the only thing you need >>to worry about is that the correct objects are present and protected >>from change by others with an appropriate maintainer. You hope that >>all other objects referring to the same routes are benign, in the >>sense that although they would potentially allow a bad thing to >>happen, at least they don't mess with the good thing that you want to >>happen. > > > which is what seems to be what happened here, though i do not completely > understand. was hoping someone could explain the sequence of events, > and what alan should/could have done. > > randy Randy, all, I already do have a response (and sort of explanation) from the NCC DB folks. I received it just before hopping on a plane to Asia. I'll dig it up soon and forward to the list. Sorry for the delay, Wilfried.
- Previous message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
- Next message (by thread): [routing-wg] network failed, was re: Notification of RIPE Database changes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]