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]/
[db-wg] New RIPE Database software
- Previous message (by thread): [db-wg] Re: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Wed Dec 20 17:32:02 CET 2006
[Apologies for duplicate e-mails] Dear colleagues, On 2 January 2007, between 07:00 and 08:00 UTC, we will deploy new software for the RIPE Database. Three changes will take place: 1. The new software will allow the creation of 32-bit (4-byte) Autonomous System Numbers (ASNs). There is more information about this in the references at the end of this e-mail. 2. There will be a change in ORGANISATION object type (from NON-REGISTRY to OTHER). There is more information about this at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00245.html 3. We will reverse changes made to the status for ERX objects. While implementing the ASSIGNED ANYCAST status, other changes were made. This prevented more specific assignments from being created within EARLY REGISTRATION ranges. These changes will be rolled back. If you have any questions about any of these changes, send an e-mail to <ripe-dbm at ripe.net>. Regards Denis Walker Database Group RIPE NCC -------- References: The new 32-bit ASN format is described in these documents: http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representation-02.txt http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-01.txt Sites using the RIPE Database software will probably have to upgrade their systems, see: http://www.ripe.net/news/asn-db-update.html We have set up an ASN32 test server. It has a copy of the RIPE Database taken on 7 November 2006. This test server does not provide any mirror stream facilities. It is available for queries: asn32.ripe.net port 43043 And for updates: asn32-dbm at localhost You may use this database to create your own test ASN32 object(s). You may also test against the existing "aut-num" object AS1.1 See 'whois -h asn32.ripe.net -p 43043 -rGB AS1.0 - AS1.65535' for more details.
- Previous message (by thread): [db-wg] Re: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]