SHALL and MUST are the same according to RFC 2119. 
-- 
Mark Andrews

> On 27 Feb 2026, at 17:28, RFC Errata System <[email protected]> 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/eid8787
> 
> --------------------------------------
> Type: Technical
> Reported by: Ulrich Windl <[email protected]>
> 
> 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.
> 
> 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 -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to