This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-announce] RIPE NCC to Assign 32-bit ASNs by Default as of 1 January, 2009
- Previous message (by thread): [ncc-announce] RIPE NCC offices closed on 25-26 December 2008 and 1 January 2009
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrew de la Haye
ncc at ripe.net
Mon Dec 22 13:56:54 CET 2008
[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
- Previous message (by thread): [ncc-announce] RIPE NCC offices closed on 25-26 December 2008 and 1 January 2009
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]