- ncc-services-wg - mailman.ripe.net

Whither dnsmon?
by Hank Nussbacher 04 Mar '11

04 Mar '11

RIPE NCC lists dnsmon here: http://www.ripe.net/data-tools/stats/dnsmon/ripe-ncc-dns-monitoring-services and indicates on that page to go to: http://dnsmon.ripe.net/ yet going to that link provides an "internal server error". Aren't RIPE NCC services monitored to make sure they are up? -Hank

2 2

New RIPE NCC Procedural Document Available
by Andrea Cima 28 Feb '11

28 Feb '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate emails] Dear Colleagues, The RIPE NCC has published a new RIPE NCC procedural document: ripe-475, "Independent Internet Number Resources – Contractual Relationship Changes between sponsoring LIR and End User" This document describes the steps to be taken when there are changes in the contractual relationship between the End User of independent Internet number resources and the sponsoring Local Internet Registry (LIR). It also describes the scenarios in which the RIPE NCC may de-register independent Internet number resources and what happens to those resources once they are de-registered. The new document is available at: http://www.ripe.net/ripe/docs/ripe-475.html Kind regards, Andrea Cima RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpfPukACgkQXOgsmPkFrjNlEwCcDtE364DhQCU0USBoK3kJhord yBgAoMbRsLFCStkXfvEaV6Mtm5b2sfxW =fKC3 -----END PGP SIGNATURE-----

8 11

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)
by Ruediger Volk, Deutsche Telekom T-Com - TE141-P1 25 Feb '11

25 Feb '11

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(a)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(a)NIC.DTAG.DE

2 1

Implementation status of RIPE-452
by Florian Weimer 23 Feb '11

23 Feb '11

Hi, what's the implementation status of RIPE-452? Is there a way to query the status of specific resources? Thanks, Florian -- Florian Weimer <fweimer(a)bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99

2 6

Announcement: RIPE NCC Training Courses
by Training Mailbox 22 Feb '11

22 Feb '11

[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 <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

Implementation of "pingable:" attribute in the RIPE Database
by Denis Walker 21 Feb '11

21 Feb '11

[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

1 0

RIPE NCC Membership Statistics published on RIPE Labs
by Mirjam Kuehne 17 Feb '11

17 Feb '11

[apologies for duplicates] Dear colleagues, With the year 2009 behind us, we looked at RIPE NCC membership growth and demographics over time. You can find some interesting statistics on RIPE Labs: http://labs.ripe.net/content/ripe-ncc-membership-growth Next we will look at the distribution of number resources among the membership. Stay tuned! Kind Regards, Mirjam Kuehne

1 1

Registering IPv6 Assignments in the RIPE Database
by Denis Walker 15 Feb '11

15 Feb '11

[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-assig… 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

1 0

Create, Update and Delete via the RESTful Web Services
by Mirjam Kuehne 15 Feb '11

15 Feb '11

[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-restf… 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

1 0

REMINDER; WAS Re: 2008-08 New Version and Draft Document Published (Initial Certification Policy for Provider Aggregatable Address Space Holders)
by Emilio Madaio 15 Feb '11

15 Feb '11

[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(a)ripe.net by 23 February 2011. Best regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0