| Internet-Draft | HTTP over Mcast QUIC | July 2022 |
| Pardue, et al. | Expires 5 January 2023 | [Page] |
This document specifies a profile of the QUIC protocol and the HTTP/3 mapping that facilitates the transfer of HTTP resources over multicast IP using the QUIC transport as its framing and packetisation layer. Compatibility with the QUIC protocol's syntax and semantics is maintained as far as practical and additional features are specified where this is not possible.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 5 January 2023.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The means to bulk transfer resources over multicast IP [RFC1112] using HTTP semantics presents an opportunity to more efficiently deliver services at scale, while leveraging the wealth of existing HTTP-related standards, tools and applications. Audio-visual segmented media, in particular, would benefit from this mode of transmission.¶
The carriage of HTTP over multicast IP may be satisfied using existing technologies, for example the Real-time Transport Protocol (RTP) [RFC3550], File Delivery over Unidirectional Transport (FLUTE) [RFC6726], and NACK-Oriented Reliable Multicast (NORM) [RFC5740]. However, such protocols typically require the translation or encapsulation of HTTP. This introduces concerns for providers of services, such as defining the translation, additional workload, complication of workflows, manageability issues, versioning issues, and so on.¶
In contrast, this document describes a simpler and more direct expression of HTTP semantics over multicast IP. HTTP over multicast QUIC is a profile of the QUIC protocol [RFC9000] (Section 4) and the HTTP/3 mapping [RFC9114] (Section 5). This includes the repurposing of certain QUIC packet fields and changes to some protocol procedures (e.g. prohibition of the usage of certain frame types) which, in turn, change the behavioural expectations of endpoints. However, the profile purposely limits the scope of change in order to preserve maximum syntactic and semantic compatibility with conventional QUIC. For the reader's convenience, the differences between this specification and conventional QUIC are summarised in Appendix C.¶
This profile prohibits the transmission of QUIC packets from receiver to sender via multicast IP. The use of side-channel or out-of-band feedback mechanisms is not prohibited by this specification, but is out of scope and these are not considered further by the present document.¶
Experience indicates that a generally available multicast deployment is difficult to achieve on the Internet notwithstanding the improvements that IPv6 [RFC8200] makes in this area. There is evidence that discretely referenced multicast "islands" can more pragmatically be deployed. Discovery of such islands by receivers, as they become available, is typically difficult, however. To address the problem, this document describes an HTTP-based discovery mechanism that uses HTTP Alternative Services [RFC7838] to advertise the existence of multicast QUIC sessions (Section 3). This provides the means for multicast-capable endpoints to learn about and make use of them in an opportunistic and user-imperceptible manner. This mechanism results in a common HTTP application layer for both the discovery and delivery of services across unicast and multicast networks. This provides support for users and devices accessing services over a heterogeneous network. This is a departure from conventional multicast discovery technologies such as SDP [RFC8866] and SAP [RFC2974].¶
The discovery mechanism also addresses some of the issues related to using QUIC over a unidirectional network association by replacing connection establishment aspects that depend on a bidirectional transport.¶
The present document includes a number of optional features. It is anticipated that further specifications will define interoperability profiles suited to particular application domains.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all captials, as shown here.¶
This document uses the Augmented BNF defined in [RFC5234] and updated by [RFC7405] along with the "#rule" extension defined in Section 7 of [RFC7230]. The rules below are defined in [RFC5234], [RFC7230], and [RFC7234]:¶
Definitions of terms that are used in this document:¶
A QUIC connection [RFC9000] carried over bidirectional unicast is defined as a conversation between two QUIC endpoints that multiplexes several logical streams within a single encryption context. This is a one-to-one relationship. Furthermore, QUIC connections achieve decoupling from the underlying network (IP and port) by means of a set of Connection IDs, with each endpoint generating these IDs and using them to identify the direction of flow. Use of a consistent connection identifier allows QUIC connections to survive changes to the network connectivity. The establishment of a QUIC connection relies upon an up-front, in-band exchange (and possible negotiation) of cryptographic and transport parameters (conveyed in QUIC handshake messages).¶
The mapping of HTTP semantics over the QUIC transport protocol [RFC9114] facilitates the transfer of hypermedia over QUIC connections. The establishment of a HTTP/3 connection relies upon all the requirements stipulated for the transport, as well as communication of HTTP-specific settings (conveyed in HTTP/3 SETTINGS frames). Such parameters may be required or optional and may be used by either endpoint to control the characteristics of connection usage.¶
This concept of a connection does not suit the carriage of HTTP/3 over unidirectional network associations such as multicast IP. In fact, there is no requirement for either endpoint (multicast sender or receiver) to be in existence in order for the other to start or join this one-sided conversation. The term "connection" is misleading in this context; therefore we introduce an alternative term "multicast QUIC session" or simply "session", which is defined as the logical entity describing the characteristics of the anticipated unidirectional flow of metadata and data. Such characteristics are expressed as "session parameters", described in Section 2.2. Advertisement of multicast QUIC sessions, specified in Section 3, allows for the senders and receivers to discover a session and to form multicast IP network associations that permit traffic flow.¶
The lifecycle of a multicast QUIC session is decoupled from the lifecycle of any particular endpoint. Multicast receivers or senders that take part in a session are called participants. The state of a session is influenced by the actions of participants. The loose coupling of participants means that they are unlikely to have a consistent shared view of the current state of a session. There is no requirement for a participant to know the session state and the present document does not define a method to explicitly determine it. The definitions of session states provided below are intended to assist higher-level operational treatment of sessions:¶
Permitted states transitions are shown in Figure 1 below.¶
The transmission of QUIC packets is expected to occur only during the Half-Established and Fully-Established states.¶
+-----------+ +------------------+ +-------------------+
| |-------->| |------->| |
| Quiescent | | Half-Established | | Fully-Established |
| |<--------| |<-------| |
+-----------+ +------------------+ +-------------------+
| |
| v
| +----------+
| | |
+------------------>| Finished |
| |
+----------+
A session begins in the Quiescent state. A typical session establishment sequence would see the transition from Quiescent to Half-Established when a sender joins the session. The transition from Half-Established to Fully-Established occurs when at least one receiver joins the session.¶
It is equally valid for a receiver to join a session in the Quiescent state, triggering the transition to Half-Established. In this case, the transition to Fully-Established takes place only when a sender joins the session.¶
Participants MAY leave a session at any time. A session enters the Finished state when all participants have left it. Senders MAY signal their intent to leave using explicit session tear-down (Section 5.4). Receivers can detect that a sender has left via idle timeout (Section 3.3) and take that as a signal to leave, or receivers may leave as part of session migration (described in the next section).¶
In a typical case, a session that is in the Fully-Established state would be closed in two stages. In the first stage the sender sends explicit shutdown messages to the multicast group and subsequently stops transmitting packets. This causes the session to transition from Fully-Established to Half-Established. In the second stage, receivers that have received explicit shutdown messages leave the multicast group. Once all receivers have left the session it transitions from Half-Established to Finished.¶
The transition from Quiescent to Finished could also occur in response to out-of-band actions, for example the availability of a session being withdrawn without any participants having made use of it.¶
Endpoints MAY migrate between multicast QUIC sessions (for example, to make use of alternate session parameters that are preferred). Session migration requires participants to leave the current session and join the new session. These actions affect the state of the respective sessions as explained above.¶
The discovery of multicast QUIC sessions is described in Section 3.¶
The characteristics of multicast QUIC sessions are expressed as session parameters, which cover cryptographic and transport parameters, HTTP-specific settings and multicast-specific configuration.¶
Session parameter exchange over IP multicast is difficult:¶
A range of strategies exists to mitigate these points. However, each has the possibility to add complexity to deployment and manageability, transmission overhead, or other such concerns. This document defines a solution that relies on the one-way announcement of session parameters in advance of session establishment. This is achieved using HTTP Alternative Services [RFC7838] and is explained in Section 3. Other advertisement solutions are not prohibited but are not explored in this document.¶
Session parameters MUST NOT change during the lifetime of a session. This restriction also applies to HTTP-level settings (see Section 5.1).¶
This document defines an optional session identifier used to identify a session. This "Session ID" affords independence from multicast IP, creating the possibility for a session to span multiple multicast groups, or to migrate a session to a different multicast group. Assignment of Session ID is considered out of this document's scope.¶
The Session ID is carried in the Destination Connection ID field of the QUIC packet (see Section 4.3). Source Connection IDs are not used.¶
The maximum size of a Session ID is 160 bits. The size of the Destination Connection ID field used to convey the Session ID SHALL be the smallest number of full bytes required to represent the full Session ID value advertised in the session-id session parameter (Section 10.2.4). If no session-id parameter is advertised, then this session has a zero-length session ID, and the Destination Connection ID field SHALL be omitted from all QUIC packets related to the session.¶
A multicast sender participating in a session with an advertised session-id session parameter MUST send QUIC packets with a matching Session ID. Conversely, a multicast sender participating in a session without an advertised session-id session parameter MUST NOT send QUIC packets with a non-zero-length Destination Connection ID field.¶
A multicast receiver participating in a session with an advertised session-id session parameter MUST validate that the Session ID of received QUIC packets matches that advertised in the session parameters (Section 10.2.4) before any HTTP-level processing is done. In the case of validation failure, the receiver SHOULD ignore the packet in order to protect itself from denial-of-service attacks.¶
The QUIC cryptographic handshake ([RFC9000] and [RFC9001]) sets out methods to achieve the goals of authenticated key exchange and QUIC packet protection between two endpoints forming a QUIC connection. The design facilitates low-latency connection; 1-RTT or 0-RTT. This specification replaces the in-band security handshake, achieving similar goals through the use of session parameters described in Section 3.1.¶
Integrity and authenticity concerns are addressed in Section 6.1 and Section 6.2 respectively. In order to protect themselves from attack vectors, endpoints SHOULD NOT participate in sessions for which they cannot establish reasonable confidence over the cipher suite or key in use for that session. Participants MAY leave any session that fails to successfully match anticipated security characteristics.¶
In this specification, connection negotiation is replaced with a session advertisement mechanism based on HTTP Alternative Services (Alt-Svc) [RFC7838]. This document specifies how the parameters of a multicast QUIC session are expressed as Alt-Svc parameters. The following sections provide a high-level view of these; further details are provided in Section 10.2, with examples provided in Appendix B.1. QUIC connection parameters not defined as, or related to, Alt-Svc parameters are not used.¶
The definition of a session (including the session ID and its parameters) is not the responsibility of any endpoint. Rather, endpoints SHOULD use session advertisements to determine if they are capable of participating in a given session. This document does not specify which party is responsible for defining and/or advertising multicast QUIC sessions.¶
Endpoints SHOULD NOT become participants in sessions where the advertisement requirements set out in the present document are unfulfilled.¶
The freshness of Alt-Svc multicast QUIC session advertisements is as described in section 2.2 of [RFC7838].¶
It is RECOMMENDED that session advertisements are carried over a secure transport (such as HTTPS) which can guarantee the authenticity and integrity of the Alt-Svc information. This addresses some of the concerns around the protection of session establishment described in Section 11.2.¶
Authors' Note: We invite review comments on mandating the use of a secure transport for advertising sessions.¶
Senders MAY also advertise the availability of alternative sessions by carrying Alt-Svc in a multicast QUIC session.¶
This specification replaces the in-band security handshake. The session parameters "cipher suite", "key" and "iv" (described below) allow for the establishment of a security context. In order to protect themselves, endpoints SHOULD NOT participate in sessions for which they cannot establish reasonable confidence over the cipher suite, key, or IV in use for that session. Endpoints SHOULD leave any sessions which fail to successfully match anticipated security characteristics.¶
Cipher suite negotiation is replaced with a "cipher suite" session parameter, which is advertised as the Alt-Svc parameter cipher-suite (Section 10.2.1).¶
The Alt-Svc "cipher-suite" parameter is OPTIONAL. If present, this parameter MUST contain only one value that corresponds to an entry in the TLS Cipher Suite Registry (see http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4). Session advertisements that omit this parameter imply that the session is operating with cipher suite 0x00,0x00 (NULL_WITH_NULL_NULL).¶
Key exchange is replaced with a "key" session parameter, which is advertised as the Alt-Svc parameter key (Section 10.2.2). The parameter carries a variable-length hex-encoded key for use with the session cipher suite.¶
The Alt-Svc "key" parameter is OPTIONAL. Session advertisements that omit this parameter imply that the key may be available via an out-of-band method not described in this document.¶
Initialization Vector (IV) exchange is replaced with an "iv" session parameter, which is advertised as the Alt-Svc parameter iv (Section 10.2.3). The parameter carries a variable-length hex-encoded IV for use with the session cipher suite and key.¶
The Alt-Svc "iv" parameter is OPTIONAL. Session advertisements that omit this parameter imply that the IV may be available via an out-of-band method not described in this document.¶
[RFC9000] specifies how the QUIC connection identifiers are used, in particular the independent selection of these identifiers by each endpoint for its peer. In a unidirectional multicast environment, there is no meaningful way for an endpoint to generate a connection identifier for its peer to use. This document defines a "session identifier" session parameter, which is advertised as the Alt-Svc parameter "session-id" (Section 10.2.4). The requirements for the usage of session identifiers have already been described in Section 2.3.¶
The Alt-Svc "session-id" parameter is optional. Session advertisements MAY contain at most one instance of a "session-id" parameter. Session advertisements that identify the same Any Source Multicast group {G} or Source Specific Multicast group {S,G} indicate that multiple sessions are multiplexed in the same multicast group and each such advertisement must carry a unique "session-id".¶
Conventional QUIC connections may be implicitly terminated following a period of idleness (lack of network activity). The optional QUIC TransportParameter max_idle_timeout provides a means for endpoints to specify the timeout period. This document defines a "session idle timeout" session parameter, which is advertised as the Alt-Svc parameter "session-idle-timeout" (Section 10.2.5). This session parameter mimics the behaviour of max_idle_timeout, providing a means for multicast QUIC sessions to define their own idle timeout periods.¶
Session idle timeout may be prevented by keep-alive strategies Section 4.10.¶
The Alt-Svc "session-idle-timeout" parameter is optional. Session advertisements MAY contain zero or more instances of this parameter. If it is repeated, the first occurrence MUST be used and subsequent occurrences MUST be ignored. Session advertisements that omit the "session-idle-timeout" parameter, or set it to zero never time out.¶
Receiving participants SHOULD leave multicast QUIC sessions when the session idle timeout period has elapsed (Section 4.7). Leaving participants MUST use the silent close method, in which no QUIC CONNECTION_CLOSE frame is sent.¶
[RFC9000] specifies a credit-based stream- and connection-level flow control scheme which prevents a fast sender from overwhelming a slow receiver at the stream level, as well as an aggregate level of all streams. Window size connection parameters are exchanged on connection establishment using the required QUIC TransportParameters initial_max_data, initial_max_stream_data_bidi_local, initial_max_stream_data_bidi_remote and initial_max_stream_data_uni. In a unidirectional multicast environment, such a scheme is infeasible.¶
This document defines a "peak flow rate" session parameter, expressed in units of bits per second, which is advertised as the Alt-Svc parameter "peak-flow-rate" (Section 10.2.7). This completely replaces the transport parameters listed above, instead indicating the maximum bit rate of QUIC payloads transmitted on all multicast groups comprising the session. It applies at the aggregate level, and is not specific to any single stream.¶
The Alt-Svc "peak-flow-rate" parameter is OPTIONAL. If the parameter is repeated the first occurrence MUST be used and subsequent occurrences MUST be ignored. Session advertisements that omit the parameter imply that the flow rate is unlimited.¶
A multicast sender SHOULD NOT cause the advertised peak flow rate of a session to be exceeded. A receiver MAY leave any session where the advertised peak flow rate is exceeded.¶
[RFC9000] considers concurrency in terms of the number of active incoming streams, which is varied by the receiving endpoint adjusting the maximum Stream ID. The initial value of maximum Stream ID is controlled by the relevant required QUIC TransportParameters initial_max_streams_bidi and initial_max_streams_uni. They are increased during the lifetime of a QUIC connection by the QUIC MAX_STREAMS frame. In a unidirectional multicast environment, there is no way for a receiver to specify an initial limit nor to increase it. Therefore in multicast QUIC, the maximum Stream ID (initial and always) is 2^62. This mechanism is not used to manage concurrency in multicast QUIC.¶
Due to the profiling of maximum Stream ID, there is no role for the QUIC STREAMS_BLOCKED frame and it is prohibited. Participants MUST NOT send this frame type. Reception of this frame type MUST be handled as described in Section 4.12.¶
This document specifies a "maximum concurrent resources" session parameter, which is advertised as the Alt-Svc parameter "max-concurrent-resources" (Section 10.2.6). This parameter replaces initial_max_stream_id_bidi and initial_max_stream_id_uni. It advertises the maximum number of concurrent active resources generated by a sender in a given multicast QUIC session.¶
The Alt-Svc "max-concurrent-resources" parameter is OPTIONAL. If the parameter is repeated the first occurrence MUST be used and subsequent occurrences MUST be ignored. Session advertisements that omit the parameter imply that the maximum concurrency is unlimited.¶
A multicast sender participating in a session MUST NOT cause the advertised "max-concurrent-resources" to be exceeded. A receiver MAY leave any session where the advertised limit is exceeded, in order to protect itself from denial-of-service attacks.¶
Authors' Note: This section will consider TransportParameters that have not already been addressed, as required.¶
Section 19.21 of [RFC9000] defines a mechanism for endpoints to show willingness to receive one or more extension frame types. It is not possible for multicast QUIC receivers to signal this information to senders.¶
This document defines an "extensions" session parameter, which is advertised as the Alt-Svc parameter "extensions" Section 10.2.10 and replaces the transport parameter exchange detailed above. The Alt-Svc "extensions" parameter is optional. Session advertisements MAY contain zero or more instances of this parameter. The parameter lists transport parameter values present in the QUIC Transport Parameter Registry as specified in Section 22.3 of [RFC9000].¶
Only transport parameters which expressly reference Multicast QUIC are considered valid extension parameters.¶
Authors' Note: The authors welcome suggestions for how to map these extension types more cleanly into this document.¶
Participants SHOULD NOT join sessions advertising extensions that they do not support, as QUIC frames are not self-describing.¶
A method to provide content integrity is described in Section 6.1. This specifies the means to convey a value computed by a particular digest algorithm. The identity of the selected algorithm is also indicated. Valid digest algorithms are collected in the IANA HTTP Digest Algorithm Values registry (http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml#http-dig-alg-1).¶
This document specifies a "digest algorithm" session parameter, which is advertised as the Alt-Svc parameter "digest-algorithm" (Section 10.2.8).¶
Authors' Note: Section 6.1 contains an author's note on the potential for content integrity to become mandatory. This section will be updated in line with the outcome of that decision.¶
The Alt-Svc "digest-algorithm" parameter is OPTIONAL. Repetition of the "digest algorithm" parameter in a single advertisement describes an algorithm set that MAY be used across the session. Session advertisements that omit the Alt-Svc parameter digest-algorithm imply that either:¶
Advertising the algorithm set for a session gives receivers the opportunity to selectively join sessions where the algorithms are known to be supported. This may help to mitigate latency issues in the receiver resulting from joining a session only to discover some of its parameters are not supported.¶
A multicast sender participating in a session MUST NOT use algorithms outside the signalled digest algorithm set. A receiver MAY leave any session where an algorithm outside the digest algorithm set is used.¶
A method to provide content authenticity is described in Section 6.2. This specifies the means to convey a value computed by a particular signature algorithm. The identity of the selected algorithm is also indicated. Valid signature algorithms are collected in the IANA Signature Algorithms registry (http://www.iana.org/assignments/signature-algorithms).¶
This document specifies a "signature algorithm" session parameter, which is advertised as the Alt-Svc parameter signature-algorithm (Section 10.2.9).¶
Authors' Note: Section 6.2 contains an author's note on the potential for content authenticity to become mandatory. This section will be updated in line with the outcome of that decision.¶
The Alt-Svc "signature-algorithm" parameter is OPTIONAL. Repetition of the "signature algorithm" parameter in a single advertisement describes an algorithm set that MAY be used across the session. Session advertisements that omit the Alt-Svc parameter signature-algorithm imply that either:¶
Advertising the algorithm set for a session gives receivers the opportunity to selectively join sessions where the algorithms are known to be supported. This may help to mitigate latency issues in the receiver resulting from joining a session only to discover some of its parameters are not supported.¶
A multicast sender participating in a session MUST NOT use algorithms outside the signalled signature algorithm set. A receiver MAY leave any session where an algorithm outside the signature algorithm set is used.¶
The profile of [RFC9000] is presented in this section. In order to preserve compatibility with conventional QUIC, the specification works with a limited scope of change. However, the nature of unidirectional multicast communications means that some protocol procedures or behaviours need to be modified.¶
Section 5.3 of [RFC9000] defines a set of required actions that a QUIC server and QUIC client must be able to perform. Due to the limitations of this profile, all of the requirements in Section 5.3 of [RFC9000] are removed except for:¶
PING frames to stop a session from expiring as described in Section 4.10.¶
The means for determining an appropriate size for QUIC packets are described in Section 14 of [RFC9000]. Implementations of this specification SHOULD bear in mind that the Path Maximum Transmission Unit (PMTU) may be affected by multicast IP technologies such as Automatic Multicast Tunneling (AMT) [RFC7450]. Additionally, consideration should be given toward the applicability of maximum transmission unit discovery methods (such as PLPMTUD [RFC4821] and PMTUD [RFC1191]) to multicast IP.¶
Endpoints implementing this specification MUST only send QUIC packets with the short header form. As short header packets do not include a length, senders MUST NOT attempt to coalesce any QUIC packets in the same UDP datagram. Therefore, all UDP datagrams sent by senders conforming to this profile contain exactly one QUIC packet.¶
All packets for this profile SHALL be numbered in the application data packet number space. The initial and handshake packet number spaces are not used by this profile, as the handshake is replaced by an out-of-band mechanism (see Section 2.4).¶
The encoding of packet numbers in QUIC packets is described in Section 17.1 of [RFC9000]. Senders must always use the same number of bytes to represent the packet number for all packets sent to a session. Because a receiver may join a session after the sender has already sent several packets, it MUST NOT assume that the first packet number will be 0.¶
[RFC9000] specifies a bit in the 1-RTT packet header as the latency spin bit that may be used to measure network round trip latency between a client and a server. This mechanism is not usable in a unidirectional multicast packet flow. Senders SHALL set the spin bit to zero in all packets. Receivers SHOULD ignore the spin bit.¶
Authors' Note: The authors welcome suggestions for the use of the spin bit in a multicast context.¶
The Destination Connection ID field MUST be non-zero-length in every QUIC packet if the session was advertised with a session-id session parameter (Section 10.2.4). If the multicast QUIC session advertisement does not carry a "session identifier" session parameter, then the Destination Connection ID MUST be zero-length in any QUIC packet for that session. In the case where multiple sessions are multiplexed on the same 5-tuple network association, the Destination Connection ID field MUST be non-zero-length in every QUIC packet and must be distinct for each session.¶
The maximum Stream ID of a multicast QUIC session is 2^62, as explained in Section 3.5. With the exception of the first client-initiated request Stream ID, which is reserved as described in Section 5.2, all Stream ID values SHALL be of the server-initiated unidirectional stream type.¶
Conventional QUIC provides stream- and connection-level flow control, and endpoints manage this by sending QUIC MAX_DATA or MAX_STREAM_DATA frames as required. When a sender is blocked from sending flow-controlled frames, it sends an informational QUIC DATA_BLOCKED or STREAM_DATA_BLOCKED frame.¶
In a unidirectional environment, the sender never has a receive window and the receiver cannot send in-band updates. Therefore, the management of flow-control windows and transmission of blockage information is not supported by this profile. The QUIC MAX_DATA, MAX_STREAM_DATA, DATA_BLOCKED and STREAM_DATA_BLOCKED frames are prohibited by this profile. Participants MUST NOT send these frame types. Reception of these frame types MUST be handled as described in Section 4.12.¶
A sender MAY prematurely terminate the transmission on any unreserved QUIC Stream ID by setting the FIN bit of a QUIC STREAM frame, or by sending a QUIC RESET_STREAM frame (as specified in [RFC9000] and [RFC9114]).¶
Receiving participants MUST NOT make any attempt to send QUIC RESET_STREAM frames to the multicast group.¶
Explicit shutdown of a multicast QUIC session using QUIC methods is not supported by this profile.¶
The QUIC CONNECTION_CLOSE frames and the Stateless Reset packet are prohibited. Participants MUST NOT send these and reception MUST be handled as described in Section 4.12.¶
Explicit session tear-down using HTTP semantics is allowed, as described in Section 5.4.¶
Implicit shutdown by means of silent close is also supported, as described in Section 3.3.¶
[RFC9000] has a connection migration feature that allows a connection to survive changes to endpoint addresses. This profile does not currently support connection migration, and as such the QUIC NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames are prohibited. Similarly, the QUIC PATH_CHALLENGE and PATH_RESPONSE frames are also prohibited, but additionally because they require bidirectional capability that this profile does not provide.¶
Endpoints participating in a session conforming to this profile MUST only use a single session ID for the duration of the session, and as such there is no mapping for the active_connection_id_limit transport parameter specified in section 5.1.1 of [RFC9000] in this profile.¶
Author's Note: Seamless migration from one multicast QUIC session to another is described in Section 2.1.3.¶
[RFC9000] specifies that clients may use Explicit Congestion Notification (ECN) [RFC3168]. ECN allows receivers to inform senders of impending congestion before packets are dropped, and the sender may then reduce its transmission rate. As ECN requires bidirectional communication for the receiver to inform the sender of the congestion, the use of ECN for this profile is prohibited.¶
Author's Note: It is the responsibility of a receiver to determine whether network conditions permit the uncongested reception of a given session based on the advertised peak-flow-rate parameter.¶
The flow of traffic in a multicast QUIC session is driven by a sender. There may be periods where the sender has no application data to send for a period longer than the session idle timeout. This profile repurposes the QUIC PING frame to act as a unidirectional keep-alive message that may be sent in order to inform receivers that the session should remain in the Fully-established state. [RFC9000] contains guidance on the sending frequency of QUIC PING frames.¶
Senders MAY send a QUIC PING frame at any time in order to inform receivers that the session traffic flow has not fallen idle. This frame MUST NOT be acknowledged. Indeed, QUIC ACK frames are prohibited by this profile (Section 4.11).¶
Receiving participants MUST NOT make any attempt to send QUIC PING frames.¶
Receivers implementing this profile MUST NOT make any attempt to acknowledge the reception of QUIC packets. The QUIC ACK frame is prohibited for both senders and receivers. Reception of this frame MUST be handled as described in Section 4.12.¶
Section 7 specifies alternative strategies for loss recovery.¶
The following QUIC packets MUST NOT be transmitted by participants: Any packets with a long header (Initial, 0-RTT Protected, Handshake, Retry), Version Negotiation, Stateless Reset.¶
The following QUIC frames MUST NOT be transmitted by participants: ACK, CONNECTION_CLOSE, CRYPTO, DATA_BLOCKED, HANDSHAKE_DONE, MAX_DATA, MAX_STREAM_DATA, MAX_STREAMS, NEW_CONNECTION_ID, NEW_TOKEN, PATH_CHALLENGE, PATH_RESPONSE, RETIRE_CONNECTION_ID, STOP_SENDING, STREAM_DATA_BLOCKED, STREAMS_BLOCKED.¶
In addition, any QUIC extension frames not advertised in the session advertisement Section 3.6 MUST NOT be transmitted by participants.¶
The following QUIC frames MUST NOT be transmitted by receivers: PING, RESET_STREAM.¶
Reception of a prohibited or non-advertised QUIC frame or packet is a protocol error. Receivers MUST ignore all prohibited QUIC frames and packets.¶
HTTP over multicast QUIC depends on HTTP server push, as described in Section 4.6 of [RFC9114]. Section 5.2 below applies an additional constraint on the use of server push. A multicast sender participating in a session pushes resources as a series of QUIC STREAM frames carrying HTTP/3 PUSH_PROMISE, HEADERS and DATA frames. Examples of this are provided in Appendix B.2. Senders MUST comply with the requirements of the session parameters, as described earlier in Section 3.¶
The profile of HTTP/3 specified in this section places additional constraints on the use of metadata compression (Section 5.3).¶
The HTTP/3 SETTINGS frame is prohibited by this profile. Participants MUST NOT make any attempt to send this frame type. Reception of this frame MUST be handled as described in Section 5.7.¶
Server push is, by default, disabled for HTTP/3 connections. A conventional HTTP/3 client enables and manages server push by controlling the maximum Push ID ([RFC9114], Section 7.2.7), achieved by sending the HTTP/3 MAX_PUSH_ID frame.¶
This profile mandates the use of server push, and specifies no means to disable it. The maximum Push ID for multicast QUIC sessions (initial and always) is 2^62. Values of Push ID SHALL be allocated in accordance with [RFC9114].¶
Server push concurrency in multicast QUIC is described in Section 3.5. There is no role for the HTTP/3 MAX_PUSH_ID frame and it is prohibited. Participants MUST NOT send this frame type. Reception of this frame type MUST be handled as described in Section 5.7.¶
For this profile, the Stream Type for any new server-initiated unidirectional stream MUST be Server Push (0x01).¶
The HTTP/3 CANCEL_PUSH frame MAY be used by sending participants to abort sending a response for the identified server push. Usage of this frame SHALL follow the guidance for servers in [RFC9114].¶
Receiving participants MUST NOT make any attempt to send HTTP/3 CANCEL_PUSH frames to the multicast group.¶
Receiving participants SHOULD ignore all frames on server-initiated unidirectional streams for which the packet containing the Push ID has not been received. Receiving participants SHOULD ignore all frames on server-initiated unidirectional streams carrying a Push ID that was not previously promised to the receiver.¶
Conventionally, pushed responses are associated with an explicit request from a client. This is not possible when using a unidirectional transport such as multicast IP. This profile reserves the first client-initiated, bidirectional QUIC stream. HTTP/3 PUSH_PROMISE frames MUST be sent on this reserved Stream ID.¶
The compression of HTTP header fields is considered in QPACK [RFC9204], which describes two methods for the compression of HTTP header fields: indexing (via static or dynamic tables) and Huffman encoding.¶
A multicast QUIC session, as described in the present document, does not provide the assurances (receiver participation, transport reliability) required to sufficiently maintain the dynamic decoding context. Therefore, this document requires that endpoints SHALL NOT use dynamic table indexing. It is RECOMMENDED that endpoints use static table indexing and/or Huffman encoding in order to benefit from the remaining compression methods available.¶
A multicast QUIC session MAY be explicitly torn down by means of the Connection: close HTTP header described in section 6.6 of [RFC7230]. A sender intending to leave the session SHOULD include the Connection: close header in its response metadata. A sender SHOULD transmit all outstanding frames related to remaining request/response exchanges before ending transmission to the multicast group. A receiver SHOULD continue to receive and process frames until all outstanding request/response exchanges are complete.¶
The HTTP/3 GOAWAY frame is prohibited. Participants MUST NOT send this and reception MUST be handled as described in Section 5.7.¶
Since multicast QUIC is an inherently unreliable delivery mechanism, portions of HTTP messages sent by the sender may not be received by the receiver. Conventional HTTP/3 frames assume reliable, in-order delivery by the underlying QUIC stream. HTTP/3 frames do not therefore carry any information indicating their position within the stream, because this information is instead carried in the QUIC STREAM frame header.¶
In multicast QUIC, packet loss leaves gaps in the flow of a stream, and therefore gaps in the HTTP/3 frame(s) that are carried on that stream.¶
PUSH_PROMISE frame renders the reception of an entire stream impossible, since the receiver ignores the new push stream that has not been promised as described in Section 5.2.¶
HEADERS frame will likely prevent the QPACK decoder from successfully parsing the received metadata, leaving the receiver unable to make use of the affected HTTP representation.¶
DATA frame header leaves a receiver unsure where to look for the start of the next HTTP/3 frame on the same stream. In the unlikely event that the receiver manages to resynchronise to the start of a subsequent HTTP/3 DATA frame, the position of the payload in the HTTP representation data is unknown because it is not explicitly signalled in the DATA frame header. The Offset field in the QUIC STREAM header describes the offset within the stream, but it is impossible for the receiver to know the size of any DATA frame headers that were lost.¶
DATA frame Data field (i.e. beyond the frame header) can be recovered using the unicast repair mechanism described in Section 7.2.¶
[H3-DATA-OFFSET] describes the DATA_WITH_OFFSET HTTP/3 extension frame type, which can be used to solve the third problem described above. Multicast QUIC sessions that make use of the DATA_WITH_OFFSET extension frame MUST advertise the session with the appropriate non-compatible experiment identifier "data-offset" in the ALPN string, as specified in Section 9.1.¶
Except where explicitly allowed by this specification (e.g. in Section 5.5 above), HTTP/3 extension frames (e.g. ALTSVC) are prohibited by this profile. Participants MUST NOT make any attempt to send prohibited extension frame types. Reception of these MUST be handled as described in Section 5.7.¶
The following HTTP/3 frames MUST NOT be transmitted by participants: GOAWAY, MAX_PUSH_ID, SETTINGS.¶
In addition, all HTTP/3 extension frame types MUST NOT be transmitted by participants.¶
The following HTTP/3 frames MUST NOT be transmitted by receivers: CANCEL_PUSH.¶
Reception of a prohibited HTTP/3 frame is a protocol error. Receivers MUST ignore prohibited HTTP/3 frames.¶
As already described in Section 3.1, the implicit cipher suite used by a multicast QUIC session makes very limited provision for security in the transport and session layers. This section profiles the use of some additional features to provide equivalent functionality at the application-layer.¶
In many applications, it is important to ensure that an HTTP representation has been received intact (i.e. has not suffered from transmission loss or random bit errors) before passing the received object on to the receiving application. A mechanism is therefore specified here to provide end-to-end content integrity protection for HTTP representations in transit. The use of this content integrity mechanism is RECOMMENDED.¶
Authors' Note: We invite review comments on mandating the use of this content integrity mechanism.¶
[RFC3230] specifies an instance digest HTTP header called Digest. A sender MAY include this header in the HTTP/3 HEADERS frame of any representation it transmits and a receiver MAY use this header to validate the integrity of the received representation once it has been reassembled. Where this validation fails, the receiver SHOULD discard the representation without processing it further.¶
Note that the digest value protects a whole HTTP instance (i.e. the representation of a resource at the point of transmission as opposed to the body of a particular HTTP message). In cases where partial representations are fragmented over one or more HTTP response messages, the digest value is computed over the complete representation prior to fragmentation into partial responses.¶
Any of the algorithms specified in the IANA registry of digest algorithms (http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml#http-dig-alg-1) MAY be used in conjunction with the Digest header. There is no requirement for participants to support the full set of algorithms.¶
In some applications, it is important for a receiver to reassure itself that an HTTP representation has been received from an authentic source. It is also sometimes useful for a receiver to know that the information has not been tampered with in transit by a malicious intermediate actor. A mechanism is therefore specified here to prove the authenticity of HTTP messages in transit. The use of this content authenticity mechanism is RECOMMENDED for senders implementing this specification.¶
Authors' Note: We invite review comments on mandating the use of this content authenticity mechanism.¶
[I-D.cavage-http-signatures] specifies a means of securely signing metadata associated with any HTTP message. The resulting digital signature is conveyed in the Signature header of the message itself. The Signature header also conveys a list of HTTP header fields over which the signature was computed. A receiver MAY verify the Signature header in order to validate the authenticity of received metadata. Where this validation fails, the receiver SHOULD discard or ignore any related metadata and/or data without processing it further.¶
Note that the signature proves the authenticity of the metadata in a single HTTP message. A Signature header MAY be included separately in the HTTP/3 PUSH_PROMISE frame (protecting the request metadata) and in the final (or only) HTTP/3 HEADERS frame relating to a particular resource (protecting the response metadata). In order to provide an additional level of protection, however, it is RECOMMENDED that the signature be computed over the combined request metadata (from the HTTP/3 PUSH_PROMISE frame) and the corresponding response metadata (from the HTTP/3 HEADERS frames) of the same resource. This binds the request metadata and response metadata together, providing the receiver with additional reassurance of authenticity. In this latter case, the combined digital signature SHALL be conveyed in the final (or only) HTTP/3 HEADERS frame.¶
In applications where the detection of replay attacks is a requirement, it is RECOMMENDED that the Date header be included in the scope of the signature. It is RECOMMENDED that receivers use the value of the Date header for replay detection using appropriate strategies (e.g. checking for freshness). The definition of such strategies is beyond the scope of this document.¶
In applications where the authenticity and integrity of the transmission are both important, it is RECOMMENDED that the Digest header specified in Section 6.1 above is included in the scope of the signature. By signing the instance digest, the authenticity and integrity of the HTTP message body are also assured in addition to that of the metadata.¶
Any of the algorithms specified in the IANA registry of signature algorithms (http://www.iana.org/assignments/signature-algorithms) MAY be used in conjunction with the Signature header. There is no requirement for participants to support the full set of algorithms.¶
In applications where there is a requirement for the content itself to remain confidential, appropriate steps SHOULD be taken to protect the application payload, for example by encrypting it. This document does not preclude the use of application-level encryption, but does not specify a mechanism for the distribution of content decryption keys.¶
Because the acknowledgement of received packets to multicast groups is prohibited by this specification (Section 4.11) the detection of discarded or corrupted packets is the sole responsibility of the receiver, and such losses must be recovered by means other than the retransmission mechanism specified in [RFC9000] and [RFC9002].¶
Authors' Note: A simple parity-based Forward Error Correction scheme was removed from the experimental QUIC wire protocol specification in version Q032.¶
A sender MAY make use of a suitable Forward Error Correction scheme to allow a receiver to reconstruct lost packets from those that have been successfully received.¶
In the case where a lost QUIC packet cannot be recovered using Forward Error Correction, either because the number of packets lost exceeds the scheme's threshold for reconstruction, or because FEC is not in use on the multicast QUIC session, a receiver MAY instead recover the missing payload data using conventional unicast HTTP requests to an origin server.¶
content-length response header carried in the HTTP/3 HEADERS frame.¶
STREAM frame headers of successfully received QUIC packets.¶
Using this information, a receiver MAY compose an efficient HTTP range request [RFC7233] to the origin server indicated in the URL. Several disjoint ranges MAY be combined into a single HTTP request. A receiver MAY direct its request to an alternative server using Alt-Svc information received on the multicast QUIC session, or else received as part of a previous unicast HTTP response according to the rules in [RFC7838].¶
Under certain circumstances, a sender may not be in full possession of a resource body when transmission begins, or may not be able to guarantee that a transmission will complete. In such cases, the sender MAY employ the syntax of an HTTP range request [RFC7233] to indicate partial content, as specified below. All receivers SHALL implement support for such HTTP range requests.¶
If partial content is to be transmitted:¶
range header (Section 3.1 of [RFC7233]) SHALL be present in the HTTP/3 PUSH_PROMISE frame.¶
The corresponding HTTP/3 HEADERS frame SHALL indicate HTTP status code 206.¶
content-range header field and the size of the complete resource indicated in a content-length header field.¶
The HTTP over multicast QUIC protocol specified in this document is identified by the application-layer protocol negotiation (ALPN) [RFC7301] identifier "h3m". The IANA registration of this protocol identifier can be found in Section 12.1. This reserves the ALPN identifier space but describes a protocol that does not use TLS. The usage of the "h3m" identifier for discoverability is described in Section 10.¶
RFC Editor's Note: Please remove this section prior to publication of a final version of this document.¶
Only implementations of the final, published RFC can identify themselves as "h3m". Until such an RFC exists, implementations MUST NOT identify themselves using this string.¶
Implementations of draft versions of the protocol MUST add the string "-" and the corresponding draft number to the identifier. For example, draft-pardue-quic-http-mcast-06 is identified using the string "h3m-06".¶
Non-compatible experiments that are based on these draft versions MUST append the string "-" and an experiment name to the identifier. For example, an experimental implementation based on draft-pardue-quic-http-mcast-06 which uses extension features not registered with the appropriate IANA registry might identify itself as "h3m-06-extension-foo". Note that any label MUST conform to the "token" syntax defined in Section 3.2.6 of [RFC7230]. Experimenters are encouraged to coordinate their experiments.¶
The announcement and discovery of services operating over multicast IP has previously been specified by the Session Description Protocol (SDP) [RFC4566], Session Announcement Protocol [RFC2974] and Session Initiation Protocol [RFC3261]. These are typically deployed together and in conjunction with a multicast-friendly transport such as the Real-time Transport Protocol (RTP) [RFC3550].¶
In contrast, the present document specifies a mechanism for advertising services that is built into HTTP metadata and is consistent across unicast and multicast resource delivery modes. This means that a single application-layer can be used for service advertisement/discovery, and for bulk data transmission/reception. Specifically, the Alt-Svc HTTP header is specified as the means to advertise multicast services from a unicast service. A unicast HTTP response MAY be decorated with an Alt-Svc value that hints to the client about the availability of the resource via a multicast QUIC session. A client that supports such a multicast QUIC session MAY then transparently switch to it.¶
Symmetrically, the Alt-Svc header can also be used to advertise the unicast service from a multicast service. A resource transmitted as part of a multicast QUIC session MAY be decorated with an Alt-Svc value that hints to the client about the availability of the resource via an alternative unicast HTTP server. A receiver MAY then use this HTTP server for unicast resource patching (Section 7.2).¶
Where HTTP over multicast QUIC sessions are advertised using Alt-Svc, the protocol identifier SHALL be "h3m", as specified in Section 9.¶
Source-specific multicast (SSM) [RFC4607] MAY be used for the delivery of multicast services.¶
Authors' Note: We invite review comments on mandating the use of source-specific multicast only.¶
This document specifies the "source-address" parameter for Alt-Svc, which is used to provide the SSM source address to endpoints.¶
Syntax:¶
source-address = uri-host; see RFC7230, Section 2.7¶
For example:¶
source-address=192.0.2.1¶
When a multicast QUIC session is provided using SSM, the source-address parameter MUST be advertised. If the parameter is repeated, the first occurrence MUST be used and subsequent occurrences MUST be ignored.¶
The concept of session parameters is introduced in Section 2.2. This section details how the session parameters are expressed as Alt-Svc parameters.¶
This document specifies the "cipher-suite" parameter for Alt-Svc, which carries the cipher suite in use by a multicast QUIC session. cipher-suite MUST contain one of the values contained in the TLS Cipher Suite Registry (http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-4):¶
Syntax:¶
cipher-suite = 4*4 HEXDIG¶
For example, the following specifies cipher suite 0x13,0x01 (TLS_AES_128_GCM_SHA256):¶
cipher-suite=1301¶
The requirements for endpoint usage of cipher-suite are described in Section 3.1.¶
This document specifies the "key" parameter for Alt-Svc, which carries the cryptographic key in use by the multicast QUIC session.¶
Syntax:¶
key = *HEXDIG¶
For example:¶
key=4adf1eab9c2a37fd¶
The requirements for endpoint usage of key are described in Section 3.1.¶
This document specifies the "iv" parameter for Alt-Svc, which carries the cipher Initialization Vector (IV) in use by the multicast QUIC session.¶
Syntax:¶
iv = *HEXDIG¶
For example:¶
iv=4dbe593acb4d1577ad6ba7dc3189834e¶
The requirements for endpoint usage of iv are described in Section 3.1.¶
This document defines the "session-id" parameter for Alt-Svc, which carries the multicast QUIC session identifier.¶
Syntax:¶
session-id = *HEXDIG¶
For example, the following specifies session 101 (0x65 hexadecimal):¶
session-id=65¶
The requirements for endpoint usage of session-id are described in Section 2.3. In the above example, the Destination Connection ID field in every QUIC packet header would be one byte in size. For a session-id of BADBEEF then then Destintation Connection ID field in every QUIC packet header would be four bytes in size.¶
This document specifies the "session-idle-timeout" parameter for Alt-Svc, which carries the idle timeout period in milliseconds of a multicast QUIC session.¶
Syntax:¶
session-idle-timeout = *DIGIT ; integer milliseconds¶
For example, the following specifies a one-minute session idle timeout period:¶
session-idle-timeout=60¶
The requirements for endpoint usage of session-idle-timeout are described in Section 3.3.¶
This document specifies the "max-concurrent-resources" parameter for Alt-Svc, which expresses the maximum number of concurrent active resources from the sender in a multicast QUIC session.¶
Syntax:¶
max-concurrent-resources = *DIGIT ; unsigned 32-bit integer¶
For example, the following specifies that no more than 12 (decimal) resources will be concurrently active in the session:¶
max-concurrent-resources=12¶
The requirements for endpoint usage of max-concurrent-resources are described in Section 3.5.¶
This document specifies the "peak-flow-rate" parameter for Alt-Svc, which expresses the expected maximum aggregate transfer rate of data from all sources of the multicast QUIC session.¶
Syntax:¶
peak-flow-rate = *DIGIT ; bits per second¶
For example, the following specifies a peak flow rate of 550 kbits/s in the session:¶
peak-flow-rate=550000¶
The requirements for endpoint usage of peak-flow-rate are described in Section 3.4.¶
This document specifies the "digest-algorithm" parameter for Alt-Svc, which carries the digest algorithm in use by a multicast QUIC session. digest-algorithm MUST contain one of the values defined in the HTTP Digest Algorithm Values registry (https://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml#http-dig-alg-1).¶
Syntax:¶
digest-algorithm = token¶
For example, the following specifies a digest algorithm of SHA-256:¶
digest-algorithm=SHA-256¶
The requirements for endpoint usage of digest-algorithm are described in Section 3.7.¶
This document specifies the "signature-algorithm" parameter for Alt-Svc, which carries the signature algorithm in use by a multicast QUIC session. signature-algorithm MUST contain one of the values defined in the Signature Algorithms registry (http://www.iana.org/assignments/signature-algorithms).¶
Syntax:¶
signature-algorithm = token¶
For example, the following specifies a signature algorithm of SHA-256:¶
signature-algorithm=rsa-sha256¶
The requirements for endpoint usage of signature-algorithm are described in Section 3.8.¶
This document specifies the "extensions" parameter for Alt-Svc, which carries a list of extension types potentially in use by a multicast QUIC session. extensions MUST only contain values from the QUIC Transport Parameter registry ([RFC9000], section 22.3) that have explicit support for multicast QUIC. Each entry in the list consists of a key identifying the transport parameter, and an optional value. Both the key and the value are hex-encoded.¶
Syntax:¶
extensions = DQUOTE ext-transport-param
*[ "," ext-transport-param ] DQUOTE
ext-transport-param = ext-key [ "=" ext-value ]
ext-key = 4*4HEXDIG; Transport Parameter key
ext-value = *HEXDIG; Optional Transport Parameter value
¶
For example, the following specifies two extensions:¶
extensions="0094,0d0d=f00"¶
The requirements for endpoint usage of extensions are described in Section 3.6¶
This document specifies a profile of QUIC and HTTP/3 that changes the security model. In order to address this, application-level security methods are described in Section 6. This document does not preclude the use of secure multicast approaches that may provide additional security assurances required for certain use cases.¶
The use of side-channel or out-of-band technologies (potentially bidirectional interactions) to support multicast QUIC sessions are considered out of this document's scope. Services using such technologies should apply their security considerations accordingly.¶
Certain multicast deployment architectures may require the use of a session decryption key shared by all participants. Furthermore, the discovery mechanism described in this document provides a means for a receiver to obtain a session decryption key without joining the session. The act of removing packet protection in order to inspect or modify application contents may, in certain deployments, be trivial. The exploration of restricting key learning or session joining to authorised participants goes beyond the scope of this document.¶
Because in-band multicast interactions are unidirectional, the impact of Pervasive Monitoring [RFC7258] on in-band traffic flows is inherently reduced. Actors can only inspect or modify sender-initiated traffic. Additional measures for content confidentiality may mitigate the impact further. This is discussed in Section 6.3.¶
Further Pervasive Monitoring concerns are addressed in the following sections.¶
Multicast QUIC sessions decouple sending and receiving participants. Session participation is subject to operations that allow an endpoint to join or leave a multicast group, typically IGMP [RFC3376] or MLD [RFC3810]. The propagation intent of these messages travelling deeper through a network hierarchy generally leads to the anonymisation of data if implemented as specified. It may be possible to gather user-identifiable messages close to the network edge, for example a router logging such messages. However, this would require wide-ranging access across Internet Service Provider networks. Therefore, while such attacks are feasible, it can be asserted that gathering and correlating user-identifiable traffic is difficult to perform covertly and at scale.¶
Sessions that use a symmetric key for packet protection are subject to the possibility of a malicious actor modifying traffic at some point in the network between a legitimate sender and one (or more) receivers. Receiver-side validation, as specified in Section 6 of the present document, and also in [RFC9000], allows for the detection of such modification. Two approaches help mitigate the impact of modification; the first is application-level methods that protect data (Section 6.1) and metadata (Section 6.2); the second is reduction of the QUIC packet attack surface by means of removal of many frame types (Section 4.12 and Section 5.7).¶
Multicast QUIC session advertisements SHOULD be conveyed over a secure transport that guarantees authenticity and integrity in order to mitigate attacks related to a malicious service advertisement, for example a "man in the middle" directing endpoints to a service that may lead to other attacks or exploitations.¶
Authors' Note: We invite review comments on mandating the use of a secure transport for advertising sessions.¶
Endpoints that make use of multicast QUIC session advertisements SHOULD have reasonable assurance that the alternative service is under control of, and valid for, the whole origin, as described in Section 2.1 of [RFC7838]. Section 6.2 discusses measures that may be used to fulfil this requirement.¶
A malicious actor may be able to stage a spoof attack by sending fake QUIC packets to a multicast QUIC session. This could affect the operation or behaviour of receivers. In a multicast scenario, this form of attack has the potential to scale massively.¶
The feasibility of spoofing a multicast sender is governed by the characteristics of the multicast deployment and network infrastructure. The use of source-specific multicast [RFC4607] may reduce the feasibility. The use of content authenticity (Section 6.2) may mitigate concerns for the application-level messages. However, there remains the possibility for transport-level messages to be spoofed. Multicast applications should consider further mitigations to address this concern.¶
Conventional QUIC strategies for protecting against replay attacks apply similarly here.¶
Certain multicast QUIC sessions may use a shared key for transport-level encryption, which would allow an attacker to record, decrypt, repackage and replay QUIC packets. Section 6.2 discusses how the application-level contents may be protected from replay (by signing the Date HTTP header), which provides some mitigation to the success rate or effects of replay attacks.¶
Since HTTP over multicast QUIC is designed to tolerate unreliable delivery, the impacts of message deletion attacks are presumed to be small. Deletion of packets carrying HTTP headers will cause a receiver to ignore subsequent packets carrying body data. Furthermore, the use of multicast QUIC sessions is opportunistic; disruption in service (for example, deleting packets and causing a receiver to fail in construction of a content object) is mitigated by falling back to a unicast service. Considerations for how this may affect the performance of the unicast service are given in Section 11.6.3.¶
The profile described in the present document provides the means for a multicast sender to protect QUIC packets with a shared key, which is not a strong protection. The weak protection of QUIC packets could present a denial-of-service risk. To mitigate the impact of handling such QUIC packets, certain frames and packets are prohibited as described in (Section 4.12 and Section 5.7).¶
The frame types that are allowed by this profile do not present a risk of denial of service. Concerns over authenticity and integrity are addressed by the application-layer protection mechanisms described in Section 6.¶
The possibility for malfunctioning or malicious participants to degrade the network is a broad issue and considered out of scope for this document. Guidelines and concerns discussed in UDP Best Practices [RFC8085] and other sources apply equally here. This specification does not preclude the use of network performance degradation mitigation solutions such as network circuit breakers.¶
Deployments that support the unicast repair mechanism described in Section 7.2 should be aware that a triggering of this behaviour (either deliberate, planned or unplanned) in a large population of multicast receivers may cause a stampeding herd of client requests to the unicast repair service. Service operators SHOULD mitigate the impact of stampeding herd on their deployment.¶
The application of receiver-side validation, as defined in the present document and in [RFC9000], adds some protection against allocating resource to the processing of bad data.¶
The unicast repair mechanism may lead to the leakage of user behaviour data. An attacker could gain insight into any receiver participating in a multicast QUIC session, for example by monitoring the TCP port of the unicast alternative. This alone is no worse than current abilities to monitor unicast interactions, for example observing the SNI field contained in a TLS ClientHello. The complete protection of unicast interactions is beyond the scope of this document. However, knowledge that a user (or group of users) has participated in a session is sensitive and may be obtained by correlation between with observable multicast and unicast traffic.¶
To give an example, a malicious "man in the middle" could purposely cause all receivers to perform a unicast repair (by disrupting the QUIC traffic flow in some way). The disruption is untargeted and may be simple to orchestrate, but the correlation of user activity data, especially across a distributed repair service (e.g. a CDN), requires resources that may reduce the attractiveness of such an attack.¶
The ability for an attacker to disrupt multicast QUIC sessions is mitigated by this profile (mainly the prohibition of frames and packets). Application-layer security measures described in Section 6 reduce the feasibility further.¶
Multicast receivers concerned about this form of leakage can eliminate this risk completely by disabling support for unicast repair, at the potential cost of reduced service quality.¶
This document creates a new registration for the identification of the HTTP over multicast QUIC protocol in the "Application-Layer Protocol Negotiation (ALPN) Protocol IDs" registry established by [RFC7301].¶
The "h3m" string identifies HTTP semantics expressed as HTTP mapped to a QUIC layer and carried over IP multicast:¶
Bulk data transport using HTTP over multicast QUIC¶
0x68 0x33 0x6D ("h3m")¶
This entry reserves an identifier that is not allowed to appear in TLS Application-Layer Protocol Negotiation.¶
This document creates seven registrations for the identification of parameters for the "Hypertext Transfer Protocol (HTTP) Alt-Svc Parameter Registry" established by [RFC7838] (http://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids).¶
source-address¶
This document, Section 10.1¶
cipher-suite¶
This document, Section 10.2.1¶
key¶
This document, Section 10.2.2¶
iv¶
This document, Section 10.2.3¶
session-id¶
This document, Section 10.2.4¶
session-idle-timeout¶
This document, Section 10.2.5¶
max-concurrent-resources¶
This document, Section 10.2.6¶
peak-flow-rate¶
This document, Section 10.2.7¶
digest-algorithm¶
This document, Section 10.2.8¶
signature-algorithm¶
This document, Section 10.2.9¶
extension¶
This document, Section 10.2.10¶
The authors would like to thank the following for their contributions to the design described in the present document: Brandon Butterworth, Chris Poole, Craig Taylor and David Waring.¶
We are also grateful to Thomas Swindells and Magnus Westerlund for their helpful review comments.¶
This appendix contains examples of multicast QUIC session advertisement and resource transfer (with and without application-layer content security).¶
This section shows several different examples of an HTTP service advertising a multicast QUIC session. Examples are given in IPv4 form, using reserved address ranges as specified in [RFC5737] and [RFC6676].¶
Advertisement of a multicast QUIC session operating on the source-specific multicast group address 232.0.0.1 on port 2000 with the source address 192.0.2.1. The session ID is 16 (0x10) and the idle timeout is one minute. At most 10 resources may be concurrently active in the session and the flow rate should not exceed 10 kbits/s. The multicast transport is unencrypted.¶
HTTP Alternative Service header field:¶
Alt-Svc:
h3m="232.0.0.1:2000"; source-address="192.0.2.1";
session-id=10; session-idle-timeout=60;
max-concurrent-resources=10; peak-flow-rate=10000
¶
Advertisement of a multicast QUIC session operating on the IPv6 globally-scoped source-specific multicast group address ff3e::1234 on port 2000 with the source address 2001:db8::1. The session ID is 16 (0x10) and the idle timeout is one minute. At most 10 resources may be concurrently active in the session and the flow rate should not exceed 10 kbits/s. The multicast transport is encrypted using the AEAD cipher suite 0x13,0x01 (TLS_AES_128_GCM_SHA256) with the shared session key and IV provided.¶
HTTP Alternative Service header field:¶
Alt-Svc:
h3m="[ff3e::1234]:2000"; source-address="2001:db8::1";
session-id=10; session-idle-timeout=60;
max-concurrent-resources=10; peak-flow-rate=10000;
cipher-suite=1301; key=4adf1eab9c2a37fd;
iv=4dbe593acb4d1577ad6ba7dc3189834e
¶
Advertisement of a multicast QUIC session operating on the IPv6 globally-scoped source-specific multicast group address ff3e::1234 on port 2000 with the source address 2001:db8::1. The session ID is 16 (0x10) and the idle timeout is one minute. At most 10 resources may be concurrently active in the session and the flow rate should not exceed 10 kbits/s. The multicast transport is encrypted using the AEAD cipher suite 0x13,0x01 (TLS_AES_128_GCM_SHA256) with the shared session key and IV provided. Content integrity is in use with the digest algorithm set restricted to SHA-256. Content authenticity is in use with the signature algorithm set restricted to rsa-sha256.¶
HTTP Alternative Service header field:¶
Alt-Svc:
h3m="[ff3e::1234]:2000"; source-address="2001:db8::1";
session-id=10; session-idle-timeout=60;
max-concurrent-resources=10; peak-flow-rate=10000;
cipher-suite=1301; key=4adf1eab9c2a37fd;
iv=4dbe593acb4d1577ad6ba7dc3189834e;
digest-algorithm=SHA-256; signature-algorithm=rsa-sha256
¶
This section shows several different examples of the HTTP message patterns for a single resource.¶
Examples that show HTTP/3 PUSH_PROMISE or HEADERS frames describe the contents of enclosed header block fragments.¶
HTTP/3 PUSH_PROMISE frame:¶
:method: GET :scheme: https :path: /files/example.txt :authority: example.org¶
HTTP/3 HEADERS frame:¶
:status: 200 content-length: 100 content-type: text/plain date: Fri, 20 Jan 2017 10:00:00 GMT¶
HTTP/3 DATA frame containing 100 bytes of response body data:¶
...¶
In this example, partial content is transferred as described in Section 8. The Range request header is used to indicate the sender's original intention to transfer all 100 bytes of the representation. The Content-Range response header indicates that only the first 50 bytes were actually sent.¶
HTTP/3 PUSH_PROMISE frame:¶
:method: GET :scheme: https :path: /files/example.txt :authority: example.org range: bytes=0-*¶
HTTP/3 HEADERS frame:¶
:status: 206 content-length: 100 content-range: bytes 0-49/100 content-type: text/plain date: Fri, 20 Jan 2017 10:00:00 GMT¶
HTTP/3 DATA frame containing 50 bytes of response body data:¶
...¶
In this example, content integrity is assured by the inclusion of the Digest response header, as described in Section 6.1.¶
HTTP/3 PUSH_PROMISE frame:¶
:method: GET :scheme: https :path: /files/example.txt :authority: example.org¶
HTTP/3 HEADERS frame including the Digest header:¶
:status: 200 content-length: 100 content-type: text/plain date: Fri, 20 Jan 2017 10:00:00 GMT digest: SHA-256=DieQ9zfRaDdyAilTVCvmBePuxMm+B6cNocP+QCrNSqo=¶
HTTP/3 DATA frame containing 100 bytes of response body data:¶
...¶
In this example, partial content is transferred as described in Section 8. The Range request header is used to indicate the sender's intention to transfer all 100 bytes of the representation. The Content-Range response header indicates that only the first 50 bytes were actually sent. Content integrity is assured by the inclusion of the Digest response header, as described in Section 6.1.¶
HTTP/3 PUSH_PROMISE frame:¶
:method: GET :scheme: https :path: /files/example.txt :authority: example.org range: bytes=0-*¶
HTTP/3 HEADERS frame including the Digest header:¶
:status: 206 content-length: 100 content-range: bytes 0-49/100 content-type: text/plain date: Fri, 20 Jan 2017 10:00:00 GMT digest: SHA-256=DieQ9zfRaDdyAilTVCvmBePuxMm+B6cNocP+QCrNSqo=¶
HTTP/3 DATA frame containing 50 bytes of response body data:¶
...¶
In this example, content integrity is assured by the inclusion of the Digest response header, as described in Section 6.1. Content authenticity is assured separately for the request and the response messages by the Signature header which protects the header fields described in further detail below. The Signature header parameter keyId contains the URL of a file containing the public key related to the multicast sender's private key used to create the digital signature.¶
HTTP/3 PUSH_PROMISE frame including a Signature header protecting the :method and :path (the request target), as well as the :scheme and :authority of the pseudo-request:¶
:method: GET
:scheme: https
:path: /files/example.txt
:authority: example.org
signature: keyId="https://example.org/mcast-sender.example.org.pem",
algorithm=rsa-sha256,
headers="(request-target) :scheme :authority",
signature="MGQCMFTaFptaM2FhgzJq2i9AaChuFDHjp6GiXVtRnI8BsA"
¶
HTTP/3 HEADERS frame including a Signature header protecting the :method, :path, :scheme and :authority of the pseudo-request above, plus the Date and Digest of the response:¶
:status: 200
content-length: 100
content-type: text/plain
date: Fri, 20 Jan 2017 10:00:00 GMT
digest: SHA-256=DieQ9zfRaDdyAilTVCvmBePuxMm+B6cNocP+QCrNSqo=
signature: keyId="https://example.org/mcast-sender.example.org.pem",
algorithm=rsa-sha256,
headers="(request-target) :scheme :authority date digest",
signature="MGUCMBgx6cuwTzg0W29zNUra8xfMsEcb3rFA3Y"
¶
HTTP/3 DATA frame containing response body data:¶
...¶
In this example, partial content is transferred and the Range header (as described in Section 8) is used to indicate that 50 bytes out of 100 bytes were transferred. Content integrity is provided by the inclusion of the Digest header, as described in Section 6.1. Authenticity is provided by the Signature header which protects the header fields described in further detail. The Signature header parameter keyId contains the URL of a file containing the public key related to the multicast sender's private key used to create the digital signature.¶
HTTP/3 PUSH_PROMISE frame:¶
:method: GET
:scheme: https
:path: /files/example.txt
:authority: example.org
range: bytes=0-*
signature: keyId="https://example.org/mcast-sender.example.org.pem",
algorithm=rsa-sha256,
headers="(request-target) :scheme :authority range",
signature="MGQCMFTaFptaM2FhgzJq2i9AaChuFDHjp6GiXVtRnI8BsA"
¶
HTTP/3 HEADERS frame protecting the :method, :path, :scheme and :authority of the pseudo-request above, plus the Date, Digest and Content-Range of the response:¶
:status: 206
content-length: 100
content-range: bytes 0-49/100
content-type: text/plain
date: Fri, 20 Jan 2017 10:00:00 GMT
digest: SHA-256=DieQ9zfRaDdyAilTVCvmBePuxMm+B6cNocP+QCrNSqo=
signature: keyId="https://example.org/mcast-sender.example.org.pem",
algorithm=rsa-sha256,
headers="(request-target) :scheme :authority
date digest content-range",
signature="MGUCMBgx6cuwTzg0W29zNUra8xfMsEcb3rFA3Y"
¶
HTTP/3 DATA frame containing response body data:¶
...¶
| Protocol feature | Unicast QUIC | Multicast QUIC profile |
|---|---|---|
| Packet number spaces | QUIC transport packets are seperated into three distinct packet number spaces: initial, handshake and application data. | All packets are numbered in the application data packet number space. |
| Transport handshake | Combined cryptographic and transport handshake stream conveying TLS handshake messages in QUIC Initial and Handshake packets. | Not used. |
| TLS cipher suite | Client's preferred cipher suite included in Client Hello message. | Cipher suite optionally advertised out of band via Alt-Svc cipher-suite parameter. Default cipher suite is 0x00,0x00 (NULL_WITH_NULL_NULL). |
| TLS session key | Session key included in Server Hello message. | Session key optionally advertised out of band via Alt-Svc key parameter. |
| TLS initialization vector | Initialization vector included in Server Hello message. | Initialization vector optionally advertised out of band via Alt-Svc iv parameter. |
| Protocol feature | Unicast QUIC | Multicast QUIC profile |
|---|---|---|
initial_max_data
|
Connection-level flow control window size. | Not used. Peak flow rate of a session optionally advertised out of band via Alt-Svc peak-flow-rate parameter. |
initial_max_stream_data_bidi_local
|
Locally-initiated bidirectional stream flow control window size. | Not used. No bidirectional streams in this profile. |
initial_max_stream_data_bidi_remote
|
Remotely-initiated bidirectional stream flow control window size. | Not used. No bidirectional streams in this profile. |
initial_max_stream_data_uni
|
Unidirectional stream flow control window size. | Not used. Peak flow rate of a session optionally advertised out of band via Alt-Svc peak-flow-rate parameter. |
initial_max_streams_bidi and initial_max_streams_uni
|
Maximum stream concurrency. | Not used. Maximum concurrent resources in a session optionally advertised out of band via Alt-Svc max-concurrent-resources parameter. |
| Protocol feature | Unicast QUIC | Multicast QUIC profile |
|---|---|---|
original_destination_connection_id
|
The value of the Destination Connection ID field from the first Initial packet sent by the client. | Not used. No client interaction. |
max_idle_timeout
|
How long to keep an idle connection open for before closing. Takes a default of 0 (never close on idle) if not specified. | Not used. Advertised out of band via Alt-Svc session-idle-timeout parameter; defaults to 0 (never close on idle) if not specified. |
stateless_reset_token
|
Used in verifying a stateless reset. | Not used. Stateless reset is not used by this profile. |
max_udp_payload_size
|
Limit of the size of packets that an endpoint is willing to receive. | Not used. Maximum packet size for a session optionally advertised out of band via Alt-Svc max-packet-size parameter. |
ack_delay_exponent
|
The exponent used to decode the ACK Delay field in the ACK frame. |
Not used. ACK frames are prohibited by this profile. |
max_ack_delay
|
Maximum time in milliseconds by which an endpoint will delay sending acknowledgements. | Not used. ACK frames are prohibited by this profile. |
disable_active_migration
|
Signals if an endpoint does not support connection migration. | Not used. Session migration not currently supported by this profile. |
preferred_address
|
Used to effect a change in server address at the end of the handshake. | Not used. No handshake in this profile. |
active_connection_id_limit
|
Not used. Only a single session identifier is used in this profile. | |
initial_source_connection_id
|
The value that an endpoint included in the Source Connection ID field of the first Initial packet it sent for the connection | Not used. No client interaction. |
retry_source_connection_id
|
The value that the server included in the Source Connection ID field of a retry packet | Not used. Retry packets are not used in this profile. |
| Protocol feature | Unicast QUIC | Multicast QUIC profile |
|---|---|---|
| Maximum packet size | Determined by path MTU discovery or other heuristic. | Determined by path MTU discovery or other heuristic. |
| Long header packet | Used for packets that are sent prior to the completion of version negotiation and before packet protection keys are established. | Prohibited. |
| Version negotiation packet | Protocol version negotiation between initiating client and server. | Not permitted. |
| Stateless reset packet | Used by a peer to terminate a connection that has become unusable. | Not permitted. (Potential denial-of-service attack vector.) |
| Short header packet | Used for packets that are sent once a connection has been established. Used to convey QUIC frames (see below). | Used to convey QUIC frames (see below). |
| Source Connection ID field, Destination Connection ID field | Connection IDs negotiated between client and server during handshake and may be changed subsequently using the NEW_CONNECTION_ID frame. |
Source Connection ID not used. Destination Connection ID redefined to be a Multicast Session ID which is optionally advertised out of band via the Alt-Svc session-id parameter. May be omitted from packets if the address/port tuple is sufficient to identify the session, in which case it is not advertised. |
| Protocol feature | Unicast QUIC | Multicast QUIC profile |
|---|---|---|
PADDING frame |
Used to pad out a QUIC packet with zero bytes. (The first packet sent on a connection must be at least 1200 bytes long to prove that the network can transmit packets of at least this size.) | Permitted, but wasteful of network capacity. |
PING frame |
Used by an endpoint to verify that its peer is still alive. Acknowledged using a regular ACK frame. |
Used by the multicast sender as a session keep-alive notification. Never acknowledged. |
ACK frames |
Used by a receiver to acknowledge receipt of data from its peer. | Both ACK frame types are prohibited. |
RESET_STREAM frame |
Request by receiver for sender to terminate a stream transmission prematurely. | Indication to receivers that the multicast sender has prematurely terminated a stream transmission. Prohibited for receivers to send. |
STOP_SENDING frame |
Flow control back pressure. Used to signal to a peer that incoming data on a stream is being discarded on receipt at the application's request. This abruptly terminates a stream. | Prohibited. |
CRYPTO frame |
Used to transmit cryptographic handshake messages. | Prohibited. |
NEW_TOKEN frame |
Used by a server to supply a token to its client to be sent in the header of an initial packet for a future connection. Used to facilitate connection migration. | Prohibited. Session migration not currently supported by this profile. |
STREAM frame |
Conveys application-layer payloads (see HTTP/3 mapping below). | Conveys application-layer payloads (see HTTP/3 mapping below). |
FIN bit on STREAM frame |
Indication by sender to its peer that a stream transmission has finished. | Indication by the multicast sender that a stream transmission has finished. |
MAX_DATA frame |
Flow control update notification. | Prohibited. |
MAX_STREAM_DATA frame |
Flow control update notification. | Prohibited. |
MAX_STREAMS frame |
Used by an endpoint to inform a peer of the maximum stream ID that it is permitted to open. | Prohibited. |
DATA_BLOCKED frame |
Notification to receiver that sender's transmission is blocked pending an update to its flow control window by peer. | Prohibited. |
STREAM_DATA_BLOCKED frame |
Notification to receiver that sender's transmission of a single stream is blocked pending an update to its flow control window by peer. | Prohibited. |
STREAMS_BLOCKED frames |
Notification to receiver that the sender wishes to open a stream but is unable to do so because the maximum stream ID has been reached for a given stream type. | Prohibited. |
NEW_CONNECTION_ID frame |
Used to provide a peer with alternative connection IDs that can be used to break linkability when migrating connections. | Prohibited. Session migration not currently supported by this profile. |
RETIRE_CONNECTION_ID frame |
Indicates that an endpoint will no longer use a connection ID that was issued by its peer. | Prohibited. Session migration not currently supported by this profile. |
PATH_CHALLENGE frame |
Used to check reachability to a peer and for path validation during connection migration. | Prohibited. |
PATH_RESPONSE frame |
Sent in response to a PATH_CHALLENGE frame. |
Prohibited. |
CONNECTION_CLOSE frame |
Notification (by either peer) of graceful connection shutdown. | Prohibited. Use HTTP explicit session tear-down instead (see Section 5.4). |
HANDSHAKE_DONE frame |
Used by a server to inform a client that the cryptographic handshake has completed. | Prohibited. |
| Protocol feature | Unicast HTTP/3 | Multicast HTTP/3 profile |
|---|---|---|
| Stream Type | Type of unidirectional stream. | Only Server Push type is permitted. |
| Push ID | Identifies a promised resource conveyed in an earlier PUSH_PROMISE frame. |
Identifies a promised resource conveyed in an earlier PUSH_PROMISE frame. |
DATA frame |
Carriage of HTTP request/response message body. | Carriage of HTTP response message body. |
HEADERS frame |
Carriage of HTTP request/response message metadata. Trailing HEADERS frame is permitted. |
Carriage of HTTP response message metadata. Trailing HEADERS frame is permitted. |
CANCEL_PUSH frame |
Used to request cancellation of server push prior to the push stream being created. | Permitted only for senders. |
SETTINGS frame |
Negotiation of HTTP/3 connection settings. | Prohibited. |
PUSH_PROMISE frame |
Carriage of HTTP pseudo-request message metadata. | Carriage of HTTP pseudo-request message metadata. All HTTP representation transfers over multicast begin this way. Stream ID of the first client-initiated bidirectional stream is reserved and all PUSH_PROMISE frames reference this as the client request from which they are notionally derived. This stream remains open while a sender is participating in the multicast QUIC session. |
GOAWAY frame |
Early notification (by either endpoint) of future connection closure, allowing for orderly completion of open streams. | Prohibited. Use HTTP explicit session tear-down instead. |
MAX_PUSH_ID frame |
Used by a receiver to control the number of server pushes that a sender can initiate. | Prohibited. |
ALTSVC HTTP/2 extension frame |
Signalling alternative service for HTTP/3 session. | Prohibited. |
| Other HTTP/2 extension frames | Prohibited. |
| Protocol feature | Unicast HTTP/3 | Multicast HTTP/3 profile |
|---|---|---|
| Huffman string compression | Header blocks may use Huffman codes to compress literal string values. | Header blocks may use Huffman codes to compress literal string values. |
| Static table | Header blocks may refer to indexed entries in the static table. | Header blocks may refer to indexed entries in the static table. |
| Dynamic table | Header blocks may insert entries into the dynamic table and subsequent header blocks may refer to their indexes. Unused as size is currently locked to 0. | Prohibited, size is currently locked to 0. |
RFC Editor's Note: Please remove this section prior to publication of a final version of this document.¶
PUSH_PROMISE frames.¶
HANDSHAKE_DONE.¶
quic Alt-Svc parameter has been removed (examples also updated).¶
extensions Alt-Svc parameter.¶
active_connection_id_limit session parameter. (draft-ietf-quic-transport-21)¶