Re: question about QPACK decode framing

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 31 October 2018 21:15 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 09962130E3C for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 14:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 xZNsI0t1ouSg for <quic@ietfa.amsl.com>; Wed, 31 Oct 2018 14:15:24 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 B2A41130E90 for <quic@ietf.org>; Wed, 31 Oct 2018 14:15:24 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id l41-v6so18861256qtl.8 for <quic@ietf.org>; Wed, 31 Oct 2018 14:15:24 -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=IL2j82afmXxYACbQQVP22rjGAzE6ggYfTF3SUuXjb4c=; b=Fw0GYD0l5pNlBO5IiJBpisGA9X4HMf+PrnyVWKrEe065Ea81HNyZDKZmujiY2fUY8h nNPS+ZtRuSMhfBr5IyOtirna52/6hVwt90XRTv8XCm514tVJ118P4PgsU1NgmNlkewJr v7hzTaeyo9RCMJanHfHy+JJ0FQSDDEDPysb3iXloFA023cf6nhP0L7vmHF2bE7g14f8V JB9WCMpGJnuo811EHhBBcPAOyjlVw1QI9OtUrs8LwXeemrslTh/uLNARpmW37VIvFzU7 s3kmicVhIXq7exCEkhHgzQkAhn2ELj9+iwXu5vtgv52q45WZwONTij9H97+jceBNmKZU R4gA==
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=IL2j82afmXxYACbQQVP22rjGAzE6ggYfTF3SUuXjb4c=; b=qX/KdT+dWdkQwa3WI+xjDqj+HlLgWciMwuJICVB7HZ8JT12g77u927jJ4nf086q0vE L+wjzlRTBTH5yL5yqHawcoMq3Wjj6MlsNNRf75WIQ7YQUpnJafrO6FlkAneqMty4DzI4 UeeyRO7PGUb0bWO7F9F2i1eu/oqqBxdXn0JSO8/fYlXfej6uEIDq3dHrGS9A4qLG0Gv5 1IJKByfnBZnO7/0IWzsRHiyvfSRRavt1KfzHPtXM6jHonE5vujODqTXHI0L6eF6RrNiY Y80LC/sdHSDSU8LNBuVeb9KghctqSIimp3BI4pl2jkWmP8Xxp28O50HM7R83KzFTC4FE X0/A==
X-Gm-Message-State: AGRZ1gLvtD4Uv5ZYlcrplr9cZ2Y4pOW3yKgOYzMMDYgUD6ffgYK4FG24 NTVxXXboVVBQQcTIzv3fPtYQlQ==
X-Google-Smtp-Source: AJdET5fTG/Zu33+JiG1tWelK9b+V3aMpPvXvjtestz32qxOsF6xbk/xmNThbOznD/JPTIaS4GNGH2Q==
X-Received: by 2002:ac8:7119:: with SMTP id z25-v6mr4287743qto.270.1541020523732; Wed, 31 Oct 2018 14:15:23 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id u27-v6sm25895700qth.39.2018.10.31.14.15.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Oct 2018 14:15:23 -0700 (PDT)
Date: Wed, 31 Oct 2018 17:15:18 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>
Cc: "quic@ietf.org" <quic@ietf.org>
Subject: Re: question about QPACK decode framing
Message-ID: <20181031211518.GA9622@ubuntu-dmitri>
Mail-Followup-To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>
References: <DM5PR21MB01241538AD5198940C463A13B3CD0@DM5PR21MB0124.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DM5PR21MB01241538AD5198940C463A13B3CD0@DM5PR21MB0124.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fcj58uI7E5zjjG5IurW-_t8PXxw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 31 Oct 2018 21:15:37 -0000

Hi Brian,

(I am assuming you're talking about processing the header block.)

The header block is in the HQ "HEADERS" frame which has a length.
Depending on your implementation, you may be able to tell if you
have the complete header block buffered.

  - Dmitri.

On Wed, Oct 31, 2018 at 08:57:27PM +0000, Brian Swander wrote:
> Is there a way to determine that we are decoding a complete set of headers a priori?   I.e. is the "headers length" encoded anywhere?   Or does decode (control stream) just have to handle the case where we only have a partial header, and we just pend and wait for more data before continuing?
> 
> Thanks
> bs