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

Agenda for RIPE 56 - 1st draft
by Gert Doering 30 Apr '08

30 Apr '08

Hi APWG folks, below you can find a draft for the agenda for the RIPE address policy WG meeting at the upcoming RIPE meeting in Berlin. The APWG meeting will take place Wednesday, 11:00-12:30 and Thursday, 09:00-10:30. If there is anything else you want to see on the agenda, please let me/us know! In the plenary section on Tuesday morning, we will have a presentation from Filiz Yilmaz on ongoing policy work in other regions, so we know what "they" are working on, and can try to learn from it. (Thanks!) The exact time lines depend a bit on the outcome of the policy proposals currently (and soon to be) in "last call". regards, Gert Doering, APWG chair ----------------------- snip ---------------- Wednesday, 11:00-12:30 A. Administrative Matters 5 min (selecting a scribe, approving the minutes, etc.) B. Overview over concluded protocols 10 min B.1 2007-07 - End Policy for IANA IPv4 allocations to RIRs withdrawn, replaced by 2008-03 B.2 2007-06 - Global Policy for the Allocation of the Remaining IPv4 ... withdrawn, replaced by 2008-03 B.3 2005-08 - Proposal to Amend the IPv6 Assignment an Utilisatio ... (change of /48 to "LIR's choice", /56, and HD-Ratio) accepted B.4 2007-03 - IPv4 Countdown Policy withdrawn, replaced by 2007-06/2007-07, replaced by 2008-03 B.5 2007-04 - IANA Policy for Allocation of ASN Blocks to RIRs accepted in RIPE region (short feedback from ICANN/AC on current global status) C. New Proposals since RIPE 55, just presentation, no discussion yet 15 min C.1 2008-01 - Assigning IPv6 PI to Every Inetnum Holder C.2 2008-02 - Assigning IPv6 PA to Every LIR C.3 2008-03 - Global Policy for the Allocation of the Remaining IPv4 Address Space (IPv4 countdown policy, revisited) [C.4 2008-* - if anything else appears in the meantime] D. "Contracts and Certification session" D.1 2007-01 - wrap up, next steps, comments from the NCC board D.2 report from the Certification Authority (CA) TF - update on operational status [Nigel Titley] 15min - life certification demo 20min - discussion: proposal for initial certifications 10min D.3 new policy proposal from the CA TF, based on discussion Thursday, 09:00-11:30 E. Restart PI discussions (if we have consensus on 2007-01) E.1 2006-01 - Provider Independent IPv6 Assignment for End User Organizations E.2 2006-05 - PI Assignment Size E.3 2008-01 - Assigning IPv6 PI to Every Inetnum Holder F. "End of IPv4" session - generic discussion on how to proceed F.1 2007-08 - Enabling Methods for Reallocation of IPv4 Resources ("The Market" proposal) F.3 2007-09 - Cooperative distribution of the end of the IPv4 free pool (Tony Hain's proposal) F.3 2008-03 - Global Policy for the Allocation of the Remaining IPv4 ... (/8 reservations to RIRs) Z. AOB -- Total number of prefixes smaller than registry allocations: 113403 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 1

2008-01 Review Period extended until 16 May 2008 (Assigning IPv6 PI to Every Inetnum Holder)
by Filiz Yilmaz 30 Apr '08

30 Apr '08

PDP Number: 2008-01 Assigning IPv6 PI to Every Inetnum Holder Dear Colleagues, The Review Period for the proposal 2008-01 has been extended until 16 May 2008. With the acceptance of this proposal, the RIPE NCC will conduct a one-time operation to assign a /56 IPv6 PI prefix to all End Users with an IPv4 assignment registered in the RIPE Database. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-01.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Filiz Yilmaz RIPE NCC Policy Development Officer

7 10

2008-03 New Draft Document Published (Global Policy for the Allocation of the Remaining IPv4 Address Space)
by Filiz Yilmaz 30 Apr '08

30 Apr '08

PDP Number: 2008-03 Global Policy for the Allocation of the Remaining IPv4 Address Space Dear Colleagues, We have published a draft document for the proposal described in 2008-03 and the proposal is moved to Review Phase. This proposal describes the process for the allocation of the remaining IPv4 space from IANA to the RIRs. When a minimum amount of available space is reached, one /8 will be allocated from IANA to each RIR, replacing the current IPv4 allocation policy. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-03.html and the draft document at: http://www.ripe.net/ripe/draft-documents/2008-03-global-policy-draft.html We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 27 May 2008. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

2 1

2007-08 Review Period extended until 28 May 2008 (Enabling Methods for Reallocation of IPv4 Resources)
by Filiz Yilmaz 28 Apr '08

28 Apr '08

PDP Number: 2007-08 Enabling Methods for Reallocation of IPv4 Resources Dear Colleagues, The Review Period for the proposal 2007-08 has been extended until 28 May 2008. This proposal outlines a framework to migrate previously allocated IPv4 resources from one Local Internet Registry (LIR) to another LIR within the RIPE NCC Service Region. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-08.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Filiz Yilmaz RIPE NCC Policy Development Officer

1 0

RIPE 55: APWG minutes (draft)
by Gert Doering 25 Apr '08

25 Apr '08

Hi APWG readers, there seems to have been a slight coordination problem regarding the posting of the APWG minutes to the mailing list - sorry for that, it seems everyone was assuming "it has already been done", but checking my archives, I can't find any trace of it. Anyway - here are the (draft) minutes from the last APWG meeting at RIPE55 in Amsterdam. Please let us know about everything that's not correct, so that I can declare the minutes as final in Berlin. (And a big thanks to the RIPE NCC folks for creating these truly amazing minutes!) Gert Doering APWG Chair ----- Forwarded message from Susannah Gray <susannah(a)ripe.net> ----- Minutes from RIPE 55 RIPE Meeting: 55 Working Group: Address Policy Status: Draft Revision Number: 0 -------------------------------------------------------------------------------- Wednesday, 24th October 2007 11-12:30 Chair: Gert Doering Minutes: Scott Donald (RIPE NCC) Jabber Scribe: Laura Cobley (RIPE NCC) ----- 1. Administrative Matters * Welcome * Select a scribe - Scott Donald (RIPE NCC) * Finalise agenda * Minutes from RIPE 54 were approved http://www.ripe.net/ripe/wg/address-policy/r54-minutes.html * Co-chair changes Andrea Borgato stepped down as co-chair of this working group. Gert Doering and Sander Steffann remain as the two co-chairs. Speak to one of the co-chairs if you are interested in becoming a co-chair. ----- 2. Overview of Concluded Policy Proposals Proposal 2006-02 "IPv6 Address Allocation and Assignment Policy" - was accepted and implemented Proposal 2006-04 "Contact E-Mail Address Requirements" - was withdrawn Proposal 2006-06 "IPv4 Maximum Allocation Period" - was accepted and implemented Proposal 2006-07 "First Raise in IPv4 Assignment Window Size" - was accepted and implemented Proposal 2007-02 "Change in IP Assignments for Anycasting DNS Policy" - was withdrawn Proposal 2007-03 "IPv4 Countdown Policy" - was withdrawn Proposal 2007-04 "IANA Policy for Allocation of ASN Blocks to RIRs" - was accepted by RIPE, and is awaiting other RIRs acceptance ----- 3. Generic Discussion on PI Session Presentation: Feedback from the RIPE NCC Executive Board Regarding Proposal 2007-01 - Axel Pawlik (RIPE NCC) http://www.ripe.net/ripe/meetings/ripe-55/presentations/pawlik-2007-01.pdf There were no questions Presentation: Proposal 2007-01 "What do we do next?" - Nick Hilliard (INEX) http://www.ripe.net/ripe/meetings/ripe-55/presentations/hilliard-2007-01.pdf Gert Doering: commented yearly price of a PI assignment could be 100-300 Euros per year. More than that and the RIPE NCC would make a surplus. The Board would decide the cost. Wilfrid Woeber (ACONET): said that Axel gave some alternative proposals but asked if this proposal was talked about/agreed by the Board? Axel Pawlik (RIPE NCC): said this proposal would make things easier for us. It puts some responsibility on members to help maintain the link with the PI holders. He thought the board would be more positive about this than the previous suggestions. The general meeting, perhaps in May, can discuss changes to the charging scheme. Wilfrid Woeber: asked from the data privacy point of view, what would happen if an end user asks for his information to be removed. From this proposal the resources would eventually be reclaimed. We would need to think about solutions to that. Nick Hilliard: said the RIPE NCC may be breaking data privacy laws for NOT maintaining accurate information on the RIPE database at the moment. Daniel Karrenberg (RIPE NCC): thanked Nick for trying to fix a problem that other people saw, and to put things right again. We tried to encourage PA and not PI in the past (since RIPE 127) but somehow PI became free of charge. So we need to correct this situation. We need to do a lot of clearing up of the old data. Todd Underwood (renesys/babbledog): said that with the DNS system if you stop paying your domain name stops resolving. But with Whois information, nothing would happen if you stopped paying and your details were removed. Nick Hilliard: said RIPE are not the police, they are clearing house and numbers registry. RIPE guarantees uniqueness of the internet resources it issues. If someone hijacks your IP space you need to take it up with the ISP and solve it yourself. Todd Underwood: said the only thing RIPE can do with an expired registration is give it to someone else, or leave it unused in this proposal. So the analogy with the DNS system is flawed. Ruedi Volk (Deutsche Telekom): said clearing up the Whois would also clean out old route objects which are referencing the IP space. Nick Hilliard: said if you stop paying you will lose the entitlement to use it. So you would lose the unique access to this space. Leo Vegoda (IANA): Supported the proposal and wanted implementation speeded up as there are thousands of entries to contact and we want to encourage light regulation of the industry (not heavy regulation). Nick Hilliard: said if consensus is reached we can start quickly. The next opportunity to implement it is May 2008 due to the budgetary impact. Leo Vegoda: agreed it must be approved by the RIPE community. Asked to keep it as simple as possible, and refinements can be made later if required. Nick Hilliard: proposed to put 2007-01 back on the address policy working group for further discussions. Daniel Karrenberg: said he saw no one against the proposal. People not updating their contact details would not be cut off if they are using the IP space. The RIPE NCC has tools (like RIS) that can see if IP space is being used. Perhaps we should add something to the policy saying that LIRs should hold information on the organisations they are routing in case we need to contact them. Nick Hilliard: said that due to data protection, all we can do is ask the LIR to contact the end user for permission to give their contact details to the RIPE NCC. We can't compel LIRs to supply this information. Daniel Karrenberg: said that end users can be encouraged to supply correct contact information to LIRs so that the LIR can update the RIPE Database. The RIPE NCC needs something in writing to implement this. Wilfrid Woeber: wanted the community to give the RIPE NCC a mandate in order to give some sticks to motivate people to collaborate. Another stick is certification, or giving the NCC the right to update objects on the RIPE Database. Another point is that PI is not free, it counts towards the billing score of an LIR for the first 12 months only. This was based on RIPE NCC not charging for holding resources. But now we see there is a running cost for holding and tracking resources so the charging scheme needs to be looked at. PI is too cheap but not free. Hans Petter Holen (Visma IT): thought it was a good proposal. We need a stronger link between the database and who is holding the resources, which is why charging and some kind of certification is needed in the long term. We need to get approval from the community on the proposal and budgetary stuff, then decide how we will police this. LIRs can filter on information on the RIPE Database for example, also black holes could be be used for people who don't pay their bills. Carsten Schiefner (Deutsche Telekom): liked the proposal. Would like more of the policing function in the proposal. Also would like to see what it would cost to implement what Hans Petter Holen suggested. Richard Cox (Spamhaus project): has investigated inappropriate bgp announcements- whatever addresses are used by people doing bad things are bogus. The only solution to get any sort of policing is to get the Tier1s on board. LIRs would need to have contractual agreements with end users saying that only they can use the IP space assigned. Have we asked them? Nick Hilliard: said this is a difficult problem- it involves creating access lists for starters. A lot of Tier1s and Tier2s filter customer announcements already. Inappropriate bgp announcements falls outside the scope of this proposal. Denis Walker (RIPE NCC): supported this proposal. The RIPE NCC is legally obliged to make sure the data on the RIPE Database is accurate so we want a mandate to clean up the database. We receive complaints sometimes due to problems originating from IP space that has incorrect contact details. But we are unable to do anything about it. Gert Doering: said he heard only supporting voices and asked for show of hands if anyone opposed this proposal- no hands went up. Action point on RIPE NCC: prepare for the implementation of Nick Hilliard's proposal if approved by the community in the Address Policy Working Group. Action point on Nick Hilliard: put proposal forward on the mailing list. ----- 4. Presentation : Proposal for Restructuring the IPv6 Address Allocation and Assignment Policy - Leo Vegoda (personal view) http://www.ripe.net/ripe/meetings/ripe-55/presentations/vegoda-v6-policy.pdf Gert Doering: said that we got rid of the 200 rule for IPv6 allocations. George Michaelson (APNIC): said people don't usually come back for more IPv6 space. We are giving out very large amounts of IPv6 space at the moment. Geoff Huston (APNIC): said the PI/PA distinction is confusing everyone and removing it would be good, because an address is an address. We need to decide what we want to achieve from the proposal and what the industry needs from us. Do we want LIRs to get an IPv6 allocation and never come back, or come back for an allocation after a certain time period (like one year). We don't want to replicate IPv4 policies which ended up in scarcity. However coming back for IPv6 allocations every year is maybe too much. Gert Doering: said a PI is given for a well defined need for a well defined network. A PA block allows for growth which is difficult to plan. Coming back every year/ 6 months for new allocations for example gives aggregation problems. Ruedi Volk: said scarcity in IPv6 is no problem, but the routing table size is. The only way to keep control of the number of routes is the PI/PA distinction. Cathy Aronson (ARIN): said one big distinction between PA and PI is that you can't easily change providers with PA. -------------------------------------------------------------------------------- Thursday, October 25, 09:00-10:30 5. Discussion of All Other Current Open Policy Proposals Proposal 2005-08 to Amend the IPv6 Assignment & Utilisation Requirement Policy Sander Steffann: consensus has been reached on this proposal and it will be going through. Proposal 2007-05 IPv6 ULA-Central Sander Steffann: this is waiting for the decision by the IETF. We will re-start this proposal if the IETF gives the go-ahead. If not approved by the IETF it will be withdrawn. ------ 6. End of IPv4 Session Presentation: Proposal 2007-06 "Global Policy for the Allocation of the Remaining IPv4 Address Space" - Roque Gagliano (ANTEL) http://www.ripe.net/ripe/policies/proposals/2007-06.html Toshiyuki Hosaka (JPNIC): also has proposal 2007-07 which is the same as the proposal above except it says only a single /8 will be given to each RIR at the point when new IANA free pool hits 5 */8 Wilfrid Woeber: said it is good to make things reasonable equal at the end. To avoid RIR shopping the number of allocations (N) should be small (1 or 2). Nick Hilliard: said fairest way is N=0. Burn rates in each RIR are significantly different, for example AFRINIC and APNIC, which could create political problems and horse trading later. Addresses should be allocated as needed not for any political purpose. Roque Gagliano: said it is possible that AFRINIC could get the last /8 for example depending on which RIR qualified for an allocation at a particular time. Jordi Palet (Consulintel): said he was against a policy change. Whatever we try to do to be fair may not work, as the policy could be changed again in a few months anyway. One of the aims of the proposal may be to give developing regions more time to implement IPv6, but this could damage the implementation of IPv6 in these regions. Ruedi Volk: said that only N=0 or 1 is acceptable. 1 gives a predictable end game. But the period before this will still be unpredictable which cannot be avoided. Raul Echeberria (LACNIC): said he has a lot of sympathy with the proposal. The current situation is against the conservation of IPs because the more you allocate the more you get. Certainty and predictability is important at the end. Gert Doering: said this proposal will move the uncertainty phase sooner. Another suggestion is to make IPs more difficult to get- we should never do that because IPs should be issued on the basis of need. Roque Gagliano: said other RIRs gave feedback saying this proposal will allow more time for planning. If the gentleman's agreement about 2 * /8s at a time is not stuck to, one of the big RIRs could get the last 8 * /8s for example. Geza Turchanyi (Magyar Telekom): said we should go to IPv6 faster to avoid this solution. The RIR receiving the last /8 will have a lot more IPs than the other RIRs have. Niall Murphy (Google): said RIR shopping should be considered in the solution. Roque Gagliano: said we don't know what will happen after exhaustion day. Some large multinational companies can already get addresses from different RIRs around the World. Niall Murphy: said some large organisations with a presence around the World will be able to RIR shopping, but smaller ones will not. N=1 or 0 looks okay, but 5 is odd. David Kessens (Nokia Siemens): said we are in the business of giving addresses to people that need it, not to reduce uncertainty for RIRs. Carsten Schiefner: said certainty argument not so important. The IP needs for larger RIRs are greater than that for smaller RIRs. Roque Gagliano: said we continue with current policies but we are only talking about the last /8s. Any formula we decide on, someone can consider unfair. Laura Cobley (RIPE NCC): Jabber comment from Per Heldahl- no matter what we do there will always be someone who gets the last /8. He thinks all the RIRs should run out at approximately the same time. He suggest that IANA could issue single /8s at a time. Gert Doering: said that was an interesting suggestion. He thought that saying the RIRs would not stick to the gentleman's agreement is somewhat offensive as it shows some mistrust. Geoff Huston: said the end of the free allocations does not mean the end of IPv4. We should be worrying about what happens next instead of this because there is not much time left. Gert Doering: summary of discussion- no support for N=5, some support for N=1. A lot of voices for 0. No consensus in the room. If we do it, N=1 is the one to pursue. We will discuss in the working group and the PDP process. Wilfrid Woeber: asked if N=5 was ratified by APNIC? Roque Gagliano: said it is waiting for the LACNIC board's decision. Wilfrid Woeber: said this will need global agreement. N=5 won't be agreed on globally. Raul Echeberria: said he thinks the board will not approve this so the discussion remains open. ----- Presentation: Proposal 2007-08 Reallocation of v4 resources - Remco van Mook (Virtu) http://www.ripe.net/ripe/meetings/ripe-55/presentations/van-mook-2007-08_re… Geoff Huston: asked if there will be any conditions or constraints on the LIR "disposing" of an allocation. In the APNIC proposal the "disposing" LIR can't get another allocation for 2 years. 2 years because it will take 1 year for the proposal to go through and APNIC will probably not be able to issue more allocations 2 years after that. So the selling LIR can't come back and get another allocation to sell. Remco van Mook: thought restraints like this would decrease liquidity of IP addresses. We would like people to start using this proposal before we run out of addresses. Geoff Huston: said in the APNIC proposal the acquirer of the allocation would be required to have a 80% usage rate on all its allocations (including acquired ones) before it could qualify for an additional allocation. Remco van Mook: said it is not in this proposal, but usage rates will be looked at under current policies. Gert Doering: said that 80% usage to qualify for an additional allocation should be made clear. Geoff Huston: said people might acquire IPs to sell them later. An idea he heard might be that allocations can only be transferred once, to try and reduce the number of speculators. Remco van Mook: said it would be bad for liquidity to only be able to transfer an allocation once. Leo Vegoda: said the proposal says allocations can only be transferred within the RIPE region. Is it an issue if the physical address of buying organisation is outside the region? Remco van Mook: said it would not be a problem as long as the address space is registered with the RIPE NCC. Laura Cobley (RIPE NCC): Jabber comment from Per Heldahl- NRO guidelines say that IPs are not held as property. These guidelines would need to be changed. Gert Doering: said the guidelines say addresses are not property but companies are being bought with networks and addresses included. Geza Turchanyi: said we should create a pool for re-using addresses. Hans Petter Holen: said people are already buying and selling companies which include IPs. Today we assign this commodity based on need. We are creating a market for this commodity. Maybe we need to do some research into what happened in other industries in the past in these situations. Cathy Aronson (ARIN): said perhaps we should have a restriction such as you are not allowed to sell IPs until 2 years after they were allocated. Remco van Mook: said that was a good idea. Mark McFadden (BT): said RIPE already has a policy and mechanism for transferring allocations between LIRs. He is worried about the unintended consequences of this proposal which are that IPs can be seen as assets so people may be taxed on them. The market part is worrying. Remco van Mook: said we should seek some advice from economic experts outside the community. Gert Doering: summary of discussion- some support and some words of caution. We need to discuss further on the mailing list. ----- 7. Formulation of an official statement from the RIPE community regarding the end of IPv4, and recommendations for moving towards IPv6. - Sander Steffann http://www.ripe.net/ripe/meetings/ripe-55/presentations/steffann-ripe-resol… Gert Doering: said external organisations have asked what our official opinion is on IPv6. As the RIPE NCC is a secretariat they can't make political statements which is why we are asking you. It will be finalised in the IPv6 working group. Jim Reid (RIPE NCC executive board): said point 5 should mention software vendors in addition to equipment vendors. Rob Blokzijl (RIPE): said this statement is meant for an external audience, like governments and policy makers. It is not a manual about how to implement IPv6. We should focus on the message and not have too much detail, or the intended audience will lose interest. Sander Steffann: said the idea is to give people a message to move to IPv6. Geza Turchanyi: said the statement that the internet will continue as normal is too strong. Jim Reid: said the message should be business as usual even if we run out of IPv4 addresses. Websites and email etc will still work after IPv4 runs out. Sander Steffann: asked for feedback on point 2. Ruedi Volk: asked if this statement is saying application providers don't have to do IPv6 until network providers and ISPs do the gateway? Sander Steffann: said maybe the wording needs to be broadened. Ruedi Volk: said we should cut down specifics as much as possible. Sander Steffann: asked for feedback on point 3. Bernard Tuy: said it is not useful to have this point here. IPv6 has been in operation for years. Rob Blokzijl: said this point will confuse the audience. It should convey the message that we don't need other organisations involvement to deal with this problem. It needs re-wording. Sander Steffann: agreed some re-wording is needed. He then asked for feedback on point 4- there were no comments. He then asked for feedback on point 5. Rob Blokzijl: said drop this as it is covered by point 4. Niall Murphy: said pressure on vendors comes in tender documents, not here. Remco van Mook: said keep the message as short as possible, the message is do IPv6 now. Geza Turchanyi: said IPv6 is running in the backbone but for DSL is poor. Some encouragement for IPv6 in this area should be encouraged. Jord Palet: said a message to end users to request IPv6 is not here. You could make separate texts for users, vendors, policy makers. The message should be focussed not short. Rob Blokzijl: said he does not agree with Jordi. The community needs a single short statement for policy makers, governments etc. There is a problem (with IPv4 exhaustion) but not as bad as people think. Sub-sections will not be useful. David Kessens: said the message needs to be short and simple. This will be discussed in the IPv6 Working Group, where a longer session has been made available. Gert Doering: summary of discussion- Sander Steffann and I will work with Rob Blokzijl and David Kessens in the working group to try and finalise this. END---- ----- End forwarded message ----- Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 110584 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

Does any kind of IPv4 transfer policy make sense
by michael.dillon＠bt.com 24 Apr '08

24 Apr '08

I've been thinking a lot about the various proposals for new IPv4 transfer policies, many of which seem to want to create a market for IPv4 address blocks. In a recent discussion, someone suggested that there are two things that RIRs can and should do, in order to mitigate the effects of IPv4 exhaustion. 1. Reclaim unused allocations 2. Allow IPv4 address block transfers In most of the discussions about IPv4 exhaustion, these two actions are treated as separate activities. The first is an extension of what the RIRs and IANA have already been doing for many years. And the second is a wonderful new idea that will let organizations buy IPv4 addresses when RIPE runs out. But if you look closely and what "transfer" means, it becomes complex, confusing, and very unclear. In my opinion, is transfer is not separate from reclamation. In fact it *IS* reclamation. Instead of RIPE looking for unused allocations, it is LIRs looking for unused assignments. What happens after the unused addresses are identified is really not as important as the fact that no reclamation/transfer can happen until unused addresses are found. How likely is it that we will find unused address blocks at a time when the fresh supply of IPv4 addresses has run out? The RIRs have always tried to have transparent processes surrounding IP addressing. That's why we have the RIPE database which publishes a directory of who uses any particular IP address range. But how accurate is it. How many of these IP addresses are really in use? As long as we assume that the RIPE database is basically accurate, and that a higher percentage of all IPv4 addresses will be in a "used" state when we reach IPv4 exhaustion, this implies that there will be very few IP address blocks available to be transferred. And if that is true, this implies that the price per address block (if selling is allowed) will be very high, and rise over time as the unused addresses in the RIPE database become more scarce. Those prices could very well rise to such a high level that it is cheaper to simply buy out smaller companies and disconnect less profitable customers in order to get access to their address blocks. I feel that we need to pay more attention to analysing what addresses are really in use (used in source/destination headers of IP packets on the Internet) and to providing support and education to LIRs so that they can better audit their own allocations. --Michael Dillon

2 1

Agenda suggestions for RIPE56?
by Gert Doering 15 Apr '08

15 Apr '08

Hi APWG folks, we're currently working on a draft agenda for the upcoming RIPE meeting in Berlin, which I'll send in a few days. The "usual" stuff will be there of course (discussion of all open policy proposals, and time generic policy discussions). If there is anything special you want to see on the Agenda, please let me know, so I can put it in. Gert Doering -- APWG chair -- Total number of prefixes smaller than registry allocations: 110584 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

proposal about 2007-1
by Frederic 10 Apr '08

10 Apr '08

hi, i propose to change:This proposal states that a contractual relationship between an End User and a sponsoring LIR or the RIPE NCC must be established before the End User receives Internet number resources by: This proposal states that a contractual relationship between an End User and a sponsoring LIR or the RIPE NCC may be established before the End User receives Internet number resources. today, is not posible to etablish relationship with ripe. now with this modification of the 2007-1 that is possible but not an obligation. bst regards. Frederic CELLA

7 9

Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
by frederic＠placenet.org 09 Apr '08

09 Apr '08

> > > address-policy-wg-admin(a)ripe.net wrote on 08/04/2008 16:29:22: > >> Frederic <frederic(a)placenet.org> >> Sent by: address-policy-wg-admin(a)ripe.net >> >> 08/04/08 16:29 >> >> To >> >> Ian.Meikle(a)nominet.org.uk >> >> cc >> >> address-policy-wg(a)ripe.net >> >> Subject >> >> Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct >> Internet Resource Assignments to End Users from the RIPE NCC) >> >> Le mardi 08 avril 2008 à 16:09 +0100, Ian.Meikle(a)nominet.org.uk a >> écrit : >> > > Leo Vegoda <leo.vegoda(a)icann.org> >> > > Sent by: address-policy-wg-admin(a)ripe.net >> > > >> > > 08/04/08 13:29 >> > > >> > > To >> > > >> > > Frederic <frederic(a)placenet.org>, Shane Kerr > <shane(a)time-travellers.org> >> > > >> > > cc >> > > >> > > Max Tulyev <president(a)ukraine.su>, "address-policy-wg(a)ripe.net" >> > > <address-policy-wg(a)ripe.net> >> > > >> > > Subject >> > > >> > > Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct >> > > Internet Resource Assignments to End Users from the RIPE NCC) >> > > >> > > Hi Frederic, >> > > >> > > On 08/04/2008 03:58, "Frederic" <frederic(a)placenet.org> wrote: >> > > >> > > [...] >> > > >> > > > why is broken ? because Ripe do not implement relation between PI >> > holder >> > > > thru Database information. >> > > > >> > > > Dead PI is like Dead Domain name. >> > > >> > > This is a fairly good analogy. My understanding of domain names is > that >> > they >> > > are normally delegated according to a contract with a registry or >> > registrar. >> > > If the contract ends the delegation is removed. >> > > >> > There is a thriving market in 'dead' domain names. Several of our >> > registrars base their business models around buying them and reviving > them. >> > For this to work they need to have a contract with us, and they need >> to > pay >> > a fee per domain name. >> > >> > However, the leverage we have is that the contract on a domain name is > time >> > limited, with on option to renew. >> >> >> it is not true for all domain. and the "not for all" is important. >> >> that why we do not support : contract for all RESSOURCE. let choice by >> change MUST by MAY. >> >> > Can you provide a counter example? > counter exemple for ? domain ? .st .nf or .eu.org. all are free. Free because 1$ some time is huge. no contract because everybody is not hijacker and all idea may be possible. bst regards. Frederic > Ian >

6 9

Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
by Max Tulyev 09 Apr '08

09 Apr '08

Sure, dealing with domains is like IP networks. But unlike domains, PI IP networks is not billed yearly (yet). May be we should return back old charging scheme when PI is billed yearly to LIRs? This will enforce return unused space, make contracts between LIRs and end-users, and so on just *automagically* ;) frederic(a)placenet.org wrote: >> Frederic, >> >> current system is NOT working well. >> >> Just because we can't trace dead companies and dead assignments and >> reuse it. In 1-2 years all unused space will be assigned. >> > > I suppose all (dead-compagny) block has an ripe datatabse record ? > > can use the same way that a drop domain name ? > > >> But if even that policy will be implemented - how we can enforce it? How >> can we revoke that space if need? >> > > I think that domain name way is interesting to implement ? > > before to be a contractual document, is a moral contract. > > bst regards. > Frederic > >> Frederic wrote: >>> We support if: >>> No Fees is required for this contractual relationship. >>> and this contractual relation ship do not exist between and user and one >>> LIR. >>> >>> else >>> we do not support, today system works well. >> >> -- >> WBR, >> Max Tulyev (MT6561-RIPE, 2:463/253@FIDO) >> > > -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

2 1

2008-1
by Frederic 09 Apr '08

09 Apr '08

we support this proposal and want extend a /64 for all identified inetnum holder like an ISP. ABOUT: General: The RIPE NCC understands that the Address Policy WG Chairs would require the full implementation of this proposal only after the outcome of Policy Proposal 2007-01, which generally discusses direct End User assignments. This would be the case even if Policy Proposal 2008-01 concludes first. our change of proposal about 2007-1, help to support 2008-1. bst regards. Frédéric CELLA

1 0

Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
by Ian.Meikle＠nominet.org.uk 08 Apr '08

08 Apr '08

> Leo Vegoda <leo.vegoda(a)icann.org> > Sent by: address-policy-wg-admin(a)ripe.net > > 08/04/08 13:29 > > To > > Frederic <frederic(a)placenet.org>, Shane Kerr <shane(a)time-travellers.org> > > cc > > Max Tulyev <president(a)ukraine.su>, "address-policy-wg(a)ripe.net" > <address-policy-wg(a)ripe.net> > > Subject > > Re: [address-policy-wg] 2007-01 Last Call for Comments (Direct > Internet Resource Assignments to End Users from the RIPE NCC) > > Hi Frederic, > > On 08/04/2008 03:58, "Frederic" <frederic(a)placenet.org> wrote: > > [...] > > > why is broken ? because Ripe do not implement relation between PI holder > > thru Database information. > > > > Dead PI is like Dead Domain name. > > This is a fairly good analogy. My understanding of domain names is that they > are normally delegated according to a contract with a registry or registrar. > If the contract ends the delegation is removed. > There is a thriving market in 'dead' domain names. Several of our registrars base their business models around buying them and reviving them. For this to work they need to have a contract with us, and they need to pay a fee per domain name. However, the leverage we have is that the contract on a domain name is time limited, with on option to renew. If they do not renew then we remove the domain name from DNS. There is then a time lag before the domain is released back into the market. In other words, we control service, so we can enforce the contract. The NCC does not have a similar lever. Regards, Ian Regards, Ian

2 2

2007-01 Last Call for Comments (Direct Internet Resource Assignments to End Users from the RIPE NCC)
by Filiz Yilmaz 08 Apr '08

08 Apr '08

PDP Number: 2007-01 Direct Internet Resource Assignments to End Users from the RIPE NCC Dear Colleagues, The proposal described in 2007-01 is now at its Concluding Phase. This proposal states that a contractual relationship between an End User and a sponsoring LIR or the RIPE NCC must be established before the End User receives Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. It also states that the text in the policy should mention more explicitly that PI assignments can not be sub-assigned. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2007-01.html Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 5 May 2008. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

11 21

Policy proposal 2007-01, "Direct Internet Resource Assignments to End Users from the RIPE NCC"
by Axel Pawlik 08 Apr '08

08 Apr '08

[ I wanted to send this a little earlier, but was caught up in transit to the ARIN meeting. cheers, Axel ] Dear all, It has come to my attention that the community has pointed out that there is no draft of an actual End User contract included in policy proposal 2007-01. This issue has been raised after the proposal was moved to the Review Phase of the Policy Development Process (PDP) and a draft policy document was published. After extensive discussion, the RIPE NCC Executive Board does not believe that the addition of a draft contract to proposal 2007-01 is necessary. Preferred model The Executive Board anticipates that this proposal will introduce a dual model whereby an End User can chose to have *either* a contract with a "sponsoring Local Internet Registry (LIR)" or directly with the RIPE NCC. The Executive Board believes that having a “sponsoring LIR” is the preferred model; the RIPE NCC currently has more than 5400 members, from which the sponsoring LIR can be chosen. This model has been outlined in the draft document. Further, the Executive Board maintains that the RIPE NCC should not be involved in any contractual processes or details that occur between an LIR and its customer. Such contracts should be formulated by the "sponsoring" LIR and not by the RIPE NCC. However, the Executive Board would like to point out that any contract between End User and "sponsoring LIR" must be formulated clearly so that the End User understands the consequences,as outlined in the RIPE proposal, of applying for or holding a direct resource assignment. Proposal 2007-01, and existing RIPE policies, already have references to such consequences and outline possible cautions that "supporting LIRs" may want to include in their customers' contracts. The RIPE NCC, however, will always available for consultation about the consequences and cautions mentioned above. Direct contracts with the RIPE NCC The Executive Board also understands that the proposal introduces the option for those End Users who cannot form a contract with a "Sponsoring LIR" to form a contract directly with the RIPE NCC. In this case the End User will be required to set up an LIR and become a RIPE NCC member. Charging Scheme If this proposal is accepted, the charging scheme applied by the RIPE NCC to "Sponsoring LIRs" will be addressed by the RIPE NCC Executive Board in due course and reviewed by the RIPE NCC membership during RIPE NCC General Meetings. Conclusion Overall, the Executive Board and I understand that the proposal's intention is to facilitate clear and improved contractual relationships with End Users so that the obligations of responsible stewardship of Internet resources can be fulfilled by LIRs and the RIPE NCC. We believe that the details of the actual contracts between End User and "supporting LIR" should be devised by the LIR. It is, of course, the responsibility of the LIRs together with the RIPE NCC to ensure that the details set out in these contracts comply with the guidelines that the RIPE policies have set. Regards, Axel Pawlik Managing Director RIPE NCC

3 4

New AS Number Block allocated to the RIPE NCC
by Alex Le Heux 07 Apr '08

07 Apr '08

Dear Colleagues, The RIPE NCC received the AS Number Block 47104 - 48127 from the IANA in April 2008. You may want to update your records accordingly. Best regards, Alex Le Heux RIPE NCC

1 0

Re: 2008-03 Discussion Period has ended (Global Policy for the Allocation of the Remaining IPv4 Address Space)
by Roque Gagliano 03 Apr '08

03 Apr '08

Filiz, I guess the option is 1) we will be presenting the proposal at RIPE meeting. Regards, Roque On Apr 2, 2008, at 8:58 AM, Filiz Yilmaz wrote: > PDP Number: 2008-03 > Global Policy for the Allocation of the Remaining IPv4 Address Space > > Dear all, > > The discussion period for the proposal described in > 2008-03 has ended. > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2008-03.html > > Please note that there we no posts to the mailing list regarding the > proposal. > > Please reply to this email to let us know how you would like to > proceed. > > * Do you want to prepare the documentation that will support this > policy change? We will send you further instructions about this. > > * Do you want to extend the discussion period? Please let us know > what > date you wish to extend it to, and we will tell the RIPE community. > > * Do you want to update the text in your proposal and set a new > discussion period? > > * Do you want to withdraw this proposal? > > Please let us know your decision in the next seven days. > > We look forward to your response. > > Regards > > Filiz Yilmaz > RIPE NCC Policy Development Officer

2 1

about policy proposal : 2008-01 Moved to Review Phase (Assigning IPv6 PI to Every Inetnum Holder)
by Frederic 01 Apr '08

01 Apr '08

<< To qualify for a direct assignment, the organisation must become a Local Internet Registry (LIR) or have a similar contractual relation >> 2006-1 The organisation MUST be LIR. but with ipv4-PI, the organisation must not be an LIR. so for Pi-ipv6 like pi-ipv4. the organisation must request assignement thru an LIR. but not MUST be an LIR. Why PI-ipv6 is not possible today ? we beleive that is it important for organisation who use Pi-ipv4 today, to have the possiblity to request PI-ipv6. so ripe must adopt the proposal of PI-ipv6, right now. We support all of proposal that not block assignment of PI-ipv6. so we support 2006-1 the status of LIR is not required by the organisation that request but the request must be done by an LIR. and we support 2008-1 and 2005-08 End User- assignent is done by LIR or ISP. : /64 for physical/extra small organisation. /56 organisation. bst regards Frederic

1 0

Questions on IPv6
by Natalya Petrova 28 Mar '08

28 Mar '08

Dear colleagues, I need your help on a question of upgrade IP- addresses from version IPv4 on version IPv6: 1) Have I understood corretly, that really start of upgrade is 04.02.2008? 2)Till what date/year is it planned to upgrade completely existing addresses with IPv4 on IPv6? 3) What completion date IP of IPv4 addresses? What parallel term IPv4 and IPv6? 4)There will be automatic a updating in base RIPE (ripe.net) structures existing IPv4 addresses on IPv6? Or it will be necessary to make a re-registration manually in base RIPE? 5)In case of our readiness for transition on IPv6 - what documents is it necessary to give to experts RIPE (in what form it is necessary to notify you and on what e-mail?) 6)Is it possible to make gradually updating IP of addresses with IPv4 on IPv6, for example part IP of Kazaktelecom addresses will be upgraded in 2009, and part IP of Kazaktelecom addresses in 2010, etc.? I ask your assistance in the explanatory. Thanks for cooperation and for the help. Best regards, Natalya

2 1

2008-01 Moved to Review Phase (Assigning IPv6 PI to Every Inetnum Holder)
by Filiz Yilmaz 28 Mar '08

28 Mar '08

PDP Number: 2008-01 Assigning IPv6 PI to Every Inetnum Holder Dear Colleagues, The impact analysis for the proposal described in 2008-01 has been published and the proposal is moved to the Review Phase. If this proposal reaches consensus, the RIPE NCC will conduct a one-time operation to assign a /56 IPv6 PI prefix to all End Users with an IPv4 assignment registered in the RIPE Database. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-01.html We encourage you to send your comments to address-policy-wg(a)ripe.net before 16 April 2008. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

19 26

RE: [address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
by Hank Nussbacher 26 Mar '08

26 Mar '08

At 12:20 AM 12-03-08 +0000, michael.dillon(a)bt.com wrote: > > "Expired per the 1st of Januari 2007" > > > > The following one is apparently still valid though: > > http://www.st-ab.nl/wetten/1064_Wet_op_het_financieel_toezicht_Wft.htm > >Yes, the little details are important. > > > There is no mention at all about virtual property or the > > 'owning' of numbers though. A zipcode is no property, nor is > > a bankaccount number etc. > >Nobody has seriously suggested that IP addresses are property or >that transfer policies would change the ownership of IP addresses. >Instead, people are talking about buying and selling contracts >which give the right to use a specific IP address allocation. >This is a lot like a commodities contract, for instance you >can buy a contract for the delivery of a ton of copper, and >then sell that contract to somebody else. You never actually >own a ton of copper because you are buying and selling contracts. >There are many varieties of contract like this, usually called >derivatives (except for insurance and re-insurance). All of >these contracts are covered by the MiFID rules and are regulated >by national regulators such as the FAS in the UK. If the wording in RIPE stated the word "lease", why wouldn't that work? A customer comes and "leases" IP space from RIPE for the duration of their contract with RIPE (membership dues, fulfillment of rules, etc.) When their membership ends, the lease is broken and the IP space returns to RIPE. I bring your attention to: http://www.ripe.net/rs/news/global-ipv6-assign-2001-12-22.html 4.1. Address space not to be considered property It is contrary to the goals of this document and is not in the interests of the Internet community as a whole for address space to be considered freehold property. The global IPv6 policies in this document are based upon the understanding that address space is lease-licensed for use rather than owned. All Internet Registries are expected to manage address space operations correctly in accordance with this principle. According to this policy, IP addresses will be allocated on a lease- license basis, with such lease-licenses to be of specific limited duration of normally one year. Conditions of a lease-license have specific conditions applied at the start or renewal of the lease. Lease-licenses will typically be renewed automatically at the end of their duration when the following two conditions are met: a) The original basis of the allocation remains valid. b) Registration requirements relating to that allocation have been fulfilled at the time of renewal However, when a lease-license is renewed, the new lease-license will be evaluated under and governed by the applicable resource allocation and renewal policies in place at the time of renewal. Changes to the conditions of current lease-licences shall be subject to a definite period of notice, except in exceptional circumstances recognized by a consensus of the Internet community. As address space is not owned, and consistent with the desire to avoid excessive fragmentation of address space, it may become necessary in extreme circumstances to renumber assignments. Such renumbering will only be undertaken after extensive consultation with the Internet community. ---------------------------------------- Unfortunately, RIPE has never used the word "lease" after 2001. The word "lease" was removed when the doc became policy: http://www.ripe.net/docs/ipv6policy.html Also the entire last paragraph was removed including the critical "As address space is not owned...". I have no clue as to whether anything similar was done for IPv4. -Hank

6 5

2008-02 Moved to Review Phase (Assigning IPv6 PA to Every LIR)
by Filiz Yilmaz 26 Mar '08

26 Mar '08

PDP Number: 2008-02 Assigning IPv6 PA to Every LIR Dear Colleagues, The impact analysis for the proposal described in 2008-02 has been published and the proposal is moved to the Review Phase. If this proposal reaches consensus, RIPE NCC will conduct a one-time operation to allocate an IPv6 block to every LIR that does not have any existing IPv6 allocation. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-02.html We encourage you to send your comments to address-policy-wg(a)ripe.net before 16 April 2008. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

12 13

RE: [address-policy-wg] [OT] IPv4 addresses in RIPE database.
by Marcin Gondek 22 Mar '08

22 Mar '08

Hello, > rule of thumb as heard in ripe-ncc's LIR workshop: > everything larger than 4 IP Adresses should be assigned in ripe-db; dsl > end users e.g. are your own infrastructre - you do not need to assign > this individually, Live example: ADSL user (a company) with assigned a 8/5 static network => /29 subnet. LIR have to/should/can add this subnet as separate inetnum in RIPE DB? -- Marcin Gondek / Drixter e-utp.net NIP: PL1181589645 REGON: 140584662 Tel. +48602159929 Fax. +48222012418 office(a)e-utp.net http://www.e-utp.net

1 0

[OT] IPv4 addresses in RIPE database.
by Marcin Gondek 22 Mar '08

22 Mar '08

Hello All, Which policy, rule or document of RIPE describes that if ISP giving to customer more than one IP address then those addresses have to/should be saved into RIPE database as independent entry of inetnum? Or there is no rule, and ISP doing it because they want to make "clear view" of used IP addresses. Thanks in advance. PS: I tried to find on RIPE website. Question is about IPv4. -- Marcin Gondek / Drixter e-utp.net NIP: PL1181589645 REGON: 140584662 Tel. +48602159929 Fax. +48222012418 <mailto:office@e-utp.net> office(a)e-utp.net <http://www.e-utp.net> http://www.e-utp.net

2 2

2007-01 End User Relationships
by michael.dillon＠bt.com 17 Mar '08

17 Mar '08

I strongly support proposal 2007-01 which states this on the web page: ----------- This proposal states that a contractual relationship between an End User and a sponsoring LIR or the RIPE NCC must be established before the End User receives Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. It also states that the text in the policy should mention more explicitly that PI assignments can not be sub-assigned. ------------ I've been personally stuck in the middle of PI applications by end users and I don't believe that we, as an LIR, add any value to the process. In some cases, I believe we just create problems because we end up passing on messages between RIPE and the End User instead of allowing the two parties to communicate directly. After all, PI means Provider Independent, and since LIRs are providers, shouldn't the End User be independent of us when they apply for their addresses? Also, I have had experience on several occasions, of helping End Users in the ARIN region apply for PI allocations there. My role was to advise, explain, educate and to review their applications before they submitted them to ARIN. Every one of these End Users were eventually successful in their application, in fact one of them got it approved the same day they applied. The reason I am telling you this is to point out, that giving End Users a direct relationship with RIPE, does not mean that the LIRs are blocked from the whole process. If the End User is a customer, we can still help them by advising, explaining, educating and reviewing the applications before they go to RIPE. --Michael Dillon

1 0

Conflict over right to use IP addresses in The Netherlands
by Sander Steffann 13 Mar '08

13 Mar '08

Hi, FYI: There is a conflict in The Netherlands about who can use certain IP addresses. When the company DIS Hosting went bankrupt, they were bought by Real Hosting. Real Hosting is now the holder of the IP blocks previously used by DIS Hosting. Now it turns out that another company, Fiberworld, is using IP space from this block... Real Hosting and Fiberworld could not come to an agreement about the ownership / transfer of those IP addresses, so Fiberworld started a lawsuit. A judge has ruled that Fiberworld must be allowed the use of the IP addresses for 30 days, so they have time to prove they have the right to use those addresses. An article about this (in Dutch): http://www.ispam.nl/archives/1703/rechtszaak-om-ip-adressen-van-dis-hosting/ - Sander

5 6