PP Allow AS Number Transfers

Slides:

Advertisements

Similar presentations

Erik Bais, May 15 th 2013 PP Resource Certification for non-RIPE NCC Members Presenter : Erik Bais –

Advertisements

Registration Services Feedback Andrea Cima RIPE NCC RIPE 66 - Dublin.

The RIPE NCC Update Ingrid Wijte Registration Services Assistant Manager.

Nigel Titley. RIPE 54, 9 May 2007, Tallinn, Estonia. 1 RIPE NCC Certification Task Force Update Presented by Nigel Titley RIPE NCC.

NCC Services to PI Resource Holders RIPE / Dublin Axel Pawlik Randy Bush Services to PI 1.

Erik Bais, May 14 th 2014 PP Allow IPv4 PI transfer Presenter : Erik Bais –

(dead) Inter-RIR Transfers to become 2014-xx (new text) Sandra Brown IPv4 Market Group.

1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.

Current Policy Topics Emilio Madaio Policy Development Officer RIPE NCC RIPE Oct - 4 Nov 2011, Vienna.

LACNIC update London, November 7th. LACNIC at a Glance One of the world’s 5 RIRs Coverage area: 32 territories 2 NIRs and also co-founders of LACNIC (NIC.br.

1 Axel Pawlik APNIC 22, 8 September 2006, Kaohsiung RIPE NCC Update APNIC 22.

Update on RIPE NCC Inter- RIR Transfer proposal Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.

APNIC Policy SIG report: Open Policy Meeting Policy SIG Report Masato Yamanishi, Chair.

Policy Implementation and Experience Report Leslie Nobile.

Database Update Kaveh Ranjbar Database Department Manager, RIPE NCC.

Draft Policy ARIN Resolve Conflict Between RSA and 8.2 Utilization Requirements.

Address Policy SIG, APNIC Policy meeting, February 27th, 2003 (1) IPv6 Policy in action Feedback from other RIR communities David Kessens Chairperson RIPE.

Regional Internet Registries Statistics & Activities IETF 55 Atlanta Prepared By APNIC, ARIN, LACNIC, RIPE NCC.

Policy Experience Report Leslie Nobile. The PDP Cycle Need Discuss Consensus Implement Evaluate

PROP Leif Sawyer. Draft Policy ARIN Eliminating Needs-based Evaluation for Section 8.2, 8.3, and 8.4 transfers of IPv4 Netblocks Author:

Erik Bais, May 13 th 2015 PP – unassigned yet General Transfer Policy Presenter : Erik Bais –

Update from the RIPE NCC Axel Pawlik ARIN XXIX, Vancouver.

Feedback from RIPE NCC Registration Services Alex Le Heux, RIPE NCC RIPE64 Ljubljana.

JPNIC Open Policy Meeting Update Yuka Suzuki IP Department Japan Network Information Center (JPNIC) NIR Meeting Aug. 21st, 2003.

Filiz Yilmaz IGF 2006, Athens RIPE Policy History Focusing on IPv4 Filiz Yilmaz Policy Development Officer

Rough Edges of Current Policies Alex Le Heux RIPE NCC Rome.

1 IP Address Space Transfer between Existing Taiwan LIRs Dr. Ching-Heng Ku, TWNIC Policy SIG, APNIC 20, Hanoi, Vietnam September 8, 2005.

Erik Bais, Nov 5 th 2014 PP Allow IPv6 Transfers Presenter : Erik Bais –

Contractual Relationship Requirements for End Users Implementation Update:

Policies for ASN Management in the Asia Pacific Region – Revised Draft Address Policy SIG APNIC14, Kitakyushu, Japan 4 Sept 2002.

IANA Update Elise Gerich | RIPE 71, Bucharest, Romania| November 2015.

RIPE Network Coordination Centre 29, 1-5 March, Kuala Lumpur 1 Axel Pawlik Update from the RIPE NCC.

Erik Bais, May 5 th 2011 PP Removal of multihomed requirement for IPv6 Presenter : Erik Bais –

Rob Blokzijl. RIPE 61 Rome, November RIPE Réseaux IP Européens Rob Blokzijl RIPE Chairman

Rob Blokzijl, RIPE 64, April 2012 IPv4 Maintenance Policy.

Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.

Contractual Relationship Requirement for End Users Implementation update policy proposal

Registration Services Feedback Andrea Cima RIPE NCC RIPE 67 - Athens.

IPv4 IXP Address Policy APNIC Policy SIG Meeting Taipei, August 2001 Philip Smith.

Prop-073 Automatic allocation/assignment of IPv6 Terry Manderson Andy Linton.

JPNIC Update Izumi Okutani Japan Network Information Center APNIC19, NIR SIG.

Abuse-c update Denis Walker Business Analyst RIPE NCC Database Team.

Prop-077: Proposal to supplement transfer policy of historical IPv4 addresses Wendy Zhao Wei, Jane Zhang & Terence Zhang Yinghao.

Contractual Relationship Requirements for End Users Implementation Update: Policy Proposal

Update from the RIPE NCC Axel Pawlik Managing Director.

Copyright (c) 2002 Japan Network Information Center Proposal for IPv6 Policy for Essential Infrastructure in the AP region Izumi Okutani IP Address Section.

Draft Policy ARIN Christian Tacit. Problem statement Organizations that obtain a 24 month supply of IP addresses via the transfer market and then.

The Importance of Whois Accuracy Leslie Nobile

Business Market Administration

Recommended Draft Policy ARIN

Regional Internet Registries An Overview

IEPG Minneapolis, March 1999

The Status of APNIC’s IPv4 Resources: Exhaustion & Transfers

Returned IPv4 Addresses

AfriNIC Transition Plan

AFRINIC Services Update

Draft Policy ARIN Cathy Aronson

Downstream Allocations by LIRs A Proposal

Locking down the final /8 Remco van Mook

A view from ARIN, LACNIC & RIPE Communities Laura Cobley

PP – Resource Authentication Key ( RAK ) code for third party authentication Presenter : Erik Bais –

PP – RIPE Resource Transfer Policies

IPv6 distribution and policy update

Leadership Group 9th November 2013 Feedback Summary.

System Fundamentals IB - Group 4 - Computer Science

Overview of policy proposals

Feedback From NCC Registration Services

PP – RIPE Resource Transfer Policies

End of IPv4 … And the road ahead … for AP-WG

RIPE Address Policy Working Group May 22, 2018, Reykjavik

Presentation transcript:

PP - 2014-13 Allow AS Number Transfers Presenter : Erik Bais – ebais @a2b-internet.com

Policy proposal info Author – Erik Bais Current status : Open for Discussion Phase end : 28 November 2014

2014 – 13 Policy proposal In short : Through the PDP process, allow AS Numbers to be transferred, just like IPv4 (PI & PA) in order to be able to maintain an updated registry. The current implementation doesn’t allow AS Numbers to be transferred.

Why this proposal ? Members have to return their (in-use ? ) AS Number if they want to merge LIR’s .. If a company would like to consolidate LIR’s after a M&A, relocate their IP administration from Entity A to Entity B, they would fall into the policy gap. As there is no infrastructure sold, it is not a M&A. Consolidation is not a transfer, but treated as such.

Why this proposal ? When you ask the RIPE NCC to merge LIR’s, you get asked: Company A will take over the LIR Account and IPv4 Allocations of Company A (or B) (no acquisition between the companies) This is the case in most of the consolidation cases.

The current issue So if a company with more than 1 LIR wants to close one of the LIR’s via a merger, they are forced to hand back the AS Number from the closing LIR. Even if they use the AS Number, because it is not seen as a merger, it is treated as a transfer..

What is the goal of the company The goal is to reduce LIR’s and list all number resources under 1 LIR. Move to a 1 Entity, 1 LIR, 1 Administration point situation.

Why does the RIPE NCC work like this ? There is an operational procedure for M&A’s which clearly states that infrastructure needs to be involved to be applicable as a M&A. Solution for IPv4 : tag the change as a transfer. Issue: There is no policy to transfer AS Numbers, so you need to hand it back to the RIPE NCC.

Where does this hurt ? Changing AS numbers on IXP’s is a painful process. Especially for older AS numbers with lots of peering sessions … ( read peering agreements )

The goal of this proposal is: To get AS Numbers to be transferred. Don’t make things more complicated than required. Avoid ways to work the system or policies that don’t benefit registry accuracy.

What do you think ? In order to get your feedback on the topic : Send your comments to <ap-wg@ripe.net WG> before 28 November 2014. This could be as simple as : I support the policy.