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

Proposed Implementation Plan for Policy Proposal 2010-06 in the RIPE Database
by Denis Walker 26 Jan '11

26 Jan '11

[Apologies for duplicate emails] Dear Colleagues, To prepare for the possible acceptance of RIPE Policy Proposal 2010-06, "Registration Requirements for IPv6 End User Assignments", the Database Group at the RIPE NCC proposes the following implementation plan. We will implement a new attribute ("assignment-size:") in INET6NUM objects, add some business logic for its use and add a new value (AGGREGATED-BY-LIR) for the "status:" attribute of an INET6NUM object. Schema and syntax changes in INET6NUM objects: - New attribute "assignment-size:" - Syntax is numeric value > 0 - INET6NUM object will include "assignment-size:" as an optional, single attribute - "assignment-size:" will not be an inverse searchable attribute - New value for the "status:" attribute of an INET6NUM object will be AGGREGATED-BY-LIR Business rules: - "assignment-size:" is optional in INET6NUM objects but required if "status:" is AGGREGATED-BY-LIR - The value of "assignment-size:" must be greater than the prefix size of the INET6NUM object containing the attribute - Parent status of INET6NUM object with status AGGREGATED-BY-LIR can be: ALLOCATED-BY-RIR ALLOCATED-BY-LIR AGGREGATED-BY-LIR - If parent status is AGGREGATED-BY-LIR, grandparent status cannot be AGGREGATED-BY-LIR - If an object has the status AGGREGATED-BY-LIR, a more specific object can only have the status AGGREGATED-BY-LIR (subject to the aforementioned constraints) We will prepare implementation of this plan during the week commencing 31 January 2011. It will be deployed during the week commencing 7 February 2011 should RIPE Policy Proposal 2010-06 be formally approved. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

[members-discuss] Re: NCC#2011014211 NCC Registration Help - Please
by RIPE NCC Customer Services 26 Jan '11

26 Jan '11

Dear Paul, Please be aware that if your company has legally changed its name, a new Standard Service Agreement with the RIPE NCC is required. The current Standard Service Agreement can be found online (for you to view) via the following link: http://www.ripe.net/ripe/docs/service-agreement.html Before we send the new Service Agreement, we need the following three things: 1. A copy of your organisation's legal registration papers (please send by email in a pdf) Official registration papers are the trade register documents that prove your organisation is a registered legal entity, authorised to carry out business activities in your country. Your local Chamber of Commerce usually issues these. 2. A proof of company namechange (Please send by email in a pdf) Please provide some proof that *COMPANY X* is now *COMPANY Y*. We prefer a certificate from the chamber of commerce, if this is not possible; a letter on company letterhead paper of the old company will do. The letter should be signed by both managing directors (Old and new company). 3. Please fill in the fields below In order for RIPE NCC to be able to send you the service agreements with the correct information, please make sure that the fields below are correct: =========================== Name of organisation: [your organisation's new legal name and type of business entity] [Must match with the name on your company registration papers] Your organisation's legal address (No PO box please): legal-addr-street: legal-addr-zip: legal-addr-city: legal-addr-country: Your organisation's postal address to where the contracts will be sent: post-addr-company: post-addr-person: post-addr-street: post-addr-zip: post-addr-city: post-addr-country: Your organisation's billing details: bill-addr-company: bill-addr-person: bill-addr-street: bill-addr-postcode: bill-addr-city: bill-addr-country: bill-mail: bill-ref: bill-vatno: ==================== When we have received all the information and documents, we will send you two copies of the new Standard Service Agreement. Please sign both copies and return one to our offices in Amsterdam. We will let you know when we will post the Service Agreements. -- If you have any questions, please feel free to contact us. Best regards, Smahena Amakran Customer Services RIPE NCC ============================================================ Visit www.IPv6ActNow.org, the one-stop website that explains eveerything you need to know about IPv6. ============================================================ On Tue, 25 Jan 2011 11:15:56 +0000, Hodges Paul wrote: > Hello > > I have am trying to update the Hiscox Group Company name and Postal Address information, but it is requesting that I enter: > > Field 'NCC members discussion' is required. > > So when I then go to the info button and follow the link (http://www.ripe.net/membership/lists.html.) through to create a NCC email address, it then re directs me to > > IPE NCC members can subscribe to this list through the RIPE NCC LIR Portal. More information on how to change or add subscriptions is available at: http://www.ripe.net/membership/subscribe-membership.html > > Which I then click on and it tells me to do: > > Change or Add Subscription Addresses > > To change or add subscription e-mail addresses, please follow these steps: > > 1. Log in to the LIR Portal<https://lirportal.ripe.net/> > 2. Click the "General" link at the top-left of the screen > 3. Click the "edit" button at the top of the screen > 4. Scroll down to the section "Subscribed Mailing Lists" > 5. Change the e-mail address in the box, or click the "Add" button to add another e-mail address > 6. Click "Update" to save your changes > So I seem to be stuck in this loop, please can you direct me to the exact URL, so that I can register a NCC email address and then in turn update the Company profile information, so that when RIPE are trying to contact Hiscox, you get directed to the correct person other than someone who has left. > Please feel free to contact me if you wish, > Regards > Paul > > > Paul Hodges > Networks and Security Technology Lead > IT Infrastructure > Hiscox plc > T +44 (0)1206 773840 > M +44 (0)7826523789 > www.hiscox.com<http://www.hiscox.com/> > > > ________________________________ > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. No one else is authorised to distribute, forward, print, copy or act upon any information contained in this email. If you have received this email in error, please notify the sender. > > Hiscox Syndicates Limited, Hiscox Insurance Company Limited, Hiscox Underwriting Limited and Hiscox ASM Limited are authorised and regulated by the Financial Services Authority. Hiscox plc is a company registered in England and Wales under company registration number 2837811 and registered office at 1 Great St Helen's, London EC3A 6HX. ---- 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.

2 1

Public demo sessions to develop RIPEstat Toolbox
by Mirjam Kuehne 20 Jan '11

20 Jan '11

[apologies for duplicates] Dear colleagues, The RIPE NCC is working on a toolbox, called RIPEstat, that will make it easier to access the various datasets maintained by the RIPE NCC. This toolbox will be developed in close cooperation with the community. We have scheduled a series of public demo sessions. The first one will take place next week Tuesday. Please find more details on RIPE Labs: http://labs.ripe.net/Members/dfk/ripestat-the-ripe-ncc-information-toolbox Kind Regards, Mirjam Kuehne RIPE NCC

1 0

New and Improved RIPE Registry Global Resource Service
by Mirjam Kuehne 12 Jan '11

12 Jan '11

[Apologies for duplicate emails] Dear colleagues, We have redesigned and improved the way we mirror other databases (Thanks to the RIPE NCC Database staff!). We now have a method of translating the operational data from other registries (for instance from other RIRs or the RADb) into the RIPE Database structure. This means the RIPE Database will contain the most complete set of operational data in (RIPE) RPSL format that has ever been available in one place. Read more on RIPE Labs: http://labs.ripe.net/Members/Paul_P_/ripe-registry-global-resource-service Kind Regards, Mirjam Kuehne RIPE NCC

3 3

RIPE NCC to Discontinue Hostcount
by Mark Dranse 05 Jan '11

05 Jan '11

[Apologies for duplicates] Dear colleagues, For the past 20 years, the RIPE NCC has maintained Hostcount, a measurement of the number Address Resource Records (A RRs) in country code Top Level Domains (ccTLDs) in the RIPE NCC service region. The aim of this project has been to gain insight into the size and the growth rate of the Internet. It has been clear for some time though, that Hostcount no longer provides a reliable indication of these things. Therefore, as of January 2011, the RIPE NCC will discontinue Hostcount. More background information on this project and its closure can be found on RIPE Labs: http://labs.ripe.net/Members/markd/hostcount Kind Regards, Mark Dranse Information Services Manager, RIPE NCC

1 0

RIPE NCC Resource Certification Service Launch
by Alex Band 05 Jan '11

05 Jan '11

Dear colleagues, The RIPE NCC is proud to announce the production launch of the RIPE NCC resource certification service. With the support of the RIPE community, we have worked very hard to create a service that will help to make our registry more robust and provide a vital element in making Internet routing more secure. Now, more than ever, it is important to be sure who is the legitimate holder of a block of IP addresses. As a first step, the RIPE NCC (in coordination with the other four RIRs) has created a hosted platform. This means that all LIRs will be able to generate a certificate of holdership that will be held in a repository maintained by the RIPE NCC. The feature set is, as it stands, very limited: the certificate will only cover Provider Aggregatable address space, and it is not yet possible to run your own Certificate Authority or generate "child" certificates to create a chain of trust. All of these capabilities will be rolled out over the course of 2011, based on the wishes and input of the RIPE community. This brings me to an important point. While the technology is now in place, the policy describing the details of the certification system has not yet passed the RIPE Policy Development Process. We have decided, however, to launch the system with the most limited feature set possible, so that the membership can try it out. Our hope is that this will make resource certification more tangible, and assist the community in making an informed decision about what the system should offer, now and in the future. I invite and encourage you to discuss this on the RIPE NCC Services Working Group mailing list: http://www.ripe.net/ripe/wg/ncc-services/index.html Ongoing development of the RIPE NCC certification service will, of course, be planned in accordance with the certification policy that is agreed on by the RIPE community. For more information, please visit: http://ripe.net/certification If you have any questions or comments, please email <certification(a)ripe.net >. Best regards, Alex Band Product Manager, RIPE NCC

2 1

How to certify resources
by Alexander.Koeppe＠merck.de 03 Jan '11

03 Jan '11

Hello List, I'm still a bit confused, what I've to do with this new certification approach. My LIR portal user has the "certification" permission. When I'm clicking on "certification" in the left pane, it says me that I don't have a CA yet. Well of course not. Not in the Internet. Do I need to create a CA over the portal frontend? And if yes, do I have to provide a server running a CA service in the Internet? Somehow I jumped around some sites and reached the following messages inside the LIR portal: "Congratulations! You now have a digital certificate covering your Provider Aggregatable (PA) address space." Well now I'm totally confused. Does that mean, that my resources are certified already? Hope some of you can help to bring some clarity to me about this topic. Thanks&Regards Alexander Koeppe This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith. Click http://disclaimer.merck.de to access the German, French, Spanish and Portuguese versions of this disclaimer.

2 1

New RIPE NCC PGP Key
by Andrea Cima 27 Dec '10

27 Dec '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicate e-mails] Dear Colleagues, On Wednesday, 5 January 2011 we will start using our 2011 key to sign e-mail 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/rs/pgp/index.html The old key remains valid until Thursday, 3 February 2011. If you have any questions about this, please contact <ncc(a)ripe.net>. 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 iEYEARECAAYFAk0YtfEACgkQXOgsmPkFrjOY9wCgtImM+qFN1KAqyVniORJ8jbf8 P9UAoKn11gqoeDn1QCx+S4A0YkBqeHgR =fHuQ -----END PGP SIGNATURE-----

1 0

2007-01 Policy Implementation - 4 January 2011 Last Day to submit End User Documentation
by Arne Kiessling 21 Dec '10

21 Dec '10

Dear Colleagues, The RIPE NCC will finish Phase Two of the 2007-01 policy implementation "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region" at the beginning of January 2011, as was announced during the RIPE NCC Services Working Group session at RIPE 61. LIRs have until 4 January 2011 to upload the required documentation for the independent resources they have marked as "My End User". This is a hard deadline; the uploading tool will no longer be available on the LIR Portal after 4 January 2011. This step is necessary to start Phase Three of the policy implementation in January 2011. The RIPE NCC will publish the procedure document for Phase Three of the policy implementation, and any other necessary information, before Phase Three starts. Draft procedure document: http://www.ripe.net/news/2007-01-phase3.html Information on the documentation required: http://ripe.net/rs/pi-existing-assignments.html Please contact <enduser-contract(a)ripe.net> if you have any questions or comments. Kind regards, Arne Kiessling IP Resource Analyst RIPE NCC

1 0

Changes to Reverse DNS DOMAIN Objects in the RIPE Database
by Denis Walker 09 Dec '10

09 Dec '10

[Apologies for duplicate mails] Dear colleagues, It was agreed at RIPE 59 in Lisbon that reverse DNS zones in the RIPE Database should not have child objects. Documentation relating to this decision and the discussion surrounding it can be found in the minutes of the RIPE 59 DNS and Database Working Groups: http://www.ripe.net/ripe/wg/dns/r59-minutes.html http://www.ripe.net/ripe/wg/db/minutes/ripe-59.html The RIPE NCC is now ready to deploy this change and clean-up the existing data. This will be done in the week commencing 13 December 2010. After deployment it will not be possible to create a reverse DNS DOMAIN object in the RIPE Database if either a more or less specific object already exists. During the data clean-up you may receive a notification that your DOMAIN object has been deleted. If this is the case there will be a less specific DOMAIN object in the database. Your object was only for documentation purposes and did not have any effect on reverse DNS. If you have any questions please contact us at <ripe-dbm(a)ripe.net>. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0