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] 2012-05 Proposal Accepted - Request for Clarification
- Previous message (by thread): [address-policy-wg] 2012-05 Proposal Accepted (Transparency in Address Block Transfers)
- Next message (by thread): [address-policy-wg] 2012-05 Proposal Accepted - Request for Clarification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck
lists-ripe at c4inet.net
Wed Feb 13 13:04:41 CET 2013
Hi, On Tue, Feb 12, 2013 at 03:55:30PM +0100, Emilio Madaio wrote: >The updated RIPE document is ripe-577 and is available at: > >https://www.ripe.net/ripe/docs/ripe-577 ripe-577 contains, in S5.5 the sentence: "Re-allocated blocks will be signed to establish the current allocation owner." What does this refer to? Does this mean these blocks will *mandatorily* be signed with a RPKI certificate and, if yes, how does that square with the NCC's stated policy that RPKI certs will always be voluntary? Regards, Sascha Luck
- Previous message (by thread): [address-policy-wg] 2012-05 Proposal Accepted (Transparency in Address Block Transfers)
- Next message (by thread): [address-policy-wg] 2012-05 Proposal Accepted - Request for Clarification
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]