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

New rules for reverse domain object creation in the RIPE Database
by Denis Walker 22 Oct '09

22 Oct '09

Dear Colleagues, [Apologies for duplicate emails] A proposal has just been sent to the DNS Working Group (DNS WG) mailing list about additional checks on creating reverse delegation DOMAIN objects. If you wish to comment, please do so on the DNS WG mailing list. This will keep any discussion concentrated in a single thread. Regards, Denis Walker Business Analyst, Database Group RIPE NCC

1 0

Proposal to Remove Routing Requirements from the IPv6 Address Allocation Policy Implemented
by Nathalie Trenaman 08 Oct '09

08 Oct '09

Dear Colleagues, We are pleased to announce that policy proposal 2000-06,"Removing Routing Requirements from the IPv6 Address Allocation Policy", has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. This proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2009-06.html The updated "IPv6 Address Allocation and Assignment Policy" document is available at: http://www.ripe.net/ripe/docs/ripe-481.html The following FAQ has also been updated to reflect this policy implementation: http://www.ripe.net/info/faq/rs/ipv6.html Regards, Nathalie Trenaman Registration Services RIPE NCC

1 0

RE: RIPE NCC Services Working Group - Draft Agenda - Updated
by Sanghani, Bijal 06 Oct '09

06 Oct '09

Please see below Updated Draft Agenda for the NCC Services Working Group - A. Administrative Matters * Welcome * Select a scribe * Jabber Monitor * Microphone Etiquette * Approve Minutes from RIPE 58 * Finalise agenda B. RIPE NCC Update - Axel Pawlik, RIPE NCC C. Contractual Relationship Requirement for End Users - Andrea Cima, RIPE NCC D. Certification Update, Alex Band, RIPE NCC E. Discussion about inet(6)num and aut-num objects to reference sponsoring LIR - Piotr Strzyzewski F. 2007-01 implementation survey. Discussion - Piotr Strzyzewski G. Recovering resources assigned to non-existing entities - Uwe Manuel Rasmussen I. Registration Data Quality Update - Robert Kisteleki H. Open Microphone Session Z. A.O.B. Regards, Bijal The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email. The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email. The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

IPv6 Assignment to RIPE NCC
by Axel Pawlik 02 Oct '09

02 Oct '09

Dear Colleagues, Following the approval of Policy Proposal 2009-02, "Allocating/Assigning Resources to the RIPE NCC", the RIPE NCC requested that an IPv6 PI assignment be assigned to it for RIPE Meetings. The RIPE NCC pool of arbiters decided, based on RIPE Policy Document ripe-476, “Allocating/Assigning Resources to the RIPE NCC", that the request met the criteria for the assignment of PI IPv6. For more information on the RIPE NCC's initial request to the arbiters, and details of the arbiters' decision, see: http://www.ripe.net/info/ncc/ipv6-pi-request-to-arbiters.pdf For more information on the arbiters, see: http://www.ripe.net/membership/arbitration.html Best regards, The Arbitration panel and Axel Pawlik Managing Director RIPE NCC

1 0

RE: RIPE NCC Services Working Group - Draft Agenda - Updated
by Sanghani, Bijal 02 Oct '09

02 Oct '09

Please see below Updated Draft Agenda for the NCC Services Working Group - A. Administrative Matters * Welcome * Select a scribe * Jabber Monitor * Microphone Etiquette * Approve Minutes from RIPE 58 * Finalise agenda B. RIPE NCC Update - Axel Pawlik, RIPE NCC (30 minutes) C. Contractual Relationship Requirement for End Users - Andrea Cima, RIPE NCC (15 minutes) D. Certification Update, Alex Band, RIPE NCC E. Discussion about inet(6)num and aut-num objects to reference sponsoring LIR - Piotr Strzyzewski (10 mins) F. Recovering resources assigned to non-existing entities - Uwe Manuel Rasmussen (10 mins) G. Open Microphone Session Z. A.O.B. Regards, Bijal The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email. The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

RIPE NCC Services Working Group - Draft Agenda
by Sanghani, Bijal 25 Sep '09

25 Sep '09

Dear All, Please see below Draft Agenda for the NCC Services Working Group - A. Administrative Matters * Welcome * Select a scribe * Jabber Monitor * Microphone Etiquette * Approve Minutes from RIPE 58 * Finalise agenda B. RIPE NCC Update - Axel Pawlik, RIPE NCC (30 minutes) C. Contractual Relationship Requirement for End Users - Andrea Cima, RIPE NCC (15 minutes) D. Certification Update, Alex Band, RIPE NCC E. Discussion about inet(6)num and aut-num objects to reference sponsoring LIR - Piotr Strzyzewski (10 mins) F. Open Microphone Session Z. A.O.B. Regards, Bijal The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

LIR Portal PI doesn't work
by Max Tulyev 16 Sep '09

16 Sep '09

Hello! I am experiencing troubles with Independent Resources part of the LIR portal. It hangs continuously, goes slow - each page opens more than 1 minute, some time shows 500 error of Java subsystem. At last, when I tried to save changes about my PI/ASN clients, it cleared all marks I did before, cancel all my work for months. Am I only such unlucky guy, or there is really something happens there?

3 6

Agenda Items for RIPE 59 - NCC Services WG
by Sanghani, Bijal 16 Sep '09

16 Sep '09

Dear All, The count down has started to RIPE 59 in Lisbon, we are starting to put together a draft agenda for the NCC Services Working Group. If anyone would like to suggest a presentation or raise a topic for discussion please let either Kurtis or me know and we'll arrange a spot on the agenda for you. Regards, Bijal Sanghani The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

Change to NIC handle usage in the RIPE Database
by Denis Walker 14 Sep '09

14 Sep '09

Dear Colleagues, On Thursday, 10 September the RIPE NCC implemented a change to NIC handle usage. It is no longer possible to re-use an old NIC handle. Additional checks are made when an update is sent to the RIPE Database to create a ROLE or PERSON object. If the NIC handle is in use, or has previously been used and deleted, the update will fail and a new error message will be returned in the acknowledgement: ***Error: The nic-hdl 'name' is not available. This change was requested by the Data Protection Task Force and discussed by the Database Working Group at RIPE 58: http://www.ripe.net/ripe/wg/db/minutes/ripe-58.html In the new implementation, users can select any NIC handle they wish in the same formats as before. The choice of characters and numbers is at the discretion of the user, within the same limits as before. The only difference is that when a NIC handle is chosen that has already been used, the update will fail. The main consequence of this is that if you delete a PERSON or ROLE object you cannot re-create it with the same NIC handle you had previously. Under the old system there was always a chance someone else could have taken your old NIC handle by the time you wanted to re-create it; this was the main reason for the change. The new system ensures that NIC handles map to people or roles uniquely over time. This change does not affect automatically generated organisation names. But we would like to hear feedback on whether it makes sense to also have these map to organisations uniquely over time. Regards, Denis Walker Business Analyst RIPE NCC

2 1

Deprecation of "rev-srv:" attribute completed
by Denis Walker 14 Sep '09

14 Sep '09

Dear Colleagues, On Wednesday, 2 September the RIPE NCC implemented the final stage of the "rev-srv:" deprecation. Information on this project can be found at: http://www.ripe.net/ripe/maillists/archives/db-wg/2009/msg00032.html There were approximately 100,000 remaining "rev-srv:" attributes. All but a small handful have been converted to "remarks:". The few remaining objects have very old syntax, mostly concerning the "status:" value and "country:" code. These old objects will be checked manually to determine the correct values. Regards, Denis Walker Business Analyst RIPE NCC

1 0