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

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

Reference Number: BMW:2551256003/23
by byte_k 16 Mar '09

16 Mar '09

-- Reference Number: BMW:2551256003/23 This is to notify you in the BMW email lottery which your email won you a BMW 7 Series Sport saloon car and a Lumb Sum of GBP250.000.00. To facilitate your claims, please contact the fiduciary manager. Mr Philips Harper. E- mail; bmwfundclaims(a)live.co.uk

1 0

You have received a card from a family member!
by webmaster＠hallmark.org 14 Mar '09

14 Mar '09

1 0

Outage report for the RIPE Database services
by Denis Walker 10 Mar '09

10 Mar '09

[ Apologies for duplicate mails ] Dear colleagues, >From approximately 10:00 (UTC) to 11:30 (UTC) on Tuesday, 10 March 2009, the RIPE Database update services were not available. This was due to a problem with the update servers. During this period it was not possible to connect to the syncupdates or webupdates services. Email updates were also delayed. All the messages received by auto-dbm(a)ripe.net were stored on our mail server. All the saved update messages have been processed. If you sent an email update to the RIPE Database service during this period, you will have already received an acknowledgment message. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

2007-01 Implementation: Model agreement and charging requirements?
by Wilfried Woeber, UniVie/ACOnet 04 Mar '09

04 Mar '09

The announcement about implemntation of 2007-01 was distributed on Feb, 12, 2009, pointing to: http://www.ripe.net/membership/lir-end-user-requirements.html At the bottom of this page there is the phrase: "A model agreement and its terms will be provided here shortly." Can we still expect to see such a model text before March 3, 2009, the "effective date" of implementation? In particular, I am interested in guidance on: "End User must pay an annual maintenance fee to the LIR for the resources." because I wouldn't want to implement a separate charging scheme for our customers holding PI resources, and which already do have a contract and are charged for our connectivity services on a less granular basis. Of course, a surcharge of 0,-- <put currency code here> would be fine :-) Regards, Wilfried.

2 2

New Documents available
by Ingrid Wijte 03 Mar '09

03 Mar '09

Dear Colleagues We have published several new RIPE Documents. The publication of these documents follows the implementation by the RIPE NCC of phase one of the previously accepted policy proposal 2007-01: "Direct Internet Resource Assignments to End Users from the RIPE NCC". Policy Documents: - ripe-449, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". It replaces ripe-441, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". - ripe-448, "Autonomous System (AS) Number Assignment Policies and Procedures". It replaces ripe-389, "Autonomous System (AS) Number Assignment Policies and Procedures". - ripe-450, "IPv6 Address Allocation and Assignment Policy". It replaces ripe-421, "IPv6 Address Allocation and Assignment Policy". - ripe-451, "IPv6 Address Space Policy for Internet Exchange Points". It replaces ripe-256, "IPv6 Address Space Policy for Internet Exchange Points". - ripe-452, "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region". This is a new RIPE Document. RIPE NCC Organisational Document: - ripe-462, "RIPE NCC End User Assignment Agreement". This is a new RIPE Document. Request Forms and Supporting Notes: - ripe-453, "Provider Independent (PI) Assignment Request Form". It replaces ripe-356, "Provider Independent (PI) Assignment Request Form". - ripe-454, "Supporting Notes for the Provider Independent (PI) Assignment Request Form". It replaces ripe-357, "Supporting Notes for the Provider Independent (PI)Assignment Request Form". - ripe-456, "AS Number Request Form". It replaces ripe-444, "AS Number Request Form". - ripe-457, "Supporting Notes for the Autonomous System Number Request Form". It replaces ripe-445, "Supporting Notes for the Autonomous System Number Request Form". - ripe-458, "Anycast Assignment Request Form". It replaces ripe-390, "Anycast Assignment Request Form". - ripe-459, "Supporting Notes for the Anycast Assignment Request Form". It replaces ripe-391, "Supporting Notes for the Anycast Assignment Request Form". - ripe-460, "IPv6 Internet Exchange Points Assignment Request Form". It replaces ripe-371, "IPv6 Internet Exchange Points Assignment Request Form" - ripe-461, "Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form". It replaces ripe-372, "Supporting Notes for the IPv6 Internet Exchange Points Assignment Request Form". The new documents are available at: http://www.ripe.net/ripe/docs/titletoc.html Recently Published section available at: http://www.ripe.net/ripe/docs/recent.html Best regards Ingrid Wijte IP Resource Analyst RIPE NCC

1 0