From ncc at ripe.net Thu Dec 4 18:32:32 2008 From: ncc at ripe.net (Flor Paredes) Date: Thu, 04 Dec 2008 18:32:32 +0100 Subject: [ncc-announce] Clarification on RIPE NCC End User Assignments Identity Verification Message-ID: <49381430.8010605@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We wish to clarify the RIPE NCC Registration Services Department procedures with regards to direct End User assignments and the requirement for company registration documents. The RIPE NCC requires some form of registration documents to be submitted with all direct End User assignments, such as ASN, PI, Anycast and IXP assignments. The rationale behind this is to ensure that the End User's proper name is registered in the RIPE Database and in our internal records. Due to the wide variety of entities requiring resources in the RIPE NCC service region, we accept a variety of documents, as long as those documents correctly verify the name of the End User. In a situation where a direct assignment is requested for an organisation that is also an LIR, we waive this requirement because a signed contract and registration documents are already on file. Occasionally, an IPRA may still ask for registration documents during the evaluation of such requests because it may not be immediately obvious from the request form that the assignment is intended for the LIR itself. Once it becomes clear that the assignment is for the LIR itself, we no longer require these documents to be submitted. Best regards, Flor Paredes Registration Services Manager RIPE NCC From bohara at ripe.net Tue Dec 16 11:47:02 2008 From: bohara at ripe.net (Ben O'Hara) Date: Tue, 16 Dec 2008 11:47:02 +0100 Subject: [ncc-announce] RIPE NCC Maintenance Announcement Message-ID: <5FC7DB40-164D-4A73-A054-D9E3529EA5CB@ripe.net> [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 From andrei at ripe.net Wed Dec 17 16:59:55 2008 From: andrei at ripe.net (Andrei Robachevsky) Date: Wed, 17 Dec 2008 16:59:55 +0100 Subject: [ncc-announce] RIPE NCC service outage update, 17 December 2008 Message-ID: <494921FB.4020500@ripe.net> 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 From laura at ripe.net Thu Dec 18 17:18:26 2008 From: laura at ripe.net (Laura Cobley) Date: Thu, 18 Dec 2008 17:18:26 +0100 Subject: [ncc-announce] New RIPE NCC PGP Key Message-ID: <494A77D2.5080909@ripe.net> [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 . Kind Regards, Laura Cobley RIPE NCC From saskia at ripe.net Mon Dec 22 10:07:02 2008 From: saskia at ripe.net (Saskia van Gorp) Date: Mon, 22 Dec 2008 10:07:02 +0100 Subject: [ncc-announce] RIPE NCC offices closed on 25-26 December 2008 and 1 January 2009 Message-ID: <494F58B6.4090300@ripe.net> Dear Colleagues, Our offices will be closed on Thursday 25 December (Christmas Day), Friday 26 December (Boxing Day) and Thursday 1 January (New Year's Day). Normal office hours will resume on respectively Monday 29 December 2008 and Friday 2 January 2009. The RIPE NCC wishes you a Merry Christmas and a Happy New Year. Regards, Saskia van Gorp Front Office Manager RIPE NCC From ncc at ripe.net Mon Dec 22 13:56:54 2008 From: ncc at ripe.net (Andrew de la Haye) Date: Mon, 22 Dec 2008 13:56:54 +0100 Subject: [ncc-announce] RIPE NCC to Assign 32-bit ASNs by Default as of 1 January, 2009 Message-ID: <494F8E96.9030303@ripe.net> [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