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

Website Launch: www.IPv6ActNow.org
by Paul Rendek 20 May '09

20 May '09

[Apologies for duplicate emails.] Dear Colleagues, The RIPE NCC is pleased to announce the launch of the IPv6 Act Now! website. www.IPv6ActNow.org is a one stop website that explains IPv6 in terms that everyone can understand and provides a variety of useful information aimed at promoting the global adoption of IPv6. The site is for anyone with an interest in IPv6, including network engineers, company directors, law enforcement agencies, government representatives and civil society. The site content is regularly updated and includes: - Education, advice and opinions from the experts - Latest IPv6-related news stories - Videos and articles from Internet community leaders - Current IPv4 exhaustion and IPv6 uptake statistics - The RIPE community's statement on IPv6 deployment, including a list of organisations supporting this statement - Information on community-developed IPv6 distribution policies - Useful links to other sources of information about IPv6 - A forum for everyone to share experiences, ask questions and find answers The site also includes contributions from other Regional Internet Registries (RIRs) and industry partners. We invite you to take a look around the site. We hope that you find it useful. If you have and comments or suggestions about IPv6ActNow!, please contact us at <ipv6actnow(a)ripe.net>. Regards, Paul Rendek Head of External Relations and Communication RIPE NCC

1 0

Announcement: DNSSEC e-learning module 1 available now
by Rumy Kanis 18 May '09

18 May '09

[apologies for duplicates] Dear Colleagues, The RIPE NCC is pleased to announce the launch of the first module of our DNSSEC e-learning course, entitled "DNS Basics". This introductory module explains how DNS works by following a simple query, and can be viewed at: https://e-learning.ripe.net/training/e-learning/ In the coming months we will be releasing several more modules. Next up are: Module 2: DNS Vulnerabilities Module 3: DNSSEC The RIPE NCC E-Learning Centre is a free-of-charge service available to everyone. If you have any questions, please feel free to contact us at <e-learning(a)ripe.net>. Happy Learning, Rumy Kanis Training Services Manager RIPE NCC

1 0

Charging scheme 2010
by Max Tulyev 15 May '09

15 May '09

Hi all, is there a good place to discuss 2010 charging scheme? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

RIPE NCC Now Accepting Requests for IPv6 PI Assignments
by Scott Donald 06 May '09

06 May '09

[Apologies for duplicate emails.] Dear Colleagues, We are pleased to announce that the RIPE NCC now accept requests for IPv6 Provider Independent (PI) assignments. This follows the accepted policy proposal 2006-01 "Provider Independent (PI) IPv6 Assignments for End User Organisations". The request form and supporting notes are available from the RIPE Document Store at: http://www.ripe.net/ripe/docs/ipv6.html Requests can also be made via the LIR Portal, which is available at: https://lirportal.ripe.net/ IPv6 PI assignments will come from reserved block 2001:678::/29. You may want to update your filters. Regards, Scott Donald Registration Services RIPE NCC

1 0

Deprecation of "rev-srv:" attribute
by Denis Walker 28 Apr '09

28 Apr '09

[Apologies for duplicate emails] Dear Colleagues, The RIPE NCC will begin implementing the deprecation of the "rev-srv:" attribute. This was discussed on the DNS WG mailing list and at the RIPE 54 Meeting in Tallinn, Estonia, during the Database Working Group session. More details are available at: http://www.ripe.net/ripe/maillists/archives/dns-wg/2007/msg00090.html The plan suggested on the mailing list will be used and there are three stages: - Stage 1: Announcement - Stage 2: Syntax change - Stage 3: Clean-up The details of each stage are outlined below. Stage 1: Announcement ---------------------- The announcement will let users know that the process is starting. Over the next month you will need to check any scripts that auto-generate INET(6)NUM objects. Make sure that no "rev-srv:" attributes are included in the generated objects. Stage 2: Syntax change ---------------------- This stage will begin on May 27 2009, when the RIPE NCC will remove the "rev-srv:" attribute from the RIPE RPSL syntax for INET(6)NUM objects. Any new objects created after this date must not have this attribute included. If any objects that include this attribute are modified, then the "rev-srv:" attributes must be removed. If you wish to keep the information for documentation purposes, change the"rev-srv:" attributes into "remarks:" attributes. The "rev-srv:" attribute will also be removed from the list of inverse query options. Stage 3: Clean-up ------------------ The final stage will begin before the RIPE 59 Meeting, which takes place from 5-9 October, 2009. The clean-up will remove any remaining "rev-srv:" attributes from these objects. They will be converted into "remarks:" attributes. If you have any questions about this, please contact <ripe-dbm(a)ripe.net>. Regards, Denis Walker Business Analyst RIPE NCC

3 2

Agenda Items for RIPE 58 - NCC Services WG
by Sanghani, Bijal 07 Apr '09

07 Apr '09

Dear All, Its about 4 weeks till RIPE 58 in Amsterdam, we've started compiling items for the 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. Kind Regards Bijal Sanghani Senior Engineer - Technical Services Group Reliance Globalcom (UK) Ltd Sovereign Court, 635 Sipson Road, West Drayton Middlesex, UB7 0JE, UK Direct: (+44) 020 8282 1564 | FAX: +44 208 282 1566 E MAIL: bsanghani(a)relianceglobalcom.com <mailto:bsanghani@relianceglobalcom.com> | URL: www.relianceglobalcom.com <http://www.relianceglobalcom.com> IMPORTANT - Please note the change of my email id from bsanghani(a)flagtelecom.com <mailto:bsanghani@flagtelecom.com> to bsanghani(a)relianceglobalcom.com <mailto:bsanghani@relianceglobalcom.com> 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

ASplain deployment
by Denis Walker 25 Mar '09

25 Mar '09

[Apologies for duplicates] Dear Colleagues, The RIPE NCC has now successfully completed the implementation of ASPLAIN format in the RIPE Database. If you are the maintainer of any routing data in the RIPE Database that is associated with 32-bit Autonomous System (AS) Numbers, please check your data to be sure that it was correctly converted. >From this point, any AS Numbers or references must be in the ASPLAIN format. The ASDOT format will no longer be accepted in RIPE NCC services such as the LIR Portal and the RIPE Database. Please note that the Routing Information Service (RIS) RIS has not been converted to ASPLAIN at this point. Some RIS tools may accept ASPLAIN input, however this is not yet officially supported. If you use AS Numbers internally, or with other tools that have not yet been updated, you may be interested in a conversion tool that has been provided by APNIC. This tool converts ASDOT format AS Numbers to ASPLAIN and back. It can be downloaded from: http://www.apnic.net/cgi-bin/convert-asn.pl If you have any concerns about this matter, please send an email to <asn32(a)ripe.net> Kind regards, Denis Walker Business Analyst Database Department RIPE NCC

1 0

Update to RIPE Database software
by Agoston Horvath 23 Mar '09

23 Mar '09

Dear Colleagues, The RIPE Database software has been updated. The update included the following changes to update notification emails: - The From: field has changed to unread(a)ripe.net - The Reply-to: field has been removed from all notification messages - The email envelope has been set to 'unread(a)ripe.net' instead of '<>'. The update also improved error reporting. For 'unreferenced object' and some other errors, the object's primary key is now included. This will make trouble-shooting easier. Kind regards, Agoston Horvath Database Group RIPE NCC

3 3

ASDOT data conversion in the RIPE Database
by Denis Walker 19 Mar '09

19 Mar '09

Dear Colleagues, The RIPE NCC is preparing for the implementation of RFC5396, which defines the representation of all AS Numbers in the ASPLAIN format. The RIPE NCC will start using the ASPLAIN format on 25 March 25 2009. On this day the RIPE NCC will convert any existing ASDOT data in the RIPE Database into ASPLAIN equivalent data. There are two ways we will do this: - If the primary key of the object contains an ASDOT, for example "aut-num: AS8.0", then the object will be deleted and re-created. - If the object contains a reference to an ASDOT, for example "import: from AS8.0", then the object will be modified. All objects altered in any way will have a "remarks:" attribute and an extra "changed:" attribute added. Notifications will be sent to the maintainers of the data for each update. The maintainers of the data do not need to do anything regarding this change. The conversion can only be done as part of the software upgrade. But if you are responsible for any ASDOT data we would ask that you check the data after the conversion is complete. Regards, Denis Walker Business Analyst RIPE NCC

1 0

Implementation of ASPLAIN Format
by Henk Uijterwaal 19 Mar '09

19 Mar '09

[Apologies for duplicates] Dear Colleagues, With the publication of RFC 5396, the IETF has standardised the representation of all Autonomous System (AS) Numbers in the ASPLAIN format. This covers both 16-bit and 32-bit AS Numbers. The previous ASDOT format is now obsolete. The RIPE NCC plans to start using the ASPLAIN format by the end of March 2009. From that time, any AS Numbers or references must be in the ASPLAIN format. The old ASDOT format will no longer be accepted in RIPE NCC services such as the LIR Portal and the RIPE Database. In order to ensure a smooth transition, any data in the RIPE Database containing an ASDOT AS Number will be converted by the RIPE NCC using the one-to-one mapping that exists between the two formats. Exact details of this conversion will be published closer to the actual date. The RIPE NCC has also provided a test database using the converted software and containing a copy of the RIPE Database. The AS Numbers in this copied data have been converted to ASPLAIN. For more details, see the earlier RIPE NCC announcement: http://www.ripe.net/ripe/maillists/archives/ncc-services-wg/2009/msg00014.h… If you use AS Numbers internally, or with other tools that have not yet been updated, you may be interested in a conversion tool provided by APNIC. This tool converts ASDOT format AS Numbers to ASPLAIN and back. It can be downloaded from: http://www.apnic.net/cgi-bin/convert-asn.pl If you have any concerns about this matter, please write to <asn32(a)ripe.net >. Kind regards, Henk Uijterwaal Senior Project Manager, RIPE NCC

2 1