From brettcarr at ripe.net Mon Dec 4 09:40:50 2006 From: brettcarr at ripe.net (Brett Carr) Date: Mon, 4 Dec 2006 09:40:50 +0100 Subject: [ncc-services-wg] Maintenance Announcement Message-ID: <038e01c7177f$e6d67bd0$8e0200c1@singel.ripe.net> [Apologies for duplicates] Dear Colleagues, On 7 December 2006, authoritative Reverse DNS Services on ns-pri.ripe.net will be unavailable for a short period between 09:00 and 10:00 UTC. During this time we need to carry out important server maintenance work. We apologise in advance for any inconvenience. If you have any questions or concerns about this, please send an e-mail to dns-help at ripe.net. Regards, -- Brett Carr Ripe Network Coordination Centre Manager -- DNS Services Group Singel 258 Amsterdam NL GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8 From henk at ripe.net Tue Dec 5 12:03:27 2006 From: henk at ripe.net (Henk Uijterwaal) Date: Tue, 05 Dec 2006 12:03:27 +0100 Subject: [ncc-services-wg] Assignments of 32 bit AS Numbers Message-ID: <457551FF.20208@ripe.net> 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-representation-02.txt 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 . 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 ------------------------------------------------------------------------------ From ncc at ripe.net Wed Dec 6 08:04:20 2006 From: ncc at ripe.net (Axel Pawlik) Date: Wed, 06 Dec 2006 08:04:20 +0100 Subject: [ncc-services-wg] NRO at ITU Telecom World, Hong Kong, China Message-ID: <45766B74.1010202@ripe.net> [Apologies for duplicate e-mails.] Dear colleagues, The NRO is taking part in the ITU Telecom World event in Hong Kong, China, from 4-8 December 2006. The 'Internet Pavilion' booth is co-sponsored by the NRO, ICANN, and ISOC and aims to promote a greater understanding of the existing open and transparent bottom-up development processes of the technical Internet community. The Internet Pavilion includes: * Multimedia presentations on Regional Internet Registry (RIR) history, the NRO and IP addressing and routing * NRO fact sheets in six official United Nations languages * Newsletters, articles and other relevant documentation Representatives from all the RIRs, ICANN and ISOC are available at the booth each day for ITU participants and journalists to seek further information. Through this initiative, the Internet Pavilion will facilitate an understanding of why a collaborative and cooperative governance model is essential for the success of the Internet and the development of the Information Society. For more information, please see: http://www.nro.net/governance/itu-exhibition-info.html Regards, Axel Pawlik RIPE NCC Managing Director From denis at ripe.net Fri Dec 15 16:00:45 2006 From: denis at ripe.net (Denis Walker) Date: Fri, 15 Dec 2006 16:00:45 +0100 Subject: [ncc-services-wg] Outage report Message-ID: <4582B89D.4070602@ripe.net> 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: Regards, Denis Walker Database Group RIPE NCC From brian at ripe.net Wed Dec 20 10:39:58 2006 From: brian at ripe.net (Brian Riddle) Date: Wed, 20 Dec 2006 10:39:58 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es Message-ID: <458904EE.2020902@ripe.net> [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 at 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 From ncc at ripe.net Wed Dec 20 10:57:48 2006 From: ncc at ripe.net (Axel Pawlik) Date: Wed, 20 Dec 2006 10:57:48 +0100 Subject: [ncc-services-wg] RIPE NCC Activity Plan and Budget 2007 Message-ID: <4589091C.1090301@ripe.net> Dear Colleagues, The RIPE NCC Executive Board has approved the RIPE NCC Activity Plan and Budget 2007. These documents have been published and are available from the RIPE Document Store. RIPE NCC Activity Plan 2007 http://www.ripe.net/ripe/docs/ap2007.html RIPE NCC Budget 2007 http://www.ripe.net/ripe/docs/budget2007.html Regards, Axel Pawlik Managing Director RIPE NCC From gert at space.net Wed Dec 20 10:46:18 2006 From: gert at space.net (Gert Doering) Date: Wed, 20 Dec 2006 10:46:18 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es In-Reply-To: <458904EE.2020902@ripe.net> References: <458904EE.2020902@ripe.net> Message-ID: <20061220094618.GJ66903@Space.Net> Hi, On Wed, Dec 20, 2006 at 10:39:58AM +0100, Brian Riddle wrote: > 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. Cool :) Did you experience any specific problems in your preparational tests, like "if mail comes from XYZ-MTA version 7.12, and the receipient MX announces TLS, it *will* fail, all the time"? Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 98999 SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234 From brian at ripe.net Wed Dec 20 11:42:07 2006 From: brian at ripe.net (Brian Riddle) Date: Wed, 20 Dec 2006 11:42:07 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es In-Reply-To: <20061220094618.GJ66903@Space.Net> References: <458904EE.2020902@ripe.net> <20061220094618.GJ66903@Space.Net> Message-ID: <4589137F.8070602@ripe.net> Hi Gert, We did see a problem with "Communigate Pro" open SSL/TLS compatibility, simple fix upgrade to latest version/patch. Otherwise no problems. Regards, Brian. Gert Doering wrote: > Hi, > > On Wed, Dec 20, 2006 at 10:39:58AM +0100, Brian Riddle wrote: >> 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. > > Cool :) > > Did you experience any specific problems in your preparational tests, like > "if mail comes from XYZ-MTA version 7.12, and the receipient MX announces > TLS, it *will* fail, all the time"? > > Gert Doering > -- NetMaster -- Brian Riddle RIPE Network Coordination Center IT Manager Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 From gert at space.net Wed Dec 20 11:46:45 2006 From: gert at space.net (Gert Doering) Date: Wed, 20 Dec 2006 11:46:45 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es In-Reply-To: <4589137F.8070602@ripe.net> References: <458904EE.2020902@ripe.net> <20061220094618.GJ66903@Space.Net> <4589137F.8070602@ripe.net> Message-ID: <20061220104645.GL66903@Space.Net> Hi, On Wed, Dec 20, 2006 at 11:42:07AM +0100, Brian Riddle wrote: > We did see a problem with "Communigate Pro" open SSL/TLS compatibility, > simple fix upgrade to latest version/patch. Otherwise no problems. That's very good news. Thanks! Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 98999 SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 D- 80807 Muenchen Fax : +49-89-32356-234 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 305 bytes Desc: not available URL: From pim at bit.nl Wed Dec 20 13:26:17 2006 From: pim at bit.nl (Pim van Pelt) Date: Wed, 20 Dec 2006 13:26:17 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es In-Reply-To: <458904EE.2020902@ripe.net> References: <458904EE.2020902@ripe.net> Message-ID: <20061220122617.GF5228@bfib.ipng.nl> Hi, | 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. This is a nice step forward. Thanks. -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim at ipng.nl http://www.ipng.nl/ IPv6 Deployment ----------------------------------------------- From denis at ripe.net Wed Dec 20 17:32:02 2006 From: denis at ripe.net (Denis Walker) Date: Wed, 20 Dec 2006 17:32:02 +0100 Subject: [ncc-services-wg] New RIPE Database software Message-ID: <45896582.9000502@ripe.net> [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 . 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. From ripe at dial.pipex.com Wed Dec 20 14:16:52 2006 From: ripe at dial.pipex.com (tp) Date: Wed, 20 Dec 2006 14:16:52 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es References: <458904EE.2020902@ripe.net> Message-ID: <03e601c72459$0f4ad440$0601a8c0@pc6> Have you documented any more about the technicalities, such as which version.release(s) you support, level negotiation, what ciphersuites .... Tom Petch ----- Original Message ----- From: "Brian Riddle" To: ; Sent: Wednesday, December 20, 2006 10:39 AM Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es > [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 at 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 > From ncc at ripe.net Wed Dec 20 10:57:48 2006 From: ncc at ripe.net (Axel Pawlik) Date: Wed, 20 Dec 2006 10:57:48 +0100 Subject: [ncc-services-wg] [ncc-announce] RIPE NCC Activity Plan and Budget 2007 Message-ID: <4589091C.1090301@ripe.net> Dear Colleagues, The RIPE NCC Executive Board has approved the RIPE NCC Activity Plan and Budget 2007. These documents have been published and are available from the RIPE Document Store. RIPE NCC Activity Plan 2007 http://www.ripe.net/ripe/docs/ap2007.html RIPE NCC Budget 2007 http://www.ripe.net/ripe/docs/budget2007.html Regards, Axel Pawlik Managing Director RIPE NCC From ncc at ripe.net Wed Dec 20 10:57:48 2006 From: ncc at ripe.net (Axel Pawlik) Date: Wed, 20 Dec 2006 10:57:48 +0100 Subject: [ncc-services-wg] [ncc-announce] RIPE NCC Activity Plan and Budget 2007 Message-ID: <4589091C.1090301@ripe.net> Dear Colleagues, The RIPE NCC Executive Board has approved the RIPE NCC Activity Plan and Budget 2007. These documents have been published and are available from the RIPE Document Store. RIPE NCC Activity Plan 2007 http://www.ripe.net/ripe/docs/ap2007.html RIPE NCC Budget 2007 http://www.ripe.net/ripe/docs/budget2007.html Regards, Axel Pawlik Managing Director RIPE NCC From brian at ripe.net Fri Dec 22 09:43:08 2006 From: brian at ripe.net (Brian Riddle) Date: Fri, 22 Dec 2006 09:43:08 +0100 Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es In-Reply-To: <03e601c72459$0f4ad440$0601a8c0@pc6> References: <458904EE.2020902@ripe.net> <03e601c72459$0f4ad440$0601a8c0@pc6> Message-ID: <458B9A9C.10401@ripe.net> Hi Tom, We will support TLS-level negotiation as described in RFC3207. In our case any MTA with TLS support based on OpenSSL 0.9.6 - 0.9.8 should work without any problem. Regards, Brian. tp wrote: > Have you documented any more about the technicalities, such as which > version.release(s) you support, level negotiation, what ciphersuites .... > > Tom Petch > > > ----- Original Message ----- > From: "Brian Riddle" > To: ; > Sent: Wednesday, December 20, 2006 10:39 AM > Subject: [ncc-services-wg] Implementing TLS/SSL on RIPE NCC external MX'es > > >> [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 at 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 >> > -- Brian Riddle RIPE Network Coordination Center IT Manager Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 From ncc at ripe.net Wed Dec 27 12:35:28 2006 From: ncc at ripe.net (Dominic Spratley - Registration Services Manager) Date: Wed, 27 Dec 2006 12:35:28 +0100 Subject: [ncc-services-wg] New PGP key Message-ID: <45925A80.3020306@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, We are approaching the new year and so we will start to use a new PGP key for signing e-mail sent from our ticketing system. On Tuesday 2nd January 2007 we will start using our 2007 key to sign e-mail. 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 28th February 2007. If you have any questions, please contact . Kind Regards, Dominic Spratley Registration Services Manager RIPE NCC From ncc at ripe.net Wed Dec 27 12:35:28 2006 From: ncc at ripe.net (Dominic Spratley - Registration Services Manager) Date: Wed, 27 Dec 2006 12:35:28 +0100 Subject: [ncc-services-wg] [ncc-announce] New PGP key Message-ID: <45925A80.3020306@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, We are approaching the new year and so we will start to use a new PGP key for signing e-mail sent from our ticketing system. On Tuesday 2nd January 2007 we will start using our 2007 key to sign e-mail. 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 28th February 2007. If you have any questions, please contact . Kind Regards, Dominic Spratley Registration Services Manager RIPE NCC