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

Verio renamed NTTCOM in RIPE Database
by Katie Petrusha 30 May '07

30 May '07

Dear Colleagues, On 31 March 2007, the Verio routing registry database was renamed NTTCOM. This change of name has been incorporated in the RIPE Database server which mirrors a number of public databases including the NTTCOM routing registry. More information about the NTTCOM routing registry is available at: http://www.us.ntt.net/about/policy/rr.cfm The list of databases mirrored by the RIPE Database server is available at: http://www.ripe.net/db/mirrored.html -- Katie Petrusha RIPE Database administration RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was performed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT - COMPLETED
by Mark Guz 24 May '07

24 May '07

Dear Colleagues, The above mentioned maintenance was preformed successfully and within the specified maintenance window. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

RIPE NCC Network Maintenance Wednesday 23 May 1700 - 1900 UTC/GMT
by Mark Guz 21 May '07

21 May '07

Dear Colleagues, Between 17:00 and 19:00 (UTC) on Wednesday, 23 May 2007, the RIPE NCC will carry out planned maintenance work on our core network infrastructure. During this period all RIPE NCC services will suffer intermittent interruptions We apologise for any inconvenience that this may cause. If you have any questions about this, please e-mail ops(a)ripe.net Regards Mark Guz Senior Engineer Operations Dept RIPE NCC

1 0

Re: [enum-wg] DNSMON for enum zones
by Ondřej Surý 11 May '07

11 May '07

Ccing to ncc-services-wg. Short summary: Discussion started on enum-wg whether DNSMON service should be extended to ENUM registry operators as well. Patrik summarized discussion so far in several points in mail I am replying at. You can find start of the thread at: http://www.ripe.net/ripe/maillists/archives/enum-wg/2007/msg00024.html Patrik Fältström píše v Čt 10. 05. 2007 v 15:08 +0300: > I see a number of different questions being discussed here, and I > think we should try to separate them: > > 1. RIPE NCC is running DNS for e164.arpa > 2. RIPE NCC should "protect their skin" and monitor the e164.arpa > zone, so they can show their service is up to current standards Shouldn't RIPE NCC do the same for all its delegations. I would broaden scope of this point to monitoring reverse delegations as well. > 3. Registry operators run DNS for zones delegated from e164.arpa, and > the delegation itself should be of some quality for ENUM to work -- > who has responsible for this? I think that responsibility lies in registry operators hands, but NCC should do monitoring and step-in if quality is too low. I don't have idea right now what "step-in" and "quality is too low" definition is. > 4. Registry operators have interest in being monitored, should they > be monitored, or (via opt-in) on request? You probably already know my opinion on that point :-), but together with previous points it gets more complicated. If answer to 2 and 3 is YES, then I think that they should be monitored and on opt-in request they could receive results/warnings/etc. Without opt-in it would be only from RIPE NCC internal needs. > 5. If there is a need for monitoring of DNS operation, is RIPE-NCC to > do that monitoring (they already do in the case of dnsmon)? Let's put another POV in play. If DNSMON was outsourced to let's say commercial service, who will ensure quality of such monitoring? I don't think that niche in this market is so big, that it will self-regulate, because of competition. Then there would be need to _monitor_ monitoring to ensure 2 and 3. Ondrej -- Ondřej Surý technický ředitel/Chief Technical Officer ----------------------------------------- CZ.NIC, z.s.p.o. -- .cz domain registry Americká 23,120 00 Praha 2,Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ sip:ondrej.sury@nic.cz tel:+420.222745110 mob:+420.739013699 fax:+420.222745112 -----------------------------------------

1 0

New E-Learning Module: Using PGP and X509 to Protect MNTNER Objects
by Rumy Kanis 03 May '07

03 May '07

Dear Colleagues, We are pleased to announce the launch of the latest module on the RIPE NCC E-Learning Centre: - Using PGP Keys and X509 Certificates in MNTNER objects This module explains the steps required to use a PGP Key and/or X509 Certificate to protect objects in the RIPE Database. The module provides step-by-step guidelines for: - Creating a KEY-CERT object - Adding the KEY-CERT object to an existing MNTNER object as a method of authentication - Updating an object protected by that MNTNER using the PGP key or X509 certificate The RIPE NCC E-Learning Centre is a free of charge service available to everyone, and can be found at https://e-learning.ripe.net. If you have any questions, please feel free to contact us at: e-learning(a)ripe.net Happy Learning, Rumy Kanis Training Services Manager

1 0