[enum-wg] DNSMON for enum zones

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 at nic.cz  http://nic.cz/
 sip:ondrej.sury at nic.cz tel:+420.222745110
 mob:+420.739013699     fax:+420.222745112
 -----------------------------------------