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] Status of /24 PI IPv4 from last /8
- Previous message (by thread): [address-policy-wg] Status of /24 PI IPv4 from last /8
- Next message (by thread): [address-policy-wg] Status of /24 PI IPv4 from last /8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Farmer
farmer at umn.edu
Tue Nov 6 18:52:20 CET 2012
On 11/6/12 10:48 , Nick Hilliard wrote: > On 06/11/2012 16:32, Tore Anderson wrote: >> 2012-03[*] won't pass soon, and there is no guarantee that it ever will. >> Judging by the discussion it stirred up at the last RIPE meeting, I >> believe it has rather slim chances of reaching consensus. > > I don't think it's all doom and gloom, btw. The comments both on the > mailing list and at the APWG session fell into a couple of different > categories: > > - yes > - no, but would support after 185.0.0.0/8 is exhausted > - no, but would support if potential abuse could be reduced > - no, under no circumstances > > What's clear is that there is no consensus on the current proposal. But I > think that it may be possible to satisfy many of the concerns of the people > who objected if the proposal were modified to e.g. reduce the possibility > of potential abusers, or maybe make it applicable only to reclaimed address > space and not 185.0.0.0/8. As currently written GPP-IPv4-2011 (AKA RIPE-2011-01) says "The Recovered IPv4 Pool will stay inactive until the first RIR has less than a total of a /9 in its inventory of IPv4 address space." So it may be some time before reclaimed address are available to be issued as PI, if you follow the suggested approach. I'm not completely familiar with the nuances of RIPE's policies, but is it possible for organizations that want PI to get it from the transfer market under RIPE's current policies? If not then that probably needs to be fixed ASAP, they probably shouldn't be shutout of both the last /8 and the transfer market. This was brought up in the discussion of 2012-02, but I don't know if it has been resolved to allow PI through transfers, and in particular inter-RIR transfers. I have no opinion on this policy, as I do not receive resources within the RIPE region. But, I will say I think it is important for end user organizations in the RIPE region to have a viable way to get IPv4 resources, be it from the last /8 or via transfers. I think it is highly problematic if there isn't some mechanism that provides for continued PI resource availability. Thanks -- ================================================= David Farmer Email: farmer at umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 =================================================
- Previous message (by thread): [address-policy-wg] Status of /24 PI IPv4 from last /8
- Next message (by thread): [address-policy-wg] Status of /24 PI IPv4 from last /8
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]