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] FW: FW: discussion about rogue database objects
- Previous message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
- Next message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Nov 13 18:40:19 CET 2014
> You may start with using DNSSEC for securing routing information ... > There was an IETF draft long long ago. draft-bates-bgp4-nlri-orig-verif-00.txt 1998. i was one of the authors. we dropped the approach because the dns based approach can only delegate singly, and make before break kinda wants duality. damn ops stuff keeps getting in the way of idealism :) randy
- Previous message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
- Next message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]