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/eid8787 -------------------------------------- Status: Rejected Type: Technical Reported by: Ulrich Windl <[email protected]> Date Reported: 2026-02-27 Rejected by: Mohamed Boucadair (IESG) (IESG) Section: 2.2 Original Text ------------- (...) SvcParamKeys SHALL appear in increasing numeric order. Clients MUST consider an RR malformed if: the end of the RDATA occurs within a SvcParam. SvcParamKeys are not in strictly increasing numeric order. (...) Corrected Text -------------- (...) SvcParamKeys MUST appear in increasing numeric order. Clients MUST consider an RR malformed if: the end of the RDATA occurs within a SvcParam. SvcParamKeys are not in strictly increasing numeric order. (...) Notes ----- The protocol will only be successful if the DNS server must provide the SvcParamKeys in increasing numeric order, because the client will consider them malformed otherwise. Usually the principle "be strict what you send, but be liberal in what you accept" seems reversed here. --VERIFIER NOTES-- Per RFC2119: 1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. -------------------------------------- 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]
