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

Re: [address-policy-wg] 2010-02 New Draft Document Published (Allocations from the last /8)
by Max Tulyev 08 Jul '10

08 Jul '10

I'm about independence from upstream provider or other telecom-engaged entity, not about payments. Gennady A. написав(ла): > Which independency you are talking about? > Currently, PIs are not actually independent. To keep them running, PI > user also have to pay support fee, like if he uses PA address space. > > 2010/7/7 Max Tulyev <president(a)ukraine.su>: >> Gennady, >> >> for now it is bad. But when there will be a lack of IPv4, we have to >> sacrifice aggregation in favour to conservation. >> >> The difference is the independence. PA is not. >> >> Gennady A. написав(ла): >>> Max, >>> /29 in the global routing table is a bad thing. >>> >>> Those who need multihoming may use PA address space. Now, when >>> contracts to support address space are necessery, there isn't much >>> dfference between PI and PA. >> -- >> WBR, >> Max Tulyev (MT6561-RIPE, 2:463/253@FIDO) >> >> > > > -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Last call to participate: 2010 Global IPv6 Deployment Monitoring Survey
by Paul Rendek 29 Jun '10

29 Jun '10

[Apologies for duplicates] Dear Colleagues, This is a last-call reminder to participate in the 2010 Global IPv6 Deployment Monitoring Survey, conducted by GNKS Consult and TNO in collaboration with the RIPE NCC. The survey is available at: http://www.surveymonkey.com/s/IPv6deploymentmonitoring2010 The deadline to complete the survey is this Thursday, 1 July 2010. All five Regional Internet Registries have committed to soliciting participation in this survey in order to compile the most complete global IPv6 deployment data possible. The goal of the survey is to gain a better understanding of where the community is moving, and what can be done to ensure the Internet community is ready for the widespread adoption of IPv6. We encourage all organisations in the RIPE NCC service region to participate in this survey, which we hope will establish a comprehensive view of present IPv6 penetration and future plans for IPv6 deployment. The survey is composed of 23 questions and can be completed in about 15 minutes. For those without IPv6 allocations or assignments, or who have not yet deployed IPv6, the questions will be fewer in number. Results of the IPv6 Deployment Monitoring Survey will be presented and discussed at RIPE 61, which will be held 15-19 November in Rome, Italy. Results will also be published on IPv6 Act Now: http://ipv6actnow.org Please provide your name and contact information on the survey form if you wish to receive the draft survey analysis when available. Please also indicate whether you are willing to share additional data with the TNO and GNKS Consult IPv6 Deployment Monitoring team. Any questions concerning the survey itself should be addressed to <info(a)gnksconsult.com>. Regards, Paul Rendek Head of External Relations and Communications RIPE NCC

1 0

AW: [address-policy-wg] 2010-02 New Policy Proposal (Allocations from the last /8)
by Marcus.Gerdon 18 Jun '10

18 Jun '10

Nick, although assignments might be out of scope here, but Max isn't strolling that far taking his thought logically. Is there a limitation on the size of a PI assignment in place at some time in any one of the lately changed policies? Without digging for any actual numbers out of daily business I'd say there's quite a number of assignments exceeding initial alloctions - and easily exceeding the proposed limit of /22 per LIR. Let me walk a bit further along Max' comment. As soon as I got that last /22 allocation which policy keeps me from requesting a /19 PI for our own use? As far as I remember (at least in v4-world) LIRs aren't excluded from PI policies. Correct me if I'm wrong, but according current practice moving all our dynamic DSL-pools into PI space would be quite valid as each customer only get's a single address with the sole purpose being the connection to our network (mirroring hosting/housing to circuit business). In addition as a LIR I might come to think of issues with equality in business when running into problems after having used up that last /22 and noticing that ISP running their business on PI space are able to further request addtional IP space. regards, Marcus ----------------------------------------------------------------------------------------- Engineering IP Services Versatel West GmbH Unterste-Wilms-Strasse 29 D-44143 Dortmund Fon: +49-(0)231-399-4486 | Fax: +49-(0)231-399-4491 marcus.gerdon(a)versatel.de | www.versatel.de Sitz der Gesellschaft: Dortmund | Registergericht: Dortmund HRB 21738 Geschäftsführer: Dr. Hai Cheng, Joachim Bellinghoven ----------------------------------------------------------------------------------------- AS8881 / AS8638 / AS13270 / AS29610 | MG3031-RIPE ----------------------------------------------------------------------------------------- > -----Ursprüngliche Nachricht----- > Von: address-policy-wg-admin(a)ripe.net > [mailto:address-policy-wg-admin@ripe.net] Im Auftrag von Nick Hilliard > Gesendet: Mittwoch, 16. Juni 2010 22:00 > An: address-policy-wg(a)ripe.net > Betreff: Re: [address-policy-wg] 2010-02 New Policy Proposal > (Allocations from the last /8) > > On 16/06/2010 19:37, Max Tulyev wrote: > > I think, the policy is fair. > > > > But you completely forget the Provider Independent > assignments there! So > > I vote for changing "LIRs" to "Companies" there. > > This policy is about allocations (i.e. to LIRs), not assignments (i.e. > directly to end users). I don't think anyone forgot > assignments - they're > just outside the scope of the policy. > > Nick > >

2 1

2010-04 New Policy Proposal (80% Rule Ambiguity Cleanup)
by Emilio Madaio 18 Jun '10

18 Jun '10

PDP Number: 2010-04 80% Rule Ambiguity Cleanup Dear Colleagues A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2010-04.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 15 July 2010. Regards Emilio Madaio Policy Development Officer RIPE NCC

7 6

Re: [address-policy-wg] 2010-04 New Policy Proposal (80% Rule Ambiguity Cleanup)
by Remco van Mook 18 Jun '10

18 Jun '10

+1 Remco ----- Original Message ----- From: address-policy-wg-admin(a)ripe.net <address-policy-wg-admin(a)ripe.net> To: address-policy-wg(a)ripe.net <address-policy-wg(a)ripe.net> Sent: Thu Jun 17 18:26:49 2010 Subject: Re: [address-policy-wg] 2010-04 New Policy Proposal (80% Rule Ambiguity Cleanup) On 17/06/2010 15:50, Emilio Madaio wrote: > http://www.ripe.net/ripe/policies/proposals/2010-04.html agree. please implement. Nick This email is from Equinix Europe Limited or one of its associated/subsidiary companies. This email, and any files transmitted with it, contains information which is confidential, may be legally privileged and is solely for the use of the intended recipient. If you have received this email in error, please notify the sender and delete this email immediately. Equinix Europe Limited. Registered Office: Quadrant House, 4 Thomas More Square, London E1W 1YW. Registered in England and Wales, No. 6293383.

9 8

Reminder: Global IPv6 Deployment Monitoring Survey
by Paul Rendek 17 Jun '10

17 Jun '10

[Apologies for duplicates] Dear Colleagues, This is a reminder to participate in the 2010 Global IPv6 Deployment Monitoring Survey being conducted by GNKS Consult and TNO, in collaboration with the RIPE NCC. The survey is now available at: http://www.surveymonkey.com/s/IPv6deploymentmonitoring2010 The survey will close on 1 July 2010. All five Regional Internet Registries have committed to soliciting participation in this survey in order to compile the most complete global IPv6 deployment data possible. The goal of the survey is to gain a better understanding of where the community is moving, and what can be done to ensure the Internet community is ready for the widespread adoption of IPv6. We encourage all organisations in the RIPE NCC service region to participate in this survey, which we hope will establish a comprehensive view of present IPv6 penetration and future plans for IPv6 deployment. The survey is composed of 23 questions and can be completed in about 15 minutes. For those without IPv6 allocations or assignments, or who have not yet deployed IPv6, the questions will be fewer in number. Results of the IPv6 Deployment Monitoring Survey will be presented and discussed at RIPE 61, which will be held 15-19 November in Rome, Italy. Results will also be published on IPv6 Act Now: http://ipv6actnow.org Please provide your name and contact information on the survey form if you wish to receive the draft survey analysis when available. Please also indicate whether you are willing to share additional data with the TNO and GNKS Consult IPv6 Deployment Monitoring team. Any questions concerning the survey itself should be addressed to <info(a)gnksconsult.com >. Regards, Paul Rendek Head of External Relations and Communications RIPE NCC

1 0

2010-02 New Policy Proposal (Allocations from the last /8)
by Ingrid Wijte 16 Jun '10

16 Jun '10

PDP Number: 2010-02 Allocations from the last /8 Dear Colleagues A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2010-02.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 11 May 2010. Regards Ingrid Wijte Policy Development Officer RIPE NCC

6 6

2009-01 Last Call for Comments (Global Policy for the Allocation of IPv4 blocks to Regional Internet Registries)
by Emilio Madaio 16 Jun '10

16 Jun '10

PDP Number: 2009-01 Global Policy for the Allocation of IPv4 blocks to Regional Internet Registries Dear Colleagues, The proposal described in 2009-01 is now at its Concluding Phase. You can find the full proposal at: http://ripe.net/ripe/policies/proposals/2009-01.html Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 14 July 2010. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Getting LIR
by danica hal 14 Jun '10

14 Jun '10

Hello, sorry for the inconvenience if this is the wrong place for this kind of question. In this case please be so kind and point me to the right place. We are thinking about getting a LIR and I need some informations about the requirements we need to fulfil. I know documents about requirements of getting PI and ASN but for getting LIR and tho PA i feel a bit clumsy.. :-) Thank you! best wishes, Danica

2 1

Global Policy for IPv4 Allocations by the IANA Post Exhaustion
by Chris Grundemann 04 Jun '10

04 Jun '10

Hello APWG, I and a group of others have been working on a global policy proposal regarding returning and re-allocating IPv4 addresses to and from the IANA post IPv4 exhaustion. As this is a global proposal, we have decided that the best approach is to float the current draft publicly in all five regions and solicit feedback, before submitting it as an official policy proposal. We hope that this will let us identify and address any problems or gaps ahead of time and thus ease the process. Barring any major issues being raised, we hope to submit the proposal next week so I would love to get your feedback incorporated by Tuesday (8 June) if at all possible. Please feel free to provide comments on or off list. Thanks in advance - have a wonderful weekend! # Global Policy for IPv4 Allocations by the IANA Post Exhaustion # Rationale: This policy defines the process for the allocation of IPv4 addresses post "Exhaustion Phase"[1]. In order to fulfill the requirements of this policy, the IANA must set up a reclamation pool to hold addresses in and distribute from in compliance with this policy. This policy establishes the process by which IPv4 addresses can be returned to and re-issued from the IANA post Exhaustion Phase. The intent of this policy is as follows: * Includes all post Exhaustion Phase address space returned to the IANA. * Allows allocations by the IANA from the Reclamation Pool once the Exhaustion Phase has been completed. * Defines "need" as the basis for further IPv4 allocations by the IANA. * Does not differentiate any class of IPv4 address space unless defined by RFC 1918. * Encourages the return of IPv4 address space by making this re-allocation process available. * Disallows transfers of addresses sourced from the Reclamation Pool in the absence of an IPV4 Global Transfer Policy to neutralize transfer process inequities across RIR regions. * Applies to legacy IPv4 Address Space initially allocated by the IANA to users including the allocations to RIRs. * Includes any length of fragments currently held by the IANA now or in the future. 1. Reclamation Pool Upon adoption of this IPv4 address policy by the ICANN Board of Directors, the IANA shall establish a Reclamation Pool to be utilized post RIR IPv4 exhaustion as defined in Section 5. As soon as the first RIR exhausts its inventory of IP address space, this Reclamation Pool will be declared active. 2. Returning Address Space to the IANA The IANA will accept into the Reclamation Pool all eligible IPv4 address space that is offerred for return. Eligible address space includes any addresses not previously designated for special use by an IETF published RFC explicitly offerred for return to the IANA by: a) The RIR to which the space is assigned b) The registrant of record where no RIR holds authority 3. Address Allocations from the Reclamation Pool by the IANA Allocations from the Reclamation Pool may begin once the pool is declared active. Aggregates in the Reclamation Pool may be divided on a CIDR boundary to the longest minimum allocation or assignment of any of the RIRs in order to complete these allocations. Addresses that are left over will be held in the Reclamation Pool until additional IP addresses are returned, or a minimum allocation unit is achieved that allows continued allocations from the pool. 4. RIR Eligibility for Receiving Allocations from the Reclamation Pool Upon the exhaustion of an RIR's free space pool, an RIR will become eligible to request address space from the IANA Reclamation Pool when it publicly announces via its respective global announcements email list and by posting a notice on its website that it has exhausted its supply of IPv4 address space. Exhaustion is defined as an inventory of less than the equivalent of a single /8 and the inability to further assign address space to its customers in units equal to or shorter than the longest of the RIR's policy defined minimum allocation unit. Any RIR that is formed after this policy has been adopted by the ICANN Board of Directors is not eligible to utilize this policy to obtain IPv4 address space from the IANA. 5. Reporting Requirements The IANA shall publish on at least a weekly basis a report that is publicly available which at a minimum details all address space that has been received and that has been allocated. The IANA shall publish a Returned Address Space Report which indicates what resources were returned, by whom and when. The IANA shall publish an Allocations Report on at least a weekly basis which at a minimum indicates what IPv4 address space has been allocated, which RIR received the allocation and when. The IANA shall publish a public report confirming RIR eligibility subsequent to Section 4. 6. No Transfer Rights Address space assigned from the Reclamation Pool is not subject to transfer outside of an ICANN Board adopted globally adopted transfer policy. The definition of Global Transfer Policy for the purpose of this policy is a global policy that has been processed and adopted by ICANN in compliance with the MoU [2] and attachments as agreed to in October 2004 between ICANN and the RIRs. 7. Definitions IANA - Internet Assigned Numbers Authority or it's successor ICANN - Internet Corporation for Assigned Names and Numbers or it's successor RIR - Regional Internet Registry as recognized by ICANN MOU - Memorandum of Understanding between ICANN and the RIR's IPV4 - Internet Protocol Version Four, the target protocol of this Global Policy 8. References 1. http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm Global Policy for the Allocation of the Remaining IPv4 Address Space, IANA, Retrieved 27 April 2010 2. http://www.nro.net/documents/aso-mou.html ICANN Address Supporting Organization (ASO) MoU , Retrieved 27 May 2010. ## Thanks again for your time and attention! ~Chris -- @ChrisGrundemann weblog.chrisgrundemann.com www.burningwiththebush.com www.coisoc.org

1 0