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

As someone who has far less experience of black magic I don't quite get the
problem or proposed solutions. New thread maybe?

On Wed, Sep 4, 2019, 3:27 AM Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
wrote:

> >>> Heiko Gerstung <heiko.gerstung@meinberg.de> schrieb am 04.09.2019 um
> 12:05
> in
> Nachricht <93C7B33D-8B6C-4FDF-A55E-7B20AB7B03BE@meinberg.de>:
> > Using a Ethernet mac address or an IP address will allow to identify a
> server
> > if it is included in the "sync chain" data set, I therefore would
> > definitively go for a random ID. I am not yet decided if it should be
> allowed
> > to let the user assign a static ID via configuration as that would make
> > duplicates/collisions more likely than the random ID approach.
>
> It there an RFC about "Operators aren't allowed to do silly things"
> already?
> ;-)
> Maybe the default (recommended setting) should be random on every daemon
> start, but I do not like seemingly arbitrary restrictions...
>
> Regards,
> Ulrich
>
> >
> > Regards,
> >     Heiko
> >
> >
> > On 04.09.19, 11:52 "ntp im Auftrag von Miroslav Lichvar"
> > <ntp-bounces@ietf.org im Auftrag von mlichvar@redhat.com> wrote:
> >>
> >> On Tue, Sep 03, 2019 at 05:05:44AM -0700, Hal Murray wrote:
> >>> I think there are two approaches.
> >>>
> >>> One is to use random data. The probability of a collision can
> >>> be made
> >>> arbitrarily small by making the number of bits in the ID big
> >>> enough. That
> >>> needs good randomness.
> >>>
> >>> The other approach is to piggyback on some other scheme that
> >>> has already
> >>> solved the problem.
> >>
> >> The former makes more sense to me. We don't need the ID to be
> >> static.
> >> Generating a random number on each start should be fine.
> >>
> >>> Can we assume that every server will have a globally routeable
> >>> IPv6 address?
> >>
> >> No. IPv6 is not universally available. Address translation is
> >> common, so we cannot assume an IPv4 or IPv6 address is unique.
> >>
> >>> Can we assume that every server will have an Ethernet host address?
> >>
> >> The vast majority will, but I'm not sure we can rely on them
> >> being random.
> >>
> >>> In both cases, for multi homed servers, just pick one. After
> >>> that choice,
> >>> it's an ID, no longer an address.
> >>
> >> Yes. And it's important that all clients get the same ID.
> >>
> >> --
> >> Miroslav Lichvar
> >>
> >> _______________________________________________
> >> ntp mailing list
> >> ntp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ntp
> >
> >
> >
> > --
> > Heiko Gerstung
> > Managing Director
> >
> > MEINBERG® Funkuhren GmbH & Co. KG
> > Lange Wand 9
> > D-31812 Bad Pyrmont, Germany
> > Phone:    +49 (0)5281 9309-404
> > Fax:        +49 (0)5281 9309-9404
> >
> > Amtsgericht Hannover 17HRA 100322
> > Geschäftsführer/Management: Günter Meinberg, Werner Meinberg, Andre
> > Hartmann, Heiko Gerstung
> >
> > Email:
> >  heiko.gerstung@meinberg.de
> > Web:
> >  Deutsch   https://www.meinberg.de
> >  English    https://www.meinbergglobal.com
> >
> > Do not miss our Time Synchronization Blog:
> >  https://blog.meinbergglobal.com
> >
> > Connect via LinkedIn:
> > https://www.linkedin.com/in/heikogerstung
> >
> >
> >
> > _______________________________________________
> > ntp mailing list
> > ntp@ietf.org
> > https://www.ietf.org/mailman/listinfo/ntp
>
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp
>