IETF Logo Mail Archive

Re: Removing packet number gaps

Victor Vasiliev <vasilvv@google.com> Tue, 02 January 2018 14:43 UTC

Return-Path: <vasilvv@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 E0E1912773A for <quic@ietfa.amsl.com>; Tue, 2 Jan 2018 06:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qEGYAH_zUfD5 for <quic@ietfa.amsl.com>; Tue, 2 Jan 2018 06:43:54 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 23334127735 for <quic@ietf.org>; Tue, 2 Jan 2018 06:43:54 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id v188so34183331qkh.11 for <quic@ietf.org>; Tue, 02 Jan 2018 06:43:54 -0800 (PST)
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=aFwSkR/QQaEJDMfAjmZ2VO3h4sbdiqwPWwuz1eLmSsg=; b=btirxH7F0hqw/JkeXcySeWn3ay4ULIlisa/JnH/DrUk1XB4XzoU47O9zArq+nNz6YZ wfknj1jueVXgBpmm9BIhLUzaYgsv1f3Em3s/PbyFO0bM+BsynQ9MX/iai3rfxEGuiPGV eCPBtztM+PU1bCmtHhmvc4ttYC69ydXRGLuWlfyx31/uN6fyyAI43Hs2rwDr0tnjLhv2 t+aIJRuNJAyfKIjJhmihYzyFd8bVolxVszOtTQ9rtR9Qrc/YD0+iBRIyADDcJa+6lBE1 40lYP9Ys+6AJ7wbQCevucp90D4iPDe96+xycowAnVFDNdTNn21wkTp+hl8YzsXMRO+Ir vedA==
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=aFwSkR/QQaEJDMfAjmZ2VO3h4sbdiqwPWwuz1eLmSsg=; b=gL3b1bLBRwrocahsuhjqQlPz5yDwPku1wUDl93H46IsmrqlM5fmH1is3jv//Rr1cGX +0VeaW+VWoL+p1NDhzNQJe2Ie06UbWzw0x1HmOvoLe5/NAFb0uSDszjTpKX6DfSPIQN4 RHFoBiThrelEkzhEciwVYKBgwIyU/feBU5xPeqbVzITij5q1V0HlUrbteIKRXJrQpWMg aPOA3gkyIJVJZw4YazxlZ8SManCVhGiUzOy9nCDxzjthfS4iAI1VQp42OlxtFzjYqJMd 6GKfPbxV98hQkd2OzvVsUvLwk6jVXO7VRE7V3aGRHQqNcTTvLSpNHU7aFp5oy16+FBxH z1bA==
X-Gm-Message-State: AKGB3mKyRTaQdzbrXRpexbQAXX09COswkElyIe3F2JZgEkeob8Iw9BYC irpsKuMWnXGQg2GdBIxqA/nuJZU4jXo8eEJZjgr7Ug==
X-Google-Smtp-Source: ACJfBot+SwnazM041cvnzRuWDECUDttn1nZqeusToIpgOLVGXXw3GKVJ+8GZuBlz/XiOm/+sVEgDtC+izzdCbaNwiOM=
X-Received: by 10.55.159.6 with SMTP id i6mr18234029qke.315.1514904232998; Tue, 02 Jan 2018 06:43:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.233.237.211 with HTTP; Tue, 2 Jan 2018 06:43:52 -0800 (PST)
In-Reply-To: <CABkgnnW89B+5Qo0u_+Wr5K0wCRZ3Wp-+CTWJbHRGGwD06hn-zw@mail.gmail.com>
References: <CABkgnnW89B+5Qo0u_+Wr5K0wCRZ3Wp-+CTWJbHRGGwD06hn-zw@mail.gmail.com>
From: Victor Vasiliev <vasilvv@google.com>
Date: Tue, 02 Jan 2018 09:43:52 -0500
Message-ID: <CAAZdMac_HjK+R-0_8i9GDvO_QjeRjciE+=ZharpP697NJYDc-g@mail.gmail.com>
Subject: Re: Removing packet number gaps
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05d984adc5990561cc20a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qkcbLOA7poP0tx2KbCKYk6Ftfno>
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, 02 Jan 2018 14:43:56 -0000

On Mon, Jan 1, 2018 at 8:57 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> However, Christian just identified one that I think makes this more
> important to address: when using a new connection ID, the gap is the
> same size on both client and server.  This makes flows linkable.  The
> gaps between the last packet on the old flow and the first packet on
> the new flow can be calculated in both directions.  Flows can be
> linked by finding flows where client-to-server packets have the same
> (or very close) gaps as server-to-client packets.
>

Why not just have different gaps for the client and the server?

v2.23.0 | Report a Bug | By Email