[as112-ops] [Ext] Re: Request to add service.arpa to AS112

[Kim Davies]

Hi Joe,

I wasn't a party to the discussions to lead to this specific construction that it be done in the same manner as home.arpa, so I am not sure what factors went into it.

With that said, while we haven't had discussions recently, my understanding is there is a reluctance to add new RR types or modes of behaviour to the root servers without specific research, testing and outreach first. Because the .ARPA zone is served directly by the root servers it is subject to this conservative approach used for the root zone. The long term plan to address this is to separate .ARPA infrastructure from the root zone per RFC 9120, but there is no timeline to complete that work. 

Where we find ourselves is we need to delegate service.arpa relatively expediently given the associated RFC is ready to be published, and therefore we don't think it can wait to be predicated on either (a) doing the necessary exploration for adding it to root infrastructure; or (b) migrating .ARPA infrastructure off the root severs first.  I think should either of those subsequently happen we could reprovision the delegation to a DNAME down the road.

kim

On 4/29/24, 07:40, "jabley at strandkip.nl <mailto:jabley at strandkip.nl>" <jabley at strandkip.nl <mailto:jabley at strandkip.nl>> wrote:


Hi Kim,


Part of the motivation for RFC 7535 was to avoid the need for reconfiguration of AS112 servers for sinking DNS traffic to new parts of the namespace, recognising that this is almost guaranteed to cause lame delegations.


Do we know why the requirements for SERVICE.ARPA is not being implemented using DNAME? Is it too late to ask, or perhaps to suggest that DNAME is the preferred way to do this?




Joe


> On Apr 29, 2024, at 16:25, Kim Davies <kim.davies at iana.org <mailto:kim.davies at iana.org>> wrote:
> 
> Dear AS112 operators:
> 
> IANA is being being asked to implement the IANA considerations of a
> new RFC-to-be, draft-ietf-dnssd-srp-25, which requires delegation of
> "service.arpa" to black hole servers as follows:
> 
> In order to be fully functional, the owner of the 'arpa.' zone must
> add a delegation of 'service.arpa.' in the '.arpa.' zone [RFC3172].
> This delegation is to be set up as was done for 'home.arpa', as a
> result of the specification in Section 7 of [RFC8375]. This is
> currently the responsibility of the IAB [IAB-ARPA]
> 
> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-srp-25 <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-srp-25>*delegation__;Iw!!PtGJab4!7R6yIbZW1rYpC8Z3nClCZ1CQVIOqaA5Q7wVmbTNDXglFMYXPytvM1XIOmrP94Dp3JkeBmROz6F3n6jrXSR84FqaPtg$ [datatracker[.]ietf[.]org]>
> 
> Therefore, just as with home.arpa we are requesting AS112 operators to
> configure their AS112 nodes as soon as practical to answer queries for
> this new zone on blackhole-[12].iana.org, so that we may delegate it in
> the .arpa zone with those two NS records. The zone should be configured
> with the "db.dd-empty" zone content described in RFC 7534.
> 
> I suspect one of the questions will be whether we can use DNAME as
> described in RFC 7535. While we have made some progress in separating
> root server infrastructure from .ARPA infrastructure (see RFC 9120),
> that work has not concluded and today they are still served through
> common infrastructure.
> 
> Our intention is to add the delegation to the .ARPA zone around mid-May,
> to provide AS112 operators time to make this configuration update.
> 
> Thank you in advance, and if you have any questions please let me know,
> or respond back to this group.
> 
> Kindest regards,
> 
> Kim Davies
> Internet Assigned Numbers Authority
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net <mailto:as112-ops at lists.dns-oarc.net>
> https://urldefense.com/v3/__https://lists.dns-oarc.net/mailman/listinfo/as112-ops__;!!PtGJab4!7R6yIbZW1rYpC8Z3nClCZ1CQVIOqaA5Q7wVmbTNDXglFMYXPytvM1XIOmrP94Dp3JkeBmROz6F3n6jrXSR-wCQThlg$ <https://urldefense.com/v3/__https://lists.dns-oarc.net/mailman/listinfo/as112-ops__;!!PtGJab4!7R6yIbZW1rYpC8Z3nClCZ1CQVIOqaA5Q7wVmbTNDXglFMYXPytvM1XIOmrP94Dp3JkeBmROz6F3n6jrXSR-wCQThlg$> [lists[.]dns-oarc[.]net]
> as112.net administrative requests
> ops at as112.net <mailto:ops at as112.net>