Domain-Connect · pawel-kow · Jul 3, 2026 · Jun 19, 2026 · Jun 19, 2026 · Jun 19, 2026
diff --git a/docs/draft-ietf-dconn-domainconnect-02.pdf b/docs/draft-ietf-dconn-domainconnect-02.pdf
diff --git a/...aft-ietf-dconn-domainconnect-02.clean.txt → ...aft-ietf-dconn-domainconnect-03.clean.txt b/...aft-ietf-dconn-domainconnect-02.clean.txt → ...aft-ietf-dconn-domainconnect-03.clean.txt
diff --git a/docs/draft-ietf-dconn-domainconnect-02.html → docs/draft-ietf-dconn-domainconnect-03.html b/docs/draft-ietf-dconn-domainconnect-02.html → docs/draft-ietf-dconn-domainconnect-03.html
diff --git a/docs/draft-ietf-dconn-domainconnect-03.pdf b/docs/draft-ietf-dconn-domainconnect-03.pdf
diff --git a/docs/draft-ietf-dconn-domainconnect-02.txt → docs/draft-ietf-dconn-domainconnect-03.txt b/docs/draft-ietf-dconn-domainconnect-02.txt → docs/draft-ietf-dconn-domainconnect-03.txt
diff --git a/docs/draft-ietf-dconn-domainconnect-02.xml → docs/draft-ietf-dconn-domainconnect-03.xml b/docs/draft-ietf-dconn-domainconnect-02.xml → docs/draft-ietf-dconn-domainconnect-03.xml
diff --git a/docs/index.html b/docs/index.html
@@ -44,10 +44,10 @@ <h1>Domain Connect — IETF Internet-Drafts (Editor's Copies)</h1>
         <h2>Domain Connect Protocol — DNS provisioning between Services and DNS Providers</h2>
         <p class="doc-id">draft-ietf-dconn-domainconnect-02</p>
         <ul class="formats">
-            <li><a href="draft-ietf-dconn-domainconnect-02.html">HTML</a></li>
-            <li><a href="draft-ietf-dconn-domainconnect-02.txt">TXT</a></li>
-            <li><a href="draft-ietf-dconn-domainconnect-02.pdf">PDF</a></li>
-            <li><a href="draft-ietf-dconn-domainconnect-02.xml">XML</a></li>
+            <li><a href="draft-ietf-dconn-domainconnect-03.html">HTML</a></li>
+            <li><a href="draft-ietf-dconn-domainconnect-03.txt">TXT</a></li>
+            <li><a href="draft-ietf-dconn-domainconnect-03.pdf">PDF</a></li>
+            <li><a href="draft-ietf-dconn-domainconnect-03.xml">XML</a></li>
         </ul>
     </div>
 

diff --git a/draft-ietf-dconn-domainconnect-02.xml.abort b/draft-ietf-dconn-domainconnect-02.xml.abort
diff --git a/draft-ietf-dconn-domainconnect-02.adoc → draft-ietf-dconn-domainconnect-03.adoc b/draft-ietf-dconn-domainconnect-02.adoc → draft-ietf-dconn-domainconnect-03.adoc
diff --git a/draft-ietf-dconn-domainconnect-async-00.adoc b/draft-ietf-dconn-domainconnect-async-00.adoc
@@ -855,7 +855,7 @@ Provider discovery.
 
 The phishing risks described in the Template Variable Phishing section of <<draft-ietf-dconn-domainconnect>> apply equally to the asynchronous flow.
 In particular, the `"properties"` parameter of the authorization request (see <<oauth-authorization-request>>) supplies variable values at consent time, and a malicious actor could craft a consent URL substituting harmful values.
-The mitigations described in <<draft-ietf-dconn-domainconnect>> (disabling the synchronous flow via `"syncBlock"`, digitally signing apply requests, and setting `"warnPhishing"`) apply to the asynchronous flow as well.
+The mitigations described in <<draft-ietf-dconn-domainconnect>> (disabling the synchronous flow via `"syncBlock"` and digitally signing apply requests) apply to the asynchronous flow as well. As in the synchronous flow, a template lacking such a mitigation is treated as susceptible to phishing by default.
 
 == IANA Considerations