Re: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum

Miroslav Lichvar <mlichvar@redhat.com> Wed, 31 August 2022 10:10 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 90261C14F723 for <ntp@ietfa.amsl.com>; Wed, 31 Aug 2022 03:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.678
X-Spam-Level:
X-Spam-Status: No, score=-7.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D59eG3WQfdoU for <ntp@ietfa.amsl.com>; Wed, 31 Aug 2022 03:10:00 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEC13C14F6EC for <ntp@ietf.org>; Wed, 31 Aug 2022 03:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1661940598; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=PCL+YRhJZ7obT8brsHXs/TrhPdsl57+PPjA5TU0jbbM=; b=DWeBo3ZsQ4584lUDmi/Hj4LeW3mGrGzTW14tlQsX+PCWM7GZArAxtBzWAysiuDyyrjXQHP HL+A7jbJ7m0KwCG83VfDuNJVcpglKxGU9KTZIohgbGe4T3n/uKLbagfgFFUE0yiRkJi3tU M3XQz+8jConXKsrGI4rgOHnpDYy4U9M=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-53-GDzsqq_hPzyxL-Dc-4zthw-1; Wed, 31 Aug 2022 06:09:56 -0400
X-MC-Unique: GDzsqq_hPzyxL-Dc-4zthw-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id CA5C9800124; Wed, 31 Aug 2022 10:09:55 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 593CD2026D4C; Wed, 31 Aug 2022 10:09:55 +0000 (UTC)
Date: Wed, 31 Aug 2022 12:09:54 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <Yw8zcotenA7vaWbw@localhost>
References: <david@venhoek.nl> <CAPz_-SVPE-Fd1vFWnbu+GAPc=y2bkJMW4pyu98bBwDfcm+R2rg@mail.gmail.com> <20220830205143.DFDC328C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <Yw8NBX6ATjRr0/A4@localhost> <C492F298020000C2AB59E961@gwsmtp.uni-regensburg.de> <F347640002000095FDA5B133@gwsmtp.uni-regensburg.de> <8F7E1DA8020000866A6A8CFC@gwsmtp.uni-regensburg.de> <630F1321020000A10004D377@gwsmtp.uni-regensburg.de> <Yw8eVn34M+Ip6ey6@localhost> <630F2E3D020000A10004D3A6@gwsmtp.uni-regensburg.de>
MIME-Version: 1.0
In-Reply-To: <630F2E3D020000A10004D3A6@gwsmtp.uni-regensburg.de>
X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/IaUQXbUu8LjM30oWe7mHwS-i9ZQ>
Subject: Re: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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, 31 Aug 2022 10:10:05 -0000

On Wed, Aug 31, 2022 at 11:47:41AM +0200, Ulrich Windl wrote:
> Well, every phone call is a "loop": The microphone records what it hears from
> the other end of the line (and sends it back, where the other end does the
> same), too.
> If the amplification is too high you'll have a never-ending loop of noise; if
> it's low, it will vanish.

It's not just amplification. If you turn on the speakerphone, there
has to be something in HW or SW that is measuring the delay and
suppresing your signal in the loop. That is quite a difficult problem.

If that doesn't work very well, you can hear your echo from the other
end. That is annoying even if it doesn't amplify.

> I think NTP should only forbid the first example of a loop.

So, instead of detecting all loops you want to detect only loops that
lead to an amplifying oscillation? How exactly would you do that and
what would be the advantage?

-- 
Miroslav Lichvar