Re: Differentiate between GQUIC and QUIC packets
Ryan Hamilton <rch@google.com> Tue, 01 August 2017 13:43 UTC
Return-Path: <rch@google.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 72D96132017 for <quic@ietfa.amsl.com>; Tue, 1 Aug 2017 06:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 iRPfqWUEnr7N for <quic@ietfa.amsl.com>; Tue, 1 Aug 2017 06:43:21 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 9D13F1243F3 for <quic@ietf.org>; Tue, 1 Aug 2017 06:43:20 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id m85so15269567wma.0 for <quic@ietf.org>; Tue, 01 Aug 2017 06:43:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IQZb1iHMiYpAuvXORjzDrI4fWk15ILoMLHfsEhWAbIc=; b=oni4uYqvOQKpaWl4K4vbk5UCoWiZOo+XkZJ+mtmQsb45ipuC7cv0wpkkGx16frhw/w 0opCGHPPU6hCdWl1gKOefGiyA8q4wVZvy14i0ypG7kmq3THRaoSFB0cMCFjnNLmmz6Xf ymv/CDeoJZqOA6hz43nd55HxlQ2/VnPC/+ArXTBYIGScPHQcWAdishznL/PiHDI2Ct00 jmO6Utnjo26Hl078Ii5+08kp6ievqY+eJHYsmC5CLDASQSbVHw2GOO0hmgSs2Y45xIKj dXdSn1qqj7Z/cWz1vwz0deTQ02lPcxLCzTxTllYSsSXBZARWz0VdHtzLVRLqJ3LXZ8Ep /d1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IQZb1iHMiYpAuvXORjzDrI4fWk15ILoMLHfsEhWAbIc=; b=Gj6DlzYijvkA5jrqXEreWkGJL/AkRQgCyHmWdAZHbWryf5pkvrjBfRd+O/aW2e4PMS s3yB8lkf+qabrczxIZpEk6QOCH0AKWASngDWgh6KAQ3tOuv+Mb/kh1TWuTPl8rX/w7Ns Wtkn+8K/UT6Xujb4HgajKkmMbIm8HfZRv2dsxDDian55DUP2ZEnMRxxTFhvop21hJlNL WuYnoEipx+DUwe8rOtNhlyKBIRr6Q0+s0QTEzIk5FBe4M3k3jEQbbYfM8IXyIVWwbd3u SAF8+iEO05n2EvCYyFSQteHyBgxYZF1qv0kT+AKTwIghpchsPliwiw0cNtfc6I5StFTr 0wRg==
X-Gm-Message-State: AIVw110tVITUGSywzrXr6gtue+ejAYiGRLpwiBqD1XC41/5VH1Hvx8dD 9FVEGcuRhRq0I5SiRrtYYmdtk0vyhqCrXKw=
X-Received: by 10.28.71.5 with SMTP id u5mr1638065wma.138.1501594998881; Tue, 01 Aug 2017 06:43:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.54.234 with HTTP; Tue, 1 Aug 2017 06:43:15 -0700 (PDT)
In-Reply-To: <CAKcm_gOK5K=jcVG3V4moTpV0-KeLAWMjtvAqX5aZt6voo4kBng@mail.gmail.com>
References: <20170801032502.GA28788@ubuntu-dmitri> <20170801032805.GA29894@ubuntu-dmitri> <CAKcm_gNQFEmws7wX5vfKCZ4QHGTHRq=Y4GxO09GxjW66dRPRig@mail.gmail.com> <20170801125031.GA2742@ubuntu-dmitri> <CAKcm_gOK5K=jcVG3V4moTpV0-KeLAWMjtvAqX5aZt6voo4kBng@mail.gmail.com>
From: Ryan Hamilton <rch@google.com>
Date: Tue, 01 Aug 2017 06:43:15 -0700
Message-ID: <CAJ_4DfTzrh+Jp-8AN0CeZuRBP5GPjKdg_uabinDuEy0D_SyzzA@mail.gmail.com>
Subject: Re: Differentiate between GQUIC and QUIC packets
To: Ian Swett <ianswett@google.com>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0720fc81c5c80555b154c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sbugM9FePydzLt2a8aGYkaXoe4g>
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, 01 Aug 2017 13:43:22 -0000
On Tue, Aug 1, 2017 at 6:08 AM, Ian Swett <ianswett@google.com> wrote: > On Tue, Aug 1, 2017 at 8:50 AM, Dmitri Tikhonov < > dtikhonov@litespeedtech.com> wrote: > >> >> Speaking of clients: is it the plan for Chrome to support both GQUIC >> and IETF QUIC during the transition period? >> >> > Chrome is in the process of migrating towards IETF QUIC, but there is a > plan to support at least two versions during the transition. > ​Google QUIC is continuously evolving. For example, we recently enabled v39 which switched from little endian to big endian, and previously v38 changed the behavior of the PADDING frame, all to match the IETF. We're working on v40 at the moment which changes the layout of the ACK and STREAM frames. So over time Google QUIC will become IETF QUIC. Cheers, Ryan
- Differentiate between GQUIC and QUIC packets Dmitri Tikhonov
- Re: Differentiate between GQUIC and QUIC packets Dmitri Tikhonov
- Re: Differentiate between GQUIC and QUIC packets Ian Swett
- Re: Differentiate between GQUIC and QUIC packets Dmitri Tikhonov
- Re: Differentiate between GQUIC and QUIC packets Ian Swett
- Re: Differentiate between GQUIC and QUIC packets Ryan Hamilton
- Re: Differentiate between GQUIC and QUIC packets Dmitri Tikhonov