[Ntp] Antw: [EXT] Re: RFC 8633 (NTP BCP), Appendix A: "restrict source ..."
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 06 July 2021 12:09 UTC
Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 873103A2525 for <ntp@ietfa.amsl.com>; Tue, 6 Jul 2021 05:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 IATjjNKbfOHq for <ntp@ietfa.amsl.com>; Tue, 6 Jul 2021 05:09:19 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A3363A2526 for <ntp@ietf.org>; Tue, 6 Jul 2021 05:09:18 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2260E6000056 for <ntp@ietf.org>; Tue, 6 Jul 2021 14:09:11 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id EEA02600004D for <ntp@ietf.org>; Tue, 6 Jul 2021 14:09:09 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 06 Jul 2021 14:09:09 +0200
Message-Id: <60E447E4020000A100042330@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Tue, 06 Jul 2021 14:09:08 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: martin.burnicki@meinberg.de
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <YNRtXhduDjU4/0T9@localhost> <36AAC858-BFED-40CE-A7F7-8C49C7E6782C@meinberg.de> <YNnSj8eXSyJ89Hwv@localhost> <D32FAF20-F529-496C-B673-354C0D60A5AF@meinberg.de> <YNrDGy2M2hpLz9zc@localhost> <60E414ED020000A100042305@gwsmtp.uni-regensburg.de> <db655230-f6dd-322c-6837-606280cddceb@meinberg.de>
In-Reply-To: <db655230-f6dd-322c-6837-606280cddceb@meinberg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/rjVldkpo3_Wb9abj_gDklDFIHhU>
Subject: [Ntp] Antw: [EXT] Re: RFC 8633 (NTP BCP), Appendix A: "restrict source ..."
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 06 Jul 2021 12:09:25 -0000
>>> Martin Burnicki <martin.burnicki@meinberg.de> schrieb am 06.07.2021 um 10:55 in Nachricht <db655230-f6dd-322c-6837-606280cddceb@meinberg.de>: > Hi Ulrich, > > Ulrich Windl wrote: >> Hi! >> >> Reading RFC 8633, Appendix A, specifically A.2, I was confused a bit: >> The last line says "restrict source..." (and the preceding lines had > "restrict default..."). >> The point is that "default" is a literal keyword, but "source" is not > (AFAIK). > > Yes, "restrict source ..." it valid syntax, which has been introduced > int ntpd 4.2.8, if I remember correctly. Sorry for that. I looked up "man ntpd.conf" for ntp-4.2.8p15-94.2.x86_64 of SLES 12 and there "source" is not explained. > > The HTML docs of the current ntpd distribution says (in access.html): > > "restrict source" configures a template restriction automatically added > at runtime for each association, whether configured, ephemeral, or > preemptable, and removed when the association is demobilized. > > If I remember correctly, this was introduced to fix a problem e.g. with > pool server entries. If you had a restrict line like > > restrict default ... nopeer > > then automatic associations e.g. due to the "pool" directive wasn't > possible. > > restrict source ... > > now adds the specified permissions to such associations that are created > automatically. OK, but still an explaining sentence wouldn't have been that wrong ;-) Regards, Ulrich > > > Martin > -- > Martin Burnicki > > Senior Software Engineer > > MEINBERG Funkuhren GmbH & Co. KG > Email: martin.burnicki@meinberg.de > Phone: +49 5281 9309-414 > Linkedin: https://www.linkedin.com/in/martinburnicki/ > > Lange Wand 9, 31812 Bad Pyrmont, Germany > Amtsgericht Hannover 17HRA 100322 > Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, > Andre Hartmann, Heiko Gerstung > Websites: https://www.meinberg.de https://www.meinbergglobal.com > Training: https://www.meinberg.academy
- [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- Re: [Ntp] NTP over PTP Doug Arnold
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- Re: [Ntp] NTP over PTP Doug Arnold
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- Re: [Ntp] NTP over PTP Doug Arnold
- Re: [Ntp] NTP over PTP Miroslav Lichvar
- Re: [Ntp] NTP over PTP Heiko Gerstung
- [Ntp] RFC 8633 (NTP BCP), Appendix A: "restrict s… Ulrich Windl
- [Ntp] Antw: [EXT] RFC 8633 (NTP BCP), Appendix A:… Ulrich Windl
- Re: [Ntp] RFC 8633 (NTP BCP), Appendix A: "restri… Martin Burnicki
- [Ntp] Antw: [EXT] Re: RFC 8633 (NTP BCP), Appendi… Ulrich Windl
- Re: [Ntp] RFC 8633 (NTP BCP), Appendix A: "restri… Harlan Stenn