►
From YouTube: IETF106-SAAG-20191121-1330
Description
SAAG meeting session at IETF106
2019/11/21 1330
https://datatracker.ietf.org/meeting/106/proceedings/
B
B
A
C
A
D
Yeah
we
there
were
presentations
on
some
ongoing
working
group
documents,
delegate,
credentials
exported
authenticators,
and
then
we
had
some
new
work
on
batch
signing
compact
II
since
I'm.
He
said
act.
If
you
helmet
and
I
just
sent
the
report
they're
just
good
to
go
so
and
then
we're
gonna
be
talking
about
yes,
Annihilator
today,
so
yeah.
D
B
D
A
E
E
B
F
A
B
They
have
the
sort
of
name
of
the
acp
domain
in
the
you
know,
domain
part
of
the
a
22
name,
but
then
there's
some
some
other
stuff
as
well,
including
like
a
arbitrary
subdomain
name
and
a
whole
form
or
extensions.
And
it's
it's
a
little
bit
weird
to
be
constructing
your
own
structured
name
within
the
constraints
of
the
a.22
name,
at
least
to
me.
G
All
right,
so
you
asked
about
possible
stuff
in
the
security
area,
so
the
UT,
a
working
group,
hasn't
met
for
awhile
and
there
is
like
the
old
stuff
to
clear
up,
but
we
had
a
couple
of
a
couple
of
us
had
a
discussion
in
a
break
whether
it's
time
to
do
a
BCP
on
deployment
experience
from
103
or
if
it's
too
soon
is
there
stuff.
You
know
that
should
get
out
there
in
terms
of
like
that
kind
of
the
kind
of
stuff
that
we
put
in
in
the
BCP
for
1.2.
B
I
think
I'd
started
talking
to
the
TLS
chairs
a
little
bit
about
that,
and
you
know
there's
maybe
some
work
to
do
in
the
space
about
updating
our
recommendations.
Like
a
is
a
PCP
210,
195
I,
don't
remember
the
RSC
75252.
You
include
to
us
we're
not
three
in
those
recommendations
but
I
think
we
and
you
Chris
and
Joe
and
Shawn.
You
can
correct
me
if
I'm
wrong,
but
I
think
we
decided
that
we
will
but
more
to
get
a
little
bit
more
deployment
experience.
G
That
was
gonna,
be
my
photo
of
question
whether
that's
gonna
be
the
focus.
Maybe
it
may
be.
It
will
be
right,
but
anyway
I
guess
the
working
group
will
hibernate
for
a
while,
and
you
know
see
if
some
something
else
turns
up
I,
don't
think
so,
but
I
think
we'll
wait
for,
for
you
guys
to
tell
us
when
it's
time
to
wake
up
and
do
some
work.
Okay,.
H
Moss
would
say
she
consulting:
you
have
TMR
ID
up
there.
The
decision
seems
to
be
to
move
forward
to
a
working
group
for
TMR
d.
We're
now
we're
here
in
the
scope
of
the
other
charter
of
interest
to
the
stag
group
would
be
Graf,
Whitaker,
tiem,
Rd,
I'm,
off
and
Adam
has
an
interesting
spelling
of
Whitaker.
So
I
suggest
you
look
at
the
boss
information
to
get
the
proper
spelling
to
find
the
draft.
The
reason
I
mention
it
is
that
one
of
the
things
that
we
have
to
struggle
with
is
authenticating.
H
These
really
short
messages
previously
sent,
which
we
hash
and
then
include
the
hashes
in
the
auth
message,
which
is
then
signed
so
discussion
on
what
we
have
created
there,
the
first
set
of
thoughts
we
have
on
that.
We're
really
open
to
other
ideas
and
thoughts,
are
working,
this
extremely
constrained
environment
and
how
to
authenticate
25,
byte
messages
and
and
to
prove
the
owner
of
which
actually
you
a
sent
those
messages
by
hashing
them
and
including
them
in
the
much
longer
auth
message.
So
a
bunch
of
other
eyes
on
that
draft
are
greatly
appreciated.
I
Just
a
quick
note,
since
you
do
have
NTP
up
there,
we
did
submit
NTS
to
the
is
G,
so
hopefully
that's
almost
done
and
we
have
adopted
two
additional
drafts
that
are
related
to
security,
one
on
rough
time
and
one
on
Chronos.
So
those
are
security,
related
items
that
are
going
on
in
the
NTP
working
group.
Thank.
B
J
Yah
react
so
there's
been
some
amount
of
activity
on
that,
so
we
Stephen
I
emerged
our
draft
we're
still
working
on
through
the
other
feedback
that
we've
gotten
and
at
this
idea
we
had
a
site
meeting.
22
people
attended
and
it
seems
like
there
was
quite
a
bit
of
interest
and
some
set
of
people
willing
to
contribute
different
aspects
of
the
topic,
and
so
we're
cranking
away,
I
think
and
gets.
The
overall
plan
is
that
we
will
provide
some
documentation
and
rationale
for
you
know
why.
Why
are
we
in
this
situation?
Essentially
I?
J
Guess
because
we've
made
some
progress
in
terms
of
communication,
security
and
now
some
of
the
threats,
our
that
we
have
to
worry
about
are
the
remaining
ones
and
that's
why
the
focus
has
has
changed,
and
you
know,
isn't
this
sort
of
supporting
documentation,
we'd
like
to
get
sort
of
one
pager
that
that
is.
You
know
this
is
how
we
would
like
to
change
our
see
3552
it's
at
least
my
interpretation
of
the
of
the
situation,
but
war
continues.
Yeah.