This report is incorrect. SvcParamValues always are presented via a char-string encoding as defined in Appendix A, so quotes are always allowed. The "single decimal integer" applies to the "value" which is derived by reversing the escaping of the char-string, producing a *OCTET in ABNF.
Thanks for the close read! Ben Schwartz ________________________________ From: RFC Errata System <rfc-edi...@rfc-editor.org> Sent: Monday, November 4, 2024 11:00 AM To: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org> Cc: julian.ke...@kit.edu <julian.ke...@kit.edu>; i...@bemasc.net <i...@bemasc.net>; mbis...@evequefou.be <mbis...@evequefou.be>; erik+i...@nygren.org <erik+i...@nygren.org>; dnsop@ietf.org <dnsop@ietf.org> Subject: [Editorial Errata Reported] RFC9460 (8168) 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://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid8168__;!!Bt8RZUm9aw!89a-tvCmf2C_SyPv1duCxMZzZCQ4exF2dwyPKvHQhOYL8XA9SSHTrggz3IllaiAH1J5LAYBIeeGbCeU_JWJN$ -------------------------------------- Type: Editorial Reported by: Julian Keck <julian.ke...@kit.edu> Section: 2.3 Original Text ------------- This record would indicate that "foo://api.example.com:8443" is aliased to "svc4.example.net". The owner of "example.net", in turn, could publish this record: svc4.example.net. 7200 IN SVCB 3 svc4.example.net. ( alpn="bar" port="8004" ) This record would indicate that these services are served on port number 8004, which supports the protocol "bar" and its associated transport in addition to the default transport protocol for "foo://". Corrected Text -------------- This record would indicate that "foo://api.example.com:8443" is aliased to "svc4.example.net". The owner of "example.net", in turn, could publish this record: svc4.example.net. 7200 IN SVCB 3 svc4.example.net. ( alpn="bar" port=8004 ) This record would indicate that these services are served on port number 8004, which supports the protocol "bar" and its associated transport in addition to the default transport protocol for "foo://". Notes ----- As far as I understand the rest of the RFC as well as the other examples provided, the port must not be quoted as stated in 7.2 ("port"): The presentation value of the SvcParamValue is a single decimal integer between 0 and 65535 in ASCII. 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
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
