Re: [DNSOP] [Editorial Errata Reported] RFC9460 (7871)

[Rebecca VanRheenen <[e-mail]>]

Hi Warren,

We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. As Stream Approver, please review and set the Status and Type accordingly (see the definitions at https://www.rfc-editor.org/errata-definitions/).

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

Information on how to verify errata reports can be found at: 
https://www.rfc-editor.org/how-to-verify/

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php

Thank you.

RFC Editor/rv



> On Mar 25, 2024, at 9:44 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted 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
> 
> --------------------------------------
> Type: Editorial
> Reported by: Shulhan <[e-mail]>
> 
> Section: D.2. ServiceMode
> 
> 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
> -----
> 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".
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> 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
>