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] [policy-announce] 2012-02 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of IPv4 Address Space)
- Previous message (by thread): [address-policy-wg] [policy-announce] 2012-02 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of IPv4 Address Space)
- Next message (by thread): [address-policy-wg] [policy-announce] 2012-02 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of IPv4 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Mon Mar 11 15:44:29 CET 2013
Hi, On Mon, Mar 11, 2013 at 03:31:21PM +0100, Richard Hartmann wrote: > On Mon, Mar 4, 2013 at 2:46 PM, Emilio Madaio <emadaio at ripe.net> wrote: > > > We encourage you to read the draft document text and send any comments > > to address-policy-wg at ripe.net before 18 March 2013. > > Needs a _lot_ more discussion. > > > 1) The impact analysis implies that this applies to RIPE LIRs getting > PA/legacy IP space from non-RIPE RIRs. As I understand the text, this > is not the case. The proposal merely deals with transfer of RIPE > PA/legacy IP space to non-RIPE LIRs. Please read the policy proposal more thoroughly. The wording change to the existing policy only covers "to non-RIPE LIRs" (indeed), but there's a whole new document, the "Inter-RIR transfer policy" - which covers to and from RIPE, starting after the block "[Following text will result in a new RIPE Policy Document ?Policy for Inter-RIR Transfers of IPv4 address space?, if the proposal reaches consensus.]" (The wording change to the existing RIPE IPv4 policy document is needed to avoid a conflict between the new document and the existing policy) Section 2.0 of that new document starts with: "2.0 Transferring IPv4 address space to the RIPE NCC service region" which I find very much to cover "to the RIPE NCC service region"...? [..] > 2) What are the requirements so that another RIR's policy is seen as > "compatible inter-RIR transfer policy"? Who defines this and where? "We permit transfers to RIPE NCC, and transfers from the RIPE NCC, when certain (locally defined) conditions are met" = compatible "We do not permit transfers outside our region" = "incompatible" Explained in more details in the new policy document... > 3) "Increases the supply of IPv4 addresses available to RIPE NCC LIRs" > > Again, I can not see this in the wording of the PDP. If anything, this > decreases the available pool. I am not saying this is good or bad, > merely stating a fact. Please read the document more thoroughly. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- Previous message (by thread): [address-policy-wg] [policy-announce] 2012-02 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of IPv4 Address Space)
- Next message (by thread): [address-policy-wg] [policy-announce] 2012-02 New Draft Document and Impact Analysis Published (Policy for Inter-RIR Transfers of IPv4 Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]