<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-ppr-dd-auth-delegation-types-00" submissionType="IETF" category="std" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="true">

<front>
<title abbrev="auth-delegation-types">DNS Protocol Modifications for Authoritative Delegation Point DNS Records</title><seriesInfo value="draft-ppr-dd-auth-delegation-types-00" stream="IETF" status="standard" name="Internet-Draft"></seriesInfo>
<author initials="P." surname="van Dijk" fullname="Peter van Dijk"><organization>PowerDNS</organization><address><postal><street></street>
<city>Den Haag</city>
<country>Netherlands</country>
</postal><email>peter.van.dijk@powerdns.com</email>
</address></author><author initials="P." surname="Spacek" fullname="Petr Spacek"><organization>ISC</organization><address><postal><street></street>
<city>Brno</city>
<country>Czech Republic</country>
</postal><email>pspacek@isc.org</email>
</address></author><author initials="R." surname="Arends" fullname="Roy Arends"><organization>ICANN</organization><address><postal><street></street>
<city>St Peter Port</city>
<country>Guernsey</country>
</postal><email>roy.arends@icann.org</email>
</address></author><date/>
<area>General</area>
<workgroup>deleg</workgroup>
<keyword>Internet-Draft</keyword>

<abstract>
<t>This document proposes modifications to the Domain Name System (DNS) protocol to support a range of authoritative resource record types at delegation points. Currently, the DNS only allows DS (Delegation Signer) records at a delegation point as authoritative data. This draft extends that model by enabling the inclusion of a range of RRtypes at delegation points. The proposed modifications preserve compatibility with existing DNS resolution behavior while providing a clear framework for identifying and processing these records as authoritative data at delegation points.</t>
</abstract>

</front>

<middle>

<section anchor="introduction"><name>Introduction</name>
<t><xref target="RFC4035"></xref> defines the DS (Delegation Signer) resource record as having a unique property: it resides solely at a delegation as authoritative data. Discussions and drafts within the DPRIVE, DNSOP, and DELEG working groups have highlighted interest in allowing additional types of data to be published at  delegation points. Some proposals have introduced new RRtypes with the assumption that authoritative servers and registry systems would eventually support them. Others have attempted to repurpose the DS record format for unrelated data. Had a range of RRtypes been designated early on to behave similarly to DS, these proposals and their associated  protocols could have been more easily developed and evaluated. This document proposes reserving such a range of RRtype codes and defines the expected behavior of DNS implementations that support them.</t>
<t>This document requests that IANA reserve such a range and defines behavior of DNS implementations.</t>
</section>

<section anchor="term"><name>Conventions and Definitions</name>
<t>The term &quot;Authoritative Delegation Types&quot; refers to set of RR types which contains exactly:</t>

<ul spacing="compact">
<li>Value 43 as defined for DS type by <xref target="RFC4034" sectionFormat="of" section="5"></xref>,</li>
<li>The range reserved by this document in <xref target="iana"></xref>.</li>
</ul>
<t>The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"></xref> <xref target="RFC8174"></xref> when, and only when, they appear in all capitals, as shown here.</t>
</section>

<section anchor="relationship-with-the-deleg-draft"><name>Relationship with the DELEG draft</name>
<t>The DELEG draft specifies one new resource record type (DELEG) that is authoritative at a delegation point and proposes protocol modifications to support DELEG.</t>
<t>The sole purpose of this document is to make sure that the protocol modifications are generic for a range of types instead of just DELEG.</t>
<t>If the WG decides to seperate the DELEG type specification from the Protocol Modifications needed to support authoritative delegation types, we can incorporate all the necessary parts in this document.</t>
</section>

<section anchor="security-considerations"><name>Security Considerations</name>
<t>To be added.</t>
</section>

<section anchor="iana"><name>IANA Considerations</name>
<t>IANA is requested to change reservations in the DNS Parameters RR TYPEs registry, with this document as the Reference.</t>

<ul spacing="compact">
<li>Range 0xFA00-0xFDFF to Registration Procedure &quot;Expert Review or Standards Action&quot;</li>
<li>Range 0xFE00-0xFEFF to Registration Procedure &quot;Private Use&quot;</li>
</ul>
</section>

<section anchor="acknowledgements"><name>Acknowledgements</name>
<t>This idea was initially proposed by Petr Spacek.</t>
</section>

</middle>

<back>
<references><name>References</name>
<references><name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4035.xml"/>
</references>
<references><name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4034.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
</references>
</references>

</back>

</rfc>
