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

RIPE NCC to Assign 32-bit ASNs by Default as of 1 January, 2009
by Andrew de la Haye 22 Dec '08

22 Dec '08

[Apologies for duplicate emails] Dear Colleagues, As of 1 January 2009, the RIPE NCC will begin assigning 32-bit (or four-byte) Autonomous System Numbers (ASNs) as default. This is in accordance with a common policy agreed on in all Regional Internet Registry (RIR) communities and described in the RIPE Document ripe-389: "Autonomous System (AS) Number Assignment Policies and Procedures". This document can be found online at: http://www.ripe.net/ripe/docs/ripe-389.html#19 16-bit ASNs and 32-bit ASNs are interoperable. Those who have previously received a 16-bit ASN will not need to renumber. It is possible, however, that some devices, either in your network or the network of your upstream provider, will not be compatible with 32-bit ASNs. It is therefore vital that network operators be aware of the new assignment policy and of their own network's status in terms of 32-bit ASN compatibility. Further information about requesting 16-bit ASNs and 32-bit ASNs can be found at: http://www.ripe.net/news/asn-32-guide.html Kind regards, Andrew de la Haye Chief Operations Officer RIPE NCC

2 1

New RIPE NCC PGP Key
by Laura Cobley 18 Dec '08

18 Dec '08

[Apologies for duplicate e-mails] Dear Colleagues, On Friday, 2 January 2009 we will start using our 2009 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, 29 January 2009. If you have any questions about this, please contact <lir-help(a)ripe.net>. Kind Regards, Laura Cobley RIPE NCC

1 0

RIPE NCC service outage update, 17 December 2008
by Andrei Robachevsky 17 Dec '08

17 Dec '08

Dear Colleagues, Due to a loop problem in out layer 2 infrastructure starting from 11:20 UTC we experienced a high volume of traffic flooding the RIPE NCC network. That caused intermittent high packet loss and affected all our online services. The issue was resolved at 15:00 UTC. All services are back to normal. We apologise for the inconvenience. Best Regards, Andrei Robachevsky

1 0

RIPE NCC Maintenance Announcement
by Ben O'Hara 16 Dec '08

16 Dec '08

[Apologies for duplicate emails] Dear Colleagues, Between 18:00 and 19:00 (UTC) on Wednesday, 17 Dec 2008, the RIPE NCC will carry out planned maintenance work on our network infrastructure. During this period there may be intermittant access to services which we host. We apologise for any inconvenience that this may cause. Regards IT Department Ripe NCC -- Ben O'Hara RIPE Network Coordination Center Systems Engineer Singel 258, Amsterdam, NL http://www.ripe.net +31 20 535 4444 PGP Fingerprint: 080A 52FF BF0A A7FB F176 E7DB 513D 9A3D E968 7DBC

1 0

new debogon announcements on RIS rrc03
by Erik Romijn 01 Dec '08

01 Dec '08

[Apologies for duplicate messages] Dear Colleagues As part of our work to de-Bogonise new address blocks, we are announcing the following new prefixes on RRC03: 110.0.0.0/24 111.0.0.0/24 110.50.0.0/22 111.50.0.0/22 110.255.0.0/16 111.255.0.0/16 Kind regards, Erik Romijn RIPE NCC

1 0

Outage report for the RIPE Database services
by Denis Walker 24 Nov '08

24 Nov '08

[ Apologies for duplicate mails ] Dear colleagues, >From approximately 07:30 (UTC) to 18:30 (UTC) on Saturday, 22 November 2008, the RIPE Database web based services were not available. This was due to the scheduled maintenance of our central filer system. During this period it was not possible to connect to the syncupdates or webupdates services or use the query web form or other web based forms. 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 acknowledgement 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

RIPE NCC Maintenance Announcement
by Gerard Leurs 20 Nov '08

20 Nov '08

[Apologies for duplicate emails] Dear Colleagues, >From 06:00-22:00 (UTC) on Saturday, 22 November 2008, RIPE NCC staff will perform scheduled maintenance work on our core storage infrastructure. The following items will be unavailable at times during this maintenance period: - www.ripe.net - k.root-servers.org - ftp.ripe.net - lirportal.ripe.net - e-learning.ripe.net The performance of dnsmon.ripe.net will be degraded during this period, and DNS zoneupdates will be unavailable. Mails sent to ticketised addresses (for example: hostmaster, ripe-dbm, ncc) will be stored on our MXes and processed after the maintenance period. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an email to <ops(a)ripe.net>. Regards, Gerard Leurs Operations Coordinator RIPE NCC

1 0

reverseDNS problem alerts - to be discussed in "Services" or "DNS" WG
by Wilfried Woeber, UniVie/ACOnet 19 Nov '08

19 Nov '08

Dear all, I am following up internally on a couple of (minor) issues related to reverse DNS configuration mechanisms. Amongst others I am looking for clarification regarding: - misleading(?) text in alert messsages, related to IPv6 - selection of master server to transfer zones from - loose ends in config automation for legacy address space What is the appropriate list or WG to raise these issues - the NCC-Services WG or the DNS WG? Thanks, Wilfried PS: I could certainly take this up privately with the NCC's staff, but I guess some of these aspects might be of interest to the community, too.

2 1

RIPE NCC statement on changes in the RIPE NCC Charging Scheme 2009
by Andrew de la Haye 10 Nov '08

10 Nov '08

[Apologies for duplicates] Dear Colleagues, Recent conversations on the RIPE mailing lists and at the recent RIPE NCC General Meeting have highlighted a number of concerns from members concerning the RIPE NCC Charging Scheme 2009. These concerns refer particularly to the changes laid out in RIPE Policy Proposal 2007-01, relating to charges for Direct End User (PI and ASN) assignments. More information on this proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html There are three areas in which we believe clarification of the RIPE NCC position would be useful. Area 1: Service Fees -------------------- In drafting the RIPE NCC Charging Scheme 2009, the RIPE NCC Board has made it a priority that the necessary changes have minimal impact on the fees paid by RIPE NCC members. The changes will affect a relatively small number of LIRs who have requested many Direct End User assignments. The Direct End User assignments will now be included in the LIR's total score for the sole purpose of calculating the LIR's billing category, and in a few cases this will mean that the LIR moves up a category (for instance, from Medium to Large). Approximately 80% of RIPE NCC members have Direct End User assigments that are taken into account for their billing score. The likelihood that an LIR will move to a higher billing category is offset, however, by the fact that the new Charging Scheme increases the upper limits of each billing category. This means that the addition of Direct End User assignments to an LIR's total score in most cases does not result in an increase in the LIR's billing category. Area 2: Processes and procedures -------------------------------- In the coming months, the RIPE NCC will develop processes and procedures to facilitate the implementation of these policy changes. This will enable us to support members to contact and update the registration of these resources. The changes will be implemented in two phases: - Phase one will involve the implementation of the new policy in relation to all new requests for PI assignments. This will happen in the first quarter of 2009. - Phase two will be to apply the new policy to existing PI assignments, or those made before the adoption of Policy Proposal 2007-01. A plan for implementation of this phase will be presented at the next RIPE NCC Services Working Group, will be held at the RIPE 58 Meeting in Amsterdam, May 2009. Area 3: Changes to future Charging Scheme ----------------------------------------- The RIPE NCC Charging Scheme is agreed on each year by the membership of the RIPE NCC. All LIRs are encouraged to participate in discussion of the Charging Scheme, and to raise any issues that they feel are important to them or the membership as a whole. These discussions can take place during the RIPE NCC General Meetings, which are held twice a year, adjacent to RIPE Meetings, or on the RIPE NCC Services Working Group mailing list: http://www.ripe.net/ripe/wg/ncc-services/index.html If you have any further questions about any of these issues, you can contact RIPE NCC staff for further information at <contact(a)ripe.net>. Regards, Andrew de la Haye Chief Operations Officer, RIPE NCC

1 0

Re: Fwd: [ncc-services-wg] The new charging sceme
by Flor Paredes 05 Nov '08

05 Nov '08

Dear Max, Indeed in the new Charging Scheme 2009 all assigned Internet Number Resources, IPv4 PI, ASNs and IPv6 PI are taken into account for each members billing score to determine the billing category for that member. In the coming months the RIPE NCC will develop processes and procedures to facilitate the implementation of the new policy 2007-01. This will enable us to support members to contact and update the registration of these resources. Please be reassured that the RIPE NCC will fully support its members and will try to minimize the operational impact of this policy change. Regards, Flor Paredes Registration Services Manager RIPE NCC > > >> From: Max Tulyev <president(a)ukraine.su> >> Date: October 31, 2008 11:04:14 GMT+01:00 >> To: ncc-services-wg(a)ripe.net >> Subject: [ncc-services-wg] The new charging sceme >> >> Hi all, >> >> I see http://www.ripe.net/ripe/docs/charging2009.html is adopted, and >> charging for ancient resources such as PI and AS for third-parties is >> resurrected. >> >> So it means I have to find these guys and say hey, RIPE billing scheme >> is changed, so I want some money and a permanent agreement. >> >> But! As I pass them their mntners, I can't enforce them to do anything. >> How can I enforce them to sign an agreement and pay money? >> >> --WBR, >> Max Tulyev (MT6561-RIPE, 2:463/253@FIDO) >> > > Best regards, > > Alex Le Heux > RIPE NCC IP Resource Analyst > >

2 1