IETF Logo Mail Archive

[DNSOP] [Technical Errata Reported] RFC7686 (6761)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 29 November 2021 19:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 D8AB43A07B9 for <dnsop@ietfa.amsl.com>; Mon, 29 Nov 2021 11:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MqSYYkkuMQvK for <dnsop@ietfa.amsl.com>; Mon, 29 Nov 2021 11:07:12 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235083A07AF for <dnsop@ietf.org>; Mon, 29 Nov 2021 11:07:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id E4E9B36417; Mon, 29 Nov 2021 11:07:11 -0800 (PST)
To: jacob@appelbaum.net, alecm@fb.com, warren@kumari.net, rwilton@cisco.com, benno@NLnetLabs.nl, suzworldwide@gmail.com, tjw.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: peter.van.dijk@powerdns.com, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20211129190711.E4E9B36417@rfc-editor.org>
Date: Mon, 29 Nov 2021 11:07:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/irPsHwSSdoeMJdqzOjwm3oSz8CA>
Subject: [DNSOP] [Technical Errata Reported] RFC7686 (6761)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2021 19:07:17 -0000

The following errata report has been submitted for RFC7686,
"The ".onion" Special-Use Domain Name".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6761

--------------------------------------
Type: Technical
Reported by: Peter van Dijk <peter.van.dijk@powerdns.com>

Section: 2

Original Text
-------------
   5.  Authoritative DNS Servers: Authoritative servers MUST respond to
       queries for .onion with NXDOMAIN.

   6.  DNS Server Operators: Operators MUST NOT configure an
       authoritative DNS server to answer queries for .onion.  If they
       do so, client software is likely to ignore any results (see
       above).

Corrected Text
--------------
   5.  Authoritative DNS Servers: Authoritative servers MUST respond non-authoritatively to
       queries for names in .onion.

   6.  DNS Server Operators: Operators MUST NOT configure an
       authoritative DNS server to answer authoritatively to queries for names in .onion.  If they
       do so, client software is likely to ignore any results (see
       above).

Notes
-----
The original text for 5 and 6 is conflicting. A name server cannot respond with NXDOMAIN (which is an authoritative answer) without having a zone configured to serve that NXDOMAIN from. Clearly the intent of the text is that clients will not find authoritative answers to .onion queries anywhere in the DNS.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7686 (draft-ietf-dnsop-onion-tld-01)
--------------------------------------
Title               : The ".onion" Special-Use Domain Name
Publication Date    : October 2015
Author(s)           : J. Appelbaum, A. Muffett
Category            : PROPOSED STANDARD
Source              : Domain Name System Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email