×
Past year
  • Any time
  • Past hour
  • Past 24 hours
  • Past week
  • Past month
  • Past year
All results
13 Jun 2023 · 1. Introduction. HTTP/3 [HTTP3] is a protocol defined on top of QUIC [RFC9000] that can multiplex HTTP requests over a QUIC connection. · 2. Protocol Overview · 3 ...
7 May 2024 · Using CSP allows authorization servers to specify multiple origins in a single response header field and to constrain these using flexible patterns (see ...
4 Mar 2024 · Protocol Overview. This document introduces a mapping of the Real-time Transport Protocol (RTP) to the QUIC transport protocol. RoQ allows the use of QUIC ...
16 Mar 2024 · The "IETF XML" Registry. This document registers two URIs in the "ns" subregistry of the IETF XML Registry [RFC3688]. Following the format in [ ...
24 Jun 2023 · Figure 2: Example: JWT using a Subject Identifier with the "sub_id" claim ... using a URI as defined in [RFC3986]. This ... in the application stack (e.g., using ...
14 Oct 2023 · 1. Loss behaviour. A Prague CCA MUST use a Reno-friendly congestion response (such as that of CUBIC [RFC9438] or Reno [RFC5681]) on detection of a loss (Req 2 ...
28 Feb 2024 · OAuth 2.0 for Browser-Based Apps. Abstract. This specification details the threats, attack consequences, security considerations and best practices that ...
17 Nov 2023 · 1. Introduction. 1.1. Document Roadmap. 1.2. Goals. 1.3. Terminology. 1.4. Recap of Existing ECN feedback in IP/TCP · 2. AccECN Protocol Overview and Rationale.
23 Feb 2024 · This document registers a URI in the "IETF XML Registry" [RFC3688]. ... For the same destination multiple DetNet flows use ... Ingress 1 192.0.2.2 Transit 1 Transit ...
5 Dec 2023 · Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP. Abstract. The purpose of this document is to guide the design of congestion ...