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

Miroslav Lichvar <mlichvar@redhat.com> Mon, 06 November 2017 12:37 UTC

Return-Path: <mlichvar@redhat.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 EFE4A13FBED for <ntp@ietfa.amsl.com>; Mon, 6 Nov 2017 04:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 G4l7bs-2Iu9q for <ntp@ietfa.amsl.com>; Mon, 6 Nov 2017 04:37:10 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CF7913FB57 for <ntp@ietf.org>; Mon, 6 Nov 2017 04:37:10 -0800 (PST)
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C26B849035; Mon, 6 Nov 2017 12:37:09 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C26B849035
Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@redhat.com
Received: from localhost (unknown [10.43.2.117]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D901D5D9C7; Mon, 6 Nov 2017 12:37:08 +0000 (UTC)
Date: Mon, 06 Nov 2017 13:36:44 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Cc: ntp@ietf.org, Aanchal Malhotra <aanchal4@bu.edu>
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABUE3XmHAgdowNV7ibfCMA0QGc6L6H=zA4=DZjgXaY8f04Cz5w@mail.gmail.com>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 06 Nov 2017 12:37:09 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/0N7Psd80QxdRfMGRQWMudf2MSA8>
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: Mon, 06 Nov 2017 12:37:11 -0000

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