Hi,
(Wes and Warren— cc’d as IAB and IESG members, do you guys have any further
guidance?)
> On Sep 9, 2021, at 12:12 PM, Joe Abley <jab...@hopcount.ca> wrote
>
> The IETF (well, the IAB) has administrative control over the contents of the
> ARPA zone. I do not know in practice whether this extends to the machinery of
> how the zone is provisioned.
>
> The operation of the zone is carried out by PTI, I think. It is distributed
> to its authoritative servers (which are also root servers) in a process that
> is similar in some respects to the way the root zone is managed.
>
> I would drop a note to Kim Davies and ask his advice if you want to make some
> kind of progress. While it seems perfectly plausible to make this kind of
> change by way of a published RFC with IAB review, it's not at all clear to me
> that such a heavyweight approach is necessary.
It might also be helpful to review RFC 3172 ("Management Guidelines &
Operational Requirements for the Address and Routing Parameter Area Domain
("arpa”)”).
It doesn’t directly address “the machinery of how the zone is provisioned” but
it does make some guidelines clear.
Personally, I’d start with the IAB or IESG, if only to find out how much
process was required to get it signed in the first place (I don’t recall, and
can’t immediately find a reference). Maintaining compliance with the evolving
spec for DNSSEC and crypto algorithms should not be too difficult, but will
probably have to be documented somewhere and approved by the IAB.
Suzanne
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
