[as112-ops] [Ext] Request to add home.arpa to AS112 repertoire

Kim Davies kim.davies at iana.org
Thu Dec 7 17:49:49 UTC 2017


Hi Joe,

Quoting Joe Abley on Thursday December 07, 2017:
> 
> On 7 Dec 2017, at 12:13, Kim Davies <kim.davies at iana.org> wrote:
> 
> > The reason for this is the .arpa zone is served by the root servers,
> > and thus to perform DNAME processing and publication for the first time
> > on the root servers we believe would necessarily require exceptional
> > outreach and planning prior.
> 
> Just curious -- is the "we" there the IANA, or the IAB, or the root server operators?

I don't want to speak for others, but the IANA team would want to be
careful and deliberate on this front, and I think those concerns were
shared by others we spoke to when we were analyzing the options. We
also informally polled some of our partners involved in managing and
publishing the root zone to get a read on their readiness to support
this, that influenced our thinking.

> My sense is that DNAME is really not a speculative or dangerous RRType, and the minimal extra processing required on the server side to follow RFC 6672 has been well-supported in all implementations used in the root server system for at least half a decade. So I assume the difficulty here is one of process, not technology -- but if that's the case, RFC 3172 seems fairly clear who the process owner is, and the IAB ought to be able to make an informed call.

I don't think anyone is suggesting the IAB shouldn't be able to make
an informed call. For me, the pragmatic question is, are any problems
with what we asked AS112 operators to do yesterday sufficient to delay
delegation of home.arpa until such time as we navigate the waters
to find a way to use DNAME instead? (Noting that I assume we could
substitute in DNAME later once things are considered ready.)

kim


More information about the as112-ops mailing list