ALTSVC Frame in HTTP/QUIC
draft-bishop-httpbis-altsvc-quic-00

Abstract

[RFC7838] defines the ALTSVC frame for HTTP/2 [RFC7540]. This frame is equally applicable to HTTP/QUIC ([I-D.ietf-quic-http]), but needs to be separately registered. This document describes the ALTSVC frame for HTTP/QUIC.

Status of This Memo

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 http://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 January 25, 2018.

Copyright Notice

Copyright (c) 2017 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 (http://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 Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. The ALTSVC HTTP/QUIC Frame
• 3. Security Considerations
• 4. IANA Considerations
• 5. References
• 5.1. Normative References
• 5.2. Informative References
• Author's Address

1. Introduction

[RFC7838] 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.

[I-D.ietf-quic-http] 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.

2. The ALTSVC HTTP/QUIC Frame

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 [RFC7838]. The ALTSVC frame type is 0xa (decimal 10), as in HTTP/2.

3. Security Considerations

This document introduces no new security considerations beyond those discussed in [RFC7838] and [I-D.ietf-quic-http].

4. IANA Considerations

This document registers the ALTSVC frame type in the “HTTP/QUIC Frame Type” registry ([I-D.ietf-quic-http]).

Frame Type:

ALTSVC

Code:

0xa

Specification:

This document

5. References

5.1. Normative References

5.2. Informative References

Author's Address