… 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…

…o describe requirements. These keywords are to be interpreted as described in [ RFC2119 ]. 3.2 . RFC 2434 Keywords The keywords "PRIVATE USE", "HIERARCHICAL ALLOCATION", "FIRST COME FIRST SERVED", "EXPERT REVIEW", "SPECIFICATION REQUIRED", "IESG APPROVAL", "IETF CONSENSUS", and "…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ] when they appear in all upper case. They may also appear in lower or mixed case as English words, without normative meaning. Throughout this document, the term "local file" is used to descri…

…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Application-Layer Protocol Negotiation 3.1. The Application-Layer Protocol Negotiation Extension A new extension type ("application_layer_protocol_negotiation(16)") is defined and MAY be …

…, "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. ECDHE_PSK Key Exchange Algorithm The cipher suites described in this document make use of the elliptic curve (EC) parameter negotiation mechanism defined in RFC 4492. When the cipher suit…

…and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. This document also reuses the SIP terminology defined in [RFC3261] and [RFC3265], and it specifies the usage of the following terms. Device: software or hardware entity containing one or mor…

…, 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 following terminology is defined. Relevant terms are directly copied from [RFC4821], and the definitions in [RFC…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 2 . Problem Statement In addition to IIDs formed from IEEE EUI-64 addresses, various new forms of IIDs have been defined, including temporary addresses [ RFC4941 ], Cryptographically Genera…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. The following definitions are used in this document: o A WebRTC browser (also called a WebRTC User Agent or WebRTC UA) is something that conforms to both the protocol specification and the …