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]/
[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 ]
bmanning at vacation.karoshi.com
bmanning at vacation.karoshi.com
Mon Sep 25 20:36:48 CEST 2006
On Mon, Sep 25, 2006 at 06:43:40AM -1000, Randy Bush wrote: > >> 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? > > the current work will provide a formally verifiable demonstration of > ownership of address space. wow... address ownership. thats kind of a new concept. last i checked, most RIRs deal with the concept of address stewardship. does that mean i can assert ownership of integers and the RIR system will back me up? > one first useful step for an isp is to use the x.509 data to verify > ownership assertions in the irr when building filter lists, for > example. > randy --bill
- 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 ]