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/policy-announce@ripe.net/
[policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Previous message (by thread): [policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [policy-announce] 2011-06 New Draft Document Published (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Milton L Mueller
mueller at syr.edu
Tue Jun 5 16:28:08 CEST 2012
> -----Original Message----- > > Besides publishing a list of v4 resources that have been moved, That is the sum and substance of what 2012-05 is intended to do. It does what ARIN and APNIC already do: provide an accessible list of resources that have been moved according to the transfer policies in place. > what does this accomplish that sub-allocations don't already do? > Is the recipient LIR charged according to the resources under their > registry file? Like the previous question that was raised, you seem to be asking questions about the transfer policy itself, not about this proposal. The transfer policy already exists and it is what it is. All this proposal does it let the community know who is using it, and to better assess and track its consequences. --MM
- Previous message (by thread): [policy-announce] [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [policy-announce] 2011-06 New Draft Document Published (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]