From no-reply at ripe.net Tue Feb 1 05:27:16 2011 From: no-reply at ripe.net (Axel Pawlik) Date: Tue, 01 Feb 2011 05:27:16 +0100 Subject: [ncc-services-wg] IANA Allocates Two /8s of IPv4 Space to APNIC Message-ID: <4D478BA4.3090203@ripe.net> [Apologies for duplicate emails] Dear colleagues, On 1 February 2011, the IANA allocated two /8s of IPv4 address space to APNIC, the Regional Internet Registry (RIR) for the Asia Pacific region. This means that only five /8s of IPv4 address space are left in the IANA free pool and the "Global Policy for the Allocation of the Remaining IPv4 Address Space" will be triggered. This policy can be found online at: http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm When this policy comes into effect, the five RIRs will each receive one of the five remaining /8s and the global IPv4 pool will be exhausted. We expect IANA to allocate these final /8s within the next few days. For further information please see: http://www.ripe.net/v4exhaustion/ Regards, Axel Pawlik Managing Director RIPE NCC From mis at wari.net Tue Feb 1 09:08:34 2011 From: mis at wari.net (Manfredo Miserocchi) Date: Tue, 01 Feb 2011 09:08:34 +0100 Subject: [ncc-services-wg] IANA Allocates Two /8s of IPv4 Space to APNIC In-Reply-To: <4D478BA4.3090203@ripe.net> References: <4D478BA4.3090203@ripe.net> Message-ID: ...so IPv4 numbers are finished !! We saw this day ! In effect we still have the last 5 /8s, but .... :) The counter shows "zero" :( http://www.wari.net/ipv4exh.htm Welcome into the fantastic IPv6 world :D Manfredo -----Original Message----- From: Axel Pawlik To: ripe-list at ripe.net, ncc-announce at ripe.net, ncc-services-wg at ripe.net Date: Tue, 01 Feb 2011 05:27:16 +0100 Subject: [ncc-services-wg] IANA Allocates Two /8s of IPv4 Space to APNIC > [Apologies for duplicate emails] > > Dear colleagues, > > On 1 February 2011, the IANA allocated two /8s of IPv4 address space to > APNIC, the Regional Internet Registry (RIR) for the Asia Pacific region. > > This means that only five /8s of IPv4 address space are left in the IANA > free pool and the "Global Policy for the Allocation of the Remaining > IPv4 Address Space" will be triggered. > > This policy can be found online at: > http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm > > When this policy comes into effect, the five RIRs will each receive one > of the five remaining /8s and the global IPv4 pool will be exhausted. > > We expect IANA to allocate these final /8s within the next few days. > > For further information please see: > http://www.ripe.net/v4exhaustion/ > > Regards, > > Axel Pawlik > > Managing Director > RIPE NCC > > Si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il presente messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo ed a non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. You are hereby informed that this message contains confidential informations intended for the addressee's use only. If yu're not the addressee and have received this message by mistake, please delete it and immediately notify us. You may not copy or disseminate this message to anyone. Thank you. From no-reply at ripe.net Wed Feb 2 01:27:00 2011 From: no-reply at ripe.net (Axel Pawlik) Date: Wed, 02 Feb 2011 01:27:00 +0100 Subject: [ncc-services-wg] IPv4 Exhaustion Announcement and Press Conference: Watch Live Message-ID: <4D48A4D4.6000805@ripe.net> [Apologies for duplicate emails] Dear colleagues, On Thursday, 3 February 2011, at 14:30 (UTC), the Number Resource Organization (NRO), along with the Internet Corporation for Assigned Names and Numbers (ICANN), the Internet Society (ISOC) and the Internet Architecture Board (IAB) will be holding a ceremony and press conference to make a significant announcement and to discuss the global transition to the next generation of Internet addresses. Much has been written in the international media over the last few weeks about the dwindling pool of IPv4 Internet addresses, and this topic will be addressed at the event. We invite everyone to view the webcast of this event at: http://www.nro.net/news/icann-nro-live-stream The event will take place at the Intercontinental Hotel in Miami on Thursday. There will be limited public seating available to attend (with press receiving seating priority) in Room ?Concourse II? at 09:30 EST for the ceremony and 10:00 EST for the press conference which follows. Regards, Axel Pawlik Managing Director RIPE NCC From ripe-wgs.cs at schiefner.de Wed Feb 2 12:15:41 2011 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Wed, 02 Feb 2011 12:15:41 +0100 Subject: [ncc-services-wg] Re: IPv4 Exhaustion Announcement and Press Conference: Watch Live In-Reply-To: <4D48A4D4.6000805@ripe.net> References: <4D48A4D4.6000805@ripe.net> Message-ID: <4D493CDD.2020309@schiefner.de> Axel, thanks for the heads-up. The recent allocation of the last two "regular" /8's to APNIC is obviously worth a press conference. Still, could you please shed some more light on the 30min "ceremony"? As at least I have no real idea what this could be like: hand shakes? Exchange of certificates? ??? Thanks in advance, Carsten Axel Pawlik wrote: > [Apologies for duplicate emails] > > Dear colleagues, > > On Thursday, 3 February 2011, at 14:30 (UTC), the Number Resource > Organization (NRO), along with the Internet Corporation for Assigned > Names and Numbers (ICANN), the Internet Society (ISOC) and the Internet > Architecture Board (IAB) will be holding a ceremony and press conference > to make a significant announcement and to discuss the global transition > to the next generation of Internet addresses. > > Much has been written in the international media over the last few weeks > about the dwindling pool of IPv4 Internet addresses, and this topic will > be addressed at the event. > > We invite everyone to view the webcast of this event at: > http://www.nro.net/news/icann-nro-live-stream > > The event will take place at the Intercontinental Hotel in Miami on > Thursday. There will be limited public seating available to attend (with > press receiving seating priority) in Room ?Concourse II? at 09:30 EST > for the ceremony and 10:00 EST for the press conference which follows. > > Regards, > > Axel Pawlik > > Managing Director > RIPE NCC From ripe-wgs.cs at schiefner.de Thu Feb 3 16:20:36 2011 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Thu, 03 Feb 2011 16:20:36 +0100 Subject: [ncc-services-wg] Re: IPv4 Exhaustion Announcement and Press Conference: Watch Live In-Reply-To: <4D493CDD.2020309@schiefner.de> References: <4D48A4D4.6000805@ripe.net> <4D493CDD.2020309@schiefner.de> Message-ID: <4D4AC7C4.8070600@schiefner.de> Carsten Schiefner wrote: > Axel, > > thanks for the heads-up. The recent allocation of the last two "regular" > /8's to APNIC is obviously worth a press conference. > > Still, could you please shed some more light on the 30min "ceremony"? As > at least I have no real idea what this could be like: hand shakes? > Exchange of certificates? ??? Seems that my crystal ball is very well polished these days: quite a show, indeed - including hand shakes and the exchange of certificates... I now wonder whether there are similar plans for the last genuine RIR->LIR allocation. Best, Carsten > Axel Pawlik wrote: >> [Apologies for duplicate emails] >> >> Dear colleagues, >> >> On Thursday, 3 February 2011, at 14:30 (UTC), the Number Resource >> Organization (NRO), along with the Internet Corporation for Assigned >> Names and Numbers (ICANN), the Internet Society (ISOC) and the >> Internet Architecture Board (IAB) will be holding a ceremony and press >> conference to make a significant announcement and to discuss the >> global transition to the next generation of Internet addresses. >> >> Much has been written in the international media over the last few >> weeks about the dwindling pool of IPv4 Internet addresses, and this >> topic will be addressed at the event. >> >> We invite everyone to view the webcast of this event at: >> http://www.nro.net/news/icann-nro-live-stream >> >> The event will take place at the Intercontinental Hotel in Miami on >> Thursday. There will be limited public seating available to attend >> (with press receiving seating priority) in Room ?Concourse II? at >> 09:30 EST for the ceremony and 10:00 EST for the press conference >> which follows. >> >> Regards, >> >> Axel Pawlik >> >> Managing Director >> RIPE NCC From no-reply at ripe.net Thu Feb 3 17:42:41 2011 From: no-reply at ripe.net (Axel Pawlik) Date: Thu, 03 Feb 2011 17:42:41 +0100 Subject: [ncc-services-wg] IPv4 Exhaustion: RIPE NCC Update Message-ID: <4D4ADB01.1070804@ripe.net> Dear colleagues, The IANA IPv4 free pool was exhausted today, 3 February 2011. Each of the Regional Internet Registries (RIRs) has now received one of the final five /8s. The RIPE NCC has been allocated 185/8. The RIPE NCC is holding reserves totaling approximately four /8s (around 75 million individual IPv4 addresses), not including 185/8. We will continue to distribute IPv4 addresses from our reserves according to the current policy, ripe-509, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region": http://www.ripe.net/ripe/docs/ripe-509.html When our reserves are exhausted, we will begin to distribute IPv4 addresses from 185/8 according to section 5.6 of ripe-509: http://ripe.net/ripe/docs/ipv4-policies.html#----use-of-last----for-pa-allocations This policy states that each Local Internet Registry (LIR) will receive one /22 (1024 IPv4 addresses) from 185/8 upon application for IPv4 resources. In order to obtain this /22 allocation, the LIR must already have requested an IPv6 allocation. For more information about how to deploy IPv6, please see: http://www.ipv6actnow.org As we unable to anticipate consumption rates, we cannot fully predict how long our reserves will last. However, we would like to reassure you that our supplies will not be exhausted within the coming months. Our Registration Services Department has seen an increase in the number of IPv4 requests in the last few days and is working hard to evaluate all requests. We ask for your patience during this busy period. Regards, Axel Pawlik Managing Director RIPE NCC From no-reply at ripe.net Thu Feb 3 17:42:41 2011 From: no-reply at ripe.net (Axel Pawlik) Date: Thu, 03 Feb 2011 17:42:41 +0100 Subject: [ncc-services-wg] [members-discuss] [ncc-announce] IPv4 Exhaustion: RIPE NCC Update Message-ID: <4D4ADB01.1070804@ripe.net> Dear colleagues, The IANA IPv4 free pool was exhausted today, 3 February 2011. Each of the Regional Internet Registries (RIRs) has now received one of the final five /8s. The RIPE NCC has been allocated 185/8. The RIPE NCC is holding reserves totaling approximately four /8s (around 75 million individual IPv4 addresses), not including 185/8. We will continue to distribute IPv4 addresses from our reserves according to the current policy, ripe-509, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region": http://www.ripe.net/ripe/docs/ripe-509.html When our reserves are exhausted, we will begin to distribute IPv4 addresses from 185/8 according to section 5.6 of ripe-509: http://ripe.net/ripe/docs/ipv4-policies.html#----use-of-last----for-pa-allocations This policy states that each Local Internet Registry (LIR) will receive one /22 (1024 IPv4 addresses) from 185/8 upon application for IPv4 resources. In order to obtain this /22 allocation, the LIR must already have requested an IPv6 allocation. For more information about how to deploy IPv6, please see: http://www.ipv6actnow.org As we unable to anticipate consumption rates, we cannot fully predict how long our reserves will last. However, we would like to reassure you that our supplies will not be exhausted within the coming months. Our Registration Services Department has seen an increase in the number of IPv4 requests in the last few days and is working hard to evaluate all requests. We ask for your patience during this busy period. Regards, Axel Pawlik Managing Director RIPE NCC ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses. From gert at space.net Thu Feb 3 18:40:11 2011 From: gert at space.net (Gert Doering) Date: Thu, 3 Feb 2011 18:40:11 +0100 Subject: [ncc-services-wg] regarding 2008-08 - was: RIPE NCC Resource Certification service update In-Reply-To: References: Message-ID: <20110203174011.GJ44800@Space.Net> Hello APWG, (copying in NCC services WG, but since this is more regarding the formal policy proposal side of things, the place to discuss it is the apwg list -> reply-To: has been set accordingly). We have a slightly weird situation here where we have a policy proposal (2008-08) that has not *yet* concluded, which give the RIPE NCC the mandate to setup and operate the infrastructure to give out certificates to LIRs from the RIPE region (PA space holders, for a start, PI to be done in the next round). This proposal has not yet concluded, due to mostly "word smithing" reasons, and also due to somewhat lacking feedback from the community (that's *you*). There was no strong resistance either, so I assume that it might eventually reach consensus. On the other hand, the RIPE NCC sees the necessity for this sort of machinery, and has started the service *already* (see below for the mail from Alex Band with the NCC view of things), without waiting for the proposal to conclude. The RIPE NCC members have approved the expenses for this as part of the NCC business plan, so the NCC has the necessary (at least financial) backing to go forward here. So, technically, we might question whether we need the policy proposal 2008-08 at all anymore, or whether it should be withdrawn (being obsoleted by events). I have discussed this with the certification task force (CA-TF) and Alex' mail also answers this - the NCC wants a clear policy document that says that not only the financial side is OK, but also that the address policy community agrees with what the NCC is doing, and gives their support to the NCC. As a consequence, you'll see 2008-08 v3.0 show up here soon, for another round of review, and I *really* would appreciate a somewhat more active feedback from the WG (you!) this time. regards, Gert Doering, APWG chair On Mon, Jan 31, 2011 at 09:30:25AM +0100, Alex Band wrote: > Dear colleagues, > > It's been one month since I sent the announcement about the RIPE NCC Resource Certification service. I would like to give you an overview of the current status. > > The facts by numbers: > ------------------------------ > LIRs who have enabled the service: 219 > Number of Route Origin Authorisations they created: 170 > Number of prefixes covered by these ROAs: 469 > Total IPv4 space covered by ROAs in the RIPE region: 40159 /24s > Total IPv6 space covered by ROAs in the RIPE region: 7340035 /48s > Unique visitors to ripe.net/certification: 1564 > Downloads of the RIPE NCC Validator: 117 > > So while 219 LIRs have enabled the service, and very diligently created a large number of ROAs to specify their routing policy, unfortunately nobody gave any feedback on any of the mailing lists. It is very important that you let your voice be heard and provide input on policy proposal 2008-08: > http://ripe.net/ripe/policies/proposals/2008-08.html > > Please note that version 3.0 of this proposal will be published very soon. As soon as it is available, I urge you to read it and provide feedback, because the fact that the current service not backed by a policy is not a sustainable state of affairs. > > Kind regards, > > Alex Band > Product Manager, RIPE NCC > http://ripe.net/certification > > P.S. Here are some links courtesy of LACNIC in case you would like to track the progress: > http://www.labs.lacnic.net/~rpki/rpki-monitor/rpki-ta-status.xml > http://www.labs.lacnic.net/~rpki/rpki-evolution-report_EN.txt > http://www.labs.lacnic.net/~rpki/rpki-heatmaps/latest/ripe-roa-heatmap.png 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3583 bytes Desc: not available URL: From tore.anderson at redpill-linpro.com Fri Feb 4 01:23:49 2011 From: tore.anderson at redpill-linpro.com (Tore Anderson) Date: Fri, 04 Feb 2011 01:23:49 +0100 Subject: [ncc-services-wg] IPv4 Exhaustion: RIPE NCC Update In-Reply-To: <4D4ADB01.1070804@ripe.net> References: <4D4ADB01.1070804@ripe.net> Message-ID: <4D4B4715.6050803@redpill-linpro.com> * Axel Pawlik > As we unable to anticipate consumption rates, we cannot fully predict > how long our reserves will last. I can understand that the NCC do not want to speculate on specific dates. However, I was wondering if there is, or if there will be, some web page or similar that continuously documents the remaining pool of IPv4 addresses, similar to what APNIC and LACNIC have? That way the LIRs themselves can easily approximate when exhaustion will occur. http://www.apnic.net/community/ipv4-exhaustion/graphical-information http://www.lacnic.net/en/registro/espacio-disponible-ipv4.html Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/ Tel: +47 21 54 41 27 From rendek at ripe.net Wed Feb 9 16:30:26 2011 From: rendek at ripe.net (Paul Rendek) Date: Wed, 09 Feb 2011 16:30:26 +0100 Subject: [ncc-services-wg] New version of www.ripe.net Message-ID: <4D52B312.1090804@ripe.net> [Apologies for duplicates] Dear Colleagues, Today, the RIPE NCC launched an updated version of the www.ripe.net website. The new site has been redesigned to provide a clearer structure, improved navigation and more efficient ways to interact with the multimedia resources and tools provided by the RIPE NCC. The driving force behind this redesign has been the needs of our members and colleagues in the Internet community. We appreciate any feedback you may have on the new version of the website. If you have any comments or suggestions, please contact the RIPE NCC at: . You can find more information at: http://www.ripe.net/internet-coordination/news/announcements/new-website Regards, Paul Rendek Head of External Relations and Communications RIPE NCC From kranjbar at ripe.net Thu Feb 10 11:57:50 2011 From: kranjbar at ripe.net (Kaveh Ranjbar) Date: Thu, 10 Feb 2011 11:57:50 +0100 Subject: [ncc-services-wg] [members-discuss] [ncc-announce] Launch of RIPE NCC LIR Locator Message-ID: <4D53C4AE.2060000@ripe.net> Dear Colleagues, We have introduced a new service, the LIR Locator: https://lirportal.ripe.net/maps/locator/ This new service is an extension of the existing list of RIPE NCC members: https://www.ripe.net/membership/indices/ and the RIPE NCC's service region map: https://www.ripe.net/lir-services/member-support/info/list-of-members In addition to clearly indicating those RIPE NCC members with an IPv6 RIPEness score of four, this new service marks the geographical location of members on a Google map. This service is accessible to the public and enables users to see the concentration of RIPE NCC members in cities and countries. RIPE NCC members can log in to to their LIR Portal account and either confirm the geo-location that we have determined for your registry's address from your public records or change it to any location within your registered country. More details about this service and future plans for it will be published on RIPE Labs shortly. Regards, Kaveh Ranjbar - Business Applications Product Owner Senior Software Engineer RIPE NCC ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses. From jblessing at llnw.com Thu Feb 10 13:29:12 2011 From: jblessing at llnw.com (James Blessing) Date: Thu, 10 Feb 2011 12:29:12 +0000 Subject: [ncc-services-wg] Re: [members-discuss] [ncc-announce] Launch of RIPE NCC LIR Locator In-Reply-To: <4D53C4AE.2060000@ripe.net> References: <4D53C4AE.2060000@ripe.net> Message-ID: <4D53DA18.5020207@llnw.com> On 10/02/2011 10:57, Kaveh Ranjbar wrote: > RIPE NCC members can log in to to their LIR Portal account and either > confirm the geo-location that we have determined for your registry's > address from your public records or change it to any location within > your registered country. What about members with multiple locations? I'd need to record at least 7... The new Lirportal site is *much slower* than the previous version J -- James Blessing +44 7989 039 476 Strategic Relations Manager, EMEA Limelight Networks ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses. From fweimer at bfk.de Thu Feb 10 13:49:41 2011 From: fweimer at bfk.de (Florian Weimer) Date: Thu, 10 Feb 2011 12:49:41 +0000 Subject: [ncc-services-wg] Re: [members-discuss] [ncc-announce] Launch of RIPE NCC LIR Locator In-Reply-To: <4D53C4AE.2060000@ripe.net> (Kaveh Ranjbar's message of "Thu\, 10 Feb 2011 11\:57\:50 +0100") References: <4D53C4AE.2060000@ripe.net> Message-ID: <824o8cuk9m.fsf@mid.bfk.de> * Kaveh Ranjbar: > We have introduced a new service, the LIR Locator: > https://lirportal.ripe.net/maps/locator/ I've tried to locate 193.227.124.1, and it is placed in the Caribbean. This does not seem right. -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstra?e 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 From feedback at ripe.net Thu Feb 10 19:03:51 2011 From: feedback at ripe.net (RIPE NCC Web Services) Date: Thu, 10 Feb 2011 19:03:51 +0100 Subject: [ncc-services-wg] Display issues with applications that use encrypted connections (https) Message-ID: <4D542887.70903@ripe.net> [Apologies for duplicates] Dear members, It has come to our attention that some users experienced graphical and functional problems when attempting to use services like the LIR Portal that are now available through SSL encryption (https). We tracked these issues and found that some combinations of operating systems and browsers (for example Safari in MacOS X versions previous to 10.6.6 and Microsoft Internet Explorer 8 or below) did not recognize our certificate as valid. Our engineers worked to correct the problem and it is now fixed. We apologise for any inconvenience this has caused and please let us know if you encounter other issues. Sincerely, -- Mihnea-Costin Grigore RIPE NCC Web Developer - http://www.ripe.net/ From mir at ripe.net Mon Feb 14 13:48:16 2011 From: mir at ripe.net (Mirjam Kuehne) Date: Mon, 14 Feb 2011 13:48:16 +0100 Subject: [ncc-services-wg] Re: [ncc-servies-wg] Launch of RIPE NCC LIR Locator Message-ID: <4D592490.4060607@ripe.net> Dear colleagues, As announced last week, you can now find technical details about the LIR Locator and a description of our future plans on RIPE Labs: http://labs.ripe.net/Members/kranjbar/ripe-ncc-lir-locator Please do not hesitate to send us any comments you might have. We want to make this a useful tool for you and welcome your feedback and suggestions. Kind Regards, Mirjam Kuehne RIPE NCC -------- Original Message -------- Subject: [ncc-services-wg] Launch of RIPE NCC LIR Locator Date: Thu, 10 Feb 2011 11:57:50 +0100 From: Kaveh Ranjbar To: ncc-services at ripe.net Dear Colleagues, We have introduced a new service, the LIR Locator: https://lirportal.ripe.net/maps/locator/ This new service is an extension of the existing list of RIPE NCC members: https://www.ripe.net/membership/indices/ and the RIPE NCC's service region map: https://www.ripe.net/lir-services/member-support/info/list-of-members In addition to clearly indicating those RIPE NCC members with an IPv6 RIPEness score of four, this new service marks the geographical location of members on a Google map. This service is accessible to the public and enables users to see the concentration of RIPE NCC members in cities and countries. RIPE NCC members can log in to to their LIR Portal account and either confirm the geo-location that we have determined for your registry's address from your public records or change it to any location within your registered country. More details about this service and future plans for it will be published on RIPE Labs shortly. Regards, Kaveh Ranjbar - Business Applications Product Owner Senior Software Engineer RIPE NCC From emadaio at ripe.net Tue Feb 15 08:50:42 2011 From: emadaio at ripe.net (Emilio Madaio) Date: Tue, 15 Feb 2011 08:50:42 +0100 Subject: [ncc-services-wg] REMINDER; WAS Re: 2008-08 New Version and Draft Document Published (Initial Certification Policy for Provider Aggregatable Address Space Holders) Message-ID: <4D5A3052.3090805@ripe.net> [Apologies for duplicates. Courtesy copy sent to Routing Working Group and RIPE NCC Services Working Group. Please direct feedback to the Address Policy Working Group mailing list.] Dear Colleagues, The new version of RIPE Policy Proposal 2008-08, "Initial Certification Policy for Provider Aggregatable Address Space Holders", was published on 9 February 2011. The time period for community review ends on 23 February 2011. Some feedback was sent to the Address Policy Working Group mailing list. However, to maintain the discussion, we strongly recommend that you share your ideas and comments and clearly let the community know if you: - Support the implementation of the proposal - Support the general principle of the proposal but would prefer another wording - Support the general principle with some details changed but agree to postpone this discussion until another stage of the policy proposal review. (This is an initial proposal that covers only PA resources. If the community supports extending certification to all resources, then another version of the proposal will be necessary.) - Do not support the proposal (please explain your motivations) You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2008-08 and the draft document at: http://www.ripe.net/ripe/policies/proposals/2008-08/draft Please send an email with your comments to address-policy-wg at ripe.net by 23 February 2011. Best regards, Emilio Madaio Policy Development Officer RIPE NCC From mir at ripe.net Tue Feb 15 15:01:26 2011 From: mir at ripe.net (Mirjam Kuehne) Date: Tue, 15 Feb 2011 15:01:26 +0100 Subject: [ncc-services-wg] Create, Update and Delete via the RESTful Web Services Message-ID: <4D5A8736.8080608@ripe.net> [apologies for duplicates] Dear colleagues, After the "Read" service has been available for some time, you can now also Create, Update and Delete objects in the RIPE Database via the RESTful Web Services. Please see a detailed description including many examples on RIPE Labs: http://labs.ripe.net/Members/Paul_P_/create-update-and-delete-via-the-restful-web-services As always, we are very interested in your feedback. We would also like to know if you are running a project in which you used the RIPE Database API. Kind Regards, Mirjam Kuehne RIPE NCC From denis at ripe.net Tue Feb 15 16:52:44 2011 From: denis at ripe.net (Denis Walker) Date: Tue, 15 Feb 2011 16:52:44 +0100 Subject: [ncc-services-wg] Registering IPv6 Assignments in the RIPE Database Message-ID: <4D5AA14C.60805@ripe.net> [Apologies for duplicate emails] Dear Colleagues The RIPE community recently approved RIPE Policy Proposal 2010-06, "Registration Requirements for IPv6 End User Assignments". The proposal is available at: [http://www.ripe.net/ripe/policies/proposals/2010-06] This has now been implemented in the RIPE Database and other RIPE NCC processes, where necessary. Details of how to use the new aggregation feature of the RIPE Database can be found at: http://www.ripe.net/data-tools/support/documentation/documenting-ipv6-assignments-in-the-ripe-database For those who have already made some IPv6 assignments, you will need to document them in the RIPE Database according to the policy if you have not already done so. All new IPv6 assignments must be registered in the RIPE Database in accordance with this policy. Regards, Denis Walker Business Analyst RIPE NCC Database Group From mir at ripe.net Thu Feb 17 16:35:33 2011 From: mir at ripe.net (Mirjam Kuehne) Date: Thu, 17 Feb 2011 16:35:33 +0100 Subject: [ncc-services-wg] RIPE NCC Membership Statistics - One Year Later In-Reply-To: <4B72B9E3.70602@ripe.net> References: <4B72B9E3.70602@ripe.net> Message-ID: <4D5D4045.9030000@ripe.net> Dear colleagues, Exactly one year ago, we published statistics on the number of RIPE NCC members and the resources distributed to them. With twelve months passed, we revisited the topic and looked at how things evolved in 2010. Please find the updated graphs and some interesting observations on RIPE Labs: http://labs.ripe.net/Members/wilhelm/members-and-number-resources-1-year-later Kind Regards, Mirjam Kuehne RIPE Labs Community Builder RIPE NCC From fweimer at bfk.de Fri Feb 18 17:16:48 2011 From: fweimer at bfk.de (Florian Weimer) Date: Fri, 18 Feb 2011 16:16:48 +0000 Subject: [ncc-services-wg] Implementation status of RIPE-452 Message-ID: <82pqqpnwr3.fsf@mid.bfk.de> Hi, what's the implementation status of RIPE-452? Is there a way to query the status of specific resources? Thanks, Florian -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstra?e 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 From denis at ripe.net Mon Feb 21 13:50:59 2011 From: denis at ripe.net (Denis Walker) Date: Mon, 21 Feb 2011 13:50:59 +0100 Subject: [ncc-services-wg] Implementation of "pingable:" attribute in the RIPE Database Message-ID: <4D625FB3.6040402@ripe.net> [Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has implemented the "pingable:" and "ping-hdl:" attributes according to the specification in RFC 5943. They can now be used in ROUTE and ROUTE6 objects in the RIPE Database. RFC 5943 describes the syntax and explains how to use them: http://tools.ietf.org/html/rfc5943 The "pingable:" addresses are already active for beacons, anchors and debogon routes announced by the RIPE NCC Routing Information Service (RIS). For an example of how these are announced, see the ROUTE object for 84.205.81.0/24. For more information about RIS beacons and anchors, please see: http://www.ripe.net/data-tools/stats/ris/ris-routing-beacons Regards, Denis Walker Business Analyst RIPE NCC Database Group From fweimer at bfk.de Mon Feb 21 16:09:04 2011 From: fweimer at bfk.de (Florian Weimer) Date: Mon, 21 Feb 2011 15:09:04 +0000 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <4D62767E.5050802@ripe.net> (Arne Kiessling's message of "Mon\, 21 Feb 2011 15\:28\:14 +0100") References: <82pqqpnwr3.fsf@mid.bfk.de> <4D62767E.5050802@ripe.net> Message-ID: <8239nhctm7.fsf@mid.bfk.de> * Arne Kiessling: > Dear Florian, > > Thank you for your email. The RIPE NCC will publish the results of > Phase 2 of the policy implementation by 5 March 2011. > > For privacy reasons, LIRs can only check in the relevant sections of > the LIR Portal (IPv4, IPv6, ASN) to see whether the documents they > submitted for a specific resource have been approved or are still > pending approval. Arne, thanks for your response. Are resource holders notified by the RIPE NCC when a LIR claims that they have a contract covering the resource? If not, how can resource holders discover which LIR is the contracting LIR? Thanks, Florian -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstra?e 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 From arne at ripe.net Mon Feb 21 15:28:14 2011 From: arne at ripe.net (Arne Kiessling) Date: Mon, 21 Feb 2011 15:28:14 +0100 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <82pqqpnwr3.fsf@mid.bfk.de> References: <82pqqpnwr3.fsf@mid.bfk.de> Message-ID: <4D62767E.5050802@ripe.net> Dear Florian, Thank you for your email. The RIPE NCC will publish the results of Phase 2 of the policy implementation by 5 March 2011. For privacy reasons, LIRs can only check in the relevant sections of the LIR Portal (IPv4, IPv6, ASN) to see whether the documents they submitted for a specific resource have been approved or are still pending approval. Florian Weimer wrote: > Hi, > > what's the implementation status of RIPE-452? Is there a way to query > the status of specific resources? > > Thanks, > Florian -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre From arne at ripe.net Tue Feb 22 13:09:16 2011 From: arne at ripe.net (Arne Kiessling) Date: Tue, 22 Feb 2011 13:09:16 +0100 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <8239nhctm7.fsf@mid.bfk.de> References: <82pqqpnwr3.fsf@mid.bfk.de> <4D62767E.5050802@ripe.net> <8239nhctm7.fsf@mid.bfk.de> Message-ID: <4D63A76C.1030207@ripe.net> Dear Florian, Holders of independent Internet number resources sign an agreement with a sponsoring LIR, so they should know which LIR they signed an agreement with. If you have a specific issue that you would like to discuss, please reply to me off list or contact . -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre Florian Weimer wrote: > * Arne Kiessling: > >> Dear Florian, >> >> Thank you for your email. The RIPE NCC will publish the results of >> Phase 2 of the policy implementation by 5 March 2011. >> >> For privacy reasons, LIRs can only check in the relevant sections of >> the LIR Portal (IPv4, IPv6, ASN) to see whether the documents they >> submitted for a specific resource have been approved or are still >> pending approval. > > Arne, > > thanks for your response. > > Are resource holders notified by the RIPE NCC when a LIR claims that > they have a contract covering the resource? If not, how can resource > holders discover which LIR is the contracting LIR? > > Thanks, > Florian From fweimer at bfk.de Tue Feb 22 13:46:36 2011 From: fweimer at bfk.de (Florian Weimer) Date: Tue, 22 Feb 2011 12:46:36 +0000 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <4D63A76C.1030207@ripe.net> (Arne Kiessling's message of "Tue\, 22 Feb 2011 13\:09\:16 +0100") References: <82pqqpnwr3.fsf@mid.bfk.de> <4D62767E.5050802@ripe.net> <8239nhctm7.fsf@mid.bfk.de> <4D63A76C.1030207@ripe.net> Message-ID: <82pqqk8cer.fsf@mid.bfk.de> * Arne Kiessling: > Holders of independent Internet number resources sign an agreement > with a sponsoring LIR, so they should know which LIR they signed an > agreement with. Hi Arne, are LIRs required to share those contracts with RIPE NCC? I wouldn't be surprised if LIRs had a wide range of views regarding the contractual requirements in RIPE-452. That's why I think that a notification of the resource owner might be helpful. > If you have a specific issue that you would like to discuss, please > reply to me off list or contact . Thanks, I will try to gather additional information from there. This mailbox is restricted to LIRs. In general, you also need a contact for resource holders, I think. (This is not a problem in my case, though.) Regards, Florian -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstra?e 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 From training at ripe.net Tue Feb 22 14:41:28 2011 From: training at ripe.net (Training Mailbox) Date: Tue, 22 Feb 2011 14:41:28 +0100 Subject: [ncc-services-wg] Announcement: RIPE NCC Training Courses Message-ID: <4D63BD08.9050105@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/lir-services/training/courses/lir/outline/ - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/lir-services/training/courses/rr/ - The IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: RIPE NCC Upcoming Courses List & Registration https://lirportal.ripe.net/lirportal/training/course-list.html If you have any questions, please do not hesitate to contact us at . Kind regards, Rumy Kanis Training Services Manager RIPE NCC From fweimer at bfk.de Wed Feb 23 17:18:25 2011 From: fweimer at bfk.de (Florian Weimer) Date: Wed, 23 Feb 2011 16:18:25 +0000 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <4D653149.8010305@ripe.net> (Arne Kiessling's message of "Wed\, 23 Feb 2011 17\:09\:45 +0100") References: <82pqqpnwr3.fsf@mid.bfk.de> <4D62767E.5050802@ripe.net> <8239nhctm7.fsf@mid.bfk.de> <4D63A76C.1030207@ripe.net> <82pqqk8cer.fsf@mid.bfk.de> <4D653149.8010305@ripe.net> Message-ID: <82lj16u3la.fsf@mid.bfk.de> * Arne Kiessling: > LIRs need to provide a copy of the contract as well as the > registration documents of the End User organisation when requesting > independent Internet number resources. This is described in the RIPE > Policy document ripe-452: Thanks for the explanation. Providing a copy of the contract to RIPE NCC is not part of RIPE-452 as far as I can see. But it's a reasonable thing to request, and addresses my concern. >> This mailbox is restricted to LIRs. > > Thank you for the feedback, we will make sure that End Users will > also be able to use this mailbox. The current auto-responder also says this: | We will handle your message as soon as possible. Please note that | enduser-contract at ripe.net was created for a specific project that is | not part of day-to-day operations. As a result, it may take a bit | longer to respond. Is this information still up-to-date? -- Florian Weimer BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstra?e 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 From arne at ripe.net Wed Feb 23 17:09:45 2011 From: arne at ripe.net (Arne Kiessling) Date: Wed, 23 Feb 2011 17:09:45 +0100 Subject: [ncc-services-wg] Implementation status of RIPE-452 In-Reply-To: <82pqqk8cer.fsf@mid.bfk.de> References: <82pqqpnwr3.fsf@mid.bfk.de> <4D62767E.5050802@ripe.net> <8239nhctm7.fsf@mid.bfk.de> <4D63A76C.1030207@ripe.net> <82pqqk8cer.fsf@mid.bfk.de> Message-ID: <4D653149.8010305@ripe.net> Hi Florian, LIRs need to provide a copy of the contract as well as the registration documents of the End User organisation when requesting independent Internet number resources. This is described in the RIPE Policy document ripe-452: "The intention of this policy document is to ensure that the RIPE NCC, as the intermediate manager of provider independent resource assignments to End Users, can confirm that the End User exists, continues to exist and that they continue to fulfil their obligations to comply with the original assignment conditions." (http://www.ripe.net/ripe/docs/ripe-452) The policy document also describes the contractual responsibilities of End Users and LIRs. For more information about the responsibilities and requirements, please visit this website: http://www.ripe.net/lir-services/resource-management/direct-assignments/requirements > This mailbox is restricted to LIRs. Thank you for the feedback, we will make sure that End Users will also be able to use this mailbox. -- Kind Regards Arne Kiessling IP Resource Analyst RIPE Network Coordination Centre Florian Weimer wrote: > * Arne Kiessling: > >> Holders of independent Internet number resources sign an agreement >> with a sponsoring LIR, so they should know which LIR they signed an >> agreement with. > > Hi Arne, > > are LIRs required to share those contracts with RIPE NCC? > > I wouldn't be surprised if LIRs had a wide range of views regarding > the contractual requirements in RIPE-452. That's why I think that a > notification of the resource owner might be helpful. > >> If you have a specific issue that you would like to discuss, please >> reply to me off list or contact . > > Thanks, I will try to gather additional information from there. > > This mailbox is restricted to LIRs. In general, you also need a > contact for resource holders, I think. (This is not a problem in my > case, though.) > > Regards, > Florian From rv at NIC.DTAG.DE Thu Feb 24 00:00:40 2011 From: rv at NIC.DTAG.DE (Ruediger Volk, Deutsche Telekom T-Com - TE141-P1) Date: Thu, 24 Feb 2011 00:00:40 +0100 Subject: [ncc-services-wg] Re: [routing-wg] [address-policy-wg] REMINDER; WAS Re: 2008-08 New Version and Draft Document Published (Initial Certification Policy for Provider Aggregatable Address Space Holders) In-Reply-To: Your message of "Tue, 15 Feb 2011 08:46:44 +0100." <4D5A2F64.9030905@ripe.net> Message-ID: <24010.1298502040@x37.NIC.DTAG.DE> Dear colleagues, I apologize for my bad habits and tradition for sending comments at the very last minute. > Dear Colleagues, > > The new version of RIPE Policy Proposal 2008-08, "Initial Certification > Policy for Provider Aggregatable Address Space Holders", was published > on 9 February 2011. The time period for community review ends on 23 > February 2011. > > Some feedback was sent to the Address Policy Working Group mailing list. > However, to maintain the discussion, we strongly recommend that you > share your ideas and comments and clearly let the community know if you: > > - Support the implementation of the proposal I support the implementation of the proposal; please find additional comments below that point out some problems and some ideas regarding required work. > - Support the general principle of the proposal but would prefer another > wording > - Support the general principle with some details changed but agree to > postpone this discussion until another stage of the policy proposal > review. (This is an initial proposal that covers only PA resources. If > the community supports extending certification to all resources, then > another version of the proposal will be necessary.) > - Do not support the proposal (please explain your motivations) > > > You can find the full proposal at: > > http://www.ripe.net/ripe/policies/proposals/2008-08 > > and the draft document at: > > http://www.ripe.net/ripe/policies/proposals/2008-08/draft > > Please send an email with your comments to address-policy-wg at ripe.net by > 23 February 2011. > > Best regards, > Emilio Madaio My "vote" on the proposal is: I agree to the policy proposal (consisting of "Summary", "Policy Text", and "Rationale") and want to see it fully executed as a minimum first step of implementing full RPKI support by RIPE NCC fitting into the global RPKI infrastructure. This MUST NOT be delayed any further (considering the long time this has been worked AND having missed a committed delivery date [Jan 1 2011] already. I have more comments (which may seem to dilute the primary statement, but hopefully help to fix problems and make more progress) This policy is simpler and more limited than would seem adequate and desirable in today's situation; it was more appropriate when initial versions were proposed. Even while some open ends are recognized the initial policy should be put in place to clearly indicate that the RIPE community is in control of setting policy for the operation of the NCC RPKI service; however we also need to recognize there is a challenge to deal here with more complexity and deeper technical detail compared with [most] other RIPE policies; this includes even the question of just how to identify/separate community and user relevant policy from implementation details. I see need for discussion of the NCC's impact analysis and other related documents (potentially including the process for document control). I have one clear and simple problem (=objection) to the NCC's impact analysis: I do not understand how the NCC can conclude that "this proposal only applies to IPv4 ..."; I do not see such restriction in the language of the proposal - and I'm sure that contributors to the proposal certainly would have expressed this unambiguously if that had been the intention. So I would like to emphasize that the intended policy OF COURSE covers both address families - and the definition of RPKI anyway! Inclusion of IPv6 is a MUST! If RIPE NCC has not yet implemented support of IPv6 they need to tell us the expected delivery date! As related documents I see (a) CPS (b) "... Deregistration of Internet number resources" (c) Certification Service Terms and Conditions (d) Certification Repository Terms and Conditions The need for (a) and (b) has been pointed out for more than 2 years; progress has been slow and late. Having a CPS is a standard requirement for serious [R]PKI CAs. I don't remember that there has been any mentioning of something like (c) and (d) in previous discussion and so they show up as somewhat of a surprise. The documents and their relation need some discussion, in particular with regard to how functions are distributed and to identify (and place) the relevant policy pieces. Somewhat as an example I'd like to mention: The elaborate standard structure that is defined for the CPS clearly includes parts that are defining user relevant policy details (some of which came up in the discussion of this policy proposal) as well as documentation of lots of implementation details that clearly should be left completely in the NCC's responsibility. (c) duplicates parts of the CPS and claims priority over the CPS and classifies the CPS as "explanatory document" - this looks questionable to me. Is it really acceptable that no notifications about replacements for revoked certificates are provided? (maybe OK for hosted service; hard to believe with full RPKI distributed CAs) For meeting the challenges and more satisfactory and satisfying results we need to establish a more detailed activity plan and focussed work. Regards, Ruediger Ruediger Volk Deutsche Telekom AG -- Internet Backbone Engineering E-Mail: rv at NIC.DTAG.DE From emadaio at ripe.net Fri Feb 25 08:51:24 2011 From: emadaio at ripe.net (Emilio Madaio) Date: Fri, 25 Feb 2011 08:51:24 +0100 Subject: [ncc-services-wg] Re: [routing-wg] [address-policy-wg] REMINDER; WAS Re: 2008-08 New Version and Draft Document Published (Initial Certification Policy for Provider Aggregatable Address Space Holders) In-Reply-To: <24010.1298502040@x37.NIC.DTAG.DE> References: <24010.1298502040@x37.NIC.DTAG.DE> Message-ID: <4D675F7C.9060902@ripe.net> Dear Wilfried and Rudiger, thank you very much for your feedback and contribution to the review of the proposal on the mailing list. I hereby will try to clarify furthermore the Impact Analysis performed and published in the Review Phase. The policy text specifically states: " Following guidelines are to apply only for certification of Provider Aggregatable (PA) address space that are held by the RIPE NCC members in good standing. " Purely in terms of policy analysis, in the RIPE NCC service region Provider Aggregatable address space is defined only in the "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", ripe-509, available at http://www.ripe.net/ripe/docs/ripe-509 Hence, according to the existing policies approved by the RIPE community, only IPv4 address space can be Provider Aggregatable. As Rudiger highlighted, we are challenged with this proposal to identify/separate community relevant policies from implementation details. The explanation given in the RIPE NCC's Understanding belongs only to the former: community relevant policies. The Understanding is meant to clarify to the community what the NCC reads in the proposal in order to give some information on how it would be implemented. The goal of the Impact Analysis is to provide relevant supporting information to facilitate the discussions. In this case, it leads into a deeper consideration of what the proposal means and the community's intentions on the whole Certification Service. I am already in touch with the proposer on this matter. Yours and all the other feedbacks presented during the last two weeks of Review Phase are going to be considered together with the Address Policy WG chairs and the next step of the policy making process will be announced to the community accordingly to the PDP. Best Regards Emilio Madaio Policy Development Officer On 2/24/11 12:00 AM, Ruediger Volk, Deutsche Telekom T-Com - TE141-P1 wrote: > Dear colleagues, > > I apologize for my bad habits and tradition for sending comments > at the very last minute. > > > Dear Colleagues, > > > > The new version of RIPE Policy Proposal 2008-08, "Initial Certification > > Policy for Provider Aggregatable Address Space Holders", was published > > on 9 February 2011. The time period for community review ends on 23 > > February 2011. > > > > Some feedback was sent to the Address Policy Working Group mailing list. > > However, to maintain the discussion, we strongly recommend that you > > share your ideas and comments and clearly let the community know if you: > > > > - Support the implementation of the proposal > I support the implementation of the proposal; > please find additional comments below that point out some problems > and some ideas regarding required work. > > > - Support the general principle of the proposal but would prefer another > > wording > > - Support the general principle with some details changed but agree to > > postpone this discussion until another stage of the policy proposal > > review. (This is an initial proposal that covers only PA resources. If > > the community supports extending certification to all resources, then > > another version of the proposal will be necessary.) > > - Do not support the proposal (please explain your motivations) > > > > > > You can find the full proposal at: > > > > http://www.ripe.net/ripe/policies/proposals/2008-08 > > > > and the draft document at: > > > > http://www.ripe.net/ripe/policies/proposals/2008-08/draft > > > > Please send an email with your comments to address-policy-wg at ripe.net by > > 23 February 2011. > > > > Best regards, > > Emilio Madaio > > > > My "vote" on the proposal is: > > I agree to the policy proposal (consisting of "Summary", "Policy Text", > and "Rationale") and want to see it fully executed as a minimum > first step of implementing full RPKI support by RIPE NCC fitting > into the global RPKI infrastructure. > This MUST NOT be delayed any further (considering the long time this has > been worked AND having missed a committed delivery date [Jan 1 2011] already. > > I have more comments (which may seem to dilute the primary statement, > but hopefully help to fix problems and make more progress) > > This policy is simpler and more limited than would seem adequate and desirable > in today's situation; it was more appropriate when initial versions were > proposed. > Even while some open ends are recognized the initial policy should be put > in place to clearly indicate that the RIPE community is in control of setting > policy for the operation of the NCC RPKI service; however we also need to > recognize there is a challenge to deal here with more complexity and deeper > technical detail compared with [most] other RIPE policies; this includes even > the question of just how to identify/separate community and user relevant policy > from implementation details. > > I see need for discussion of the NCC's impact analysis and > other related documents (potentially including the process for > document control). > > I have one clear and simple problem (=objection) to the NCC's impact analysis: > I do not understand how the NCC can conclude that "this proposal only applies > to IPv4 ..."; I do not see such restriction in the language > of the proposal - and I'm sure that contributors to the proposal > certainly would have expressed this unambiguously if that had been the > intention. > So I would like to emphasize that the intended policy OF COURSE covers both > address families - and the definition of RPKI anyway! > Inclusion of IPv6 is a MUST! > If RIPE NCC has not yet implemented support of IPv6 they need to tell us > the expected delivery date! > > As related documents I see > > (a) CPS > (b) "... Deregistration of Internet number resources" > (c) Certification Service Terms and Conditions > (d) Certification Repository Terms and Conditions > > The need for (a) and (b) has been pointed out for more than 2 years; > progress has been slow and late. > Having a CPS is a standard requirement for serious [R]PKI CAs. > I don't remember that there has been any mentioning of something like > (c) and (d) in previous discussion and so they show up as somewhat > of a surprise. > The documents and their relation need some discussion, in particular with > regard to how functions are distributed and to identify (and place) > the relevant policy pieces. > > Somewhat as an example I'd like to mention: > The elaborate standard structure that is defined for the CPS clearly includes > parts that are defining user relevant policy details (some of which came up > in the discussion of this policy proposal) as well as documentation of lots of > implementation details that clearly should be left completely in the > NCC's responsibility. > (c) duplicates parts of the CPS and claims priority over the CPS and > classifies the CPS as "explanatory document" - this looks questionable to me. > Is it really acceptable that no notifications about replacements for > revoked certificates are provided? (maybe OK for hosted service; > hard to believe with full RPKI distributed CAs) > > For meeting the challenges and more satisfactory and satisfying results we > need to establish a more detailed activity plan and focussed work. > > > Regards, > Ruediger > > > Ruediger Volk > > Deutsche Telekom AG -- Internet Backbone Engineering > > E-Mail: rv at NIC.DTAG.DE > From hank at efes.iucc.ac.il Mon Feb 28 09:58:48 2011 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Mon, 28 Feb 2011 10:58:48 +0200 Subject: [ncc-services-wg] New RIPE NCC Procedural Document Available In-Reply-To: <4CC98252.7060303@ripe.net> References: <5.1.0.14.2.20101028092029.03663d20@efes.iucc.ac.il> <5.1.0.14.2.20100628175858.08875d30@efes.iucc.ac.il> <5.1.0.14.2.20100628175858.08875d30@efes.iucc.ac.il> <5.1.0.14.2.20101028092029.03663d20@efes.iucc.ac.il> Message-ID: <5.1.0.14.2.20110228105600.03792380@efes.iucc.ac.il> At 16:01 28/10/2010 +0200, Arne Kiessling wrote: Hi again. I'd like to explore again Phase 3. This document is from Aug 2010. Under the timeframes section, there are specific things RIPE NCC would be doing to reclaim resources. Has any of this started? I ask since we had about 5-6 ASNs that were listed as "not our end user" and I now see they no longer appear under our LIR Portal, yet nothing has changed under the ASN object in the RIPE database. Wasn't this supposed to start "no later than 3 January 2011"? Are any statistics available about how many objects are now in this "limbo" state? How much IPv4 address space would RIPE NCC be able to reclaim? Regards, Hank >Dear Hank, > >thank you for your email. > > > Has the RIPE NCC set a timeframe for implementing Phase 3? > >- Phase 2 of the policy implementation is still ongoing and we are >receiving the required documentation from LIRs on a daily basis. > >The RIPE NCC will present more details on the implementation of Phase 3 at >RIPE 61. The plan is to start Phase 3 after RIPE 61 and no later than 3 >January 2011. > > >Kind regards, > >Arne Kiessling >IP Resource Analyst >RIPE NCC > > >Hank Nussbacher wrote: > >>Phase 3 was published in August 2010: >>http://www.ripe.net/news/2007-01-phase3.html >>Has the RIPE NCC set a timeframe for implementing Phase 3? >>Regards, >>Hank