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 <m...@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 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
