- ncc-services-wg - mailman.ripe.net

Mailing List
by Maurice Coates 07 Feb '07

07 Feb '07

-- Regards Maurice Coates Customer Expressions Corporation Business Development Europe Lippmannweg 14 D-64405 Fischbachtal Lichtenberg, Germany Tel: 0049 6166 932143 Tel: 0049 171 532 4677 mcoates(a)customerexpressions.com Our mission is to provide the tools and counsel needed to enable organizations to optimize business processes related to: i-Sight Customer Service and Complaint Management i-Sight Corrective Actions and Quality Management i-Sight Call Handling and Help Desk Management i-Sight Case Management http://www.customerexpressions.com

1 0

Tonight's RIPE NCC Maintenance Rescheduled for 13 February
by Mark Guz 06 Feb '07

06 Feb '07

[Apologies for duplicate e-mails] Dear Colleagues, We have cancelled plans to carry out maintenance work on our core network infrastructure this evening. This means that RIPE NCC services will be available as usual. We will carry out this maintenance work on Tuesday, 13 February between 21:00 and 23:00 (UTC). During this time, many of our services will be unavailable. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net>. Regards, Mark Guz Senior Engineer RIPE NCC Singel 258 Amsterdam 1016 AB Tel: +31 (0) 20 535 4444 Fax: +31 (0) 20 535 4445

1 0

RIPE NCC Announces New Membership Discussion List
by Paul Rendek 30 Jan '07

30 Jan '07

[Apologies for duplicate e-mails] Dear Colleagues, In response to requests from the membership, the RIPE NCC has created a members-only opt-in list where RIPE NCC members can discuss membership related issues. The new RIPE NCC Membership Discussion List (members-discuss(a)ripe.net) provides a useful, publicly archived way for members to discuss important membership issues. The RIPE NCC Membership Discussion List is one of several mailing lists for RIPE NCC members. For more information about these lists, including a description of the topics they cover and subscription details, go to: http://www.ripe.net/membership/lists.html RIPE NCC members can subscribe to this list through the RIPE NCC LIR Portal. Please note that an LIR login will be required. More information about setting up an LIR Portal account is available at: https://lirportal.ripe.net/lirportal/getting_started.html Regards, Paul Rendek Head of Communications RIPE NCC

1 0

(no subject)
by Mark Guz 30 Jan '07

30 Jan '07

[Apologies for duplicate e-mails] Dear Colleagues, On Tuesday 6 February, between 21:00 and 23:00 (UTC), the RIPE NCC will carry out planned maintenance work on our core network infrastructure. RIPE NCC services will be temporarily unavailable during this period. We apologise for any inconvenience that this may cause. This work is due to BGP load balancing issues between our NikHef and Telecity peering points. If you have any questions about this, please send an e-mail to: <ops(a)ripe.net>. Regards -- Mark Guz Senior Engineer RIPE NCC Singel 258 Amsterdam 1016 AB Tel: +31 (0) 20 535 4444 Fax: +31 (0) 20 535 4445 http://www.ripe.net

1 0

RIPE NCC Planned Maintenance, February 2007
by RIPE NCC 29 Jan '07

29 Jan '07

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC will perform planned maintenance work that will affect a number of servers. The maintenance work will take place on: Thursday, 1 February 2007 between 21:00 and 23:00 UTC Wednesday, 7 February 2007 between 21:00 and 23:00 UTC During this maintenance, individual servers may experience short outages. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to: ops(a)ripe.net

1 0

LIR Portal Outage: 23 January 2007
by Mark Guz 23 Jan '07

23 Jan '07

[Apologies for duplicate e-mails] Dear Colleagues, On Tuesday, 23 January, between 21:00 and 22:00 (UTC), the RIPE NCC will carry out urgent maintenance work that will cause outages to the RIPE NCC LIR Portal. We recommend that you avoid using the RIPE NCC LIR Portal until this maintenance work has been completed. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to: <ops(a)ripe.net>. Regards -- Mark Guz Senior Engineer RIPE NCC Singel 258 Amsterdam 1016 AB Tel: +31 (0) 20 535 4444 Fax: +31 (0) 20 535 4445 http://www.ripe.net

1 0

ASN32 deployment
by Denis Walker 03 Jan '07

03 Jan '07

[Apologies for duplicate e-mails] Dear colleagues, This morning, between 07:00 and 09:00 (UTC), we deployed new software for the RIPE Database. Three changes were made: 1. The new software allows 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. The ORGANISATION object type NON-REGISTRY has been changed to OTHER. The RIPE NCC modified all existing organisation objects which had the old type. There is more information about this at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00245.html 3. We reversed changes made to the status of 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 have been 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 Our test database (e-mail to <test-dbm(a)ripe.net> or access through webupdates) also now handles the new AS number format.

2 1

New PGP key
by Dominic Spratley - Registration Services Manager 27 Dec '06

27 Dec '06

[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 <lir-help(a)ripe.net>. Kind Regards, Dominic Spratley Registration Services Manager RIPE NCC

1 0

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

22 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

4 6

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