JamBot Logo
1-72 of about 72 matches for site:www.rfc-editor.org floor layer
https://www.rfc-editor.org/rfc/rfc8446
RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc5246.html
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc8446
RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc5246.html
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc9325
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used
https://www.rfc-editor.org/rfc/rfc5246
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc8446.html
RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc9325
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used
https://www.rfc-editor.org/rfc/rfc5246
RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc4346.html
RFC 4346: The Transport Layer Security (TLS) Protocol Version 1.1 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc4346
RFC 4346: The Transport Layer Security (TLS) Protocol Version 1.1 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc8446.html
RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata
https://www.rfc-editor.org/rfc/rfc4582
1 . Floor Participant to Floor Control Server Interface Floor participants request a floor by sending a
https://www.rfc-editor.org/rfc/rfc5018
order to generate forged floor requests or to grant or deny existing floor requests. Client impersonation is
https://www.rfc-editor.org/rfc/rfc9325.html
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used
https://www.rfc-editor.org/rfc/rfc7525
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are widely
https://www.rfc-editor.org/rfc/rfc7919
RFC 7919: Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS) [ RFC Home ] [ TEXT | PDF | HTML
https://www.rfc-editor.org/rfc/rfc3261.html
Internet Society (2002). All Rights Reserved. Abstract This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for
https://www.rfc-editor.org/rfc/rfc6716
4.2 . SILK Decoder .............................................. 32 4.2.1 . SILK Decoder Modules ............................... 32 4.2.2 . LP Layer Organization .............................. 33 4.2
https://www.rfc-editor.org/rfc/rfc6716
4.2 . SILK Decoder .............................................. 32 4.2.1 . SILK Decoder Modules ............................... 32 4.2.2 . LP Layer Organization .............................. 33 4.2
https://www.rfc-editor.org/rfc/rfc6716.html
4.2 . SILK Decoder .............................................. 32 4.2.1 . SILK Decoder Modules ............................... 32 4.2.2 . LP Layer Organization .............................. 33 4.2
https://www.rfc-editor.org/rfc/inline-errata/rfc6716.html
4.2. SILK Decoder ..............................................32 4.2.1. SILK Decoder Modules ...............................32 4.2.2. LP Layer Organization ..............................33 4.2
https://www.rfc-editor.org/rfc/rfc6716.txt
4.2. SILK Decoder ..............................................32 4.2.1. SILK Decoder Modules ...............................32 4.2.2. LP Layer Organization ..............................33 4.2
https://www.rfc-editor.org/rfc/rfc5836.txt
round trips needed for a new EAP exchange. Delays incurred within each protocol layer affect the ongoing
https://www.rfc-editor.org/rfc/rfc5836.html
round trips needed for a new EAP exchange. Delays incurred within each protocol layer affect the ongoing
https://www.rfc-editor.org/materials/abbrev.expansion.txt
Layer 2 Forwarding (L2F) L2SS - L2-Specific Sublayer (L2SS) L2TP - Layer 2 Tunneling Protocol (L2TP) L2VPN *- Layer 2 Virtual Private Network
https://www.rfc-editor.org/rfc/rfc6101.txt
Netscape Communications ISSN: 2070-1721 P. Kocher Independent Consultant August 2011 The Secure Sockets Layer (SSL) Protocol Version 3
https://www.rfc-editor.org/rfc/rfc871.txt
of which are to be modular. E.g., in the Host-Host layer of the
https://www.rfc-editor.org/rfc/inline-errata/rfc3261.html
rules defined by that layer. Not every element specified by the protocol contains every layer. Furthermore, the elements
https://www.rfc-editor.org/rfc/rfc3261.txt
rules defined by that layer. Not every element specified by the protocol contains every layer. Furthermore, the elements
https://www.rfc-editor.org/rfc/rfc2246.html
All Rights Reserved. Abstract This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The
https://www.rfc-editor.org/rfc/inline-errata/rfc3261.html
rules defined by that layer. Not every element specified by the protocol contains every layer. Furthermore, the elements
https://www.rfc-editor.org/rfc/rfc3261.txt
rules defined by that layer. Not every element specified by the protocol contains every layer. Furthermore, the elements
https://www.rfc-editor.org/info/rfc5018
Search RFCs Advanced Search RFC Editor RFC 5018 Connection Establishment in the Binary Floor Control Protocol (BFCP), September
https://www.rfc-editor.org/rfc/inline-errata/rfc4346.html
Independent Obsoletes: 2246 E. Rescorla Category: Standards Track RTFM, Inc. April 2006 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc4346.txt
Independent Obsoletes: 2246 E. Rescorla Category: Standards Track RTFM, Inc. April 2006 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc2246
All Rights Reserved. Abstract This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The
https://www.rfc-editor.org/rfc/rfc2246.txt
All Rights Reserved. Abstract This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The
https://www.rfc-editor.org/rfc/rfc5246.txt
4366 E. Rescorla Updates: 4492 RTFM, Inc. Category: Standards Track August 2008 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/inline-errata/rfc5246.html
4366 E. Rescorla Updates: 4492 RTFM, Inc. Category: Standards Track August 2008 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc3261
Internet Society (2002). All Rights Reserved. Abstract This document describes Session Initiation Protocol (SIP), an application-layer control (signaling) protocol for
https://www.rfc-editor.org/rfc/rfc6238
All the communications SHOULD take place over a secure channel, e.g., Secure Socket Layer/Transport Layer Security (SSL
https://www.rfc-editor.org/rfc/rfc6238
All the communications SHOULD take place over a secure channel, e.g., Secure Socket Layer/Transport Layer Security (SSL
https://www.rfc-editor.org/rfc/rfc9325.txt
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used
https://www.rfc-editor.org/rfc/inline-errata/rfc6026.html
agents) and proxies (proxies forward the response upstream, the transaction layer at user agents forwards
https://www.rfc-editor.org/rfc/inline-errata/rfc8446.html
6961 August 2018 Updates: 5705, 6066 Category: Standards Track ISSN: 2070-1721 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc6026.txt
agents) and proxies (proxies forward the response upstream, the transaction layer at user agents forwards
https://www.rfc-editor.org/rfc/rfc6026.html
agents) and proxies (proxies forward the response upstream, the transaction layer at user agents forwards
https://www.rfc-editor.org/rfc/rfc8446.txt
6961 August 2018 Updates: 5705, 6066 Category: Standards Track ISSN: 2070-1721 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc8725
to adhere to those stricter requirements. Furthermore, this document provides a floor, not a ceiling
https://www.rfc-editor.org/rfc/inline-errata/rfc8446.html
6961 August 2018 Updates: 5705, 6066 Category: Standards Track ISSN: 2070-1721 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc8446.txt
6961 August 2018 Updates: 5705, 6066 Category: Standards Track ISSN: 2070-1721 The Transport Layer Security (TLS) Protocol Version
https://www.rfc-editor.org/rfc/rfc8996.txt
Deprecating TLS 1.0 and TLS 1.1 Abstract This document formally deprecates Transport Layer Security (TLS) versions 1
https://www.rfc-editor.org/rfc/rfc9510
encode (v): if (v == 0) return (0, 0) if (v < 2 * C) // subnormal a = floor (v * 4 / C) // round
https://www.rfc-editor.org/rfc/inline-errata/rfc6238.html
All the communications SHOULD take place over a secure channel, e.g., Secure Socket Layer/Transport Layer Security (SSL
https://www.rfc-editor.org/rfc/rfc6238.txt
All the communications SHOULD take place over a secure channel, e.g., Secure Socket Layer/Transport Layer Security (SSL
https://www.rfc-editor.org/rfc/rfc9510.html
encode (v): if (v == 0) return (0, 0) if (v < 2 * C) // subnormal a = floor (v * 4 / C) // round
https://www.rfc-editor.org/rfc/rfc2543.txt
about the underlying transport and network-layer protocols. The lower-layer can provide either a
https://www.rfc-editor.org/rfc/rfc8725.html
to adhere to those stricter requirements. Furthermore, this document provides a floor, not a ceiling
https://www.rfc-editor.org/rfc/rfc8725
to adhere to those stricter requirements. Furthermore, this document provides a floor, not a ceiling
https://www.rfc-editor.org/rfc/rfc8725.txt
to adhere to those stricter requirements. Furthermore, this document provides a floor, not a ceiling
https://www.rfc-editor.org/rfc/rfc6760
is located. Furthermore, since many existing IP services such as lpr *do* already use additional application-layer demultiplexing information such as
https://www.rfc-editor.org/rfc/rfc4377
result in churn, alarm flapping, etc. 4.6 . Alarm Suppression, Aggregation, and Layer Coordination Network elements MUST
https://www.rfc-editor.org/rfc/rfc2476
a secure environment, by securing the submission connection at the transport layer, or by using an
https://www.rfc-editor.org/rfc/rfc5808
Figure 1 shows the assumed communication model for both a Layer 7 location configuration protocol
https://www.rfc-editor.org/rfc/rfc1213
interfaces to support IP. (For example, devices without IP, such as MAC-layer bridges, could not be
https://www.rfc-editor.org/rfc/rfc7748.html
a high level of practical security in cryptographic applications, including Transport Layer Security (TLS). These curves
https://www.rfc-editor.org/rfc/inline-errata/rfc7748.html
a high level of practical security in cryptographic applications, including Transport Layer Security (TLS). These curves
https://www.rfc-editor.org/bcp/bcp195.txt
and Datagram Transport Layer Security (DTLS) Abstract Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are widely
https://www.rfc-editor.org/rfc/rfc1907
current DESCRIPTION "The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location
https://www.rfc-editor.org/rfc/rfc6550.txt
Contents 1. Introduction ....................................................8 1.1. Design Principles ..........................................8 1.2. Expectations of Link-Layer Type ...........................10 2. Terminology
https://www.rfc-editor.org/rfc/rfc871
of which are to be modular. E.g., in the Host-Host layer of the