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

Slides:



Advertisements
Similar presentations
LACNIC Policy Update Roque Gagliano LACNIC. Current Policies Proposals - LACNIC As a result of the Open Policy Forum at LACNIC XI four policy proposals.
Advertisements

Axel Pawlik. LACNIC III, November 2002, Mexico City. 1 6bone Address Registry Proposal Axel Pawlik / Mirjam Kühne RIPE NCC.
Erik Bais, May 15 th 2013 PP Resource Certification for non-RIPE NCC Members Presenter : Erik Bais –
Registration Services Feedback Andrea Cima RIPE NCC RIPE 66 - Dublin.
IPv4 Address Transfer proposal APNIC prop-050-v002 Geoff Huston.
IPv4 Run Out and Transitioning to IPv6 Marco Hogewoning Trainer, RIPE NCC.
1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
Draft Policy Clarifying Requirements for IPv4 Transfers.
ARIN Policy Experience Report Leslie Nobile. Review existing policies – Ambiguous text/Inconsistencies/Gaps/Effectiveness Identify areas where new or.
Improving 8.4 Anti-Flip Language. Problem Statement Current policy prevents an organization that receives BLOCK A in the previous 12 months from.
ARIN Transfer Policy Slow Start and Simplified Needs Verification.
Recommended Draft Policy Section 8.4 Inter-RIR Transfer of ASNs.
Current Policy Topics Emilio Madaio Policy Development Officer RIPE NCC RIPE Oct - 4 Nov 2011, Vienna.
ARIN Clarifying Requirements for IPv4 Transfers Dan Alexander- Primary Shepherd David Farmer- Secondary Shepherd.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
Update on RIPE NCC Inter- RIR Transfer proposal Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.
APNIC Last /8 Policy Implementation Report Sanjaya Services Area Director.
2009-3: Allocation of IPv4 Blocks to Regional Internet Registries.
Policy Implementation and Experience Report Leslie Nobile.
PDO Activities Emilio Madaio Policy Development Officer RIPE NCC RIPE Oct - 4 Nov 2011, Vienna.
Life After IPv4 Depletion Leslie Nobile. Overview ARIN’s current IPv4 inventory Trends and observations Ways to obtain IP addresses post IPv4 depletion.
Prop-080: Removal of IPv4 Prefix Exchange Policy Guangliang Pan Resource Services Manager, APNIC.
PROP Leif Sawyer. Draft Policy ARIN Eliminating Needs-based Evaluation for Section 8.2, 8.3, and 8.4 transfers of IPv4 Netblocks Author:
Update from the RIPE NCC Axel Pawlik ARIN XXIX, Vancouver.
6bone address registry proposal Bob Fink ESnet 17 July 2002 Yokohama.
Feedback from RIPE NCC Registration Services Alex Le Heux, RIPE NCC RIPE64 Ljubljana.
Unintended side-effects Amending the transfer policy (soon to be called ) James Blessing, Sandra Brown, Remco van Mook.
Erik Bais, Nov 5 th 2014 PP Allow IPv6 Transfers Presenter : Erik Bais –
Policies for ASN Management in the Asia Pacific Region – Revised Draft Address Policy SIG APNIC14, Kitakyushu, Japan 4 Sept 2002.
ARIN Allow Inter-RIR ASN Transfers. Problem Statement We already allow transfer of ASNs within the ARIN region. Recently APNIC implemented a policy.
Erik Bais, May 5 th 2011 PP Removal of multihomed requirement for IPv6 Presenter : Erik Bais –
Draft Policy ARIN Modify 8.4 (Inter-RIR Transfers to Specified Recipients) Authors: David Huberman and Tina Morris AC Shepherds: Cathy Aronson and.
Rob Blokzijl, RIPE 64, April 2012 IPv4 Maintenance Policy.
A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Emerging Registry Criteria ASO General Assembly Budapest, 19 May 2000.
Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.
News from APNIC German Valdez Communications Area Manager RIPE October 2008.
Registration Services Feedback Andrea Cima RIPE NCC RIPE 67 - Athens.
1 A Closer Look at the Final /8 Policy Sam Dickinson Senior Policy Specialist, APNIC Thursday, 26 August 2010.
Políticas en discusión en otros RIRs Juan Alejo
Draft Policy ARIN Modify 8.4 (Inter-RIR Transfers to Specified Recipients) Presented by Chris Tacit.
1 IANA global IPv6 allocation policy [prop-005-v002] Policy SIG 1 Sept 2004 APNIC18, Nadi, Fiji.
Prop-077: Proposal to supplement transfer policy of historical IPv4 addresses Wendy Zhao Wei, Jane Zhang & Terence Zhang Yinghao.
Advisory Council Shepherds: David Farmer & Chris Grundemann Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA.
Policy SIG Report APNIC AGM Friday 29 August 2008 Christchurch, New Zealand 1.
Update from the RIPE NCC Axel Pawlik Managing Director.
60 Draft Policy ARIN NRPM 4 (IPv4) Policy Cleanup.
Whois & Data Accuracy Across the RIRs. Terms ISP – An Internet Service Provider is allocated address space by an RIR for the purpose of providing connectivity.
ARIN Update John Curran President and CEO, ARIN Focus IPv4 to IPv6 Transition Awareness – Targeting ISPs and Content Providers Continued enhancements.
8 th Address Policy SIG Report Takashi Arano Yong Wan Ju Kenny Huang Chair/co-Chairs of APNIC Address Policy SIG.
Draft Policy ARIN Christian Tacit. Problem statement Organizations that obtain a 24 month supply of IP addresses via the transfer market and then.
Recommended Draft Policy ARIN
Head Of Member Services
Legacy Resources in the Research & Education Community
Draft Policy ARIN Amy Potter
Recommended Draft Policy ARIN : Post-IPv4-Free-Pool-Depletion Transfer Policy Staff Introduction.
Draft Policy ARIN Cathy Aronson
Recommended Draft Policy Section 8
IPv4 space advances from brokers – what you need to know
Policy SIG Wednesday 3 March 2010
News from APNIC ARIN XXII 16 October 2008.
PP – RIPE Resource Transfer Policies
Overview of policy proposals
ARIN Inter-RIR Transfers
Recovery of Unused Address Space prop-017-v001
Experimental Internet Resource Allocations
Overview of policy proposals
Recommended Draft Policy ARIN : Modify 8
PP – RIPE Resource Transfer Policies
PP Allow AS Number Transfers
Removing aggregation criteria for IPv6 initial allocations
Presentation transcript:

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

Erik Bais, May 13 th 2015 Policy proposal info Author – Erik Bais Current status : Not submitted yet. (Draft ready) 2

Erik Bais, May 13 th 2015 Policy proposal In short : Create a single policy document, with all relevant policy text. The goal is to remove all transfer related text from the other policy documents and stream- line where possible the policy text to a common agreed policy text. 3

Erik Bais, May 13 th 2015 Why this proposal ? It is a full mess. ( Yes I created the mess myself, but this is the clean-up. ) Currently the following resources and policies have policy text related to transfers : IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region IPv4 PI Assignment Policy ( in the IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region ) IPv6 Address Allocation and Assignment Policy Autonomous System (AS) Number Assignment Policies And there will be a special section in regards to inter RIR transfers as that is currently also approved. 4

Erik Bais, May 13 th 2015 Point 2 (skipping the introduction) 2 Transfer policy Any legitimate resource holder is allowed to transfer complete or partial blocks of address space or number resource that were previously allocated or assigned to them by the RIPE NCC or otherwise through the Regional Internet Registry system. Resources may only be transferred to another resource holder who is a member of an RIR that allows transfers. Q: Does this “a member” work for PI Space holders ? 5

Erik Bais, May 13 th Temp or permanent basis of the transfer Current text: Re-allocation must be reflected in the RIPE Database. This re-allocation may be on either a permanent or non-permanent basis. IPv4 PA Re-assignments must be reflected in the RIPE Database. This re-assignment can either be on a permanent or non-permanent basis. – IPv4 PI Re-assignments must be reflected in the RIPE Database. This re-assignment can either be on a permanent or non-permanent basis. – AS Number Transfers must be reflected in the RIPE Database. This transfer may be on either a permanent or non-permanent basis. – IPv6 Proposed text : Transfers must be reflected in the RIPE Database. This transfer may be on either a permanent or non-permanent basis 6

Erik Bais, May 13 th Transfer Policy restrictions Time restrictions for re-transferring a resource LIRs that receive a re-allocation from another LIR cannot re-allocate complete or partial blocks of the same address space to another LIR within 24 months of receiving the re-allocation. – IPv4 PA Parties that receive a re-assignment from another party cannot re- assign complete or partial blocks of the same address space to another party within 24 months of receiving the re-assignment. – IPv4 PI No restriction for IPv6 or AS Numbers. Comments on the AS numbers is that during the AS Transfer policy discussion was to see if there is an option to restrict the almost depleted 16 bit AS numbers. 7

Erik Bais, May 13 th Transfer Policy restrictions Proposal for generalization: A 24 month waiting period for depleted resources... ( PA IPv4, PI IPv4 and 16 bit AS numbers. ) after receiving of the resource. Which means also for new allocations or allocations via M&A. 8

Erik Bais, May 13 th Inter RIR Transfer 5.1 Scope The policy for transferring Internet number resources to or from the RIPE NCC service region will apply to any type of Internet number resources for which there is a transfer policy within the RIPE NCC service region. With this policy, legacy resources can be transferred to or from the RIPE NCC service region, in spite of the fact there is no specific transfer policy for them. While the transfer is in process, during the time the internet number resources are registered in the RIPE NCC service region, then RIPE policies will apply. 5.2 Transferring Internet Resources to the RIPE NCC Service Region The RIPE NCC shall accept all transfers of Internet number resources to its service region, provided that they comply with the policies relating to transfers within its service region. For transfers from RIR regions that require the receiving region to have needs- based policies, recipients must provide a plan to the RIPE NCC for the use of at least 50% of the transferred resources within 5 years. 9

Erik Bais, May 13 th Inter RIR Transfer 5.3 Transferring Internet Resources from the RIPE NCC Service Region When transferring Internet number resources to another RIR, the RIPE NCC will follow the transfer policies that apply within its own service region. The RIPE NCC will also comply with the commitments imposed by the receiving RIR in order to facilitate the transfer. ( No longer required : Policy for Inter-RIR Transfers of Internet Resources ) 10

Erik Bais, May 13 th Transfer Statistics May need some other wording for the AS number resources. The RIPE NCC will publish a list of all resources transferred under this section. The publication shall occur on monthly basis or more frequently if the RIPE NCC so chooses. The list will contain information about approved and non-approved transfers. 11

Erik Bais, May 13 th Transfer Statistics The following information will be published for approved transfers: the name of the transferring party, the resource originally held by the transferring party, the name(s) of the receiving party or parties, each subdivided prefix (each partial block derived from that original block) or resource transferred the date each prefix was transferred. Non-approved transfers will be published in an aggregate statistics. In the statistics the following information will be published the number of requested transfers not approved after the RIPE NCC’s evaluation, the sum of the number of addresses included in the requested transfers. Neither the blocks nor the organizations involved will be identified in these statistics. 12

Erik Bais, May 13 th Final remarks Please note that the current legitimate resource holder always remains responsible for the entire allocation it receives from the RIPE NCC until the transfer of resource to the receiving party is completed or is returned. The resource holder must ensure that all policies are applied. Transferred resources are no different from the allocations made directly by the RIPE NCC and so they must be used by the receiving party according to the policies described in the respective documents. The RIPE NCC will record the change of allocation after the transfer. 13

Erik Bais, May 13 th 2015 Next steps : After input, we will take the draft and work on a final version. Submit that to the PDO process. And the RIPE NCC will put the proposal on the Mailing list. Estimated in 2 to 3 weeks max. 14

Questions?