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

Re: [address-policy-wg] Easy to remember IP-address
by Sergey Gotsulyak 05 Apr '10

05 Apr '10

Shane Kerr wrote: > To be clear, we're not talking about anyone getting more or less address > space, or allocating in a way that makes aggregation more difficult. I > thought those were the two basic goals of IP allocation policy, right? > The RIPE NCC does not have any restrictions on which particular > resources it allocates or assigns. In fact, I am pretty sure that any > sensible person would argue that the RIPE NCC should have as much > freedom as possible to do things in the most efficient way. So I think > the RIPE NCC already has the power to issue "vanity addresses" in the > rare case where someone asks for these. As far as we're concerned we're going to follow all the necessary requirements and formalities needed for assignment of a block of IP-addreesses. We're ready to apply throught a standard procedure from the name of our company, or through one of the present LIRs. We could even get a status of a LIR for our company if needed and pay the initial fee and yearly fees. We hope that an assignment of the minimal IP block of addresses 2.2.2.0/24 (or 2.2.2.0/21) will not cause any routing problems, because the availability of this address from any part of the world will be achieved throught BGP Anycast. > Mostly I find it a pity that the NCC wasn't more accommodating and that > we're having this discussion at all. Maybe the software used for this > process does not have a manual override or something? Oh well, compared > to the horror stories I hear about the bad old days, I guess we have no > complaints.... > In the end I suppose we can just let the addresses fall wherever and let > "the market" sort it out, now that there is a "trading" policy. While > the desire for vanity addresses might accelerate the process of IP > addresses becoming property, that is probably inevitable, so it won't > change the big picture too much. -- Kind regards, Sergey Gotsulyak Ideco Sales Team 280 Madison Ave, Suite 912 New York, NY 10016 Phone: (800) 715-3502 Email: goz(a)idecogateway.com Web: www.idecogateway.com

1 0

Re: Easy to remember IP-address
by Sergey Gotsulyak 05 Apr '10

05 Apr '10

Shane Kerr wrote: > As for actually getting the RIPE NCC to issue a resource based on a > request... I think there are two ways to go about this. One is making it > a POLICY matter, and going through the PDP and updating the relevant > documents. The other is solving it PROCEDURALLY, which basically means > convincing the RIPE NCC to accept special requests and handle them when > possible. Very interesting idea. If there is a way to solve our issue PROCEDURALLY, that means there's no need to alter the present POLICY. > In summary: > * I support allowing people to request specific unused resources > * I hope that can be done without a policy change In fact we originally hoped to solve our issue in this manner, when we addressed RIPE directly. Do you know of any similar requests in the past? How were they solved? Who can we refer to in RIPE NCC with this request? -- Kind regards, Sergey Gotsulyak Ideco Sales Team 280 Madison Ave, Suite 912 New York, NY 10016 Phone: (800) 715-3502 Email: goz(a)idecogateway.com Web: www.idecogateway.com

1 0

2010-02 New Policy Proposal (Revoke and Re-assign Fairly)
by Nick Hilliard 02 Apr '10

02 Apr '10

Number: 2010-01 Policy Proposal Name: Revoke and Re-assign Fairly Author: Nick Hilliard, INEX Proposal Version: 1.0 Submission Date: 1 April 2010 Current Phase: Discussion - Open for Discussion Phase ends/ended: 1 April 2010 Latest Status: Initial Community Discussion Suggested WG for Discussion and Publication: Address Policy Proposal Type: New Policy Term: Indefinite Policy Documents to be Affected: * IPv4 Address Allocation and Assignment Procedures for the RIPE NCC Service Region (ripe-492) Summary of Proposal: This proposal revokes all previous IPv4 LIR allocations and direct / LIR assignments, returning all ERX and RIPE NCC-assigned IPv4 address space back to the RIPE NCC, where it can be re-assigned fairly, using new policies and guidelines. The RIPE NCC has been acting as RIR in the European / Middle-East geographical areas since 1989. Due to egregiously lenient policies and gross end-user address wastage, in combination with a more recent tendency to horde IPv4 addresses in anticipation of a future shortage, recent research has suggested that approximately 97% of IPv4 address assigned and allocated through the RIPE NCC aren't actually used at all, and never were. Furthermore, this research suggests that if all this address space were returned to the RIR for re-assignment, this would create enough slack space in the IPv4 address pool to service all future requests in the RIPE NCC service region for approximately 100-150 years, based on current actual run-rate, rather than the current fantasy figures published by the RIPE NCC. Also included as part of this policy is a future restriction to limit all future direct assignments to 640 IPv4 address, because that should be enough for anyone. Policy Text: a. Old text Remove sections 5, 6 and 7 in RIPE 492. b. New policy text Insert new section 5 in RIPE 492: -- 5.0 Policies and Guidelines for Allocations and Assignments An allocation is a block of IPv4 addresses from which assignments are taken. All allocations and assignments made prior to April 1, 2010 are hereby revoked, cancelled, and made null and void. LOL!!11!!!1! The RIPE NCC will allocate 640 IPv4 addresses to each LIR, because that that should be more than enough for anyone. PI assignments requests will be greeted with even more giggles than they currently are. -- a. Arguments supporting the proposal Every LIR and PI holder is hoarding address space like there's no tomorrow. By forcing a reboot of the entire registry system, every holder will be equally wrong-footed, and will realise that there's no need to hoarde address space after all. This policy will have the side effect of ensuring that this insane rush to IPv6 is entirely unnecessary, proving beyond all doubt that the ITU seriously has no clue when it comes to Internet resource assignment. b. Arguments Opposing the Proposal It is likely that nay-sayers and other party-poopers will come out of the wood-work to bleat about how this proposal is unfair. The author advises that they get a life and stop hoarding numbers. After all, they're only numbers. And if they really need more, they can contact me directly (see contact details above). Some companies will attempt to claim that they have more than 640 customers. Clearly, this can't be true because any company with more than 640 customers would be making a profit, which everyone knows to be a ridiculous claim.

13 14

Re: [address-policy-wg] Easy to remember IP-address
by Sergey Gotsulyak 01 Apr '10

01 Apr '10

Gennady, are you trying to say that Google doensn't know the best marketing techniques? P.S: Google has chosen for their DNS-service an easy to remember 8.8.8.8 address ;-) > Remembering domain names and IP addressess are absolutely different > things. Domain names are on the user level, IP addressess are not. > Let's not make such "dirty hacks" to multi-level networking model :) > (I avoid "7-level OSI model" phrase here). > So, it's bad idea to build PR/marketing campaign based on "beautifull" > IP-address. It's something like beautifull (from user, not engineer > view) design of motherboards, gearboxes, etc.. It may be fine, but not > more, there is a lot of more important things user should consider > about. > I completely can't understand, why you so need "easy-to-remember" > addressess and don't you have a better way to make your services more > user-friendly and PRable.

2 1

Easy to remember IP-address
by Sergey Gotsulyak 01 Apr '10

01 Apr '10

Gentlemen, Some days ago, I told Jaap Akkerhuis about allocation of 2.2.2.0/24 address space for our DNS-service and he advice me to contact this workgroup. Our company Ideco is located in Russia and is in the business of developing and selling Internet gateways for small and middle businesses in Russia as well as billing software for ISPs. We’re now starting a new project for Russia and Eastern Europe that will provide secure Internet access for educational institutions, commercial and non-profit organizations. We’re planning to set up a number of DNS-centers that will block malware, adult websites and phishing links. For this project we’ll need an easy to remember IP-address, for example like the one for Google Public DNS service (8.8.8.8) We have contacted RIPE NCC with a request to get a block of addresses 2.2.2.0/24, but were told that the standard procedure does not allow us to choose an address range. Is it possible to modify current Address Policy? -- Kind regards, Sergey Gotsulyak Ideco Sales Team 280 Madison Ave, Suite 912 New York, NY 10016 Phone: (800) 715-3502 Email: goz(a)idecogateway.com Web: www.idecogateway.com

13 21

2010-01 New Policy Proposal (Temporary Internet Number Assignment Policies)
by Ingrid Wijte 18 Mar '10

18 Mar '10

PDP Number: 2010-01 Temporary Internet Number Assignment Policies 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-01.html We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 15 April 2010. Regards Ingrid Wijte Policy Development Officer RIPE NCC

5 9

IPv6 allocations for 6RD
by Jan Boogman 11 Mar '10

11 Mar '10

Hi, we are planning to offer IPv6 connectivity to our xDSL and FTTH customer base via IPv6-6RD. (see <http://tools.ietf.org/html/draft-townsley-ipv6-6rd-01> or for a working implementation Free's presentation at RIPE-58: <http://www.ripe.net/ripe/meetings/ripe-58/content/presentations/ipv6-free.p…>). We asked RIPE NCC for a larger than /32 allocation (because of the way how 6RD encapsulates the customers IPv4 address in his IPv6 address and also because we want to give the customer a small subnet). The IPRA now isn't sure how to proceed and after consultation with the Policy Development Manager asked me to pose the question to the community at large. What do you think, should RIPE NCC allocate larger than /32 blocks to LIRs for cases like this and not only based on the number of end-customers? Cheers Jan Swisscom IP-Plus - AS3303

13 34

Re: [ncc-services-wg] Status Update - Independent Resource Assignments (Policy Proposal 2007-01)
by David Monosov 09 Mar '10

09 Mar '10

Dear Andrew, ncc-services-wg, address-policy-wg, Thank you kindly for this update, it is encouraging to see the success of this initiative. I can't help but notice that the number of marked resources you provide in this report appears to be significantly lower than that in a similar report Andrea Cima provided to address-policy-wg on 26/10/2009 (the previous report states 23,790 resources are marked, while only 22,958 are reported as marked in this update). Could you please elaborate on the nature of this adjustment? Additionally, it has been previously mentioned that a procedural document detailing Phase 3 of the implementation of this proposal will be made available before implementation begins. Seeing that the final deadline is less than two months and a fortnight away, how soon can we expect this document to be available, and are there any operational specifics you can already share with us? -- Respectfully yours, David Monosov Andrew de la Haye wrote: > Dear Colleagues, > > In March 2009, the RIPE NCC began Phase 1 of the policy implementation > "Contractual Requirements for Provider Independent Resource Holders in > the RIPE NCC Service Region". This phase focused on new assignments of > independent Internet number resources only (PI assignments, AS Numbers, > IPv6 Internet Exchange Point (IXP) assignments and Anycasting > assignments). The implementation was carried out successfully and the > majority of RIPE NCC members are aware of the policy and contractual > requirements and are able to provide the necessary documentation when > requesting independent resources on behalf of their End Users. > > Phase 2 of the policy implementation began at the end of May 2009. This > phase focuses on existing assignments (almost 27,000). In the first step > of this phase, the RIPE NCC approached LIRs and asked them to specify > whether: > - The resources were used for the LIR's network infrastructure > - The resources were used by one of the LIR's End Users > - The End User was no longer the LIR's customer > > LIRs must provide documentation for the resources marked as "My End > User" by the end of Phase 2. This documentation should be the "End User > Assignment Agreement" between the LIR and the End User regarding the > registration of the independent Internet resources the End User holds > and the official company registration documents of the End User > organisation. > > Initially, Phase 2 was scheduled to end on 31 December 2009. However, > due to the lower-than-expected number of documents received, the > deadline was first extended until 1 March 2010 and then until 17 May > 2010, which will be the final deadline. > > > The figures showing the progress of Phase 2, as of 1 March 2010, are > presented below. > > > LIRs Participating > ----------------------- > Total LIRs to participate in Phase 2: 4,903 > Number of LIRs participated at 1 March: 4,178 > Percentage of participating LIRs: 85.2% > > > Total Resources Marked > ------------------------------ > Total amount of resources to be marked in Phase 2: 26,940 > Total amount of resources marked at 1 March: 22,958 > Percentage of resources marked: 85.2% > > > Status of 22,958 Resources Marked > ------------------------------------------ > - 5,373 are marked "My Infrastructure" (23.4%) by 3,956 LIRs > - 6,025 are marked "Not My End User" (26.25%) by 712 LIRs > - 11,560 are marked "My End User" (50.35%) by 996 LIRs > > > Status of 11,560 Resources Marked "My End User" > ------------------------------------------------------------- > - 4,849 have missing documents (42%) > - 4,522 have submitted documents (39%) > - 2,189 have approved documents (19%) > > > Regards, > Andrew de la Haye

2 1

followup on RIPE 59: feedback from the RS department
by Gert Doering 26 Feb '10

26 Feb '10

Hi APWG, at the last RIPE meeting in Amsterdam, I asked the RIPE NCC RS department to provide feedback to us regarding the day-to-day working with our policies. We make the policies, but we don't really know how well they work (especially for the great mass of LIRs that don't participate in the policy-making process) unless we get feedback. Alex Le Heux from the RIPE NCC volunteered, and reported the top three issues that cause the most questions and discussion between RS and the LIRs requesting resources. See here for the details: http://www.ripe.net/ripe/meetings/ripe-59/presentations/leheux-rough-edges-… The three issues were: - differences between IPv4 and IPv6 policy - interpretation of the AS number policy - interpretation and wording of the 80% rule At the meeting, we discussed only one of these (the interpretation of the AS number policy, see page 10-16 in the PDF), because we ran out of time - and instead of rushing all three items, the WG chairs decided to focus on one, and bring up the other two on the list. Regarding the interpretation of the AS number policy, feedback from the audience in the room (plus comments in the hallways) was quite clear - everybody who voiced their opinion argued that a LIR that can document multiple distinct routing policies is entitled to multiple AS numbers, even if it's the same organization running all of the network(s). So the Registration Services department was asked to accept multiple AS requests for the same organization if an individual unique routing policy can be documented. For details of this discussion, please see the APWG R59 minutes: http://www.ripe.net/ripe/wg/address-policy/r59-minutes.html Next steps: the WG chairs will bring up the other two items to the AWPG mailing list in the next days. We need to get feedback from the community on the intent and interpretation of the current policy, and if the result is that the current policy is not really what the community wants, get the necessary changes under way. regards, Gert Doering, APWG Chair -- Total number of prefixes smaller than registry allocations: 144438 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

New Draft Document: Autonomous System (AS) Number Assignment Policies
by Filiz Yilmaz 16 Feb '10

16 Feb '10

Dear Colleagues, At the RIPE 59 Meeting in Lisbon last October, the RIPE NCC announced that it would undertake a project to improve the language of various RIPE policy documents, without changing their substance or meaning. This project is aimed at improving the clarity and readability of RIPE Documents. For more information, see: http://www.ripe.net/ripe/updated-documents/ A draft of the first RIPE Document to be revised is now available: "Autonomous System (AS) Number Assignment Policies and Procedures". We have published the draft document in two layouts. The first layout contains only the proposed text, in full, and is available at: http://www.ripe.net/ripe/updated-documents/ASN-v1.html The second layout contains both the current text and the proposed text side by side, and is available at: http://www.ripe.net/ripe/updated-documents/ASN-v2.html At the top of both draft documents there is a summary of the proposed changes. There are two changes we would like to highlight because they constitute a slightly larger change. Paragraph 4.0 - Returning AS Numbers Excerpt from current version: "If an organisation has an AS Number that is no longer in use, it can be returned to the public pool of AS Numbers..." Excerpt from proposed draft: "If an organisation no longer uses the AS Number, it must be returned to the public pool of AS Numbers." The main difference is that the current version says the AS Number "can" be returned, while the draft version says the AS Number "must" be returned. The change was made to better reflect the intention of the policy and to be consistent. In other policy documents, for other Internet resources, the wording of the policy states "must". The other larger change is the addition of the following paragraph: Paragraph 5.0 - Validity of an Assignment This paragraph is copied from the IPv4 policy document ("IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"). As this seems to be a shared policy principle, applicable to all Internet resources, we feel it is appropriate to add this text to the AS policy document, both for clarity and consistency. Other smaller changes are listed at the top of document. Please review the text and send your feedback to the Address Policy Working Group mailing list. The period for review is four weeks and lasts until 26 February 2010. After the review period, the Address Policy WG chairs will conclude whether or not there is consensus on the draft document. Kind regards, Filiz Yilmaz Policy Development Manager RIPE NCC

5 5