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

2012-08 Discussion Period extended until 13 February 2013 (Publication of Sponsoring LIR for Independent Number Resources)
by Emilio Madaio 16 Jan '13

16 Jan '13

Dear Colleagues, The Discussion Period for the proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources", has been extended until 13 February 2013. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-08 We encourage you to review this policy proposal and send your comments to <ncc-service-wg(a)ripe.net>. Regards, Emilio Madaio Policy Development Officer RIPE NCC

1 0

[news] Update: New RIPE NCC PGP Key
by Brian Riddle 14 Jan '13

14 Jan '13

[Apologies for duplicate emails] Dear colleagues, On Monday, 7 January 2013 we announced that we would start using our 2013 key to sign emails from our ticketing system. Due to technical problems we have to publish a new key which will be published today, Monday, 14 January 2013. This 2013 key has been signed by the 2012 key as described in the key management policy on our website: <https://www.ripe.net/lir-services/resource-management/contact/pgp-authentic…> The new 2013 key will be activated Thursday, 17 January 2013. The original 2012 key will remain valid until Thursday, 31 January 2013. We apologise if this has caused you any inconvenience. If you have any questions about this, please contact <ops(a)ripe.net>. Kind regards, Brian Riddle RIPE NCC

1 0

New on RIPE Labs: RIPE NCC Training Report 2012 & Plans for 2013
by Mirjam Kuehne 11 Jan '13

11 Jan '13

Dear colleagues, Please find a summary of our training activities in 2012 and plans for 2013 on RIPE Labs: https://labs.ripe.net/Members/mirjam/ripe-ncc-training-report-2012 Kind regards, Mirjam Kuehne RIPE NCC

1 0

RDNS checks
by Daniel Suchy 07 Jan '13

07 Jan '13

Hello, when I was trying updating some reverse DNS records, I had problem due to RDNS check - and I think there's bug in implementation - RDNS checks should be done against DNS servers listed in *updated* (new, submited) record, not against servers from *current* (old) record from RIPE database. Of course, "old" servers doesn't provide proper answers, but now I'm not able to update the records (by other way than delete/recreate objects)... With regards Daniel

2 1

Update - RIPE Database Proxy Service Issues
by Axel Pawlik 07 Jan '13

07 Jan '13

[Apologies for duplicate emails] Dear colleagues, Thank you for your comments on this issue. I would like to point out that the *DRAFT* Activity Plan and Budget is published around September of each year, allowing members ample time to read it before it is discussed at the Autumn General Meeting. The RIPE NCC Executive Board then takes the outcome of the discussions and any new developments into consideration before finalising and approving the definitive Activity Plan and Budget, which is then published before the end of the year. On 13 December 2012, we informed the membership of the definitive Activity Plan and Budget and listed the changes from the draft plan. Please note that the membership does not vote on either the draft or the final Activity Plan and Budget - this is one of the member-elected Executive Board's functions. One of the modifications that took place from the draft to the final Activity Plan was the addition of the RIPE Database Proxy Service as a member-only service. This was a follow-up on an action point that stemmed from the Data Protection Task Force and a need to strengthen our contractual relationship between the current users of the RIPE Database Proxy Service and the RIPE NCC ensuring compliance with Dutch and EU legislation. Partially based on the membership's vote of approval regarding the new Charging Scheme of "one LIR, one fee" and partially based on the fact that the RIPE Database Proxy Service is only actively used by less than a handful of entities (both members and non-members), the Executive Board made the decision, which they felt was in the members' interest, to ask the users of this service to sign both a specific RIPE Database Proxy Service Agreement and the Standard Service Agreement (Membership Agreement) that adheres to both EU and Dutch legislation, which would entail the users of this service paying the annual membership fee. Based on the recent mailing list discussions it seems apparent that this is a contentious issue that requires further membership and community discussion. Therefore, we will keep the RIPE Database Proxy Service running as it was in 2012 (i.e., no fee and no Membership Agreement) until we have completed these discussions. We will prepare a legal analysis of the options at hand for the contractual documentation required to use this service and gauge whether or not the membership feels that we should charge a fee for this service. Regards, Axel Pawlik Managing Director RIPE NCC

3 3

RIPE Database Proxy Service Issues
by Axel Pawlik 04 Jan '13

04 Jan '13

[Apologies for duplicate emails] Dear colleagues, There has been discussion on various mailing lists regarding the status of the RIPE Database Proxy Service. Before I address the issues that arose, I'd like to give you some background information on the service itself that may help with the discussions. Technical Background -------------------- To prevent the automatic harvesting of personal information (real names, email addresses, phone numbers) from the RIPE Database, there are PERSON and ROLE object query limits defined in the RIPE Database Acceptable Use Policy. This is set at 1,000 PERSON or ROLE objects per IP address per day. Queries that result in more than 1,000 objects with personal data being returned result in that IP address being blocked from carrying out queries for that day. Users of the RIPE Database have unlimited access to Network Information Centre (NIC)-related objects. They can use the -r flag in order to filter out personal objects and query NIC objects without any limitations. The RIPE Database Proxy Service allows websites to provide a third party interface to the RIPE Database. Without the proxy service, the third parties would quickly run into the limits set on RIPE Database queries. With the proxy service, we whitelist the third party IP address and ask them to pass their user's IP address to us, so limits are only set on the user's IP address, not the third party's. There is no technical way to ensure that the user IP addresses passed to us by the third party are valid. Potentially, third party users of the proxy service could harvest all personal data in the RIPE Database (approximately 2 million objects) in a matter of hours. To ensure that the RIPE NCC's Terms and Conditions are followed, we require a contract between the third party and the RIPE NCC. Users of the Proxy Service -------------------------- In the past ten years, the RIPE NCC has had 31 requests for the proxy service and over the past year, there have been only four active users of the service. Of these four, one is already a RIPE NCC member. NIC Information --------------- All NIC information is still available without access to the proxy service. In the normal presentation of whois data, there is a redirect system that allows users with a normal whois client to deal directly with the RIPE Database whois service. There is no need for a proxy service in this scenario. The proxy service is only necessary if the data needs to be presented in alternative forms, such as on a third party's website. The limits imposed on RIPE Database queries only apply to personal data. Users can always access NIC data in any form they like if they are happy not to receive personal data. On 6 March 2012, the RIPE NCC proposed to change the default behaviour of the query system to instead return only "ALLOWED" results if a user had reached their daily personal data query limit, but there was disagreement over this on the mailing list so the change was not implemented. The proposal is available at: http://www.ripe.net/ripe/mail/archives/db-wg/2012-March/003885.html Legal Considerations -------------------- The RIPE NCC operates under European Data Protection laws, so to avoid risk in this area we insist on having a contract with third parties who wish to use the proxy service. The RIPE NCC and its Executive Board believes that the proxy service should become a member service because it tightens the contractual relationship between the RIPE NCC and third parties. Currently, no such agreement that meets the EU Data Protection legislation is in place between the RIPE NCC and the proxy service users. In order to tighten the contractual relationship between the RIPE NCC and the Proxy service users, taking into account the recent approval of the Charging Scheme 2013 that caused a simplification of the contractual agreements between the RIPE NCC and its service users, the RIPE NCC offered to conclude the membership agreement for continuation of the service. Next Steps? ------------ The Executive Board approved changes to the draft version of the Activity Plan and Budget 2013, and the RIPE NCC published the final version on 13 December 2012: http://www.ripe.net/internet-coordination/news/announcements/ripe-ncc-activ… We do apologise, however, that the changes regarding the proxy service were not more explicitly communicated to the members and the RIPE community in advance of the final publication of the Activity Plan. The RIPE NCC asks that non-RIPE NCC member proxy service users become members but we propose to waive their membership fee until the discussion of the RIPE NCC Charging Scheme 2014 takes place. This will give the membership and community the opportunity to discuss the best way forward for the proxy service in the coming months while ensuring a strong contractual bond between the RIPE NCC and users of this service. In the meantime, there will be no changes to the proxy service and no loss of functionality for the community. The RIPE NCC and its Executive Board will return to its members with proposals for ways to ensure that their wishes are met with regard to service developments while allowing the RIPE NCC to be operate efficiently and responsively. If you have any comments on this issue, please direct them to this mailing list. Best regards, Axel Pawlik Managing Director RIPE NCC

14 29

Fwd: GeekTools Whois Proxy and RIPE/RIPE-NCC
by Nick Hilliard 02 Jan '13

02 Jan '13

This seems odd. I can't seem to find any mention of charging for bulk whois access in the RIPE NCC AGM or the PDP. Am I missing something here? Nick -------- Original Message -------- Subject: GeekTools Whois Proxy and RIPE/RIPE-NCC Date: Mon, 31 Dec 2012 10:41:54 -0500 From: Rodney Joffe <rjoffe(a)centergate.com> To: nanog(a)nanog.org NANOG and ARIN Friends, 14 Years ago, at the suggestion of Jon Postel and some of the early participants in NANOG, we developed the GeekTools Whois proxy to make it easier for *us* - network security and abuse techs - to deal with the expanding number of gtlds and registrars and the varied whois servers that were appearing. The service had both a CLI and web interface. The service also led directly to the creation of whois-servers.net, which now seems to be part of a number of *nix distributions. The service has been up for 14 years, and over that time we have fulfilled the requirements of all of the whois server operators in regards to minimizing and stopping abuse of the GT whois proxy by domain scrapers, spammers, etc, while enabling the security folks to do their jobs. In some cases we have even written code to pass the ip address of the requestor to the whois server registry operator when they wanted to manage quota's directly. We think we have a really good relationship with all of the whois server operators, and I think we provide a useful service to the community, and is widely used. And in 14 years we have never been tarred as an enabler of abuse of "the whois" system. There has obviously never been any kind of charge or fee for using the proxy, or any of the other tools on GeekTools. In about 2002 we started placing a banner ad on the web interface page to offset some of the costs for the bandwidth that the proxy consumes. An average of about $70 a month for over the last 10 years. Actual bandwidth costs are higher than that of course, but it was a thought in 2002 that we had frankly forgotten about until recently. Two weeks ago RIPE-NCC, who provide the whois data for IP addresses in the RIPE region, informed us that based on decisions by their members, as of January 1st 2013, tomorrow, they would no longer provide whois proxy query response services to GeekTools unless we ponied up $1,800 a year for RIPE membership. I don't work very well above layer 7. It is what it is. So I wanted to let you know that as of midnight tonight, apparently, you won't be able to use GeekTools for RIPE related queries. If you have automated scripts, and you are one of the users who has expanded access to GeekTools, you'll need to find an alternative for RIPE queries *today*. My guess is that you will be able to query RIPE directly, once you have worked out that the address space is within RIPE's assignments. I think its wrong to have to pay for whois data that is part of a community resource . So I won't do it.

7 11

RIPE NCC Webinars - new dates
by Training Mailbox 21 Dec '12

21 Dec '12

[Apologies for duplicate e-mails] Dear colleagues, We are pleased to announce the launch of new dates for our Webinars for LIRs. The RIPE NCC Webinars are live, one hour online training courses that allow participants to interact with our trainers without leaving their desks. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <e-learning(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 1

New on RIPE Labs: Conclusions Drawn from Reverse DNS Event
by Mirjam Kuehne 21 Dec '12

21 Dec '12

[apologies for duplicates] Dear colleagues, On Wednesday 13 June 2012, an unknown error caused the removal of several zone files from the configuration of our reverse DNS provisioning system. Following up from the initial report published on RIPE Labs, we further analysed what caused the incident and implemented a number of procedures to decrease the likelihood of this happening in the future. Please see the report on RIPE Labs: https://labs.ripe.net/Members/dfk/conclusions-drawn-from-reverse-dns-event Kind regards, Mirjam Kuehne RIPE NCC

1 0

New RIPE NCC PGP Key
by Andrea Cima 21 Dec '12

21 Dec '12

[Apologies for duplicate e-mails] Dear Colleagues, On Monday, 7 January 2013 we will start using our 2013 key to sign e-mails from our ticketing system. The new key has been signed by the old key as described in the key-management policy on our web site: https://www.ripe.net/lir-services/resource-management/contact/pgp-authentic… The old key remains valid until Thursday, 31 January 2013. If you have any questions about this, please contact <ops(a)ripe.net>. Kind Regards, Andrea Cima RIPE NCC

1 0