IETF Logo Mail Archive

[DNSOP] Incompatibility with indicating client support for EDE (draft-ietf-dnsop-structured-dns-error)

Tommy Pauly <tpauly@apple.com> Mon, 22 May 2023 16:20 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDD0C1516E0 for <dnsop@ietfa.amsl.com>; Mon, 22 May 2023 09:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdyWT1TeUyBw for <dnsop@ietfa.amsl.com>; Mon, 22 May 2023 09:20:43 -0700 (PDT)
Received: from ma-mailsvcp-mx-lapp03.apple.com (ma-mailsvcp-mx-lapp03.apple.com [17.32.222.24]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 6D1A7C15154E for <dnsop@ietf.org>; Mon, 22 May 2023 09:20:43 -0700 (PDT)
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by ma-mailsvcp-mx-lapp03.apple.com (Oracle Communications Messaging Server 8.1.0.22.20230228 64bit (built Feb 28 2023)) with ESMTPS id <0RV2003YSIPTYO00@ma-mailsvcp-mx-lapp03.apple.com> for dnsop@ietf.org; Mon, 22 May 2023 09:20:18 -0700 (PDT)
X-Proofpoint-GUID: cgmuZk9FQISaAB08mLYnPkWnMhuXupbp
X-Proofpoint-ORIG-GUID: cgmuZk9FQISaAB08mLYnPkWnMhuXupbp
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.573, 18.0.957 definitions=2023-05-22_11:2023-05-22, 2023-05-22 signatures=0
X-Proofpoint-Spam-Details: rule=interactive_user_notspam policy=interactive_user score=0 spamscore=0 mlxscore=0 bulkscore=0 adultscore=0 malwarescore=0 phishscore=0 suspectscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2304280000 definitions=main-2305220136
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : message-id : date : to; s=20180706; bh=IFaIjYPBctAs6Fyh1C6X8DzcQGsYIDH6guSJc5MdI2c=; b=w2kAgqgjT/jV5y0ECHIc//yO58HwDwqs1BgrR4JyZP+QCbS7zXktTouw9mRmeKwHRwkT IETb9Y5fz2Qv3e3g0Km5zd+zco7a8jRnrDpKk6adE0r65tjf4wnEoLbDLamg1ZlhrxhV 8cVp0pGwMIlRkZsGiJTClH1anppsEn/XadD6cPw3Mak1EAeYpUczmGVAaFeGa7b7rAmh izbzrt7Uit59430mZX/AElqRY23r5chrEBK3VD8BFoxEdqLYuoTLGhNrNfOjX1mkCxRw sRkV1JupAmMSOEz2+HCd2hykMazQ0a4NMoQ5jRONPxjLKJNfbOvJisg8l1lFcu7XEw15 QQ==
Received: from rn-mailsvcp-mmp-lapp02.rno.apple.com (rn-mailsvcp-mmp-lapp02.rno.apple.com [17.179.253.15]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.22.20230228 64bit (built Feb 28 2023)) with ESMTPS id <0RV200OJKIPT6A10@rn-mailsvcp-mta-lapp01.rno.apple.com> for dnsop@ietf.org; Mon, 22 May 2023 09:20:17 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp02.rno.apple.com by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.22.20230228 64bit (built Feb 28 2023)) id <0RV200G00IMLD700@rn-mailsvcp-mmp-lapp02.rno.apple.com> for dnsop@ietf.org; Mon, 22 May 2023 09:20:17 -0700 (PDT)
X-Va-A:
X-Va-T-CD: f4439a1f3baad66c778bad7f442511f1
X-Va-E-CD: 18f5caa257a2dfaf3d0a537795158a39
X-Va-R-CD: bec69915deaac6c1d3bc6de9eb1f4611
X-Va-ID: c66d0176-17ad-43e9-afbf-143739cb1ef2
X-Va-CD: 0
X-V-A:
X-V-T-CD: f4439a1f3baad66c778bad7f442511f1
X-V-E-CD: 18f5caa257a2dfaf3d0a537795158a39
X-V-R-CD: bec69915deaac6c1d3bc6de9eb1f4611
X-V-ID: 12fab4bd-4008-4254-834a-740e9c6c30f8
X-V-CD: 0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.573, 18.0.957 definitions=2023-05-22_11:2023-05-22, 2023-05-22 signatures=0
Received: from smtpclient.apple (unknown [17.230.1.116]) by rn-mailsvcp-mmp-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.22.20230228 64bit (built Feb 28 2023)) with ESMTPSA id <0RV200L0WIPSKQ00@rn-mailsvcp-mmp-lapp02.rno.apple.com> for dnsop@ietf.org; Mon, 22 May 2023 09:20:17 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_787E1867-3FA0-4374-960A-F32A6D74DB18"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3762.100.4.1.11\))
Message-id: <1BE5004E-B64D-407D-80F5-EB25D7BB671C@apple.com>
Date: Mon, 22 May 2023 09:20:06 -0700
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3762.100.4.1.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_px3gFmv96Urxf5I83fz-WkBHac>
Subject: [DNSOP] Incompatibility with indicating client support for EDE (draft-ietf-dnsop-structured-dns-error)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2023 16:20:47 -0000

Hello DNSOP,

In draft-ietf-dnsop-structured-dns-error, there’s a description of how clients should indicate that they understand extended DNS errors (EDE) by sending an empty EDE option. 

https://www.ietf.org/archive/id/draft-ietf-dnsop-structured-dns-error-02.html#name-client-generating-request

This is something that makes a lot of sense to me, and provides a great way to indicate that a client would prefer to receive proper blocked/filtered errors (with possible extra text) as opposed to a forged answer.

However, in testing this out, I’m seeing inconsistent compatibility with some public resolvers. I was testing enabling this for encrypted resolvers only, and I see the following behavior for a sampling of resolvers using DoH:

1.1.1.1 - NOERROR, works fine!
9.9.9.9 - NOERROR, works fine!
8.8.8.8 - FORMERR on all responses
dns.adguard-dns.com - SERVFAIL on all responses

Do we think that this should be allowed in queries (and thus this is a bug in resolvers like 8.8.8.8 or AdGuard)? Or is there a problem with the approach this document is suggesting?

Best,
Tommy

v2.23.0 | Report a Bug | By Email