Re: [enum-wg] 9.3.e164.arpa down
-
To: Jim Reid jim@localhost, Klaus Darilion <klaus.mailinglists@localhost
-
From: John C Klensin john+ietf@localhost
-
Date: Wed, 15 Nov 2006 20:48:26 -0500
--On Wednesday, 15 November, 2006 09:05 +0000 Jim Reid
jim@localhost wrote:
> On Nov 15, 2006, at 08:47, Klaus Darilion wrote:
>
>> The Italian ENUM name servers are down/broken. This will
>> cause lots of trouble (long call setups) for ITSPs which
>> perform ENUM lookups.
>>
>> How should we handle such situations? By RIPE (deleting the
>> delegation), by monitoring registries and skipping ENUM
>> lookup for certain countries?
>
> Klaus, this was discussed at the last RIPE meeting. What a
> countrydoes with its ENUM name servers is a National Matter.
> This is notsomething that RIPE NCC should interfere with and
> it must NEVER pullan ENUM delegation unilaterally. A
> delegation under e164.arpa shouldonly get deleted by the NCC
> -- not RIPE! -- if instructed to do so bythe ITU or the
> appropriate Administration. Read the IAB instructionsand ITU
> MoU to the NCC for details of the scope of NCC's
> ENUMresponsibilities.
>
> What we -- for some definition of "we" -- should do in this
> situationis inform the Administration concerned and politely
> ask them to fixthe problem. IMO this definition of "we" means
> you and the ITSPs whoare having trouble. It doesn't mean RIPE
> NCC unless the relevantAdministration has asked the NCC to
> monitor their ENUM delegation.
>
>> AFAIR this is not the first problem with 9.3.e164.arpa
>
> If that's the case, perhaps ITSPs should reconfigure their
> softwareuntil the DNS infrastructure for this domain is
> reliable enough.
of course, the other comment that could have been made here is
that there is a reason for the long-standing rule that specifies
that any domain have multiple servers (at least two) that do not
fate-share. In other words, there are suppose to be servers
that are sufficiently separated physically and in terms of
network connectivity that the odds of all of them being
unavailable at once are low to none.
To the extent to which properly-separated and adequately
independent servers would have solved or prevented this problem,
the affected parties should, as Jim suggests, inform the
Administration concerned and offer some appropriate advice.
john
|