IETF Logo Mail Archive

Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- NTP Extension Field drafts -- Four separate drafts

Miroslav Lichvar <mlichvar@redhat.com> Mon, 02 September 2019 09:59 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 98F9E120129 for <ntp@ietfa.amsl.com>; Mon, 2 Sep 2019 02:59:02 -0700 (PDT)
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 KSvaotr0UIdG for <ntp@ietfa.amsl.com>; Mon, 2 Sep 2019 02:58:59 -0700 (PDT)
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 DDF461200CE for <ntp@ietf.org>; Mon, 2 Sep 2019 02:58:59 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 76CE0307D851 for <ntp@ietf.org>; Mon, 2 Sep 2019 09:58:59 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EE3E15D6A7 for <ntp@ietf.org>; Mon, 2 Sep 2019 09:58:58 +0000 (UTC)
Date: Mon, 02 Sep 2019 11:58:54 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: ntp@ietf.org
Message-ID: <20190902095854.GC15024@localhost>
References: <Ulrich.Windl@rz.uni-regensburg.de> <5D6CB84E020000A100033405@gwsmtp.uni-regensburg.de> <20190902093750.DA05940605C@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190902093750.DA05940605C@ip-64-139-1-69.sjc.megapath.net>
User-Agent: Mutt/1.12.0 (2019-05-25)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.48]); Mon, 02 Sep 2019 09:58:59 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/wGTh9c38TGl-QAf6_etWs7Av0JM>
Subject: Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- NTP Extension Field drafts -- Four separate drafts
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Sep 2019 09:59:03 -0000

On Mon, Sep 02, 2019 at 02:37:50AM -0700, Hal Murray wrote:
> 
> Ulrich.Windl@rz.uni-regensburg.de said:
> > But remember that a "node" is NOT "an IP address". With multi-homed hosts you
> > can have interesting synchronization loops... ;-) 
> 
> Is there a problem with using an IPv6 address to identify a system?  (if you are multi-homed, just pick one)

If the system has multiple addresses, its clients may not know all of
them and may fail to detect loops. Addresses are no good.

We need each server (or rather the clock) to have an ID and extend the
protocol to exchange this ID so clients (that operate also as servers)
can reliably detect 1-degree loops. The suggested-refid EF basically
does that.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email