February 2009 - ncc-services-wg

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

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

RIPE NCC Scheduled Maintenance - Tuesday, 3 March 2009
by Andrea Cima 26 Feb '09

26 Feb '09

[Apologies for duplicate emails] Dear Colleagues, We will carry out planned maintenance on Tuesday, 3 March 2009 from 15:00 to 19:00 (UTC). During this time, the LIR Portal, the NEW LIR Application software and the RIPE NCC ticketing system will not be available. Emails sent to the RIPE NCC ticketised mailboxes will be queued and then processed normally when service returns. We apologise for any inconvenience this may cause. Kind regards, Andrea Cima Customer Services Manager RIPE NCC

1 0

Test Database for ASPLAIN Implmentation
by Denis Walker 26 Feb '09

26 Feb '09

Dear Colleagues, The RIPE NCC is preparing for the implementation of the IETF RFC 5396. This defines the representation of all AS Numbers in the ASPLAIN format. There is now a test RIPE Database server available using the new software for ASPLAIN. It is a static copy of the NRTM RIPE Database from 19 February 2009, excluding all personal data. All ASDOT objects and references have been converted to ASPLAIN. We did a very simple conversion on this test database which may have broken some referential integrity rules. If you experience any problems please contact <asn32(a)ripe.net>. To access this test database: Query: whois-asn32-test.ripe.net (port 43) Mailupdates: asn32-test-dbm(a)ripe.net Syncupdates: http(s)://syncupdates-asn32-test.db.ripe.net Please test any internal scripts or third party tools you may use for accessing the RIPE Database which involve AS Numbers. Please send any feedback or comments by 13 March 2009 to <asn32(a)ripe.net>. Regards, Denis Walker Business Analyst RIPE NCC

4 7

2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC
by Andrea Cima 16 Feb '09

16 Feb '09

[Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that phase one of policy proposal 2007-01, "Direct Internet Resource Assignments to End Users from the RIPE NCC", will be implemented on 3 March 2009. This change will require that an End User have a contractual relationship with a sponsoring LIR or the RIPE NCC before the End User can receive Internet number resources (Autonomous System (AS) Number, Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP) and anycasting assignments) directly from the RIPE NCC. The full text of policy proposal 2007-01 can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html Phase one addresses the implementation of the new policy in relation to all new requests for independent numbering resource assignments. Please note that from 3 March 2009, End Users requesting independent numbering resources must sign a contract with a sponsoring LIR or with the RIPE NCC in order to receive those resources. Requests for independent numbering resources that do not demonstrate such a contract will not be processed by the RIPE NCC. Information on the required content of contracts between End Users and sponsoring LIRs is available at: http://www.ripe.net/membership/lir-end-user-requirements.html Phase two of policy proposal 2007-01 will address the contractual relationship between End Users who hold previously assigned independent numbering resources and the RIPE NCC or a sponsoring LIR. A plan for implementation of this phase will be presented at the next meeting of the RIPE NCC Services Working Group, which will take place at the RIPE 58 Meeting in Amsterdam from 4-8 May 2009. Kind regards, Andrea Cima RIPE NCC

5 5