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

Joe Abley jabley at hopcount.ca
Thu Dec 7 17:55:40 UTC 2017


Hi Kim,

On 7 Dec 2017, at 12:49, Kim Davies <kim.davies at iana.org> wrote:

> 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.

Sure. I'm really just curious as to what you think the risk profile is. When you say careful and deliberate, who are the relying parties? Root server operators, IANA in the generation of the ARPA zone, resolver operators, homenet users, others?

I suspect the only unknown here is "homenet users" and since there's no installed base of expectations with regard to home.arpa names that's a no-op. That's really what I'm getting at.

If you ever wanted a benign test case to deploy a DNAME in a zone served by a root server, this is surely it.

> 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?

Right, and the pragmatic response to that is that I don't think you have a good way of measuring what problems emerge. Which brings us full circle to the reason we wrote 7535 in the first place, hence my (hopefully gentle, certainly well-intentioned :-) questions about why it isn't being used.


Joe




More information about the as112-ops mailing list