[DNSOP] [Errata Rejected] RFC9460 (7871)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 16 April 2024 08:41 UTC

Return-Path: <wwwrun@rfcpa.amsl.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 82874C14EB19; Tue, 16 Apr 2024 01:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, 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
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 SIPlB4dr-WHY; Tue, 16 Apr 2024 01:41:29 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 AAB50C14F60D; Tue, 16 Apr 2024 01:41:29 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7CFF218FB976; Tue, 16 Apr 2024 01:41:29 -0700 (PDT)
To: ms@kilabit.info, ietf@bemasc.net, mbishop@evequefou.be, erik+ietf@nygren.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240416084129.7CFF218FB976@rfcpa.amsl.com>
Date: Tue, 16 Apr 2024 01:41:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/OvZUR53r4LIElKOqm94ObTHW-6w>
Subject: [DNSOP] [Errata Rejected] RFC9460 (7871)
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: Tue, 16 Apr 2024 08:41:33 -0000

The following errata report has been rejected for RFC9460,
"Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)".

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

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Shulhan <ms@kilabit.info>
Date Reported: 2024-03-25
Rejected by: Warren Kumari (Ops AD) (IESG)

Section: D.2

Original Text
-------------
example.com.   SVCB   1 foo.example.com. key667="hello0qoo"

\# 32 (
00 01                                              ; priority
03 66 6f 6f 07 65 78 61 6d 70 6c 65 03 63 6f 6d 00 ; target
02 9b                                              ; key 667
00 09                                              ; length 9
68 65 6c 6c 6f d2 71 6f 6f                         ; value
)

\x00\x01                                           # priority
\x03foo\x07example\x03com\x00                      # target
\x02\x9b                                           # key 667
\x00\x09                                           # length 9
hello\xd2qoo                                       # value

Corrected Text
--------------
example.com.   SVCB   1 foo.example.com. key667="hello0qoo"

\# 32 (
00 01                                              ; priority
03 66 6f 6f 07 65 78 61 6d 70 6c 65 03 63 6f 6d 00 ; target
02 9b                                              ; key 667
00 09                                              ; length 9
68 65 6c 6c 6f 88 71 6f 6f                         ; value
)

\x00\x01                                           # priority
\x03foo\x07example\x03com\x00                      # target
\x02\x9b                                           # key 667
\x00\x09                                           # length 9
hello\x88qoo                                       # value

Notes
-----
Original report:
The escaped octal number "0" when encoded to hexadecimal should be "88" or "\x88", NOT "d2" or "\xd2".

The "d2" or "\xd2" is hexadecimal value for decimal number "210".


WK Edit: I am rejecting this Errata -- the display format (key667="hello0qoo") is encoded using the DNS RFC1035 syntax, which specifies:
\DDD            where each D is a digit is the octet corresponding to
                the decimal number described by DDD.

This is, um, surprising to many, and a relatively common source of issues in the DNS parsing world. 

I encourage future updates of the RFC to include a "footnote" / parenthetical pointing this out...
 --VERIFIER NOTES-- 
   I am rejecting this Errata -- the display format (key667="hello0qoo") is encoded using the DNS RFC1035 syntax, which specifies:
\DDD where each D is a digit is the octet corresponding to
the decimal number described by DDD.

This is, um, surprising to many, and a relatively common source of issues in the DNS parsing world.

I encourage future updates of the RFC to include a "footnote" / parenthetical pointing this out...



--------------------------------------
RFC9460 (draft-ietf-dnsop-svcb-https-12)
--------------------------------------
Title               : Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Publication Date    : November 2023
Author(s)           : B. Schwartz, M. Bishop, E. Nygren
Category            : PROPOSED STANDARD
Source              : Domain Name System Operations
Stream              : IETF
Verifying Party     : IESG