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]/
Heads up: Long AS-sets announced in the next few days
- Previous message (by thread): Heads up: Long AS-sets announced in the next few days
- Next message (by thread): New AS Number Block allocated to the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Massar
jeroen at unfix.org
Thu Mar 3 20:19:24 CET 2005
On Thu, 2005-03-03 at 13:51 -0500, Blaine Christian wrote: >And, of course, the RPSEC working group draft that is supposed to target the >BGP requirements for those proposed systems is... > >http://www.ietf.org/internet-drafts/draft-ietf-rpsec-bgpsecrec-01.txt > >The folks who worked on S-BGP and SO-BGP participated in it's creation (as >well as several operators). Please note that there are more than just two >proposed mechanisms for securing BGP. The two mentioned above are just the >most popular <grin>. Thanks for the new reading material, I had not seen that one yet... *print* will be a nice read (hmmm, actually I should swear at you for even more reading material, for which I have no time, oh well :) Greets, Jeroen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 240 bytes Desc: This is a digitally signed message part URL: </ripe/mail/archives/routing-wg/attachments/20050303/70f0dbaa/attachment.sig>
- Previous message (by thread): Heads up: Long AS-sets announced in the next few days
- Next message (by thread): New AS Number Block allocated to the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]