From eromijn at ripe.net Mon Dec 1 15:02:26 2008 From: eromijn at ripe.net (Erik Romijn) Date: Mon, 01 Dec 2008 15:02:26 +0100 Subject: [ncc-services-wg] new debogon announcements on RIS rrc03 Message-ID: <4933EE72.8050907@ripe.net> [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 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-services-wg] 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-services-wg] 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-services-wg] 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 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-services-wg] 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 From president at ukraine.su Mon Dec 22 21:02:21 2008 From: president at ukraine.su (Max Tulyev) Date: Mon, 22 Dec 2008 22:02:21 +0200 Subject: [ncc-services-wg] RIPE NCC to Assign 32-bit ASNs by Default as of 1 January, 2009 In-Reply-To: <494F8E96.9030303@ripe.net> References: <494F8E96.9030303@ripe.net> Message-ID: <494FF24D.9090507@ukraine.su> Hi Andrew, Will this affect requests sent this year, but completed after January, 1st? Andrew de la Haye wrote: > [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 > -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)