Skip to content

draft-ietf-dconn-domainconnect-03 early Dnsdir review #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pawel-kow wants to merge 3 commits into
base: ietf/draft-ietf-dconn-domainconnect-XX
Choose a base branch
from
Open

draft-ietf-dconn-domainconnect-03 early Dnsdir review #203

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7350957
draft-ietf-dconn-domainconnect-03 early Dnsdir review
pawel-kow Aug 21, 2026
0d5cb5f
Merge branch 'ietf/draft-ietf-dconn-domainconnect-XX' into pawel-kow/…
pawel-kow Aug 25, 2026
b4cefec
Further fix on CNAM placement text
pawel-kow Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
139 changes: 79 additions & 60 deletions docs/draft-ietf-dconn-domainconnect-04.clean.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ Table of Contents
capitals, as shown here.

The Terms like "*Registrar*", "*Authoritative server*", "*Zone*",
"*Zone Apex*" or "*Sub Domain*" are used as defined in [RFC8499].
"*Zone Apex*" or "*Sub Domain*" are used as defined in [RFC9499].

This specification uses the Augmented Backus-Naur Form (ABNF)
notation of [RFC5234]. The following ABNF rules are imported from
Expand Down Expand Up @@ -1007,11 +1007,7 @@ Table of Contents
| | | |work only when both |
| | | |"domain" and "host" |
| | | |apply parameters are |
| | | |provided, for example |
| | | |when the template |
| | | |contains a CNAME record |
| | | |targeted at the fully |
| | | |qualified domain name. |
| | | |provided. |
| | | |The default is "false". |
+-------------+--------+-------------------+------------------------+
|*Critical |Array of|crit |(OPTIONAL) A list of the|
Expand Down Expand Up @@ -1240,6 +1236,11 @@ Table of Contents
order to avoid necessity of per provider adjustment to the
application flow.

Records forming the same RRset (i.e., sharing "host"/"name" and
record type) SHOULD be given the same "ttl" value in the template
definition, since [RFC2181] Section 5.2 requires all resource
records in an RRset to share a single TTL.

Support of variables in this field is OPTIONAL for DNS Provider.

"Data":
Expand Down Expand Up @@ -1455,7 +1456,7 @@ Table of Contents

The value in the template could simply contain "%servercluster%", and
the fully qualified string passed in. Alternatively, the value in
the template could contain "%var%.example.com" and a value of "01",
the template could contain "s%var%.example.com" and a value of "01",
"02", or "03" passed in. By placing more fixed data into the
template, the template is less prone to error or misuse and allows
better review of intent by the DNS Provider when onboarding the
Expand Down Expand Up @@ -2580,18 +2581,18 @@ Table of Contents

4. *Resolve variables* - All variable expressions in active template
records are substituted with the values provided by the caller,
producing a concrete set of DNS resource records (RRs) to be
applied (see Section 9.2).
producing the Rendered Record Set: a concrete set of DNS resource
records (RRs) to be applied (see Section 9.2).

a. abort if rendered RRs are not possible to be applied to the
target zone

5. *Perform conflict detection* - The DNS Provider checks the
resolved RR set against the existing zone content according to
the conflict detection rules (see Section 10.4).
Rendered Record Set against the existing zone content according
to the conflict detection rules (see Section 10.4).

a. Identify individual zone records that conflict with the
resolved RR set.
Rendered Record Set.

b. (only DNS Providers tracking template state): Check each
resolved RR against essential records of previously applied
Expand Down Expand Up @@ -2620,7 +2621,13 @@ Table of Contents

a. Remove all records pre-calculated for removal from the zone.

b. Write the resolved RR set to the zone in totality.
b. Write the Rendered Record Set to the zone in totality.

i. Note: if the Rendered Record Set yields differing "ttl"
values across new and existing RRs that form the same
RRset, the DNS Provider MUST reconcile them to a single
TTL (e.g., by taking the lowest value), per [RFC2181]
Section 5.2

c. (only DNS Providers tracking template state): Record the new
template instance for the "domain" and "host" pair and remove
Expand Down Expand Up @@ -2680,7 +2687,8 @@ Table of Contents
host, unless otherwise specified.

* A CNAME record conflicts with any other record on the same host,
and any existing records conflict with a CNAME.
including another CNAME, and any existing records conflict with a
CNAME.

* An NS record conflicts with all other records on the same host,
and with any record whose host is subordinate to the NS host. For
Expand Down Expand Up @@ -2708,10 +2716,11 @@ Table of Contents
the same host whose value starts with
"txtConflictMatchingPrefix".

Note: DNS Provider MUST also check applicability of all generated
records to the target DNS zone in its own system. For example it is
very common for DNS provider not to allow CNAME records to be at the
zone apex.
Note: A DNS Provider MUST also check the applicability of all
generated records to the target DNS zone against constraints imposed
by the DNS protocol itself, such as the coexistence rules of
[RFC2181], as well as any other local capabilities, limits or
policies.

10.4.1. Conflict Detection Special Handling

Expand Down Expand Up @@ -3002,7 +3011,7 @@ Table of Contents
specification that extends this document. See Section 3,
Paragraph 13.

* *Class*: the handling class of the type. The value MUST be one of
* *Handling*: the handling of the type. The value MUST be one of
"Fully Specified" (RDATA broken into dedicated template fields) or
"Computed" (records derived by a defined computation). A
"Reserved" entry MAY leave this field unassigned.
Expand Down Expand Up @@ -3037,7 +3046,7 @@ Table of Contents

Status: One of "Active", "Deprecated", or "Reserved".

Class: "Fully Specified" or "Computed"; omitted for a "Reserved"
Handling: "Fully Specified" or "Computed"; omitted for a "Reserved"
entry.

DNS RR TYPE: The name of the corresponding IANA DNS RR TYPE, or "N/
Expand All @@ -3051,42 +3060,42 @@ Table of Contents
The following types from this specification constitute the initial
contents of the registry:

+=============+========+===========+=======+========+=============+
| *RR Type* |*Status*| *Class* |*DNS RR|*Kind* | *Reference* |
| | | |TYPE* | | |
+=============+========+===========+=======+========+=============+
| "A" |Active | Fully |"A" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "AAAA" |Active | Fully |"AAAA" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "CNAME" |Active | Fully |"CNAME"|IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "MX" |Active | Fully |"MX" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "TXT" |Active | Fully |"TXT" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "SRV" |Active | Fully |"SRV" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "NS" |Active | Fully |"NS" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "SPFM" |Active | Computed |"N/A" |IETF | This |
| | | | |Standard| document |
+-------------+--------+-----------+-------+--------+-------------+
| "APEXCNAME" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+-----------+-------+--------+-------------+
| "REDIR301" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+-----------+-------+--------+-------------+
| "REDIR302" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+-----------+-------+--------+-------------+

Table 9: Initial Domain Connect Fully Specified Record Types
+=============+========+============+=======+========+=============+
| *RR Type* |*Status*| *Handling* |*DNS RR|*Kind* | *Reference* |
| | | |TYPE* | | |
+=============+========+============+=======+========+=============+
| "A" |Active | Fully |"A" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "AAAA" |Active | Fully |"AAAA" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "CNAME" |Active | Fully |"CNAME"|IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "MX" |Active | Fully |"MX" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "TXT" |Active | Fully |"TXT" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "SRV" |Active | Fully |"SRV" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "NS" |Active | Fully |"NS" |IETF | This |
| | | Specified | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "SPFM" |Active | Computed |"N/A" |IETF | This |
| | | | |Standard| document |
+-------------+--------+------------+-------+--------+-------------+
| "APEXCNAME" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+------------+-------+--------+-------------+
| "REDIR301" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+------------+-------+--------+-------------+
| "REDIR302" |Reserved| Computed |"N/A" |Other | [DC-SPEC] |
+-------------+--------+------------+-------+--------+-------------+

Table 9: Initial Domain Connect Fully Specified Record Types

12.3. Domain Connect Settings Properties Registry

Expand Down Expand Up @@ -3449,6 +3458,16 @@ Change from draft-ietf-dconn-domainconnect-03 to -04
* Added dc-template-property, dc-unprefixed-property, and dc-vnd-
property to Terminology.

* Corrected nits from early Dnsdir review.

* Clarified RR placement constraints arising from the DNS protocol.

* Noted RRset TTL consistency requirements in Template Record and
Steps to Apply a Template.

* Introduced Rendered Record Set terminology in Steps to Apply a
Template to disambiguate from RRset.

Change from draft-ietf-dconn-domainconnect-02 to -03

* Classified template record types as Fully Specified, Computed, or
Expand Down Expand Up @@ -3720,11 +3739,11 @@ Normative References
RFC 9110, June 2022,
<https://www.rfc-editor.org/info/rfc9110>.

Informative References
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", IETF, DOI 10.17487/RFC2181, RFC 2181, July
1997, <https://www.rfc-editor.org/info/rfc2181>.

[RFC8499] "Hoffman, P., Sullivan, A., and K. Fujiwara, "DNS
Terminology", IETF, DOI 10.17487/RFC8499, RFC 8499,
January 2019, >.".
Informative References

[RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type
Structured Syntax Suffixes", IETF, DOI 10.17487/RFC6839,
Expand Down
Loading