Re: Idea for packet numbers
Jana Iyengar <jri@google.com> Wed, 26 July 2017 14:16 UTC
Return-Path: <jri@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 BBD37132044 for <quic@ietfa.amsl.com>; Wed, 26 Jul 2017 07:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, 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 kgjfxLSPSXeI for <quic@ietfa.amsl.com>; Wed, 26 Jul 2017 07:16:39 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 F0C07132040 for <quic@ietf.org>; Wed, 26 Jul 2017 07:16:38 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id b8so8281898pgn.0 for <quic@ietf.org>; Wed, 26 Jul 2017 07:16:38 -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=G9GpGNIf7IdyO8IhUwRdjsXyD0tm8qBXGjRzpXQt5WM=; b=ho+shzcC2OVDbA+OMuYXnJ1FLWC1OPsLlX8FgYqY8aHvglvS28Qeoq+fS3CYjc4cI5 4906oj1gfSjYfFmkhCW6qLtvvlKweL3ATs60NUzq41UyGxLPkqwiT+aN9B8PxkdlvMln riJ4OjR/BXNptyLNltM85hMn8s9dGBc5SpDzPuZrFkJw+SygJWiZ5+V2Rjp1G8S/rBbt F8ORNh+6Q3JKNlAeDDZi91azcCHwX1eIumoh/KX5XjvjffFkLKZKXkxRnCoOcIINJT4Q OiB5JJQoRfD/4/niFnXp2Oh7oSTOoyX9yhM42F1O2KBsSZKC7FrIq4eOA/IYlfMc7HLh Z5eA==
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=G9GpGNIf7IdyO8IhUwRdjsXyD0tm8qBXGjRzpXQt5WM=; b=OjXLuwA5CjlptJ5HwLwnxIX8dX9cAFxDF0eoO55WAnfvZUh++Hpi7RZgFbvSDZMFQE MBl9Kp9m4t/9+MxDPewvyo5sgpF0+qioE6jRmADHZNahPHui6wuZ1E1sSJx/yro367gK 6uZe6tPLXAZFGo6qMxxYjFkFowGpGO8j4fiAUebSFG4ekgimL9ZZlxUIRla9U78Sd84P 9lfKTrO/xNRipmC5PlmIY4FHbPLM9MV1Mmh20/aXm8eWy757ocr6yGzVqfyp43Wntz1P AGssVP837VtvECHUC1P3WfqP9SB1WtryyszGmo/d+uinwGtkXXaMoTOSQIxOwaMjy+nW G5lw==
X-Gm-Message-State: AIVw113JNHSAx+KHJN9VrcfjPm5rkmEx0snh+rDeUjavmSWCOzmQGMYm up3YNeO9vEcKzZ0AOu0vVJAr2SjykeOf
X-Received: by 10.84.216.81 with SMTP id f17mr1101670plj.117.1501078598291; Wed, 26 Jul 2017 07:16:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.153.19 with HTTP; Wed, 26 Jul 2017 07:16:37 -0700 (PDT)
Received: by 10.100.153.19 with HTTP; Wed, 26 Jul 2017 07:16:37 -0700 (PDT)
In-Reply-To: <c7941a67-6eaa-cd58-d0e2-a764478aa5b0@ericsson.com>
References: <c7941a67-6eaa-cd58-d0e2-a764478aa5b0@ericsson.com>
From: Jana Iyengar <jri@google.com>
Date: Wed, 26 Jul 2017 14:16:37 +0000
Message-ID: <CAGD1bZaFd4NHzv9sSugBZFDHxAam64dSPmBoxvYS4hm-kpD0bA@mail.gmail.com>
Subject: Re: Idea for packet numbers
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19a6a8a2026705553918e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZtObrJ6euDuUGqiy183H2JayKUI>
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: Wed, 26 Jul 2017 14:16:41 -0000
(Going back to the original discussion) Magnus, IIUC, you are asking for a network device to be able to observe packets within a flow. don't understand what the value of encrypting the high order bits is if there are enough low order bits to allow linkability across packets within a flow. After all, the point of encyptimg packet number is to avoid linkability, isn't it? - jana On Jul 20, 2017 3:00 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com> wrote: > Hi, > > There has been some discussion around packet numbers. For passive > detection of packet loss in measurements and network management, it would > be really good if the packet numbers where continuous and not only > monotonically increasing. As this enables one to determine losses upstream > of the measurement point. At the same time I understand there are benefits > with being able to introduce gaps into the packet number to test the > receiver's behaviour. > > To enable both of these capabilities I would propose that the N least > significant bits of the packet number are strictly increased by one. Then > one can introduce gaps in the bits above the N ones. Yes, that will burn > through the packet number space faster as the gaps may become larger than > was the case without this. However, I don't see that this will have > significant effect unless the sender introduce gaps very frequently so that > the length of the packet number field needs to be much larger due to the > outstanding sequence number space is much larger. > > The value of N can clearly be discussed but it should be selected so that > reordering and common burst durations are shorter than the time to wrap the > strictly increase amount of bits. If the higher bits are available to > measurement node, some possibility to infer gaps will also be possible. It > might be that N needs to be scaled with throughput with a minimal value. > N=8 would mean 256 packets between wraps. I think that is a reasonable > minimal value. However, that will wrap in 28 ms at 100 mbps of payload > (assuming 1400 bytes of payload per packet). > > So what people think about this idea? > > > Cheers > > Magnus Westerlund > > ---------------------------------------------------------------------- > Media Technologies, Ericsson Research > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Torshamnsgatan 23 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > >
- Idea for packet numbers Magnus Westerlund
- Re: Idea for packet numbers Martin Thomson
- Re: Idea for packet numbers Mikkel Fahnøe Jørgensen
- Re: Idea for packet numbers Magnus Westerlund
- Re: Idea for packet numbers Martin Thomson
- Re: Idea for packet numbers Magnus Westerlund
- Re: Idea for packet numbers Martin Thomson
- Re: Idea for packet numbers Spencer Dawkins at IETF
- Re: Idea for packet numbers Dmitri Tikhonov
- RE: Idea for packet numbers Swindells, Thomas (Nokia - GB/Cambridge, UK)
- Re: Idea for packet numbers Ian Swett
- Re: Idea for packet numbers Mikkel Fahnøe Jørgensen
- RE: Idea for packet numbers Swindells, Thomas (Nokia - GB/Cambridge, UK)
- Re: Idea for packet numbers Dmitri Tikhonov
- RE: Idea for packet numbers Kyle Rose
- RE: Idea for packet numbers Swindells, Thomas (Nokia - GB/Cambridge, UK)
- RE: Idea for packet numbers MORTON, ALFRED C (AL)
- Re: Idea for packet numbers Ian Swett
- RE: Idea for packet numbers Swindells, Thomas (Nokia - GB/Cambridge, UK)
- Re: Idea for packet numbers Dmitri Tikhonov
- RE: Idea for packet numbers Swindells, Thomas (Nokia - GB/Cambridge, UK)
- Re: Idea for packet numbers Jana Iyengar
- Re: Idea for packet numbers Dmitri Tikhonov