…of this specification. A discussion of the meanings of these terms appears in [ RFC2119 ]. 1.2.2 . Syntactic Notation This specification uses the Augmented Backus-Naur Form (ABNF) [ RFC5234 ] notation for the formal definitions of the syntax of messages. Characters will be specif…

…" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119] Requirements phrased in the imperative as part of algorithms (such as "strip any leading s…

…ords MAY , MUST , MUST NOT , and SHOULD are to be interpreted as described in [ RFC2119 ]. 4.1 Documents Conforming documents are those that comply with all the conformance criteria for JF2 documents. For readability, some of these conformance requirements are phrased as conforma…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. Note that all examples in this document are informative, and are not meant to be interpreted as normative requirements. A strictly conforming XHTML+RDFa document is a document that requires…

… 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. 3 . The SETTINGS_ENABLE_CONNECT_PROTOCOL SETTINGS Parameter This document adds a new SETTINGS parameter to those …

…ONAL, when they appear in this document, are to be interpreted as described in [RFC2119]. 3. Problem Statement and Considerations When a stateless IPv4/IPv6 translator receives an ICMPv6 message [RFC4443] (for example, "Packet Too Big") sourced from a non-IPv4- translatable IPv6 …

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

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

… 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 terms are used: client: The endpoint initiating the TLS connection. connection: A transport-layer c…

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

…ative except sections explicitly marked as non-normative, examples, and notes. [RFC2119] Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example" , like this: This is an example of an informative exam…

… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. Abbreviations: LDP Label Distribution Protocol LDPoIPv4 LDP-over-IPv4 transport connection LDPoIPv6 LDP-over-IPv6 transport connection FEC Forwarding Equivalence Class TLV Type Length Value…

…, RECOMMENDED , SHOULD , and SHOULD NOT are to be interpreted as described in [ RFC2119 ]. 1.3.1 Conformance Requirements Related to Selectors Not all Selectors are relevant for all media types; some combinations are meaningless or not formally defined. An implementation may ther…

… 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. 3 . Curve25519 and Curve448 Algorithm Identifiers Certificates conforming to [ RFC5280 ] can convey a public key …

…and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. All numeric values are in network byte order. Values are unsigned unless otherwise indicated. Literal values are provided in decimal or hexadecimal as appropriate. Hexadecimal literals are p…