- ncc-announce - mailman.ripe.net

Maintenance Announcement - 22/01/2009
by Ben O'Hara 19 Jan '09

19 Jan '09

[Apologies for duplicate mails] Dear Colleagues, Between 17:00 and 18:00 (UTC) on Thursday 22 Jan 2009, the RIPE NCC will carry out planned maintenance work on our network infrastructure. During this period all RIPE NCC services will suffer intermittent interruptions We apologise for any inconvenience that this may cause. Regards Ben -- 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

Updated RIPE Documents
by Laura Cobley 15 Jan '09

15 Jan '09

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of two updated RIPE Documents, ripe-444, 'Autonomous System Number Request Form' and ripe-445, 'Supporting Notes for the Autonomous System Number Request Form'. The updated documents are available at: http://www.ripe.net/ripe/docs/asnrequestform.html http://www.ripe.net/ripe/docs/asnsupport.html These updates have been made to correct an administrative error. Best Regards, Laura Cobley Registration Services RIPE NCC

1 0

Updated RIPE Documents
by Laura Cobley 08 Jan '09

08 Jan '09

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of two updated RIPE Documents, ripe-442, 'Autonomous System Number Request Form' and ripe-443, 'Supporting Notes for the Autonomous System Number Request Form'. The updated documents are available at: http://www.ripe.net/ripe/docs/ripe-442.html http://www.ripe.net/ripe/docs/ripe-443.html These updates have been made to reflect the default assignment of 32-bit AS Numbers as of 1 January 2009, in accordance with ripe-389, 'Autonomous System (AS) Number Assignment Policies and Procedures': http://www.ripe.net/ripe/docs/ripe-389.html. Best Regards, Laura Cobley Registration Services RIPE NCC

1 0

RIPE NCC Maintenance Announcement
by Ben O'Hara 05 Jan '09

05 Jan '09

[Apologies for duplicate emails] Between 18:00 and 19:00 (CET) on Wednesday, 7th Jan 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

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

1 0

RIPE NCC offices closed on 25-26 December 2008 and 1 January 2009
by Saskia van Gorp 22 Dec '08

22 Dec '08

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

1 0

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

Clarification on RIPE NCC End User Assignments Identity Verification
by Flor Paredes 04 Dec '08

04 Dec '08

[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

1 0