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

Re: [address-policy-wg] 2013-03 New Policy Proposal (No Need - Post-Depletion Reality Adjustment and Cleanup)
by Randy Bush 26 Mar '13

26 Mar '13

this proposal seems sensible. randy

1 0

Policy Proposal 2012-05, "Transparency in Address Block Transfers" Implemented
by Andrea Cima 25 Mar '13

25 Mar '13

[Apologies for duplicate emails] Dear colleagues, We are pleased to announce that RIPE Policy Proposal 2012-05, "Transparency in Address Block Transfers", has been implemented. The RIPE NCC is now publishing the required statistics at: https://www.ripe.net/lir-services/resource-management/ipv4-transfers/table-… This page will be updated weekly. The data is also available in JSON format here: https://www-static.ripe.net/dynamic/table-of-transfers/transfers.json The full policy proposal can be found at: http://www.ripe.net/ripe/policies/archived-policy-proposals/proposals/2012-… The updated RIPE Document 582, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", can be found at: http://www.ripe.net/ripe/docs/ripe-582 If you have any questions, please contact <ncc(a)ripe.net>. Regards, Andrea Cima RIPE NCC Registration Services

1 0

Re: [address-policy-wg] 2012-02 New Draft Document and Impact Analysis Published(Policy for Inter-RIR Transfers of IPv4 Address Space) (Tore Anderson)
by sandrabrown＠ipv4marketgroup.com 22 Mar '13

22 Mar '13

>>Back in December, I suggested that the wording be changed from ?LIRs? to >>something more generic. The rationale was that if the policy explicitly >>refers to LIRs only, this will prevent inter-region transfers of PI >>address space held by non-LIRs, even if the IPv4 policy is amended to >>allow for in-region transfers of PI addresses. >>The proposer responded: ?I am quite willing to change the wording from >>LIR's to Organizations if all agree?. I saw no objections, but version >>2.0 still refers to LIRs specifically. So I'd still like to see this >>changed. >>That said... >>I support the idea of allowing inter-region transfers in general as long >>as the marginal cost of doing so is reasonably low, so I feel a bit bad >>about this, but: I do *not* support this proposal. >>The reason for this is that inter-region transfers are being used as an >>argument against proposal 2013-03, see: >>http://www.ripe.net/ripe/mail/archives/address-policy-wg/2013-March/007757.… >>My view is that if the cost of allowing for inter-region transfers >>(specifically in a way that is compatible with ARIN's policy) is to >>uphold the need bureaucracy and operational overhead relating to >>assignments for all RIPE region LIRs, then the marginal cost is not >>reasonably low, but unacceptably high. If it's an either/or situation >>between 2012-02 and 2013-03, I'm firmly in the 2013-03 camp. I elaborate >>on why here: >>http://www.ripe.net/ripe/mail/archives/address-policy-wg/2013-March/007764.… >>This issue might be resolved by having 2012-02 add some text that >>upholds the need principle for transfers coming in from regions that >>demand it (read: ARIN), or for the recipient LIRs of such transfers >>overall. I have no suggestion on exactly how this text could look like, >>I'm afraid. I suspect the proposer would have to discuss it with ARIN >>staff in order to get confirmation that any proposed text does indeed >>satisfy their definition of ?needs-based general number resource policies?. >>Tore Tore, I agree with all you say, and in fact, the more open and inclusive the process, the better. The problem I ran into in trying to include PI space and end user space in inter-Regional transfers, is that it is not included in intra-regional transfers, and to change 2012-02 to include more, I would have to open a larger kettle of fish. So I chose to keep the scope narrow for now, thinking that the scope could be widened for all assignment types later. The warning that no needs justification in the RIPE region will give cause for ARIN to not allow inter-RIR transfers from ARIN to RIPE does not hold water. Say ARIN is giving out new IP's that will shortly be traded to RIPE and monetized, if RIPE does not have a needs justification checkpoint. That implies that ARIN has no confidence in its own needs justification system for new IP's. The counter point is that there are many address holders from, say the 1990's, who want to monetize and they didn't just get IP's and they still have their IP's exposed to that same needs justification on their buyers (ie. the wrong party, it's the sellers who are supposedly in the wrong). Needs justification is supposed to be on the part of the buyer, but as I understand it, this ARIN argument is that needs justification is needed to prevent the seller from getting away with IP theft. RIPE needs justification on the buyer will not prevent a new IP recipient in the ARIN region from selling its IP's to RIPE. The needs justification argument fails in this case. Needs justification arguments in the past were that buyers of IP's had to prevented from stockpiling and cornering the market. I guess the proponents of this theory have realized that cornering the IP market could be like cornering the silver market. http://en.wikipedia.org/wiki/Nelson_Bunker_Hunt So if there is no argument in favor of needs justification to prevent sellers from cheating, and no argument to prevent buyers from cheating, Tore's idea must be a good one. Still, +1. Sandra

1 0

2012-03 New Draft Document and Impact Analysis Published (Intra-RIR Transfer Policy Proposal)
by Emilio Madaio 21 Mar '13

21 Mar '13

Dear Colleagues The draft document for the version 3.0 of the proposal 2012-03, "Intra-RIR Transfers Policy Proposal", has been published. The impact analysis that was conducted for this proposal has also been published. The only change in the new version is: -removed a modification to the second paragraph of section 5.5, "Transfer of Allocation", in the RIPE Policy document ripe-592, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2012-03 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2012-03/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 18 March 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

5 5

2012-03 Review Period extended until 17 April 2013 (Intra-RIR Transfer Policy Proposal)
by Emilio Madaio 21 Mar '13

21 Mar '13

Dear Colleagues, The Review Period for the proposal 2012-03 has been extended until 17 April. 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 17 April 2013. Regards, Emilio Madaio Policy Development Officer RIPE NCC

2 2

Re: [address-policy-wg] 2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by Carlos Friacas 21 Mar '13

21 Mar '13

Support. On Thu, 28 Feb 2013, Marco Schmidt wrote: > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2013-02/ > > We encourage you to review this proposal and send your comments to > <apwg-chairs(a)ripe.net> before 28 March 2013. > > Regards > > Marco Schmidt > on behalf of the Policy Development Office > RIPE NCC > >

1 0

Support for 2013-03
by Eirik Hjelle 21 Mar '13

21 Mar '13

I support 2013-03 by Tore Anderson of Linpro I represent LIR: Blix Group AS LIR: Blix Solutions AS -- Eirik Hjelle CEO • Blix Solutions AS ☎ +(47) 21 55 56 66 IP Transit • Colocation • Dedicated servers

1 0

Re: [address-policy-wg] 2012-02 New Draft Document and Impact Analysis Published(Policy for Inter-RIR Transfers of IPv4 Address Space)
by sandrabrown＠ipv4marketgroup.com 20 Mar '13

20 Mar '13

>>I'm worried by the wooliness of phrases such as >>"The Originating LIR and the IPv4 address space transferred are in >>compliance with the Originating Policy" >>I really don't know what this means and I see a world of pain unless >>it's clarified. What does "in compliance with" actually mean in this >>context? Currently the only RIR's with similar transfer policies are ARIN and APNIC. As an example, if the LIR is in ARIN region, then the LIR must be in compliance with ARIN policy in order to transfer its IPv4 address space to a RIPE LIR. The ARIN based LIR would apply to ARIN and request to transfer. (That is how it works for ARIN to APNIC transfers today.) ARIN makes sure the LIR has registration of the space before making the transfer. Similarly, I would expect for a RIPE to ARIN or APNIC transfer RIPE needs to ensure that the RIPE LIR has correct registration of the IP space being transferred.

2 1

DRAFT agenda for RIPE66
by Gert Doering 20 Mar '13

20 Mar '13

Hi APWG folks, RIPE meeting orga, below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Dublin in the following two time slots: Wednesday, May 15, 09:00 - 10:30 Wednesday, May 15, 11:00 - 12:30 The exact time lines depend a bit on how much discussion is going on, so we might move items one time slot "up" or "down". As we're conflicting with both database and DNS, we might have to shift stuff around somewhat more than usual to accomodate conflicts of interest - so if there is something that should be in "the other slot", tell me. If you have anything else you want to see on the agenda, or of we need to change anything, please let us know. regards, Gert Doering, APWG chair ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters (welcome, thanking the scribe, approving the minutes, etc.) B. Current Policy Topics - Emilio Madaio - global policy overview "what's going on?" - common policy topics in all regions (end of IPv4, transfers, ...) - overview over concluded proposals in the RIPE region since RIPE65 - brief overview over new proposals (if any) D. Feedback From NCC Registration Service - Andrea Cima F. Discussion of open policy proposals 2012-02 Policy for Inter-RIR transfers of IPv4 Address Space 2012-03 Intra-RIR transfer policy proposal 2012-04 (IPv4) PI assignments from the last /8 2013-02 Removal of requirement for certification of reallocated IPv4 addresses ---------------------------------------------------------------------- Wednesday, 11:00-12:30 ---------------------------------------------------------------------- G. Discussion of open policy proposals (continued) 2013-03 No Need - Post-Depletion Reality Adjustment and Cleanup Y. Open Policy Hour "The Open Policy Hour (OPH) is a showcase for your policy ideas. If you have a policy proposal you'd like to debut, prior to formally submitting it, here is your opportunity." Z. AOB -- 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

1 0

RIPE NCC to Assign 16-bit ASNs Until ASN Pool is Replenished
by Andrew de la Haye 19 Mar '13

19 Mar '13

Dear colleagues, The RIPE NCC has less than 100 32-bit Autonomous System Numbers (ASNs) available in its pool. Given current assignment rates, we expect that we will run out of 32-bit ASNs before May 2013. We will soon begin to assign 16-bit ASNs for all requests until our pool has been replenished by IANA. This will not result in any operational issues for requestors as 16-bit ASNs are compatible with equipment designed to run BGP. This situation was anticipated and covered during the RIPE NCC Registration Services update during the RIPE 65 Meeting. You can see the details in the "Feedback from RIPE NCC Registration Services" presentation available at: <https://ripe65.ripe.net/programme/meeting-plan/address-policy-wg/> -------------------------- Replenishing our ASN Pool -------------------------- The RIPE NCC requests additional ASNs from IANA based on "IANA Policy for Allocation of ASN Blocks to RIRs: <https://www.ripe.net/ripe/docs/ripe-480> Under this policy, we need to demonstrate 80% usage of "the previously received ASN block" (which includes both 16-bit and 32-bit ASNs we received from IANA on 3 March 2012) to replenish our ASN pool. We are expecting to reach this usage rate within six to eight months. The RIPE NCC will return to the usual procedure of assigning 32-bit AS numbers "by default" once our ASN pool is replenished. -------------------------------------------------------------------- Background on 32-bit ASN assignments in the RIPE NCC service region -------------------------------------------------------------------- The RIPE NCC assigns ASNs based on the "Autonomous System (AS) Number Assignment Policies and Procedures": <https://www.ripe.net/ripe/docs/ripe-52>. In accordance with the RIPE Address Policy Working Group decision, announced at: <http://www.ripe.net/ripe/mail/archives/address-policy-wg/2010-January/00497…>, the RIPE NCC assigns 32-bit ASNs by default unless a 16-bit ASN is specifically requested. As a result of this practice, 32-bit ASNs are currently supported by most vendors and routed globally. Of the 3,400 32-bit ASNs in the global routing table, 64% were assigned by the RIPE NCC within its service region (Europe, the Middle East and parts of Central Asia). Best regards, Andrew de la Haye Chief Operations Officer RIPE NCC

9 9