<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.huque-dnsop-multi-alg-rules" target="https://datatracker.ietf.org/doc/html/draft-huque-dnsop-multi-alg-rules-06">
   <front>
      <title>Multiple Algorithm Rules in DNSSEC</title>
      <author initials="S." surname="Huque" fullname="Shumon Huque">
         <organization>Salesforce</organization>
      </author>
      <author initials="P." surname="Thomassen" fullname="Peter Thomassen">
         <organization>deSEC, SSE</organization>
      </author>
      <author initials="V." surname="Dukhovni" fullname="Viktor Dukhovni">
         <organization>Google LLC</organization>
      </author>
      <author initials="D." surname="Wessels" fullname="Duane Wessels">
         <organization>Verisign</organization>
      </author>
      <author initials="C." surname="Elmerot" fullname="Christian Elmerot">
         <organization>Cloudflare</organization>
      </author>
      <date month="July" day="7" year="2025" />
      <abstract>
	 <t>   This document restates the requirements on DNSSEC signing and
   validation and makes small adjustments in order to allow for more
   flexible handling of configurations that advertise multiple Secure
   Entry Points (SEP) with different signing algorithms via their DS
   record or trust anchor set.  The adjusted rules allow both for multi-
   signer operation and for the transfer of signed DNS zones between
   providers, where the providers support disjoint DNSSEC algorithm
   sets.  In addition, the proposal enables pre-publication of a trust
   anchor in preparation for an algorithm rollover, such as of the root
   zone.

   This document updates RFCs 4035, 6840, and 8624.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-huque-dnsop-multi-alg-rules-06" />
   
</reference>
