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] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Previous message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Next message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Henk Steenman
Henk.Steenman at ams-ix.net
Wed Oct 26 22:15:04 CEST 2011
I fully support this proposal - Henk Steenman On Oct 26, 2011, at 4:34 PM, Tom Hodgson wrote: > On Tue, 25 Oct 2011, Emilio Madaio wrote: >> >> A proposed change to RIPE Document ripe-530, "IPv4 Address Allocation >> and Assignment Policies for the RIPE NCC Service Region", is now >> available for discussion. >> > > > I do wonder how many special cases we will see crop up before we've let v4 exit stage left, however the benefits brought by the reservation of a /16 for increased network interconnection I think justify the addition to the policy. There is a question of whether the IXP should just become an LIR to receive an allocation that way, however I neither believe that an IXP should be forced into becoming an LIR or that all IXPs necessarily have an appropriate entity with which to do so, especially when they are in the startup phase. > > Therefore I support this policy. > > -- > Tom Hodgson > tom at someaddress.net >
- Previous message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
- Next message (by thread): [address-policy-wg] 2011-05 New Policy Proposal (Safeguarding future IXPs with IPv4 space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]