Re: [Ntp] Drafts on interleaved modes and correction field

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Wed, 08 November 2017 17:32 UTC

Return-Path: <tal.mizrahi.phd@gmail.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 219111293FF for <ntp@ietfa.amsl.com>; Wed, 8 Nov 2017 09:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VQHIg9tBpD5Z for <ntp@ietfa.amsl.com>; Wed, 8 Nov 2017 09:32:16 -0800 (PST)
Received: from mail-ot0-x244.google.com (mail-ot0-x244.google.com [IPv6:2607:f8b0:4003:c0f::244]) (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 DA7D1129477 for <ntp@ietf.org>; Wed, 8 Nov 2017 09:32:08 -0800 (PST)
Received: by mail-ot0-x244.google.com with SMTP id s88so2965738ota.4 for <ntp@ietf.org>; Wed, 08 Nov 2017 09:32:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YIsbiT9rLG++//jgL4nBkvsiPYyr3fAeIyMOWaxb+PU=; b=oxEHpebvCcFs9KxLYmI7IDr/Fba6Zc402oqZzn0Oh1Hn4cqoZTn4oJCE/ooGcDd/7d GdcAFYb5IlH731VC8RFGOXhNdi0EswNJ3LX3lo/S7nJGU3LQougSXIZQu2+Gsj47Xfmi qvinqiKAplMbI2DBq+PL1AFhFY/hWqZ6Pwnc7FDmblTbkqLqZMwwIfvxj/mlSzIG0uif 6QPrbXqhcLlfb7rgFaXcyzWjKYHCG/YFJxWpAgPCHeBgxoUzScurPfANuBsu5CUEsMxN 35vREsG+jxCIT/GWbGnpfB95c51xHmtawopXl6ibJct9/0fyJMQldGwrUbrB+HzMRIW6 hHeg==
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=YIsbiT9rLG++//jgL4nBkvsiPYyr3fAeIyMOWaxb+PU=; b=dIYbc9DBlD89nwo/rEXcKeabNS0qZbd1maZopZ3FfOzJn0CjVzApMj8408JjL9YTy8 o+wggZ9VRfjgj4PLl/sCBKIJ8BewJnCE8RQFEaKf/ALRQvx1cK7mOXA29KBj60zmFcts 0BMUN3oB5GJdl4RSKJSc/G2Y/ffjaOovayYZDVdM5Q/eTiah+OeoXruDzQh9YV5lXEYP Ei/i3hXbNSEcVpS1vMMciGf+hs1i/RWuGCzsd0Mp+y4MTkFPrvO7UsN+s6KT9rO+AaIk X2Wlk6zU5byzUgtHxYbkSjOesYubxqWYxMR/ge4r5w8BoGk1eMGcSgwoeWZrLmOb7zQT 120w==
X-Gm-Message-State: AJaThX4l1ddyf6J4F+gKSRQD80rh2n2gG6aOc8j+j/dHAYOAlGQ5wH2M JnkJAxQizRl4V2oEDdFLdcpB4W79/BWFmhtlE7AYEA==
X-Google-Smtp-Source: AGs4zMZ5zAbuk0c1kvK67WPEFkuGaf/G1/AcnzPcH7r13ZOoJIgDCHknOc8Iejpum9ldsIswhFvOAKeac3BjWPBMG58=
X-Received: by 10.157.47.145 with SMTP id r17mr775884otb.108.1510162328316; Wed, 08 Nov 2017 09:32:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.168.25.194 with HTTP; Wed, 8 Nov 2017 09:32:07 -0800 (PST)
In-Reply-To: <20171106123644.GA16738@localhost>
References: <20171031090139.GD15597@localhost> <CABUE3XmV1sUvq0KAJVrQv1sZ8vK6R8GwR+qeO1huTUgnOdujfQ@mail.gmail.com> <20171031135247.GB7648@localhost> <CABUE3X=pDEL9mcfoTGJw3PbwzHKnDTddr7Aqk71PyEBY77kzSw@mail.gmail.com> <20171031155717.GC7648@localhost> <CABUE3Xmz0YQ4OoDtE2SB-zimsA5yY32M1j3qotv_si4_OiqyHw@mail.gmail.com> <CABUE3XmHAgdowNV7ibfCMA0QGc6L6H=zA4=DZjgXaY8f04Cz5w@mail.gmail.com> <20171106123644.GA16738@localhost>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Wed, 08 Nov 2017 19:32:07 +0200
Message-ID: <CABUE3XkCkWoDyJ8cWHJCCjbpoEnt5bJ1JnmuQKseg++oz0BkhQ@mail.gmail.com>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: ntp@ietf.org, Aanchal Malhotra <aanchal4@bu.edu>
Content-Type: multipart/alternative; boundary="001a113cf8c221f408055d7c1184"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2U_6vSIAvTwoMYzNvJj6UJxr1AQ>
Subject: Re: [Ntp] Drafts on interleaved modes and correction field
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2017 17:32:18 -0000

Hi Miroslav,

> Do you know if there are any switches that actually support it?

Yes, some switches actually support it fast-to-slow cut-through.

>If a switch cut through from a faster link to a slower link, it would
>know the length of the packet and could calculate the (negative)
>correction before the correction field was transmitted, right?

Hmmm... So the switch would have to evaluate the packet length based on the
Length field in the UDP header, and use that in the correction field
computation.
It would be significantly easier to implement a correction field
computation based on first-bit-in-to-first-bit-out.


I may be missing something here, but I would argue that if we consistently
compute the correction based on first-bit-in-to-first-bit-out, the packet
transmission times on both directions would cancel out, and would not
affect the symmetry of the computation.
Can you provide an example in which this hypothesis is wrong?

Thanks,
Tal.



On Mon, Nov 6, 2017 at 2:36 PM, Miroslav Lichvar <mlichvar@redhat.com>
wrote:

> On Wed, Nov 01, 2017 at 11:41:26AM +0200, Tal Mizrahi wrote:
> > Small correction:
> > Slow-to-fast cut-through is *not* possible.
> > Fast-to-slow cut-through *is* possible.
>
> Do you know if there are any switches that actually support it? I
> suspect the buffering would be a major complication for a relatively
> small improvement in the overall latency.
>
> If a switch cut through from a faster link to a slower link, it would
> know the length of the packet and could calculate the (negative)
> correction before the correction field was transmitted, right? I
> assume that the field is in the second half of the packet and the
> ratio between the speeds is at least 2:1.
>
> I think the draft can specify that the correction needs to be
> calculated from the end of the reception and beginning of the
> transmission if the link speeds are different. If the speeds are
> equal, it can be any combination of beginning/end of the
> reception/transmission, because a symmetric correction will be made in
> the opposite direction. The delay will be different, but there won't
> be any asymmetry.
>
> Does that make sense?
>
> > > On Tue, Oct 31, 2017 at 5:57 PM, Miroslav Lichvar <mlichvar@redhat.com
> >
> > > wrote:
> > >
> > >> On Tue, Oct 31, 2017 at 04:59:52PM +0200, Tal Mizrahi wrote:
> > >> > Moreover, we never know which nodes along the path use
> > >> store-and-forward,
> > >> > and which nodes use cut-through. In cut-through forwarding the
> packet
> > >> > transmission may start before the last bit is received, so it
> certainly
> > >> > makes more sense to measure the first-bit-in-to-first-bit-out.
> > >>
> > >> That's a good point. With cut-through switching the correction would
> > >> be negative and generally couldn't be determined in time to be put in
> > >> the packet as the length is unknown. Are there any switches that can
> > >> cut-through from a faster link to slower link?
> > >>
> > >> Maybe it would make sense to allow corrections from preamble RX
> > >> timestamps when the link speeds are equal.
>
> --
> Miroslav Lichvar
>