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/address-policy-wg@ripe.net/
[address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Mon Sep 25 17:30:29 CEST 2006
Randy Bush wrote: >> Though hopefully it will have public records for ISPs to see who has >> been assigned the IP block through the established process, right? > > if we are lucky, this time next year, you will be able to verify an X.509 > certificate chain with rfc 3779 resource extensions, and have significant > confidence in rights to address and asn resources. As I can understand, I can verify origin of prefix, prefix itself, but it can't authorize is that certain as-path legitimate or not. Like I can figure it out from routing registry DB. Isn't it? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
- Next message (by thread): [address-policy-wg] 2006-05 New Policy Proposal (PI Assignment Size)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]