<?xml version="1.0" encoding="utf-8"?>
<?xml-model href="rfc7991bis.rnc"?>
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="info"
  docName="draft-bortzmeyer-resinfo-dnssecval-00"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="IETF"
  xml:lang="en"
  version="3">

  <front>
    <title abbrev="Resinfo DNSSEC">DNS Resolver Information Key for DNSSEC validation</title>

    <seriesInfo name="Internet-Draft" value="draft-bortzmeyer-resinfo-dnssecval-00"/>
   
    <author fullname="Stéphane Bortzmeyer" initials="S." surname="Bortzmeyer">
      
      <organization>Afnic</organization>
      <address>
        <postal>
          <street>7 avenue du 8 mai 1945</street>
          <city>Guyancourt</city>
          <code>78280</code>
          <country>FR</country>
          <!-- Uses two letter country code -->
        </postal>        
        <email>bortzmeyer+ietf@nic.fr</email>  
        <uri>https://www.afnic.fr/</uri>
      </address>
    </author>
   
    <date year="2024"/>

    <area>General</area>
    <workgroup>Internet Engineering Task Force</workgroup>

    <keyword>DNS DNSSEC RESINFO</keyword>

    <abstract>
      <t>This document is the specification of a DNS Resolver
      Information Key <xref target="RFC9606"/> for DNSSEC validation, "dnssecval".</t>
    </abstract>
 
  </front>

  <middle>
    
    <section>
      <name>Introduction</name>
      <t>RFC 9606 created a DNS record type RESINFO to
      allow resolvers to publish information about their capabilities
      and policies. This information is encoded as {key, value}
      pairs. Keys are in an IANA registry and this specification adds
      a new key, to indicate that the resolver validates with DNSSEC <xref target="RFC4033"/><xref target="RFC4034"/><xref target="RFC4035"/>.</t>
      
      <section>
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
          "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
          RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
          interpreted as described in BCP 14 <xref target="RFC2119"/>
          <xref target="RFC8174"/> when, and only when, they appear in
          all capitals, as shown here.</t>
      </section>

    </section>
    
    <section>
      <name>The key</name>
      <t>The name of the key is "dnssecval", for "DNSSEC validating
      [resolver]". The presence of this key indicates that the DNS resolver
   validates all answers with DNSSEC <xref target="RFC4033"/> <xref
   target="RFC4034"/> <xref target="RFC4035"/>. Note
   that, per the rules for the keys defined in Section 6.4 of <xref target="RFC6763"/>
   if there is no '=' in a key, then it is a boolean attribute, simply
   identified as being present, with no value.</t>
     <t>The resolver which announces this capability in a RESINFO
     record MAY add DNSSEC-specific EDE (Extended DNS Error Codes,
     <xref target="RFC8914"/>) to the value of the "exterr" key.</t>
    </section>
    
    <section anchor="IANA">
      <name>IANA Considerations</name>
      <t>IANA is requested to add "dnssecval" and a reference to this
      document to the registry "DNS Resolver Information Keys".</t>
    </section>
    
    <section anchor="Security">
      <name>Security Considerations</name>
      <t>DNSSEC is a very important tool for the security of the DNS
      and therefore it is important for users to know in advance if
      the resolver they consider supports DNSSEC or not. It would be
      better to assume that every resolver validates (thus rendering
      this document useless) but it is not the case today.</t>
      <t>As with any information published in the DNS, the key in the
      RESINFO may be wrong or outdated. They should be regarded with care.</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.6763.xml"/>
        <xi:include
            href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9606.xml"/>
        
      </references>
 
      <references>
        <name>Informative References</name>
        <xi:include
            href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4033.xml"/>
        <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.4035.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8914.xml"/>
      </references>
    </references>
    
    <section anchor="Acknowledgements" numbered="false">
      <name>Acknowledgements</name>
      <t>My cat did nothing to help.</t>
    </section>
    
 </back>
</rfc>
