diff --git a/draft-homburg-deleg-incremental-deleg.html b/draft-homburg-deleg-incremental-deleg.html
index 2ce6340..e8ac3a3 100644
--- a/draft-homburg-deleg-incremental-deleg.html
+++ b/draft-homburg-deleg-incremental-deleg.html
@@ -2125,7 +2125,41 @@
+
+
+Table 1:
+Comparison of [I-D.dnsop-deleg] with [this document]
+
+
+
+ [I-D.dnsop-deleg] |
+ [this document] |
+
+
+
+
+ Requires implementation in both authoritative name server as well as in the resolver |
+ Only resolver implementation required. But optimized with updated authoritative software. |
+
+
+ Authoritative name servers need to be updated all at once |
+ Authoritative name servers may be updated gradually for optimization |
+
+
+ DNSKEY flag needed to signal DELEG. Special requirements for the child domain. |
+ No DNSKEY flag needed. Separation of concerns. |
+
+
+ New semantics about what is authoritative (BOGUS with current DNSSEC validators) |
+ Works with current DNS semantics. Easier to implement. |
+
+
+ No extra queries |
+ An extra query per zone to determine presence of the _deleg label, and per authoritative server when incremental deleg support is not yet detected |
+
+
+
@@ -2154,9 +2188,9 @@
10. IANA Considerations
Per [RFC8552], IANA is requested to add the following entry to the DNS "Underscored and Globally Scoped DNS Node Names" registry:ΒΆ
-
+
-Table 1:
+Table 2:
Entry in the Underscored and Globally Scoped DNS Node Names registry
diff --git a/draft-homburg-deleg-incremental-deleg.txt b/draft-homburg-deleg-incremental-deleg.txt
index 75edf5a..db70c83 100644
--- a/draft-homburg-deleg-incremental-deleg.txt
+++ b/draft-homburg-deleg-incremental-deleg.txt
@@ -841,6 +841,36 @@ Table of Contents
7.3. Comparison with [I-D.dnsop-deleg]
+ +=========================+========================================+
+ | [I-D.dnsop-deleg] | [this document] |
+ +=========================+========================================+
+ | Requires implementation | Only resolver implementation required. |
+ | in both authoritative | But optimized with updated |
+ | name server as well as | authoritative software. |
+ | in the resolver | |
+ +-------------------------+----------------------------------------+
+ | Authoritative name | Authoritative name servers may be |
+ | servers need to be | updated gradually for optimization |
+ | updated all at once | |
+ +-------------------------+----------------------------------------+
+ | DNSKEY flag needed to | No DNSKEY flag needed. Separation of |
+ | signal DELEG. Special | concerns. |
+ | requirements for the | |
+ | child domain. | |
+ +-------------------------+----------------------------------------+
+ | New semantics about | Works with current DNS semantics. |
+ | what is authoritative | Easier to implement. |
+ | (BOGUS with current | |
+ | DNSSEC validators) | |
+ +-------------------------+----------------------------------------+
+ | No extra queries | An extra query _per zone_ to determine |
+ | | presence of the _deleg label, and _per |
+ | | authoritative_ server when incremental |
+ | | deleg support is not yet detected |
+ +-------------------------+----------------------------------------+
+
+ Table 1: Comparison of [I-D.dnsop-deleg] with [this document]
+
8. Implementation Status
*Note to the RFC Editor*: please remove this entire section before
@@ -868,7 +898,7 @@ Table of Contents
| SVCB | _deleg | [this document] |
+---------+------------+-----------------+
- Table 1: Entry in the Underscored and
+ Table 2: Entry in the Underscored and
Globally Scoped DNS Node Names
registry