- db-wg - mailman.ripe.net

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

New RIPE Documents 395 and 396, on AS Number Requests
by RIPE NCC Webmaster 23 Nov '06

23 Nov '06

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of two updated RIPE Documents. ripe-395 - Supporting Notes for the Autonomous System Number Request Form is available at: http://www.ripe.net/ripe/docs/asnsupport.html ripe-396 - AS Number Request Form is available at: http://www.ripe.net/ripe/docs/asnrequestform.html We have updated the documents to include 4-byte (32 bit) AS Numbers, which can be requested from 1 January 2007. Best Regards, Laura Cobley Registration Services RIPE NCC

1 0

Re: [db-wg] 96.0.0.0/20
by Randy Bush 16 Nov '06

16 Nov '06

> according to our logs the mail was sent: i found the problem the mail is being sent as From MAILER-DAEMON Thu Nov 16 18:01:47 2006 Return-path: <> you should not be doing this! that is reserved for mail delivery failures. randy

2 1

Re: [db-wg] 96.0.0.0/20
by Randy Bush 16 Nov '06

16 Nov '06

> Stab in the dark, so I could be completely off here, but did you try > adding a "password: RPSL" to the top of the request? (Look at the > "RIPE-NCC-RPSL-MNT" object for a possible reason to try that.) yep. still zero response to email to auto-db i have a suspicion it may be due to the database having an outdated pgp key, and i am signing with a new one (bellovin and austein made me upgrade a 12 year old one, so don't blame me:-). which leaves me with the question of how to change a key-cert: object without digging up the old key! randy

2 2

ASN32 test server
by Katie Petrusha 16 Nov '06

16 Nov '06

[Apologies for duplicate mails] Dear colleagues, As you may be aware, from 1 January 2007, it will be possible to request 32-bit ASNs (ASN32 objects). You can find the policy on these 4-byte ASNs at: http://www.ripe.net/ripe/docs/ripe-389.html Although the first of these will not appear in the RIPE Database until the start of next year, we have set up an ASN32 TEST server. This server has a copy of the RIPE Database as of 2006.11.07. It is available for queries: asn32.ripe.net port 43043 And for updates: asn32-dbm(a)ripe.net 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. Please note that updates made to the ASN32 TEST Database will not change any data in the RIPE Database. The notifications are disabled to avoid confusion, the acknowledgements will be sent as usual. We hope it is clear that these are test messages. The following banner has been added to mails: ############################################################## # # # This is the ASN32 Test Server # # # # This update DID NOT affect any RIPE Database objects # # # # To update the live RIPE Database, mail to auto-dbm(a)ripe.net# # # ############################################################## If you have any questions, contact ripe-dbm(a)ripe.net. -- Katie Petrusha RIPE NCC

1 0