[Add] Section 4 of the draft DDR spec makes erroneous(?) reference to since-renamed(?) field SvcDomainName

Hazel Smith <hazelesque@google.com> Mon, 26 July 2021 14:59 UTC

Return-Path: <hazelesque@google.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 133413A184A for <add@ietfa.amsl.com>; Mon, 26 Jul 2021 07:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.097
X-Spam-Level:
X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdnACM-YNNo3 for <add@ietfa.amsl.com>; Mon, 26 Jul 2021 07:59:25 -0700 (PDT)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 393033A1843 for <add@ietf.org>; Mon, 26 Jul 2021 07:59:08 -0700 (PDT)
Received: by mail-ot1-x334.google.com with SMTP id i39-20020a9d17270000b02904cf73f54f4bso8373458ota.2 for <add@ietf.org>; Mon, 26 Jul 2021 07:59:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=OrsWamKxWRlXv3mLjmnUC6Y9l6yIuswjYuJuKah2vMo=; b=jyxOS1GoQQU7iTL4ZORVexl3HvO+CHsrwuc++TiSTZpvsBkAJL8kCbFfK/+d7Svl65 tHLDt1+h6o8n1G2YAmMoFTDqcXAxnAQvgpCFZLHdHhAlW5YBHYSVtKtm0h3M3G34BbTm 7X0npg6gT/x6G1EuUHsfWmPAvhAmqja3Zgt3VwNuNBmRMmxisVCERbBul2dt7Ku0yvvt XfYSf3s6pMRDIqb0lTy5DWalQEitemu/4K2Z6PXhCmvtkh/qQ1V/Kx9ufkx0P6g+seLv kt/xEOXwDY/u0lhQJjT2PGuL+WpbLzlisA3zWGnyv0ha/wMQlf+N6fkfr+HeQZbnWJ4b V8Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=OrsWamKxWRlXv3mLjmnUC6Y9l6yIuswjYuJuKah2vMo=; b=UJAPcU5kPlM0CUl8uudboSBEs+auJQ7GI+4FX5VKiLhFx8NBqYB2xKZZoZq7euAXXG S822EvoywcUjmKa0Jeh038asM0GwP+kN0WsumcLeIeJ/iplv/4juAbMBDaR+CWwrqkVT W64IACpzDr0o7E6EUUxH6HE5jdNI+nbYRJrZFlEj6DEddsB0zCkmPdqyYb34IJY+zqTQ xFlH9gyurjOlnzaFCnhRXWT6CSVI2J0MxwPFbkptD0O1TmXDbt9ZCMK7N2bjTdo57m9s DKFJ/E/cWH38E+ysDp0ayADRpJBOSYbLexKoKollqv79si0QlZ+JUiOcNUwh6sJt/jiq ncGQ==
X-Gm-Message-State: AOAM532ZBNTmcpZ2F9iCMxcfjP2wPRfNaoBpplbX/9bh1E1dkh68a6QX N7ibsRoph02wwE236KuMd9GT9XKkitpAQvE0O2zkNrU5ZLM7ieWz
X-Google-Smtp-Source: ABdhPJyYTEUXp6PI89vheE83Rd/Q3XnsGA40K+Fi8izlNAAlB2qFVd3bPcjvXSJx12zh476bXVG49HEGPNJKyATxidA=
X-Received: by 2002:a9d:12f:: with SMTP id 44mr12533056otu.14.1627311546288; Mon, 26 Jul 2021 07:59:06 -0700 (PDT)
MIME-Version: 1.0
From: Hazel Smith <hazelesque@google.com>
Date: Mon, 26 Jul 2021 15:58:55 +0100
Message-ID: <CAP5=bJGbaa8FHMp0jakkjRV+PPE6Ywv8_agzMWfzwxct1KAB0A@mail.gmail.com>
To: add@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/ASiTxCIOvS0ICQpqNB8uGlSuoVk>
Subject: [Add] Section 4 of the draft DDR spec makes erroneous(?) reference to since-renamed(?) field SvcDomainName
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2021 14:59:30 -0000

Dear Adaptive DNS Discovery Working Group,

I see that Section 4 of the draft DDR specification [I-D.ietf-add-ddr]
makes reference to the field "SvcDomainName", as follows:

> "the SVCB response MUST NOT use the "." value for the SvcDomainName"

However, the field name "SvcDomainName" appears only twice in the
draft SVCB/HTTPS specification [I-D.ietf-dnsop-svcb-https], and in
both cases in the context of the HTTPS (nee HTTPSSVC) RRType.

(The name "SvcDomainName" appears 28 times in the expired HTTPSSVC
draft [I-D.nygren-httpbis-httpssvc], compared to the aforementioned
twice in the draft combined SVCB/HTTPS specification
[I-D.ietf-dnsop-svcb-https] where instead the name TargetName appears
43 times.)

Given that document says that the HTTPS RR type is an "SVCB-compatible
RR type", and Section 1.2 of that document defines the second
(mandatory) field of the SVCB RR as TargetName, I believe that
references in both that document and in the draft DDR specification to
"SvcDomainName" may in fact be in error, and that in the place of
"SvcDomainName" the string "TargetName" should appear.

As such, I thought I would raise what appears to be an inconsistency
in updating these various drafts.

Kind Regards,

Hazel Smith <hazelesque@google.com>
Site Reliability Engineer, Traffic Control SRE, Google


--
[I-D.ietf-add-ddr]
              Pauly, T., Kinnear, E., Wood, C.A., McManus, P., Jensen,
              T., "Discovery of Designated Resolvers", Work in
              Progress, Internet-Draft, draft-ietf-add-ddr-02, 8 July
              2021, <https://datatracker.ietf.org/doc/html/draft-ietf-add-
              ddr-02>


[I-D.ietf-dnsop-svcb-https]
              Schwartz, B., Bishop, M., and E. Nygren, "Service binding
              and parameter specification via the DNS (DNS SVCB and
              HTTPS RRs)", Work in Progress, Internet-Draft, draft-ietf-
              dnsop-svcb-https-06, 16 June 2021,
              <https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-
              https-06.txt>.

[I-D.nygren-httpbis-httpssvc]
              Schwartz, B., Bishop, M., and E. Nygren, "HTTPSSVC
              service location and parameter specification via the DNS
              (DNS HTTPSSVC)", Expired & archived, Internet-Draft,
              draft-nygren-httpbis-httpssvc-03, 8 July 2019,
              <https://datatracker.ietf.org/doc/html/draft-nygren-httpbis-
              httpssvc-03>.