ALTO Extension: New Transport Layer Protocols
draft-gao-alto-new-transport-00

Document Type Active Internet-Draft (individual)
Author Kai Gao 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO                                                              K. Gao
Internet-Draft                                        Sichuan University
Intended status: Standards Track                         2 November 2020
Expires: 6 May 2021

             ALTO Extension: New Transport Layer Protocols
                    draft-gao-alto-new-transport-00

Abstract

   The current ALTO transport is based on HTTP/1.x connections between
   ALTO servers and ALTO clients.  On the other hand, recent extensions
   to HTTP/1.x such as HTTP/2 [RFC7540] and HTTP/3 [I-D.ietf-quic-http]
   introduce capabilities such as server push and stream multiplexing,
   which can potentially be integrated into ALTO to improve ALTO
   capabilities such as incremental updates.  This document identifies
   use cases of ALTO and its extensions that may benefit from the
   advanced features of HTTP/2 and HTTP/3, and proposes ALTO extensions
   to fully leverage the benefits.

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 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 6 May 2021.

Copyright Notice

   Copyright (c) 2020 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

Gao                        Expires 6 May 2021                   [Page 1]
Internet-Draft                 ALTO-TRANS                  November 2020

   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
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   2
   3.  HTTP/2 and HTTP/3 Protocol Overview . . . . . . . . . . . . .   3
     3.1.  HTTP/2  . . . . . . . . . . . . . . . . . . . . . . . . .   3
       3.1.1.  Persistent Connection . . . . . . . . . . . . . . . .   3
       3.1.2.  Server Push . . . . . . . . . . . . . . . . . . . . .   3
       3.1.3.  Stream Multiplexing . . . . . . . . . . . . . . . . .   3
     3.2.  HTTP/3  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  ALTO Use Cases  . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Transport of Dependent Information Resources  . . . . . .   3
     4.2.  Transport of Incremental Update . . . . . . . . . . . . .   4
     4.3.  Transport of Multipart Messages . . . . . . . . . . . . .   4
   5.  Issues  . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Server Push/Stream Multiplexing for Filtered Services . .   4
   6.  ALTO Extensions . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The ALTO protocol {{RFC7285} and its extensions are based on HTTP/1.x
   connections between ALTO servers and clients.  Recently, newer
   versions of the HTTP protocol, i.e., HTTP/2 [RFC7540] and HTTP/3
   [I-D.ietf-quic-http], are introduced to the IETF.  The upgrades have
   many benefits such as performance gains and new features, most
   notably server push and stream multiplexing.  While the ALTO base
   protocol should work on top of HTTP/2 and HTTP/3 and gain performance
   improvement without modification, it is worth looking into the
   question of whether and how ALTO can further take advantage of the
   new features.

   The purpose of this document is 1) to identify use cases of the ALTO
   protocol and its extensions that may benefit from the new features of
   HTTP/2 and HTTP/3, and 2) to propose extensions to fully leverage the
   benefits.

2.  Conventions and Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Gao                        Expires 6 May 2021                   [Page 2]
Show full document text