[DNSOP] Re: I-D Action: draft-ietf-dnsop-delext-08.txt

Petr Špaček <[email protected]> Thu, 9 Jul 2026 15:26:27 +0200
Newsgroups gmane.ietf.dnsop
Message-ID <[email protected]>
On 09. 07. 26 15:06, [email protected] wrote:
> Hi Petr,
> 
>> The current draft does not have OLD/NEW blocks of text, but it in
>> fact does update behavior described by 1034/1035, 2136,
>> 4033/4034/4035, 5155, 6672, and 6840 at very least.
> 
> I wasn't looking necessarily for changes using OLD/NEW, but a clear statement of how to interpret each of the (candidate) updates you had in mind.
> 
> I'm puzzled by the list you provided as the doc does not even have 4035, 5155, 6672, 6840 as normative references. 1034/1035 are not listed as well, but I'm not putting these under the same category as the other because these can be "safely assumed to be known to practitioners" [1].
 > > Cheers,
> Med
> 
> [1] https://datatracker.ietf.org/doc/statement-iesg-iesg-statement-normative-and-informative-references-20060419/

You are right, it is a terrible mess I'm jointly responsible for!

If I understand correctly, we should add much better references to the 
document?


For me as a implementer it is kind of no-brainer that new delegation 
mechanism and new signing rules imply changes to previous specs, but I 
can see it it can be confusing.

Please advise.




Bit of history for the benefit of WG and other readers:

1. This document should not to exist.
The whole thing would make sense more sense under deleg WG as part of 
DELEG draft, or a small separate draft, but deleg WG was not allowed to 
do that.

2. Then this document was intended to be be a single-paragraph 'range 
0xF000-0xF1FF has new purpose and reg procedure' piece done in dnsop 
with rest done in deleg.

3. Then people started to have the opinion that delext must also define 
all the protocol bits, not just the registry procedure.

Consequently, three years of work in DELEG WG were moved piece by piece 
from deleg to delext document. Suddenly delext is not a single paragraph 
of IANA Considerations but a full blown protocol document.

Originally, we as authors did not intend to have it this way. Our human 
minds are sometimes stuck with the old simple model, which is now 
inadequate.

Naturally, when moving pieces from deleg document we missed many things, 
'Updates' tag included - because originally it should not have happened 
at all! My mind is still catching up with the new reality.

Long story short, I, as one of the listed authors, apologize for the 
mess we created and ask for forgiveness.

-- 
Petr Špaček

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]