… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. The following terms are used throughout this document: Web PKI: The Public Key Infrastructure (PKI) model employed by browsers to authenticate web servers. This employs a set of trusted pub…
…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 …
…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. 3 . Acronyms AC Attachment Circuit BPDU Bridge Protocol Data Unit CE Customer Edge device FEC Forwarding Equivalence Class FIB Forwarding Information Base GRE Generic Routing Encapsulation …
… 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…
… "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. The following terms or concepts are used throughout this document: Man-in-the-middle (MITM) attack: Active modification of network traffic by an adversary able to thereby compromise the con…
…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. 2 . Suite B and Secure Shell Several RFCs have documented how each of the Suite B components are to be integrated into Secure Shell (SSH): kex algorithms ecdh-sha2-nistp256 [ SSH-ECC ] ecdh…
…nd " 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. ¶ As noted above, the core problem this specification attempts to address is the situation where even after local…
…nd "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [ RFC2119 ]. This document uses the same terminology as ICE (see Section 3 of [RFC5245] ). 3 . Overview of Operation The usage of ICE with TCP is relatively straightforward. This specification mainly de…