idnits 2.17.1 draft-bishop-httpbis-altsvc-quic-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.ietf-quic-http], [RFC7540], [RFC7838]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 24, 2017) is 2466 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-34) exists of draft-ietf-quic-http-04 -- Obsolete informational reference (is this intentional?): RFC 7540 (Obsoleted by RFC 9113) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 HTTPbis M. Bishop 3 Internet-Draft Microsoft 4 Intended status: Standards Track July 24, 2017 5 Expires: January 25, 2018 7 ALTSVC Frame in HTTP/QUIC 8 draft-bishop-httpbis-altsvc-quic-00 10 Abstract 12 [RFC7838] defines the ALTSVC frame for HTTP/2 [RFC7540]. This frame 13 is equally applicable to HTTP/QUIC ([I-D.ietf-quic-http]), but needs 14 to be separately registered. This document describes the ALTSVC 15 frame for HTTP/QUIC. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on January 25, 2018. 34 Copyright Notice 36 Copyright (c) 2017 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. The ALTSVC HTTP/QUIC Frame . . . . . . . . . . . . . . . . . 2 53 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 54 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 57 5.2. Informative References . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. Introduction 62 [RFC7838] defines HTTP Alternative Services, which allow an origin's 63 resources to be authoritatively available at a separate network 64 location, possibly accessed with a different protocol configuration. 65 It defines two mechanisms for transporting such information, an HTTP 66 response header and an HTTP/2 frame type. 68 [I-D.ietf-quic-http] describes the required updates for HTTP/2 frames 69 to be used with HTTP/QUIC. Only a few modifications are required for 70 the ALTSVC frame. No modifications are required for the "Alt-Svc" 71 header field. 73 2. The ALTSVC HTTP/QUIC Frame 75 The ALTSVC HTTP/QUIC frame advertises the availability of an 76 alternative service to an HTTP/QUIC client. 78 An ALTSVC frame from a server to a client on stream 1 (not 0, as in 79 HTTP/2) indicates that the conveyed alternative service is associated 80 with the origin contained in the Origin field of the frame. 82 An ALTSVC frame from a server to a client on a stream other than 83 stream 1 indicates that the conveyed alternative service is 84 associated with the origin of that stream. 86 The layout and semantics of the frame are identical to those of the 87 HTTP/2 frame defined in [RFC7838]. The ALTSVC frame type is 0xa 88 (decimal 10), as in HTTP/2. 90 3. Security Considerations 92 This document introduces no new security considerations beyond those 93 discussed in [RFC7838] and [I-D.ietf-quic-http]. 95 4. IANA Considerations 97 This document registers the ALTSVC frame type in the "HTTP/QUIC Frame 98 Type" registry ([I-D.ietf-quic-http]). 100 Frame Type: ALTSVC 102 Code: 0xa 104 Specification: This document 106 5. References 108 5.1. Normative References 110 [I-D.ietf-quic-http] 111 Bishop, M., "Hypertext Transfer Protocol (HTTP) over 112 QUIC", draft-ietf-quic-http-04 (work in progress), June 113 2017. 115 [RFC7838] Nottingham, M., McManus, P., and J. Reschke, "HTTP 116 Alternative Services", RFC 7838, DOI 10.17487/RFC7838, 117 April 2016, . 119 5.2. Informative References 121 [RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext 122 Transfer Protocol Version 2 (HTTP/2)", RFC 7540, 123 DOI 10.17487/RFC7540, May 2015, 124 . 126 Author's Address 128 Mike Bishop 129 Microsoft 131 Email: michael.bishop@microsoft.com