►
From YouTube: IETF109-NTP-20201116-0900
Description
NTP meeting session at IETF109
2020/11/16 0900
https://datatracker.ietf.org/meeting/109/proceedings/
A
A
A
A
A
A
A
So
the
next,
so
the
first
part
of
the
first
agenda
item
is
our
ntp
working
group
status.
We
have
a
couple
documents
that
are
with
the
iesg.
Now
we
have
the
mode
6
commands
and
the
yang
data
module
model,
so
there's
no
updates
to
those.
Yet
we
also
have
two
documents
that
are
ready
for
the
iesg
that
have
not
been
submitted.
A
A
C
C
Sound
so
great,
it
looks
like
that's
working
all
right,
so
I'll
be
discussing
rough
time,
the
rough
time
hackathon
experience
and
the
next
steps
in
the
protocol.
I
noticed
that
a
number
of
people
are
new,
so
I'll
give
a
quick
recap
of
rough
time.
So
it's
essentially
certificate
transparency
for
time.
C
It
will,
however,
ensure
at
the
time
is
correct,
and
one
of
the
wrinkles
in
this
is:
you
need
a
monotonic
time
representation,
because
you
want
to
have
the
case
that
you
can
compare.
The
timestamps
and
you'll
always
have
a
later.
A
causally
later
timestamp
be
a
numerically
greater
value
and
to
adopt
this,
we
use
a
representation
based
on
the
modified
julian
date
and
microsecond
since
midnight.
So
there's
a
number
there's
some
bit
packing.
C
So
I
meant
the
hackathon,
so
worker,
cloudflare
and
cloudflare
has
a
client
and
server
implementation
and
there's
now
a
branch
that
implements
the
rough
time
version.
3
draft
there's
still
work
to
be
done
on
updating
the
interfaces
with
some
of
the
changes
that
have
happened
in
the
draft
and
fixing
some
of
the
usability
issues
around
the
library
that
we
provide,
but
that
you
know
general
cleanup,
but
it
does
implement
it
and
the
server
interoperated
within
it
with
a
client
from
johann.
C
C
C
C
I
I
think
at
that
point,
we'll
we'll
sort
of
be
ready
for
a
working
glass
call
didn't
find
any
issues
with
interoperability.
I
don't
think
from
from
the
draft
tax:
that's
pretty
pretty
nice,
some
particular
areas
of
concern.
So
I
mentioned
earlier
that
there
was
this
problem
with
minimum
with
getting
the
information
out
of
the
kernel.
C
Well,
if
your
minimum,
you
can
only
that
only
changes.
The
time
by
one
second
so
is,
is
having
a
server
say.
Okay,
I
only
know
the
time
within
a
second.
I
am
just
using
get
time
a
day
enough
or
maybe
it
needs
to
be
a
little.
It
needs
to
be
a
little
bigger
with
a
modified
julian
date.
Representation.
C
C
You
need
to
know
whether
what
the
last
seconds
number
is
there's
also
invalid
representations.
The
number
of
seconds
in
a
day
is
not
a
power
of
two
and
because
it
is
not
a
power
of
two,
there
are
a
number
of
values
that
should
never
appear
and
the
invitation
when
you
program
this
is
to
do
your
arithmetic
on
a
degenerate
representation.
Just
take
the
set
microseconds
part
and
add
in
the
timestamp
normalize
afterwards.
C
C
C
There's
a
small
number
of
earlier
versions
deployed
mostly
of
the
google
version
that
was
kicking
around
for
madame
langley,
not
enough
financial,
three
servers,
I
I
think,
there's
exactly
one
of
them
and
it's
not
working
right
now
and
got
restarted
every
day
and
there
need
to
be
places
to
report
malfeasance
there
needs
and
we
also
need
clients
and
just
as
a
this
is
a
certificate
verifying
client
needs
to
have
policies,
certificates,
verifies
or
a
certificate.
Transparency,
implementation,
a
client
that
uses
certificate.
Transparency
needs
to
trust
her
in
logs.
C
C
D
C
A
A
C
A
A
A
A
So
this
is
the
contribution
from
marislav
that
will
get
submitted
at
some
point.
The
other
thing
that
I
wanted
to
point
people
to
was
the
track.
The
wiki
which
we
haven't
updated
in
a
while.
But
if
you
look
at
the
wiki,
there's
a
potential
ntp
work
items
and
there's
basically
a
list
of
version,
4
issues
and
a
version
5
feature
requests.
A
A
C
I
don't,
I
think
at
this
point,
it's
pretty
early
to
say
much
about
it,
it's
in
part
because
it
intro
it
talks
a
lot
about
the
data
format,
but
doesn't
talk
about
gathering
for
some
of
the
more
interesting
extensions,
but
I
I
think
it's
in
reason.
You
know,
I
think
it's
in
reasonably
good
shape
for
your
starting
point.
C
A
D
C
Okay,
watson
yeah,
I'm
not
sure
what
was
meant
by
narrowing
the
scope.
If
I
I
think
there
was
some
degree
of
agreement
that
we
should
specify
the
network
lay
in
the
network,
wire
format
and
the
algorithms
for
steering
somewhat
independently,
basically
split
split,
the
current
structure,
where
it's
algorithms
for
treating
the
clock
and
the
network
protocol
in
one
big
document
and
split
it
up
in
part,
because
we
of
operational
experience
where
you
can
use
other
algorithms
that
works
fine,.
A
A
A
E
Here
we
go
okay
great,
so
I
I
just
wanted
to
follow
up
on
that
last
comment
about
other
modes
of
operation
and
the
possibility
of
marking
marking
them.
As
you
know,
no
longer
recommended
or
something
you
know.
I
think
I
think
this
is
a
discussion
worth
having
you
know.
We
want
backwards
compatibility,
but
we
could
say
we're
phasing
these
loads
out.
E
A
A
We
have
been
promising
some
rechartering
texts
for
a
while,
but
we
have
not
done
that
yet
I
just
had
that
open.
I
have
created
an
ether
pad
to
start
collaborating.
We
got
some
volunteers
at
our
last
virtual
interim
to
work
on
the
to
work
on
some
chartering
text
and
we
did
not
make
any
progress
on
that.
That's
mostly
my
fault
for
not
pulling
it
together.