From b943ea7f698b5411d05a4c4fb8473324741b437c Mon Sep 17 00:00:00 2001 From: Erik Nygren Date: Wed, 5 Oct 2022 10:40:51 -0400 Subject: [PATCH 1/2] Some implementations may not allow A/AAAA records on names starting with an underscore As discussed in dnsop and approved for inclusion, note that some implementations may not allow A/AAAA records on names starting with an underscore. See: https://mailarchive.ietf.org/arch/msg/dnsop/LhEufm0a8IjoXZ_ck0b9RTSkDTc/ --- draft-ietf-dnsop-svcb-https.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/draft-ietf-dnsop-svcb-https.md b/draft-ietf-dnsop-svcb-https.md index 8b4eea1..7d7ae99 100644 --- a/draft-ietf-dnsop-svcb-https.md +++ b/draft-ietf-dnsop-svcb-https.md @@ -498,8 +498,6 @@ is the effective TargetName: svc2.example.net. 300 IN A 192.0.2.2 svc2.example.net. 300 IN AAAA 2001:db8::2 - - # Client behavior {#client-behavior} "SVCB resolution" is the process of enumerating the priority-ordered endpoints @@ -1371,6 +1369,13 @@ this is likely unnecessary and makes responses slower and larger. Also, zone structures that require following more than 8 aliases (counting both AliasMode and CNAME records) are NOT RECOMMENDED. +## Operational considerations + +Note that some implementations may not allow A or AAAA records on names +starting with an underscore due to various interpretations of RFCs. +This could be an operational issue when the TargetName contains an attrleaf label, +as well as using an TargetName of "." when the owner name contains an attrleaf label. + ## Examples ### Protocol enhancements From 89fdc7fd3b1015c72907b963f78a1674560bb2b9 Mon Sep 17 00:00:00 2001 From: Erik Nygren Date: Wed, 5 Oct 2022 10:43:39 -0400 Subject: [PATCH 2/2] Fix whitespace --- draft-ietf-dnsop-svcb-https.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/draft-ietf-dnsop-svcb-https.md b/draft-ietf-dnsop-svcb-https.md index 7d7ae99..f8f4579 100644 --- a/draft-ietf-dnsop-svcb-https.md +++ b/draft-ietf-dnsop-svcb-https.md @@ -498,6 +498,8 @@ is the effective TargetName: svc2.example.net. 300 IN A 192.0.2.2 svc2.example.net. 300 IN AAAA 2001:db8::2 + + # Client behavior {#client-behavior} "SVCB resolution" is the process of enumerating the priority-ordered endpoints @@ -1371,7 +1373,7 @@ Also, zone structures that require following more than 8 aliases ## Operational considerations -Note that some implementations may not allow A or AAAA records on names +Note that some implementations may not allow A or AAAA records on names starting with an underscore due to various interpretations of RFCs. This could be an operational issue when the TargetName contains an attrleaf label, as well as using an TargetName of "." when the owner name contains an attrleaf label.