October 2009 - address-policy-wg

2009-03 Last Call for Comments (Run Out Fairly)
by Ingrid Wijte 29 Oct '09

29 Oct '09

PDP Number: 2009-03 Run Out Fairly Dear Colleagues, The proposal described in 2009-03 is now at its Concluding Phase. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2009-03.html Please note that we have also updated the proposal to version two. This new version has some minor textual changes, clarifying the intent of paragraph 6.3. Please e-mail any final comments about this proposal to address-policy-wg(a)ripe.net before 26 November 2009. Regards Ingrid Wijte Policy Development Officer RIPE NCC

1 0

Details regarding the progress of 2007-01 Phase 2 implementation?
by David Monosov 27 Oct '09

27 Oct '09

Dear address-policy-wg, As phase 2 of the implementation of 2007-01 is well underway and gradually approaching its conclusion, it might be both interesting and beneficial to see some details about the success of this effort so far. Could RIPE NCC furnish the following data at their earliest convenience for the benefit of this work group, and if workload permits, provide monthly updates until phase 2 is complete? - Number and % of direct assignments marked by LIRs as "My End User". - Number and % of direct assignments marked by LIRs as "Not My End User". - Number and % of direct assignments marked by LIRs as "My Infrastructure". - Number and % of direct assignments marked by LIRs as "My End User" for which contracts and registration information were provided but are not yet processed. - Number and % of direct assignments marked by LIRs as "My End User" for which contracts and registration information were provided and subsequently approved by RIPE NCC. - Number and % of direct assignments marked by LIRs as "My End User" for which contracts and registration information were provided and subsequently rejected by RIPE NCC. - Number and % of direct assignments which fall under the scope of 2007-01 phase 2 which remain completely untreated. This data should provide some insight about the challenges that further implementation phases will entail, and create an opportunity for the community to address such challenges on the policy level in a timely manner if required. -- Respectfully yours, David Monosov

4 6

Allocations/assignements statistics ?
by Bernard Dugas 24 Oct '09

24 Oct '09

Dear Colleagues, To analyse the use of IPV4 currently, i need to have the number and size of IPV4 prefixes, PA allocated and PI assigned, and ASN, linked to the 5 membership categories. It should be consistent with other data avalaible, meaning that snapshot of 20090930 would be optimal. Thanks a lot, Best regards, -- __Bernard DUGAS ______________________________________________________

2 2

RIPE staff vs Court
by Max Tulyev 24 Oct '09

24 Oct '09

Hello! Today I just got a strange letter from RIPE staff. I didn't saw anything like that before. They told me about a ten of networks registered through our LIR. All these networks have changed admin-c and tech-c to other country, and routed through one server on that country. Based on this, RIPE man sent the notification about reclamation of that networks, as "that seems to don't be valid anymore." Of course, I immediately contacted my client and asked what's happened. He said they work as usual, but one certain offshore IT company is used to manage their networks. So they changed contact details to that company, as that company is correct contact point in any network questions. And traffic flows through the offshore company site as they manage and control it, hosts data, etc. >From one point of view, situation seems very strange. From second - nothing to be not real in practice. So we (first time?) faced with IP reclamation dispute. I don't really know did our clients something bad - perhaps no, as none from these nets listed at Spamhouse ;). I think it is 50/50. May be they told me (and RIPE) truth, may be lied. I can't 100% check it by tools/rights/possibilities I have. But about ten of businesses are on decision of one person that "seems to ...". My strong position is THERE SHOULD BE A COURT DECISION OR OUR COMMUNITY COURT-LIKE STRUCTURE, and only that structure based on court-like controversy process (if not a real court) can make a decision about reclaim any address space. NO WAYS LIKE "IT SEEMS TO...". So now we have: http://www.ripe.net/ripe/docs/ripe-475.html#42 My proposal is to change: "Violation of Law by the End User, supported by a Dutch court order; or violation of RIPE Policy by the End User" to "Violation of Law by the End User, supported by a Dutch court order; or violation of RIPE Policy by the End User, SUPPORTED BY..." By what? By Dutch Court? By some independent court-like staff? Any ideas? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

6 12

Re: [address-policy-wg] Inet6num requirements in the db
by Arkley, Patrick 13 Oct '09

13 Oct '09

I'm fine with that. Thanks. / Patrick Arkley ** sent from mobile device ** ----- Original Message ----- From: Gert Doering <gert(a)space.net> To: Arkley, Patrick Cc: address-policy-wg(a)ripe.net <address-policy-wg(a)ripe.net> Sent: Tue Oct 13 09:29:31 2009 Subject: Re: [address-policy-wg] Inet6num requirements in the db Hi, there's two parallel "inet6num registration" discussions going on at the same time - let me respond to this one first, because it's a bit easier. On Fri, Oct 09, 2009 at 01:52:07PM +0200, Arkley, Patrick wrote: > I seem to recall from the RIPE meeting that Axel talked about the RIPE > database as a valuable source of information. Also other organisations > thinks it is a valuable and trustworthy source. It is also a very easy > way of finding out the most likely users (at least one step down stream > from the LIR) of a specific IP-range. > > But how come there is no requirement to add end-user objects for IPv6? > Only the LIR's allocations are required. If we want to continue the work > that has been done for IPv4 I think we need end-user objects for IPv6 as > well. Regarding end-user registrations in the RIPE DB, there are a few conflicting interests to balance: - finding someone "who can make it stop" in case of net-abuse - knowing the end user - protection of personal data for private users - documenting that the network resources are properly used The crucial one is balancing the first one vs. the third one. For private users, there really is no point in having the contact data of the end customer in the database - because if they get some angry e-mails or phone calls from someone who is just now being attacked from their PC, the chance is very high that this end user has no idea whatsoever to do about it. So the best point of contact in that case might be the ISP, who knows the customer, knows whom to call, and how to bring the message "your 0wn3d" across. Now, if there is not much sense in having that data around (because it won't help), EU data protection requires that we don't store it in the first place... Now, for enterprise customers, or multi-level ISP re-seller structures, the question of "whom to contact" and responsibility for abuse handling is different again - so for these, registering the inet6num: objects makes very much sense, and is perfectly fine according to data protection laws (because there is an operational purpose of storing the data). There has been long discussions about this whole topic, mostly taking place in the database working group, and this is the resulting compromise: - you *can* store the end user objects in the RIPE DB, if it makes sense - you don't *have* to store them (in a publically visible database), if it does not make sense - the data needs to be made available to the RIPE NCC, so that for additional allocations, the usage ratio of your allocation can be verified - but that can be in a private DB only accessible to the NCC. So - basically this means "the contact of last resort is the LIR, and if they are not publishing end-user contact data, they (need to!) take responsibility for handling all issues relating to that network block". I assume that this answer is not exactly what you have hoped for, but I think that this should at least clarify the reasoning a bit. Gert Doering -- APWG chair -- Total number of prefixes smaller than registry allocations: 141055 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 Verizon Sweden AB - registrerat i Sverige med organisationsnummer 556489-1009– huvudkontorets adress: Armégatan 38, Box 4127, 171 04 Solna, Sverige

1 0

Inet6num requirements in the db
by Arkley, Patrick 13 Oct '09

13 Oct '09

Hi. I seem to recall from the RIPE meeting that Axel talked about the RIPE database as a valuable source of information. Also other organisations thinks it is a valuable and trustworthy source. It is also a very easy way of finding out the most likely users (at least one step down stream from the LIR) of a specific IP-range. But how come there is no requirement to add end-user objects for IPv6? Only the LIR's allocations are required. If we want to continue the work that has been done for IPv4 I think we need end-user objects for IPv6 as well. Maybe there is good reasoning behind this but the explanation I got from the RIPE NCC crew was not satisfactory. Best regards Patrick Arkley Verizon Europe Verizon Sweden AB - registrerat i Sverige med organisationsnummer 556489-1009- huvudkontorets adress: Armegatan 38, Box 4127, 171 04 Solna, Sverige

2 1

Registration of IPv6 DHCPv6-PD pools
by Daniel Roesen 10 Oct '09

10 Oct '09

Hi, the current IPv6 Address Allocation and Assignment Policy (RIPE-481) states: http://www.ripe.net/ripe/docs/ripe-481.html#registration_assignment ======================================================================= 5.5. Registration When an organisation holding an IPv6 address allocation makes IPv6 address assignments, it must register assignment information in a database, accessible by RIRs as appropriate. (Information registered by an RIR/NIR may be replaced by a distributed database for registering address management information in future). Information is registered at the granularity of End Site assignments. [...] ======================================================================= Let's assume a residential eyeball network with $BIGNUM customers provides a dynamic /56 via DHCPv6-PD to each customer by default, from a large pool of /56s. I'm not sure what the implications of above policy is, especially in regards to the last sentence, "Information is registered at the granularity of End Site assignments.". Given that the End Site identity changes dynamically in a relatively high frequency, and considering $BIGNUM in the 6 to 7 figure range, it certainly won't be sensible pumping a $BIGNUM count of /56 inet6nums into the RIPE DB, all with "descr: dynamic end site network". Unfortunately it seems that this is actually required ny the policy though, wether in the RIPE DB or a DB operated by the LIR in question, accessible to the NCC. Providing dynamic networks to end sites instead of only single addresses is something new to the community. I'm looking for clarification on how we're going to handle those kind of deployments in regard of assignment registration. Best regards, Daniel -- CLUE-RIPE -- Jabber: dr(a)cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

3 3

2009-01, Global Policy for the allocation of IPv4 blocks to Regional Internet Registries
by Filiz Yilmaz 09 Oct '09

09 Oct '09

Dear Colleagues, 2009-01, "Global Policy for the allocation of IPv4 blocks to Regional Internet Registries" is a global policy proposal. You may remember discussions on it started in all regions around the beginning of 2009. The full text of the proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2009-01.html AfriNIC, APNIC and LACNIC have reached consensus on the proposal so far. In ARIN, however, a revised text, different to the one in submitted to the RIPE Policy Development Process (PDP) and in other regions, was introduced by the ARIN Advisory Council (ARIN AC). Following community discussion at the ARIN Public Policy Meeting in April 2009, the ARIN AC was tasked with further editing the text. This situation was reported to the RIPE community at RIPE 58. The RIPE community's feedback at that time was that the ARIN version of the proposal should be considered. Today, the ARIN AC has submitted a revised text for discussion in the ARIN community. You can find the current ARIN version of the proposal at: https://www.arin.net/policy/proposals/2009_3.html For your convenience, the major differences between the original ARIN text, the new ARIN version and the current RIPE version have been summarised below. Kind regards, Filiz Yilmaz Policy Development Manager RIPE NCC -------------------------------------------- Old ARIN "A. Phase I" Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration. At quarterly intervals, each RIR shall return to the IANA any legacy address space recovered, and may return to the IANA any non-legacy address space recovered, in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. New ARIN "A. Phase I" Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration and designate any such space for return to the IANA. Each RIR shall at quarterly intervals return any such designated address space to the IANA in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. RIPE "3.1 Phase I" Each RIR through their respective chosen policies and strategies may recover IPv4 address space which is under their administration. Each RIR shall at quarterly intervals return any such recovered address space to the IANA in aggregated blocks of /24 or larger, for inclusion in the recovered IPv4 pool. --------------------------------------------

9 16

Re: [address-policy-wg] 2009-01, Global Policy for the allocation of IPv4 blocks to Regional Internet Registries
by John Curran 09 Oct '09

09 Oct '09

> it's the tragedy of the americas, a few hudred years of colonialism, > and it goes on. To understand concerns in the ARIN region, I'd recommend that folks read the actual policy text and staff assessment at <https://www.arin.net/policy/proposals/2009_3.html >. Because this global policy results in significant departure from RFC2050 need-based allocation (with one equal allocation unit per RIR each 6 month period even if less than regional demand), there are challenges of equity that result from mandating the return to the IANA. The reality is that returned address space has been going back to IANA and will continue to do under current practices; see <http://blog.icann.org/2008/02/recovering-ipv4-address-space/ > for more information. Thanks! /John John Curran President and CEO ARIN

5 6

Proposal to Remove Routing Requirements from the IPv6 Address Allocation Policy Implemented
by Nathalie Trenaman 08 Oct '09

08 Oct '09

Dear Colleagues, We are pleased to announce that policy proposal 2000-06,"Removing Routing Requirements from the IPv6 Address Allocation Policy", has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. This proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2009-06.html The updated "IPv6 Address Allocation and Assignment Policy" document is available at: http://www.ripe.net/ripe/docs/ripe-481.html The following FAQ has also been updated to reflect this policy implementation: http://www.ripe.net/info/faq/rs/ipv6.html Regards, Nathalie Trenaman Registration Services RIPE NCC

1 0