December 2006 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 16 May '18

16 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

New RIPE Database software
by Denis Walker 20 Dec '06

20 Dec '06

[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(a)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-representatio… 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@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.

1 0

Implementing TLS/SSL on RIPE NCC external MX'es
by Brian Riddle 20 Dec '06

20 Dec '06

[Apologies for duplicate e-mails] Dear Colleagues, After our successful implementation testing of Transport Layer Security (TLS) over the last few months, we will be implementing TLS on our external mail exchanges (MXs). We will upgrade our mail server software on 8 January 2007, followed by implementation of TLS on 10 January 2007. If you experience problems with mail delivery to the RIPE NCC after the implementation, please send a e-mail to ops(a)ripe.net. To do this, however, you might have to disable TLS on your MX server or send the email from a MX server that does not have TLS enabled. Regards, Brian Riddle IT Manager RIPE NCC

2 1

LIR allocation list
by Dmitry Morozovsky 18 Dec '06

18 Dec '06

Dear colleagues, Is there publicly available list of all NCC allocations anywhere? I remember that at least several years ago there was such document, but cannot find it anymore, neither on http://www.ripe.net/ nor on ftp://ftp.ripe.net/ Any hints? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck(a)rinet.ru *** ------------------------------------------------------------------------

3 2

Outage report
by Denis Walker 15 Dec '06

15 Dec '06

Dear Colleagues, >From Thursday, 14 December 2006 to mid afternoon on Friday, 15 December 2006, our Test Database server was unable to send e-mail. This may have delayed acknowledgments for updates to the Test Database and data consistency reports. This problem was due to an internal DNS issue on one of our servers. It has now been resolved. All queued mails have now been sent. We apologise for any inconvenience. If you have any questions or concerns about this, please contact us at: <ripe-dbnm(a)ripe.net> Regards, Denis Walker Database Group RIPE NCC

1 0

New organisation type proposal "NON-REGISTRY" => "OTHER"
by Katie Petrusha 11 Dec '06

11 Dec '06

[Apologies for duplicate mails] Dear colleagues, This is a proposal to change the organisation type "NON-REGISTRY" to "OTHER" for ORGANISATION objects in the RIPE Database. Motivation: The RIPE ENUM Working Group needs a more general organisation type for the ORGANISATION object. Many organisations have the organisation type "NON-REGISTRY". In the context of the RIPE Database, this is correct. However, some organisations have different functions in other contexts. The RIPE ENUM Working Group proposes changing the organisation type from "NON-REGISTRY" to "OTHER". More details are available at: http://www.ripe.net/ripe/maillists/archives/enum-wg/2006/msg00100.html Implementation: The proposed change involves changing the syntax of the ORGANISATION object in the RIPE Database. It does not involve any new or changed authorisation rules or changes to any other objects. Consequences for Existing Objects: Around 20,000 ORGANISATION objects in the RIPE Database have the status of "NON-REGISTRY". The RIPE NCC will modify these objects. Before making any changes, we will tell the object holders about what will happen. If you have any questions about this, send an e-mail to <ripe-dbm(a)ripe.net> Kind Regards, -- Katie Petrusha RIPE NCC

1 0

Assignments of 32 bit AS Numbers
by Henk Uijterwaal 05 Dec '06

05 Dec '06

Dear Colleagues, From 1 January 2007, the RIPE NCC can assign 32-bit Autonomous System Numbers (ASNs). There is more information about this policy in ripe-389: http://www.ripe.net/ripe/docs/ripe-389.html Details of how to request a 32 bit ASN are in ripe-396: http://www.ripe.net/ripe/docs/asnsupport.html ASN32 objects will appear in the RIPE Database from 1 January 2007. Their format is different from the current 16-bit ASNs. The new format is described in these documents: http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representatio… http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-01.txt The introduction of 32-bit ASNs may have an effect on tools that query the RIPE Database or those based on RPSL. A test server is available. There is more information at: http://www.ripe.net/news/asn-test-server.html Sites using the RIPE Database software will probably have to upgrade their systems, see: http://www.ripe.net/news/asn-db-update.html For more information, please contact us at <asn32(a)ripe.net>. Answers to frequently asked questions will appear in the RIPE NCC FAQ at: http://www.ripe.net/info/faq/ Kind Regards, The RIPE NCC -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------

1 0

CRYPT-PW Deprecation Project: Phase 1
by Agoston Horvath 01 Dec '06

01 Dec '06

[Apologies for duplicate mails] Dear Colleagues, Phase 1 of the CRYPT-PW deprecation project will start today, Thursday, 30 November 2006. This project will deprecate RIPE Database passwords that use the CRYPT-PW authentication method. Notification e-mails will be sent today to over 8300 e-mail addresses, concerning a total of 3587 objects with CRYPT-PW authentication only. Another 326 objects have other authentication methods in addition to CRYPT-PW. If you receive a separate notification e-mail you will have to change your password authentication method to PGP, X.509 or MD5-PW. To change your password authentication method from CRYPT-PW to MD5-PW, use the CGI at: http://www.ripe.net/cgi-bin/crypt2md5.cgi More information about the project can be found at: http://www.ripe.net/db/support/security/crypt-pw_deprecation/ *Key dates* Thursday, 30 November 2006: Notification (Phase 1) Wednesday, 10 January 2007: Reject new CRYPT-PW (Phase 2) Wednesday, 21 February 2007: Remove CRYPT-PW from RIPE Database (Phase 3) If you have any questions, contact: ripe-dbm(a)ripe.net. Regards, Agoston Horvath Database Group RIPE NCC

2 2