Draft-ietf-dnsop-delext-13 has just been submitted. Please review that instead:

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-delext/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-dnsop-delext-13.html 
<https://www.ietf.org/archive/id/draft-ietf-dnsop-delext-1.html>

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-delext-13

Warmly,

Roy

> On 29 Oct 2026, at 20:09, Ondřej Surý <[email protected]> wrote:
> 
> (We have a synchronized WGLC with DELEG working group, so this message to the 
> working group is sent in a bit unusual way, so we keep this linked together.)
> 
> This message starts a WG Last Call for:
> draft-ietf-dnsop-delext-12
> 
> This Working Group Last Call ends on 2026-11-12
> 
> This document should be reviewed in parallel with the corresponding DELEG 
> draft (https://datatracker.ietf.org/doc/draft-ietf-deleg/).
> 
> Abstract:
>  The Domain Name System (DNS) protocol permits Delegation Signer (DS)
>  records at delegation points.  This document specifies modifications
>  to the DNS protocol to permit a range of Resource Record types at
>  delegation points.  These modifications are designed to maintain
>  compatibility with existing DNS resolution mechanisms and provide a
>  secure method for processing these records at delegation points.
> 
>  This document updates RFCs 1034, 4035, 6672, 6840, 6895 and 9824.
> 
> File can be retrieved from:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-delext-12.txt
> 
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping [email protected]
> in copy. Objections should be explained and suggestions to resolve them are
> highly appreciated.
> 
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [1].
> Appropriate IPR disclosures required for full conformance with the provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can be
> found at [3].
> 
> Thank you.
> 
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-delext/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-delext-12.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-delext-12
> 
> --
> Ondřej Surý (He/Him)
> 
> A gentle nudge is always appreciated if I take a little longer to reply.
> 
>> On 29. 10. 2026, at 16:23, Brian Haberman via Datatracker <[email protected]> 
>> wrote:
>> This message starts a WG Last Call for:
>> draft-ietf-deleg-13
>> 
>> This Working Group Last Call ends on 2026-11-12
>> 
>> This document should be reviewed in parallel with the corresponding DNSOP 
>> draft (https://datatracker.ietf.org/doc/draft-ietf-dnsop-delext/).
>> 
>> Abstract:
>>  This document specifies a new extensible method for the delegation of
>>  authority for a domain in the Domain Name System (DNS) using DELEG
>>  and DELEGPARAM records.
>> 
>>  A delegation in the DNS enables efficient and distributed management
>>  of the DNS namespace.  The traditional DNS delegation is based on NS
>>  records which contain only hostnames of servers and no other
>>  parameters.  In classic DNS, both parent and child zones contain
>>  copies of NS delegation records, which can potentially be out of sync
>>  and confusing.  The new delegation records are extensible, can be
>>  secured with DNSSEC, and eliminate the problem of having two sources
>>  of truth for delegation information.
>> 
>> File can be retrieved from:
>> https://www.ietf.org/archive/id/draft-ietf-deleg-13.txt
>> 
>> Please review and indicate your support or objection to proceed with the
>> publication of this document by replying to this email keeping [email protected] 
>> in
>> copy. Objections should be explained and suggestions to resolve them are
>> highly appreciated.
>> 
>> Authors, and WG participants in general, are reminded of the Intellectual
>> Property Rights (IPR) disclosure obligations described in BCP 79 [1].
>> Appropriate IPR disclosures required for full conformance with the provisions
>> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
>> Sanctions available for application to violators of IETF IPR Policy can be
>> found at [3].
>> 
>> Thank you.
>> 
>> [1] https://datatracker.ietf.org/doc/bcp78/
>> [2] https://datatracker.ietf.org/doc/bcp79/
>> [3] https://datatracker.ietf.org/doc/rfc6701/
>> 
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-deleg/
>> 
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-ietf-deleg-13.html
>> 
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-deleg-13
>> _______________________________________________
>> dd mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
> 
> _______________________________________________
> DNSOP mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

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

Reply via email to