Re: [ippm] New QUIC Packet Loss Measurement (draft-cfb-ippm-spinbit-measurements)

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Wed, 22 April 2020 20:05 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 0C0E63A07E1 for <quic@ietfa.amsl.com>; Wed, 22 Apr 2020 13:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 dZjfRFid6SXd for <quic@ietfa.amsl.com>; Wed, 22 Apr 2020 13:05:45 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 83FBE3A07E7 for <quic@ietf.org>; Wed, 22 Apr 2020 13:05:45 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id 20so3827688qkl.10 for <quic@ietf.org>; Wed, 22 Apr 2020 13:05:45 -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:content-transfer-encoding :in-reply-to:user-agent; bh=DHV4Q7JtKVmq2wNuIDcl7z9Ph7B/AjbL5HWsDsH/ryc=; b=DdMLpjF10ddOVCe6pRMy/T9PP2TWWa/K4ZMsWQT+iotkkA4rhajFm3Mb+r7c416zuc 3vWSKc4og+p7cLcsVmB5P504kCNWAMfyIvFIU9a3J96PMsmGfPoAfbzsaiRzaVz9zgRM i1hZ91IkrkeaT3aGGlsCU2OOD2jlzXrfiYn4uuGUccAiAU8BmGAvye+qSZMRt55J+Jni aDz+nXewe4d30I/SwumJoymzXGAh83shWN60W3GkSbT1mLawFP+NtmN/BMAckc/36PXo NBc94emjrjaeHzcpLSErK5YTU22OJwLSaBiCvj40z8u92f4U0j0u5RSrfSEIcenklnaj NqQw==
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 :content-transfer-encoding:in-reply-to:user-agent; bh=DHV4Q7JtKVmq2wNuIDcl7z9Ph7B/AjbL5HWsDsH/ryc=; b=QhWNzHTkb76stkmqrs0OOwI4TtP77TKSUitYBSu7Di45kXBSYNH1iJ3YRdkOxdgfQh /TQGsOpHC3/43xxGonCDmEmSq5EZf61gI8j4kHTsV+Geb0l66EZrdA+mfgnrLX8PHJAe wFxwhwh1WWSHzMPlmxLH2s4TXOF2FPJ4WHLVfj9G240G0xRqsIOfRx5rMoRNouNVLbp5 kb7yQNn9tI1oSrTGCA6DM22ZkOo6fY7DZsOPmPPMMHwrPcgf3Xc9guzTdVQFPftkFO5v LFhQckDXTlA7pEB/Pt784jPBMRD8XmLKJuisHcuPizidDFo5hP+2vkmTe/S6CxGj6gUd YEFA==
X-Gm-Message-State: AGi0PubFwr6upGVdwpSHN0JKWQUskfRLyLTENd2pkzoUcgK+FmA4FZ/O Ru0uXDBFtQ3TBJFBtqIf7Q/s3g==
X-Google-Smtp-Source: APiQypJhZYI1OfkkBkczcvm01zYrb1nE5HfG/iO4r0THZ0nUXq1i6dmf4t7esrtYvQwCftpqLnbfGw==
X-Received: by 2002:a37:96c4:: with SMTP id y187mr39428qkd.126.1587585944311; Wed, 22 Apr 2020 13:05:44 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id k2sm213926qta.39.2020.04.22.13.05.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Apr 2020 13:05:43 -0700 (PDT)
Date: Wed, 22 Apr 2020 16:05:31 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: "Bulgarella Fabio (Guest)" <fabio.bulgarella=40guest.telecomitalia.it@dmarc.ietf.org>
Cc: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, Ian Swett <ianswett@google.com>, Cociglio Mauro <mauro.cociglio=40telecomitalia.it@dmarc.ietf.org>, "isabelle.hamchaoui@orange.com" <isabelle.hamchaoui@orange.com>, Riccardo Sisto <riccardo.sisto@polito.it>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "quic@ietf.org" <quic@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Subject: Re: [ippm] New QUIC Packet Loss Measurement (draft-cfb-ippm-spinbit-measurements)
Message-ID: <20200422200530.GA11856@lubuntu>
Mail-Followup-To: "Bulgarella Fabio (Guest)" <fabio.bulgarella=40guest.telecomitalia.it@dmarc.ietf.org>, "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, Ian Swett <ianswett@google.com>, Cociglio Mauro <mauro.cociglio=40telecomitalia.it@dmarc.ietf.org>, "isabelle.hamchaoui@orange.com" <isabelle.hamchaoui@orange.com>, Riccardo Sisto <riccardo.sisto@polito.it>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "quic@ietf.org" <quic@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
References: <3ca3b5aae01d4650a3451639268b3f1e@TELMBXD14BA020.telecomitalia.local> <CAKcm_gMEELBizN_h5+s3Ow0LKXEgTRGg+-AqzJMZXVBDwQcDLA@mail.gmail.com> <6b9e74ac94114d28ae4a66f1e9625ebd@usma1ex-dag1mb6.msg.corp.akamai.com> <1587582698016.72632@guest.telecomitalia.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1587582698016.72632@guest.telecomitalia.it>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YWnW-K9qv5CN_zBBuB7RfbRtzCY>
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, 22 Apr 2020 20:05:47 -0000

Hello,

On Wed, Apr 22, 2020 at 07:11:38PM +0000, Bulgarella Fabio (Guest) wrote:
> 4. First of all, our solution is not dependent on any specific protocol
> implementation unlike the QL and therefore there shouldn’t be problems
> related to the quality of the implementation. In other words, our
> portion of code is always the same, in every protocol implementation.

I do not understand this part.  Problems in which protocol
implementation do you mean -- the loss measurement protocol
or some other protocol?  If the former, I do not understand
what you mean by "our portion of code:"  Each implementer will
write his own code, with his own bugs.

> Secondly, as anticipated in point 2, by observing only one direction
> we can measure the losses in the operator's domain (Qbit) and the
> end-to-end in the opposite direction (Rbit). So, our solution does work
> also for asymmetric path segments.

I already covered this, but I believe it can bear restating:
Besides loss measurement, a probe should aid to locate the source
of the loss: upstream or downstream.  A single QR probe cannot do it.
Do you not agree that locating loss source is one of the probe's goals?

  - Dmitri.