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/connect-wg@ripe.net/
[connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call
- Previous message (by thread): [connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call
- Next message (by thread): [connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Wed Jun 5 18:28:44 CEST 2024
stravos: first: sorry i try not not to do walls of text. i also tend not to read them. life is short. > can you please elaborate a bit more regarding your concern on the > concentration of authority? Let me ask you quickly a question: Aren’t > we doing this already with RPKI system? somewhat over twenty years ago, when we were designing rpki and its initial uses, i pushed strongly on this issue. unfortunately, non- hierarchic trust research lagged, and still lags, hierarchic by decades. so much for web of trust. the ip resource alocation administrative *authority* is hierarchic, iana, rirs, lirs, ... the irr authority is not necessarily a hierarchy. i trust NTT because they have proven to be a trustworthy peer, not because APNIC says to. and lastly, the rpki does provide for and encourage CA distribution. unfortunately hierarchic, see above. > it had 5 root TALs only it was designed to have one, iana randy
- Previous message (by thread): [connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call
- Next message (by thread): [connect-wg] BCOP for the use of IRR DBs in IXP RS - Last call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]