Re: Differences between iQUIC and gQUIC

Ian Swett <ianswett@google.com> Mon, 18 October 2021 21:59 UTC

Return-Path: <ianswett@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 A38803A0E7C for <quic@ietfa.amsl.com>; Mon, 18 Oct 2021 14:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.097
X-Spam-Level:
X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 WKYqRJuFVhgn for <quic@ietfa.amsl.com>; Mon, 18 Oct 2021 14:59:30 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 B74CC3A0E68 for <quic@ietf.org>; Mon, 18 Oct 2021 14:59:30 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id q189so401506ybq.1 for <quic@ietf.org>; Mon, 18 Oct 2021 14:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gyuQxJUKChlhawbDqpMeF44vh8uWZayckyzJrz5KkXc=; b=F93+1SBNwMp1WnAStjRa4aW3yXf7GGELEk5rApYVgaj/LjIhuIwO3ojcJDlgKhPrPS onvLzV83OcKgMVTE9Hioq8xQsD8DBcB4CGM7momYbyMCjJ9LW/H94Yom/55lDCvIDqR5 jFI6nsvzX4OeDeYv5b1wlSMSJ5J6x/RmuGnm6Bl/Ao3kT+J4Lsk+bqYHLmmtJtGkc4u5 Jc9ffAiE7qqjnjD7Y2SajhLDoHNLLRAlQT+yp/43IbsSWpk+WHoj/Qu7ArNc/V+Ztd0N i242BIxIPTHpasu2637VL8haiOULpow72n7QT/GI15LGOEX/hdJO89vGl6mWP5TQH0rY 8Zrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gyuQxJUKChlhawbDqpMeF44vh8uWZayckyzJrz5KkXc=; b=Sr++zGQnJ7KXbVMG+mGmTKPa+aX1edZTOP5/83WHDh0Ak8Z28JvZqfw5i2B1JD6XEm ioQPD0LVJB0KaTA/VBKJqkYPE//JTRdsb+wNTNqiXHmLZTGJiD8To9duNMUFKlo0yXyq KVzFAWxVWwujMRBmgk24IuJbHlEd/4A4Fxz9ViVk6ZcC2i43xaNiFIdLcnhlVUsWH8u7 tlxr1LeTch4h+VfB15cfwQoEgTT7118WvfYqyjK3z+JZxWZa7zICsOnXELB0Lgckl8HH uVKIoxuqCJibB66UGFyb6pt/qxLy3MJsH0RuUq+UnUWpeBH8ROYe16p/fRZf9U0sF3OH 9k0A==
X-Gm-Message-State: AOAM530p70qD/l/1pe3KzvCYcyLmz70pyzYu5JdJtafEaKah8srdLpb6 sT8rjDXjmupUaWoPet1Enb32Zzws7NyQDxEe5QZbGw==
X-Google-Smtp-Source: ABdhPJyGmxHNbQIa5U1JuHDYY8oHFC7NwMY2FYMvUS1/qstX/gM14pzh6mgsziHSWwaB2V/uIsGGGyRZ/g86jxFwVw0=
X-Received: by 2002:a25:49c3:: with SMTP id w186mr33569240yba.429.1634594369619; Mon, 18 Oct 2021 14:59:29 -0700 (PDT)
MIME-Version: 1.0
References: <b12dde7c79c04b6cbabbeff6d11fac4e@rwth-aachen.de> <CADdTf+ib7Qw4EiHqNrOeCUSN8OHWndcBFZE8v2pRMVULV1bBgg@mail.gmail.com>
In-Reply-To: <CADdTf+ib7Qw4EiHqNrOeCUSN8OHWndcBFZE8v2pRMVULV1bBgg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 18 Oct 2021 17:59:18 -0400
Message-ID: <CAKcm_gM0DPttYuQZXcmsF_mS5hm=pPW3hSOrcLHGgw32eT+LpQ@mail.gmail.com>
Subject: Re: Differences between iQUIC and gQUIC
To: Matt Joras <matt.joras@gmail.com>
Cc: "Feltgen, Eric" <eric.feltgen@rwth-aachen.de>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c1426c05cea7a890"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NfNz4VrYaE8xpas0-BAxCaGb6vI>
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: Mon, 18 Oct 2021 21:59:36 -0000

I agree with all of Matt's points.

And there are a lot of differences, more than I could enumerate.

Ian

On Mon, Oct 18, 2021 at 2:55 PM Matt Joras <matt.joras@gmail.com> wrote:

> Hi Eric,
>
> In general I would advise not assuming the findings for studies
> focused on Google QUIC will apply to IETF QUIC. While many findings
> may apply, they are different protocols with different designs, and
> any research done on Google QUIC most likely focused on a single
> implementation (the Chromium implementation). Even within a single
> standard (IETF QUIC), we expect there are going to be different
> experimental results depending on implementations studied [1]. As such
> I would say right now it's best to rely on research conducted on IETF
> QUIC, rather than trying to transform results previously obtained for
> Google QUIC.
>
> All the best,
> Matt Joras
>
> [1]
> https://www.researchgate.net/publication/342783300_Same_Standards_Different_Decisions_A_Study_of_QUIC_and_HTTP3_Implementation_Diversity
>
> On Mon, Oct 18, 2021 at 2:43 PM Feltgen, Eric
> <eric.feltgen@rwth-aachen.de> wrote:
> >
> > Dear QUIC working group,
> >
> > I am a CS student at RWTH Aachen University currently researching papers
> on the performance of QUIC in the context of a seminar. In the past years,
> there have been many papers on this topic testing many different versions
> of Google's QUIC. Over the years, many changes have been made to the
> protocol and the implementation at Google.
> >
> > In order to understand which results are comparable to the standardized
> version of QUIC (RFC 9000), it would be helpful to which changes have been
> made in the last years of the Google version and how the last QUIC versions
> by Google compare to the QUIC standard. In my research so far, I found out
> that forward error correction has been removed from the Google version a
> couple of years ago. So my question is whether there are any breaking
> changes that have been made in the development of the IETF standard which
> could result in different behaviour.
> >
> > Thank you in advance for any response! It would help a lot to understand
> the development stop of the QUIC standard within the last years.
> >
> > Best regards,
> >
> > Eric Feltgen
> >
>
>