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

2011-02 Removal of multihomed requirement for IPv6 PI
by Dan Luedtke 02 Jul '11

02 Jul '11

Dear Community, I can't wait for this change to happen. As I discussed at IPv6 Kongress in Frankfurt, Germany, there are more than a handful of people wanting that change. For example, I have an IPv4 PI network and adopted early to IPv6 using an IPv6 PA network. Never did, nor will I ever understand why multihoming is required for an IPv6 PI network but not for an IPv4 PI network. I support this draft and like to thank everyone who made it happen. This is an important step awaited by me and many others, even if the community decides not to do it. best regards, Dan Luedtke

2 1

IETF working group on renumbering in IPv6
by Shane Kerr 24 Jun '11

24 Jun '11

All, There is some idea to work on the renumbering problem in IPv6. This is certainly of interest to IPv6 folks, but I am including the address policy folks as this may ultimately have impact there. Cheers, -- Shane

2 1

Legal counsel on 2008-08 (Initial Certification Policy in the RIPE NCC Service Region)
by Sander Steffann 02 Jun '11

02 Jun '11

Hello WG, I asked the RIPE NCC to get legal counsel on the possibilities of a court ordering the RIPE NCC to revoke or confiscate RPKI certificates. Here is the full answer we received: ========== The RIPE NCC is an association under Dutch law and therefore subject to the Dutch legislation. RIPE NCC has consulted several external lawyers, and has obtained an analysis of the legal situation based on current, existing Dutch legislation. This analysis takes into account Dutch Criminal, Civil and Administrative law. Certificates are directly linked to the registration of the Internet number resources. There is no specific Dutch legislation that can be used to order the deregistration of Internet number resources or change the registration details of Internet number resources. Nor is there any legislation that applies to the revocation of certificates over Internet number resources. In the absence of such legislation, a court cannot order the revocation of certificates. It is the RIPE NCC’s view, based on this analysis, that the RIPE NCC cannot be ordered to revoke resource certificates. ========== Of course laws can change, but the advice above may address some of the concerns raised about the RPKI infrastructure. Sander Steffann APWG co-chair

24 84

Regarding fragmentation and aggregation of IPv4 address space
by Ronak Banka 01 Jun '11

01 Jun '11

Respected Team members, Myself Ronak banka currently doing my internship at NAv6, USM Malaysia under the supervision of Dr. Raja Kumar. I am presently conducting a Research on estimating the fragmentation and aggregation of IPv6 address space by comparing it with fragmentation and aggregation of IPv4 address space under RIPE, so I was in search of data regarding reasons for fragmentation of the address space and % contribution of those different reasons to fragmentation. If you could help me in this matter by providing any important details I would be thankful to you. Waiting for your reply in anticipation. -- Ronak Banka Internship student National Advance IPv6 Centre (NAv6) USM Malaysia contact: +60143064063

1 0

Cosmetic Surgery Project: Extended Review period on the new draft document for IPv6 Address Policy
by Emilio Madaio 31 May '11

31 May '11

Dear colleagues, At RIPE 59 in Lisbon in October 2009, the RIPE NCC announced that it would undertake a project to make various RIPE policy documents easier to understand without changing the meaning of the text. As already announced, the latest draft document produced according to the project is available at: http://www.ripe.net/ripe/updated-documents/ This is the merger of the three policy documents: -ripe-512 "IPv6 Address Allocation and Assignment Policy" -ripe-451 "IPv6 Address Space Policy for Internet Exchange Points" -ripe-233 "IPv6 Addresses for Internet Root Servers in the RIPE Region" The announcement of the publication of this new draft is available at: http://www.ripe.net/ripe/maillists/archives/address-policy-wg/2011/msg00243… The Address Policy Working Group co-Chairs decided to extend the review period until 13 June 2011 to allow the community more time to give their feedback. We encourage you to read this merged version and send any comments to address-policy-wg(a)ripe.net by 13 June 2011. Best Regards Emilio Madaio Policy Development Officer RIPE NCC

3 2

2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
by Emilio Madaio 27 May '11

27 May '11

Dear Colleagues, A proposed change to RIPE Document ripe-509, "IPv4 Address Allocation and Assignment Policy for the RIPE NCC Service Region", is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2011-03/ We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 17 June 2011. Regards Emilio Madaio Policy Development Officer RIPE NCC

19 40

RE: [address-policy-wg] getting second IPv6 PA as a LIR
by poty＠iiat.ru 23 May '11

23 May '11

>> And why wouldn't the Internet work with 600,000 prefixes in the DFZ? > > Now all of a sudden for instance Cisco 7600 3CXL isn't enough to old a full table (at around 750k). > > Also, IPv6 uses twice the TCAM resources as IPv4... so, basically what you are saying is that you know that your routers need an upgrade in 5 years and you don't want to pay for an upgrade or you can't figure out a business plan which covers the costs for that? But you are telling small ISPs/NCOs/"hobbyusers"/whatever THEY don't get their business plan right if they don't can afford paying $$$ for PI space or rather would prefer to pay other bills with the money? WTF?! ------ No, the problem that the small ISPs you are speaking about will have to spend that money to swallow such routing table. And it is not $2000, "slightly" more...

10 14

re: [address-policy-wg] 2011-03 New Policy Proposal (Post-depletion IPv4 address recycling)
by boggits 20 May '11

20 May '11

On 20 May 2011 14:15, Remco Van Mook <Remco.vanMook(a)eu.equinix.com> wrote: > > Unsurprisingly, as the author I fully support this policy proposal and I > would for the sake of the PDP encourage others to voice their agreement as > well - no response means no progress. I also support the proposal, my only thought would be if it might be better to use this change to make an overwrite of the 'current process' at the point of the first allocation of a /22 from the last /8 for the purpose of the avoidance of doubt... J -- James Blessing 07989 039 476 -- James Blessing 07989 039 476

1 0

PP - 2011-02 - Removal of multihomed requirement for IPv6
by Adil H. Baghir 16 May '11

16 May '11

Hi, I highly support the policy... Adil H. Baghir Internet Development Chief Engineer Data & Solutions Planning and Design P.O.Box 69179 Riyadh 11423 Kingdom of Saudi Arabia Tel: +966 56 031 3263 Fax: +966 56 041 3263 Mobile: +966 542 33 66 00 eMail: a.baghir(a)mobily.com.sa<mailto:a.baghir@mobily.com.sa> [cid:image001.jpg@01CC13AD.44C394C0] ------Disclaimer------ This email and any files transmitted with are classified as confidential unless otherwise specified. This e-mail is intended solely for the use of the individual or entity to whom this e-mail is addressed. If you have received this email by mistake, please notify the sender and delete this e-mail immediately and permanently. Although measures were taken to free this e-mail and its attachments from any malicious code infection, it is the responsibility of the recipient to check this email and any attachments for the presence of such infection. The use of EEC(Mobily) e-mail service is limited for EEC(Mobily) business use only.

1 0

minutes from RIPE 61
by Gert Doering 13 May '11

13 May '11

Hi APWG, since there were no more comments, we have declared the minutes from RIPE 61 (Rome) to be final. The minutes can be found here: https://www.ripe.net/ripe/apwg/minutes61 Gert Doering -- NetMaster -- did you enable IPv6 on something today...? 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