- address-policy-wg - mailman.ripe.net

Re: [address-policy-wg] 2012-02 Discussion Period extended until 22 October 2012 (Policy for Inter-RIR Transfers of IPv4 Address Space)
by sandrabrown＠ipv4marketgroup.com 25 Sep '12

25 Sep '12

Thank you for your comments Tore. --------------------------------------------------------------- I support this proposal, but wonder why it specifically refers to LIRs rather than something generic like ?organisations?? That excludes transfers of direct assignments to/from End Users [who are not also LIRs]. In other places, the text refers to ?any IPv4 address space?, which seems to indicate that direct assignments are in scope, too. --------------------------------------------------------------- I am quite willing to change the wording from LIR's to Organizations if all agree. Then all five transfer examples defined by Tore would be allowed. --------------------------------------------------------------- Finally, an editorial/language feedback: ?Apart from transfers of address space within the service region of the RIPE NCC, this policy defines the framework that outlines what specific rules apply to IPv4 address space transfers in between the different RIR regions.? --------------------------------------------------------------- I agree with Tore's editorial change. This sentence will now read: This policy defines the framework that outlines specific rules which apply to IPv4 address space transfer between the RIR regions. Thank you. Sandra Brown IPv4 Market Group sandrabrown(a)ipv4marketgroup.com

1 0

Re: [address-policy-wg] 2012-02 Discussion Period extended until 22 October 2012 (Policy for Inter-RIR Transfers of IPv4 Address Space)
by Tore Anderson 25 Sep '12

25 Sep '12

* Emilio Madaio > The Discussion Period for the proposal 2012-02,"Policy for Inter-RIR > Transfers of IPv4 Address Space", has been extended until 22 October > 2012. I support this proposal, but wonder why it specifically refers to LIRs rather than something generic like «organisations»? That excludes transfers of direct assignments to/from End Users [who are not also LIRs]. In other places, the text refers to «any IPv4 address space», which seems to indicate that direct assignments are in scope, too. While it is the case that the RIPE region currently does not have a transfer policy for assignments, that may change in the future. I don't know about other regions (but obviously policies may change here too). Some hypothetical examples (I am assuming we are not running into any restrictions found in the remote region's transfer policy): 1) A RIPE region LIR wants to transfer and unused IPv4 allocation to an out-of-region End User (who is not a LIR), which will register the prefix in the Destination RIR's database as a direct assignment. 2) Same as #1, but the End User happens to also be a LIR. 3) An out-of-region End User (who is not a LIR), has a unused IPv4 direct assignment he wishes to transfer to a RIPE region LIR, who intend to register the prefix in the RIPE database as ALLOCATED PA. 4) Same as #3, only that the End User happens to also be a LIR. As I understand the proposed policy, #1 and #3 would not be allowed, but #2 and #4 would. Is my understanding correct? Also, assuming that a transfer policy has since been established in the RIPE region covering transfers of direct assignments: 5) Out-of-region End User wants to transfer a direct assignment to a RIPE region End User. Neither are LIRs. This would not be permitted by this policy either, correct? Finally, an editorial/language feedback: «Apart from transfers of address space within the service region of the RIPE NCC, this policy defines the framework that outlines what specific rules apply to IPv4 address space transfers in between the different RIR regions.» Native speakers please correct me if I'm wrong, but I've been taught that if you say «Apart from This, That» in English, the logical interpretation of that statement is "This AND That" (with an emphasis on "That"). It is however fairly clear from reading the rest of the proposal that the intended logical meaning in this case is "not(This) AND That". I don't think it particularly good form to start a policy with a statement of what it *isn't*, so I would suggest simply deleting the entire «Apart from transfers of address space within the service region of the RIPE NCC,» text. It is redundant in any case, as section 1.1 clearly declares in-region transfers as being out of scope. -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/

1 0

Re: [address-policy-wg] 2012-03 Discussion Period extended until 22 October 2012 (Intra-RIR transfer policy)
by Tore Anderson 24 Sep '12

24 Sep '12

* Emilio Madaio > We encourage you to review this policy proposal and send your comments > to <address-policy-wg(a)ripe.net> before 22 October 2012. I am really struggling with this sentence: «Other than for an additional allocation, for the purpose of determining need, a period of 24 months is used in evaluating a transferred allocation.» The interpretation I eventually ended up with, is that it means that the new 24 month period only comes into effect for initial allocations, i.e., only for transfers where the recipient LIR holds no IPv4 PA allocations. For transfers where the recipient LIR has an additional allocation, the effective need period will still be three months. Is that correct? In any case, I think it would be good this sentence could be rewritten so it is easier to understand. Another thing I am wondering about, is the new 24 month period. Prior to «Run Out Fairly», the period was 12 months. This was determined by 2006-06, which intended to harmonise the need period across the five regions. With that in mind, I would like to see why 24 months was chosen. Is 2006-06's rationale no longer valid? What are the need periods currently used for allocation transfers in the other regions? Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/

1 0

2012-03 Discussion Period extended until 22 October 2012 (Intra-RIR transfer policy)
by Emilio Madaio 24 Sep '12

24 Sep '12

Dear Colleagues, The text of the policy proposal 2012-03, "Intra-RIR transfer policy" has been revised. We have published the new version (version 2.0) today. As a result a new Discussion Phase is set for the proposal until 22 October 2012. Highlights of the changes: -additional wording on the second paragraph of section 5.5 You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-03 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net> before 22 October 2012. Regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

2012-02 Discussion Period extended until 22 October 2012 (Policy for Inter-RIR Transfers of IPv4 Address Space)
by Emilio Madaio 24 Sep '12

24 Sep '12

Dear Colleagues, The Discussion Period for the proposal 2012-02,"Policy for Inter-RIR Transfers of IPv4 Address Space", has been extended until 22 October 2012. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-02 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

Temporary Internet Assignments policy
by Nick Hilliard 19 Sep '12

19 Sep '12

There's a thread on nanog-l at the moment about temporary internet assignments: > http://mailman.nanog.org/pipermail/nanog/2012-September/051655.html I had already booked a slot in the AP-WG under AOB to talk about this because the policy is broken and needs fixing. Specifically, the timescales specified in the policy allow the assignment to be made one week before use: the consistent feedback is that this isn't enough time for large conference organisers to get things organised in time. The problems we're trying to address are: - enough time for debogonisation - enough time for pre-configuring equipment prior to shipment (which can be weeks in advance) - not knowing well in advance what address ranges you're going to get causes massive headaches, which is exactly what you don't need coming up to a frenzied configuration - conference attendees often arrive several days earlier than the conference formally starts, and they expect teh interwebs to work There are a couple of options for dealing with this: 1. specify new time limits (e.g. receive one month in advance, hand back one week after) 2. don't specify time limits but allow the IPRAs to have discretion on what seems sensible to them 3. keep the current time limits but ask the RIPE NCC whether it would be possible to implement a booking system. I.e. your assignment would only be active during the requested time period, but you would know well in advance what the options were. If anyone has opinions on which of these they prefer (or any other suggestions on how to deal with the issue), can you either post here or let me know off-list and I'll summarise at RIPE65 in advance of posting a policy amendment for ripe-526 shortly after the meeting? Nick

10 12

RIPE 553 & last /8 <-> Anycast assignments
by Carsten Schiefner 18 Sep '12

18 Sep '12

All - as I have just discussed this privately with a colleague: is it the case that as a side effect of section 5.6 "Use of last /8 for PA Allocations" of RIPE 553: https://www.ripe.net/ripe/docs/ripe-553#-----use-of-last-8-for-pa-allocatio… there won't be any more Anycast assignments following section 6.9 "Anycasting TLD and Tier 0/1 ENUM Nameservers" of this policy: https://www.ripe.net/ripe/docs/ripe-553#-----anycastying-tld-and-tier-1-enu… either? As such 'Assignments for authoritative TLD or ENUM Tier 0/1 DNS lookup services are subject to the policies described in the RIPE Document entitled "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region"' as this section states. I tried various ways of interpretation, but failed to come to terms eventually. Any hints, anyone? Thanks and best, Carsten

2 4

Re: [address-policy-wg] [policy-announce] 2012-04 New Draft Document Published (PI Assignments from the last /8)
by Erik Bais 17 Sep '12

17 Sep '12

Dear Emilio & Nick, Thanks for the update on the proposal. I would like to state that I'm not in favor of this policy change. Obviously it is very appealing to open up the last /8 also for end-user assignments, even with the additions of limiting only to a /24 max. But I'm afraid that there will be a run on the last possible addresses and that there won't be any IP space left for new LIR's if they require it. ( Do I even dare to state anything about routing table explosion because of it ? ) For me this is a no-go policy change. IPv4 is over in a couple weeks in the RIPE region. Let's move on. Regards, Erik Bais

23 49

Re: [address-policy-wg] Revert Run Out Fairly after IPv4 depletion
by Hank Nussbacher 14 Sep '12

14 Sep '12

> > Dear Colleagues > > > > A proposed change to RIPE Document ripe-553, "IPv4 Address Allocation > > and Assignment Policy for the RIPE NCC Service Region", is now > > available for discussion. > > > > > > You can find the full proposal at: > > > > https://www.ripe.net/ripe/policies/proposals/2012-06 > >I see the noble goal of this proposal - but why bother? Do we have even >enough time for this proposal to become valid policy change according to >all valid rules of PDP? > >http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-po… > >According to this graph we have one month to go. > >Cheers, Jan Zorz Reading over http://www.ripe.net/ripe/policies/proposals/2012-06 Revert "Run Out Fairly" after IPv4 depletion 5.0 states "As of 1 July 2011, the RIPE NCC will start allocating enough address space to LIRs to meet their needs for a period of up to three months." Can someone explain to me how these two recent allocations fit into this rule (extracted from the delegated file): ripencc|IR|ipv4|5.112.0.0|1048576|20120629|allocated ripencc|IR|ipv4|5.208.0.0|1048576|20120904|allocated -Hank

8 17

Re: [address-policy-wg] 2012-05 New Policy Proposal (Transparency in Address Block Transfers)
by McTim 14 Sep '12

14 Sep '12

On Mon, Jun 4, 2012 at 7:24 AM, Emilio Madaio <emadaio(a)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

8 14