Re: [dns-privacy] [core] [DNSOP] WGA call for draft-lenders-dns-over-coap

Ben Schwartz <> Tue, 20 September 2022 15:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ABD17C15A723 for <>; Tue, 20 Sep 2022 08:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.607
X-Spam-Status: No, score=-17.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PZ-c2NonH_4l for <>; Tue, 20 Sep 2022 08:11:01 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::92e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id D7604C1522D2 for <>; Tue, 20 Sep 2022 08:11:01 -0700 (PDT)
Received: by with SMTP id p17so1180178uao.11 for <>; Tue, 20 Sep 2022 08:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=16idLj/fQS53J8Ge1+yi34cKeYxD2zOIF4wOG/XszLs=; b=r+cxQpCU2e5NjwJHnB2ZuWmetMyloHPUA2C1GW5SESl9urT6RkwSSiKOU0dOIZ9Jrz 3zKF9RN/s7SFvCICnZ+h2WcKQvv/7ek7LepxIaaWBmi3i0w6w61tnnL4EKnyedEprJZl mZWCG6cW8zQqlJLnDrEErFWxWusd06XJlvYr4cgKvu46Rc2b0AZNuT20liqFvX4F4tU0 vha9PWwja7obb7tIoh5lPB3irvGLTT98IbX+EoH9pr6UrcMsPMzmC/9SRg6/H3bnnDtk FyTbPELLcjr/puybxAamJ6NM6t8u/QQKvUfWorn8qPCCetA6oOrgz3FNHyue7tduza8g wsKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=16idLj/fQS53J8Ge1+yi34cKeYxD2zOIF4wOG/XszLs=; b=K8Va6RX60Yw1uUFiDMwv5Rdtm1epM++5XqSI9ZTTgL2sTPG6SE7BlD7+KrlW0w44lB fd9vGQwBK9PI0gCrFeD9Juf6yoaipirEhs3bqRYeC4Bf4p458LpTp58VfsVad2qrHQeT V8vMSAuedCbiY33e4n4KtpkZ5IE8sZLlAp8aBJTsilf2gxuyIqL1MUDyC4cqvV34N1Qu DBWvYeQq/0Kh6uEq/qftE0SRqWRSTjrS4OTIC03BA7uDYiwICA7a8DBw/K0IkrZOZJed vEJQmTiUT6NjGBtYs8WA0CDxoqLZPlQKsULEskDqqdPVvX43gQFLqSVWTP1jndQ+tG2E KLGA==
X-Gm-Message-State: ACrzQf3oObBwP1YpuQr7OP63tF4K23KJStavzpHpzXi9tM/P37+CBUc0 Xnapa6TkFizosXK2R1TjZR0KVUovoGha1hCJlgIqp4CI2l0=
X-Google-Smtp-Source: AMsMyM4apTI8S2a/2KFWougqwPlMfEv9Y922c8Ewnl7O5tC9UBfeyyoS8GUPc+vfkNH3wr+k1bes6wTr+O4OC3Eec6g=
X-Received: by 2002:ab0:6035:0:b0:3bf:2e26:699 with SMTP id n21-20020ab06035000000b003bf2e260699mr2964467ual.102.1663686660201; Tue, 20 Sep 2022 08:11:00 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Ben Schwartz <>
Date: Tue, 20 Sep 2022 11:10:48 -0400
Message-ID: <>
To: Martine Sophie Lenders <>
Cc:, DNS Privacy Working Group <>, dnsop <>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="0000000000006d1c4d05e91d3c56"
Archived-At: <>
Subject: Re: [dns-privacy] [core] [DNSOP] WGA call for draft-lenders-dns-over-coap
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Addition of privacy to the DNS protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Sep 2022 15:11:05 -0000


Thanks for the proposed updated text regarding CNAMEs.  I agree that it is
an improvement, but I still think it would be better to omit entirely.  By
writing that implementations SHOULD follow RFC 1034, you imply that they
are permitted not to, which seems objectionable.  I think it would be much
clearer to simply say that use of DoC does not alter the DNS message

I feel similarly about the Additional section.  If you think that it would
be useful to deviate from ordinary practices regarding the Additional
section, I think this should be in a separate draft on compact DNS
responses, not coupled to DoC.  For example, such compactification might be
even more relevant to UDP Do53 than to DoC.


On Mon, Sep 19, 2022 at 7:30 AM Martine Sophie Lenders <> wrote:

> Hi,
> Sorry for the late reply, I was away from any keyboard for the past two
> weeks.
> I think there might be a misunderstanding regarding the CNAME behavior,
> due to some poor wording in our draft: The CNAMEs should, of course, only
> be resolved in such a way, if the queried record was an A or AAAA record.
> This does not, to my understanding, contradict the behavior described for
> CNAMEs in RFC 1034. We propose a different wording for the first sentence
> in 5.1 to prevent such misunderstandings in the future:
>     In the case of CNAME records in a DNS response to an A or AAAA record
> query, a DoC server SHOULD follow common DNS resolver behavior [RFC1034
> <>
> ] by resolving a CNAME until the originally requested resource record
> type is reached.
> Regarding the population of the additional section, we also follow
> recommendations in RFC 1034, to only include records useful to the client.
> We deem this particularly noteworthy when it comes to DNS, as from our
> analysis of DNS traffic, responses can become quite large due to an
> abundance of records in the Additional section. With the message size
> constraints in LLNs, it might thus be necessary to prune the DNS message
> for records actually useful to the querying DoC client.
> Lastly, mind, that, at least in our model for DoC, a DoC client does not
> further distribute the information it gathered via DoC.
> Regards
> Martine
> Am 06.09.22 um 17:06 schrieb Ben Schwartz:
> Some further notes on this draft.
> Section 5.1 says that a DoC server "SHOULD" follow CNAMEs.  This is a
> misunderstanding of the nature of DNS transports.  DoC is a DNS transport,
> like DoT and DoH.  The choice of transport is independent of the DNS
> server's answering behavior, which must not be modified by the transport.
> Indeed, DPRIVE is now chartered to enable the use of alternate transports
> for recursive-to-authoritative queries for which CNAME following has
> entirely different rules.  This is possible precisely because the choice of
> transport does not alter the logical DNS contents.
> Section 5.1 also proposes that the population of the Additional section
> might follow different logic when using DoC.
> Modifying the logical DNS behavior would create a wide range of exciting
> and unpredictable compatibility issues when trying to use a new transport.
> I urge the authors to delete Section 5.1, which would resolve this
> problem.  The draft could instead note that the DNS queries and responses
> are not modified when using DoC, except under private arrangement between
> the client and server.
> On Fri, Sep 2, 2022 at 12:20 PM Jaime Jiménez <> wrote:
>> Dear CoRE WG,
>> Thanks to the authors and the reviewers that provided comments on the
>> list for this draft. Given the in-room support and the list discussion
>> during the WGA the chairs believe that there is sufficient support for the
>> adoption of this document in CoRE.
>> The authors are advised to resubmit the draft-core-dns-over-coap and to
>> set up a document repo under the CoRE Github organization at
>> BR,
>> Jaime Jiménez on behalf of the CoRE chairs.
>> On 15.8.2022 11.26, Jaime Jiménez wrote:
>> Dear CoRE WG,
>> We would like to start the call for adoption on draft-lenders-dns-over-coap.
>> The draft defines a protocol for sending DNS messages over secure CoAP (DTLS and/or OSCORE). The draft was discussed during IETF114 and on IETF113 and was well-received by the group.
>> During the last IETF meeting there were no objections for adoption so we confirm this now on the mailing list. Please let us know if you support adopting this draft. As many people will still be on vacation, we the WGA call will last a couple of weeks, ending the *1st of September*.
>> Note that DNSOP and DPRIVE are in the loop as the draft is relevant for their working groups too.
>> BR,
>> --
>> Jaime Jiménez
>> _______________________________________________
>> core mailing listcore@ietf.org
>> --
>> Jaime Jiménez
>> _______________________________________________
>> DNSOP mailing list
> _______________________________________________
> core mailing listcore@ietf.org