--On Thursday, 13 December, 2007 17:35 +0100 Stephane Bortzmeyer
<bortzmeyer@xxxxxx> wrote:
> On Thu, Dec 13, 2007 at 11:25:27AM -0500,
> John C Klensin <john-ietf@xxxxxxx> wrote
> a message of 40 lines which said:
>
>> IMO, it would be really helpful if relevant WGs or other
>> groups concerned with DNS operations and configurations would
>> take the question up again, review it, and make some sort of
>> definitive contemporary statement (even if that were only "it
>> depends" with an explanation of the tradeoffs).
>
> An important reason why we SHOULD have DNS reliability
> (including geographical variety) even if service X is down is
> because there are several services, not just the Web. OK, if
> the Web site is down, it is not *too* important (but it is
> important, for the reasons you mention) if I cannot resolve
> www.ietf.org but email, jabber, etc, continue to live and need
> the DNS.
This is consistent with my instincts (and has been for many
years), but Dave is not the first person to take the other
position.
> So, I believe that the future DNS service of the IETF,
> announced on ietf-announce is badly designed. As we say in
> french "The shoemaker always has the worst shoes".
Let's drop this. Russ has indicated that an arrangement for one
or more secondaries that don't fate-share is in the process of
being finalized and I've seen off-list correspondence from Ray
that indicates the same thing. I'm also aware of other
well-distributed parties who have volunteered if additional
distribution is needed (and so, presumably, is Ray by now). My
understanding is that there will be no period in which all of
the IETF's DNS servers fate-share. I hope, as others have
suggested, that the transition will be handled carefully and in
the right order of events, but I don't have any reason to
believe that it will not be (and assume that Ray and others will
ask for help from experts if they need it). That moves the
"future DNS service..." issue into "transitory learning pains of
the new secretariat" rather than a [dead] horse we need to kick
further.
john
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf