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]/
Hierarchical Authorisation in the RR
- Previous message (by thread): Hierarchical Authorisation in the RR
- Next message (by thread): (rough) draft agenda for DB-WG mtg. during RIPE 27
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carol Orange
Carol.Orange at ripe.net
Thu May 15 19:20:23 CEST 1997
Hi Curtis, Curtis Villamizar writes: >> This proposal is inadequate. The whole point of hierarchical >> authorization is to add some checks to the CIDR prefix (radix tree) >> hierarchy which this does not address at all. The proposal is not intended to address the question (or provide an implementation) of authorization based on the CIDR prefix hierarchy. There remains much controversy on that point, which I was specifically trying to avoid in order to make progress in an agreed upon direction. My proposal is intended to provide some clearly desirable form of authorization, which everyone seems to want, while the issues surrounding CIDR prefix hierarchical authorization get settled. Perhaps the title "AS Route Announcement Authorization" would be more accurate? Greetings, -- Carol
- Previous message (by thread): Hierarchical Authorisation in the RR
- Next message (by thread): (rough) draft agenda for DB-WG mtg. during RIPE 27
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]