… and " OPTIONAL " in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174 when, and only when, they appear in all capitals, as shown here. The term "byte" is used in its now-customary sense as a synonym for "octet". All multi-byte values are encoded in netwo…

…with RFC 2119 The term not required is equivalent to the term may as defined in RFC2119 [RFC2119] Some terms have been capitalized in this document (and in other W3C materials) to indicate that they are entities with special relevance to the W3C Process. These terms are defined w…

…and " OPTIONAL " in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Conformance criteria and considerations regarding error handling are defined in Section 2 of [HTTP] 1.2. Syntax Nota…

…rpreted as described in Keywords for use in RFCs to indicate requirement levels RFC2119 ]. RFC-2119 keywords are formatted in uppercase and contained in an element with class="rfc2119" . When the keywords shown above are used, but do not share this format, they do not convey form…

…" in the normative parts of this document are to be interpreted as described in RFC2119. The key word "OPTIONALLY" in the normative parts of this document is to be interpreted with the same normative meaning as "MAY" and "OPTIONAL". For readability, these words do not appear in a…

…HOULD", "MUST", and "MUST NOT" are to be interpreted as described in RFC 2119 [ RFC2119 ]. However, for readability, these words do not appear in all uppercase letters in this specification. [6.1] RDF ::= ['< rdf :RDF>'] obj * ['</ rdf :RDF>'] [6.2] obj ::= description container …

…Words that denote a conformance clause or testable assertion use keywords from [RFC2119] must must not should recommended may and optional . The keywords must must not should recommended may and optional in this specification are to be interpreted as described in [RFC2119] Variab…

… and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [ RFC2119 ]. Character names in this document use the notation for code points and names from the Unicode Standard [ Unicode ]. For example, the letter "a" may be represented as either <U+0061> or <LATI…

…ed as described in "Key words for use in RFCs to Indicate Requirement Levels" [ RFC2119 ]. The interpretation should only be applied when the terms appear in all capital letters. 2 . Terminology The terms "JSON Web Signature (JWS)", "Base64url Encoding", "Header Parameter", "JOSE…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 3 . SCRAM-SHA-256 and SCRAM-SHA-256-PLUS The SCRAM-SHA-256 and SCRAM-SHA-256-PLUS SASL mechanisms are defined in the same way that SCRAM-SHA-1 and SCRAM-SHA-1-PLUS are defined in [ RFC5802 …

…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. The reader is assumed to be familiar with the terms used in the SAML 2.0 core specification [ OASIS-SAMLv2-CORE ]. 1.2 . Applicability Because this mechanism transports information that sho…

…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. Belshe & Peon Expires August 4, 2012 [Page 46] Internet-Draft SPDY Feb 2012 9 . Acknowledgements Many individuals have contributed to the design and evolution of SPDY: Adam Langley, Wan-Teh…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. As defined in [ RFC2781 ], the three charsets "utf-16", "utf-16le", and "utf-16be" are used to label UTF-16 text. In this document, "the UTF-16 family" refers to those three charsets. By co…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. Formal syntax is defined by [ RFC5234 ] including the core rules defined in Appendix B of [RFC5234] . Example lines prefaced by "C:" are sent by the client and ones prefaced by "S:" by the …

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. Uberti, et al. Expires August 31, 2019 [Page 6] Internet-Draft JSEP February 2019 3 . Semantics and Syntax 3.1 . Signaling Model JSEP does not specify a particular signaling model or state …