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] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Previous message (by thread): [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
McTim
dogwallah at gmail.com
Tue Jun 5 15:39:02 CEST 2012
On Mon, Jun 4, 2012 at 7:24 AM, Emilio Madaio <emadaio at ripe.net> wrote: > > Dear Colleagues, > > A proposed change to RIPE Document ripe-553, "IPv4 Address Allocation > and Assignment Policies for the RIPE NCC Service Region", is now > available for discussion. Besides publishing a list of v4 resources that have been moved, what does this accomplish that sub-allocations don't already do? Is the recipient LIR charged according to the resources under their registry file? -- Cheers, McTim "A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel
- Previous message (by thread): [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
- Next message (by thread): [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]