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/eid8168

--------------------------------------
Status: Rejected
Type: Editorial

Reported by: Julian Keck <[email protected]>
Date Reported: 2024-11-04
Rejected by: Warren Kumari (Ops AD) (IESG)

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.


[WK: Rejecting this errata with a note from the DNSOP list: 
https://mailarchive.ietf.org/arch/msg/dnsop/BHLZtTaDLiHcMWe2NDnl_HJ0RwM/

Text: 
"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"
 --VERIFIER NOTES-- 
 Thank you for the Errata report. 

I'm rejecting it as per: 
https://mailarchive.ietf.org/arch/msg/dnsop/BHLZtTaDLiHcMWe2NDnl_HJ0RwM/

Thanks again,
Warren (Ops AD)

--------------------------------------
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 -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to