Re: Why allow empty STREAM frames when offset is zero?

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Thu, 10 May 2018 19:10 UTC

Return-Path: <dtikhonov@litespeedtech.com>
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 2D4FD1270AB for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.com
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 xU6nPGZ8b6BN for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 517E6126FB3 for <quic@ietf.org>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id c2-v6so3997697qtn.9 for <quic@ietf.org>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=H9+vuyfENML4FxZi+b9Evi/oj2W9VyTjKPMxq2DLbXE=; b=CJs5drhTGwjIMBCT2APTLmHSM6bYtXp4voLTyTmrZpvfI8EgMuuLu2F3ohRKVePSF8 0ZLZfEp2f3vfqOahXCAr8VqbnueXWibXXYJ/kLqaS/WsxwE3uTxEU7oTBEFH7hvmUxf7 Bo0vs6NZiQ1xfNFyAqXf+mZtcdyD4ZMIndZ3wBfZqwhjvlphBzOw/4maKMM9jk3m4H0h hVbMbwpqHWzn9NYyNmUTFDgzWNCYxCx6iVU73tYMOkb6wSydigYppCnXqy/HN0uVDVL0 efUEYvEwmngcV1s9gkTDkYfBug4ObMmUMvGM5WZlEwX5CqmpoEzpKCefuiPDUaRWYt/l ccAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=H9+vuyfENML4FxZi+b9Evi/oj2W9VyTjKPMxq2DLbXE=; b=mflTwjP7oLUA7ISZ/vuMYXERx4g4xJMSWs+xshCR5L6EMVDbmGxvXGz6VyzPT2ZJVb uIS4XDt97D9awjryG+tDsQl+5Gz6+EN9UVaqp42xLXq8IuyaSigOR+D8ernUs9i9J4LT sSFniSVd0mnEPzWn9jlxmLYNT+3HmJzdxpao3pz7CTdNw6uBkXSWQ3SM1HIi9jY1QVjo Rbz+U8d+eZ/yDS1hv58Cf/AAkUixIPnHhcoXfolNFvX8pkpEAh5tnYWzgJwL72FqbpZy DtqCy8D4oo3zDHQdJg2mObOjjbTUNZiB5tcb8d5L6P36srojpWA43DRGJLyY57tdrXVh +4CQ==
X-Gm-Message-State: ALKqPwfKnokWRTsW3G5kDhVhtDi9MYmhV8AjbDhGkxkPe5IRCpvVPP7L WbkBgfyOtubW+b0POVrK0tG54g==
X-Google-Smtp-Source: AB8JxZqbCmanH8l1BlWoHk0/DF7ogi5+3JJAVtO0PuJs0WYKiZKJpsLbkvAciuhCBVB0GFHjD3UGCA==
X-Received: by 2002:aed:23f5:: with SMTP id k50-v6mr2654053qtc.367.1525979449363; Thu, 10 May 2018 12:10:49 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id p63-v6sm997455qkd.92.2018.05.10.12.10.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 12:10:48 -0700 (PDT)
Date: Thu, 10 May 2018 15:10:46 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Nick Banks <nibanks@microsoft.com>
Cc: Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?
Message-ID: <20180510191045.GB23837@ubuntu-dmitri>
Mail-Followup-To: Nick Banks <nibanks@microsoft.com>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri> <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RlpetHXpu-dT35G_KWcy3AyKqjo>
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: Thu, 10 May 2018 19:10:53 -0000

On Thu, May 10, 2018 at 07:02:06PM +0000, Nick Banks wrote:
> If you are moving from multiple TCP connections to a single QUIC
> connection, it could be seen as the equivalent of a single TCP
> connect event.

Hmm!  This is an interesting way to look at it.

  - Dmitri.