IETF Logo Mail Archive

Unreliable Stream Support for QUIC

"Philipp S. Tiesel" <phils@in-panik.de> Tue, 05 September 2017 16:30 UTC

Return-Path: <phils@in-panik.de>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FEC9132D8D for <quic@ietfa.amsl.com>; Tue, 5 Sep 2017 09:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrXlgHMyslxh for <quic@ietfa.amsl.com>; Tue, 5 Sep 2017 09:30:14 -0700 (PDT)
Received: from einhorn-mail.in-berlin.de (einhorn-mail.in-berlin.de [217.197.80.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83516132D93 for <quic@ietf.org>; Tue, 5 Sep 2017 09:30:11 -0700 (PDT)
X-Envelope-From: phils@in-panik.de
X-Envelope-To: <quic@ietf.org>
Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id v85GTnkR009156 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <quic@ietf.org>; Tue, 5 Sep 2017 18:29:49 +0200
Received: from [2001:638:809:ff1f::8295:dc3a] by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <phils@in-panik.de>) id 1dpGjD-0005Sv-C2 for quic@ietf.org; Tue, 05 Sep 2017 18:29:31 +0200
From: "Philipp S. Tiesel" <phils@in-panik.de>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Unreliable Stream Support for QUIC
Message-Id: <A9B224F6-E917-4A7F-ABF7-29FC2C60C5A6@in-panik.de>
Date: Tue, 05 Sep 2017 18:29:48 +0200
To: QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UBUrn7tmh3GwWs6VhD_2vzyU6fM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 16:30:19 -0000

Hi,

as promised, we just submitted a draft on unreliable streams for QUIC,
including support for partial reliability: 
   https://datatracker.ietf.org/doc/draft-tiesel-quic-unreliable-streams/

TL;DR: 

 - In principal, supporting unreliable streams in QUIC
   does not require changes to the datft-05 wire-protocol.

 - To get a nice interface between QUIC transport and the
   application, we need one bit in the stream frame header
   to indicate whether a stream is supposed to be reliable.


To give an application example, we did also draft how HTTP/2 over QUIC
can be extended to support partial reliability based on the draft above:
   https://datatracker.ietf.org/doc/draft-tiesel-quic-unreliable-http/

We have no finished implementation yet, but are working on one. 

AVE!
  Philipp S. Tiesel / phils…

v2.23.0 | Report a Bug | By Email