Akamai

mbishop@evequefou.be

Applications HTTPbis Internet-Draft defines the ALTSVC frame for HTTP/2 . This frame is equally applicable to HTTP/QUIC (), but needs to be separately registered. This document describes the ALTSVC frame for HTTP/QUIC.

defines HTTP Alternative Services, which allow an origin’s resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration. It defines two mechanisms for transporting such information, an HTTP response header and an HTTP/2 frame type. describes the required updates for HTTP/2 frames to be used with HTTP/QUIC. Only a few modifications are required for the ALTSVC frame. No modifications are required for the “Alt-Svc” header field.

The ALTSVC HTTP/QUIC frame advertises the availability of an alternative service to an HTTP/QUIC client. An ALTSVC frame from a server to a client on stream 1 (not 0, as in HTTP/2) indicates that the conveyed alternative service is associated with the origin contained in the Origin field of the frame. An ALTSVC frame from a server to a client on a stream other than stream 1 indicates that the conveyed alternative service is associated with the origin of that stream. The layout and semantics of the frame are identical to those of the HTTP/2 frame defined in . The ALTSVC frame type is 0xa (decimal 10), as in HTTP/2.

This document introduces no new security considerations beyond those discussed in and .

This document registers the ALTSVC frame type in the “HTTP/QUIC Frame Type” registry (). ALTSVC 0xa This document

This document specifies "Alternative Services" for HTTP, which allow an origin's resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration. The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC, and describes how HTTP/2 extensions can be ported to QUIC. This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients.This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.

A substantial portion of Mike’s work on this draft was supported by Microsoft during his employment there.