►
From YouTube: IETF-SCITT-20221212-1600
Description
SCITT meeting session at IETF
2022/12/12 1600
https://datatracker.ietf.org/meeting//proceedings/
E
C
A
A
F
F
F
A
E
A
A
F
A
G
A
G
A
G
A
A
A
So
just
keep
that
in
mind
and
now,
if
we,
if
we
go
to
that
link
and
and
now
we
keep
trying
to
make
sure
that
this
is
somehow
displays
some
in
some
way,
I
will
let
Hank
talk
a
little
bit
about
what
what's
happening
with
this
BR
and
and
like
what
are
the
open
issues?
What
can
be
improve
or
whether
anyone
has
any
questions
on
on
this
PR
thanks.
G
Okay,
thank
you
harness
so
yeah
I
took
a
little
bit
over
the
reins
here
for
this
document
as
yoga
just
PTO
until
the
beginning
of
next
year
and
so
yeah
via
had
a
relatively
young
refactoring
of
the
whole
document,
which
yogish
basically
rewrote
from
scratch,
including
two
exemplary
use
cases
in
detail.
These
are
called
firmware,
delivery
to
a
large
set
of
constrained,
OT
devices
and
the
other
one
was
called
up.
I
don't
know.
G
That's
me
often,
no,
it's
also
not
correct
I'm
I'm,
looking
at
the
different,
probably
I,
can't
see
the
other
headings
so
I'm.
Sorry
for
that.
So,
but
there
are
two
use
cases
from
yogesh,
basically
structured
into
a
general
generic
overview,
then
into
a
leading
into
the
actual
use
case,
and
then
a
problem
summary
why
the
problem
summary
was
a
list
of
pallets
items.
Always
so
I
tried
to
adhere
to
that
structure,
but
it
was
very
difficult
for
me
to
formulate
additional
use
cases
in
that
structure.
G
So
I
was
not
waiting
for
my
time
that
I
scheduled
this
dick
to
reward
or
rephrase.
This
is
our
use
case
about
the
trust,
one,
the
image
to
the
email
list,
but
try
to
get
other
use
cases
too
in
order
to
get
an
understanding
how
to
phrase
them
and
how
to
mostly
adhere
to
yogish
template.
So
my
the
results
were
two
other
use
cases.
G
One
is
called
updated
statements
over
time
and
the
statement
literally
means
statement,
as
used
in
the
in
the
now
come
on
skid
architecture.
I
think
we
had
this
rewarding
of
statement,
sign
statement
and
transparent
statement.
So
these
these
these
initial
things
that
are
signed
in
a
claim
they
are
now
basically
changing
over
time.
How
would
we
deal
with
that?
That's
the
first
one
and
the
second
one
is
about
promoting
software.
G
So
if
you're
not
the
if
the
original
place,
you
are
you're,
not
not
getting
software
from
the
original
place,
but
but
from
a
from
a
packager
or
from
another
website
in
the
internet.
How?
How
can
you
make
sure
that
this
is
actually
the
thing
you
want
to
have?
So
that's
that's
the
second
use
case
and
this
this
starts
with
very
Layman's
words
and
limits.
G
Remember
it's
a
description
with
single
sentences
that
actually
go
through
a
process
of
things
happening
as
not
deliberately
not
using
architecture,
language
or
terminology,
but
layman's
terms
and
and
then
highlight
how
this
works.
So
it
really
would
help
if
you
could
look
at
the
or
Insurance,
maybe
trying.
That
is,
if
you
could
look
at
the
document
itself,
because
otherwise
it
will
start
to
explain
what
what
was
written
there.
But
these
two
examples
helped
me
to
find
a
pattern.
G
First
of
all,
these
selection
have
been
done
by
me.
They
are
not
reviewed
by
others
or
were
not
reviewed
by
others
before
I
think.
Meanwhile,
they
experience
some
review
from
others,
especially
Brian
I
think
made
a
whole
food,
but
also
others
chimed
in
here
and
made
small
fixes
to
text
so
it's
red
by
a
few
stakeholders,
I
assume
and
and
and
then
creating
a
feeling
for
how
this
could
work.
G
G
G
So
I
think
that's
that's
pretty
straight
or
forward
for
me
and
and
maybe
when
yogas
comes
back,
we
can
find
a
compromise
between
the
two
styles
that
now
exist,
because
the
three
first
ones
are
different
styles
but
similar
to
yogish's
one,
and
we
can
find
a
common
group
but
I
think
the
content
is
for
these
five
use
cases
is
there
now
and
we
have
to
agree
on
how
to
actually
mold
it
and
phrase
or
massage
it.
So
they
look
comparable
because
I
broke
interoperability.
G
G
Maybe
dick
can
a
little
bit
elaborate
on
on
what
he
thinks
or
how
well
this
worked
out
and
if
you
have
never
used
leakage
before
below
your
name
on
the
top
there's
a
there's,
a
hand.
That
is
a
strikethrough.
If
you
unstrike
your
hands
so
to
speak,
you
are
in
the
queue
and
there's
a
microphone
on
the
very
right.
You
have
to
also
get
that
activated
next
to
the
camera
icon
such
and
then
you
can
and
then
your
Audible,
whatever.
E
E
A
G
A
B
A
A
Has
someone
had
the
chance
to
look
at
this
VR
I?
Send
it
out
in
the
in
the
agenda
and
meeting
invite,
but
I
wasn't
quite
sure
whether
any
one
of
you
has
had
a
chance
already
to
to
look
into
the
use
case
description
and
whether
you're
happy
with
it
or
or
maybe
you
had
have
suggestion
for
some
new
text.
F
Just
a
cursory
review,
the
the
format
of
it,
the
way
that
Hank
has
broken
out
into
the
description,
and
then
you
know
the
what
the
consumer
wants
and
then
the
need
for
standardization
that
that
makes
sense
to
me.
Yeah
I
have
a
follow-on
question
from
that.
I
think
we
want
to
go
from
here.
The
use
case
description
too,
at
some
point
creating
a
list
of
user
requirements.
A
H
A
C
B
H
A
A
A
D
D
D
F
F
H
D
H
H
H
A
A
F
F
F
H
C
A
A
And
I
think
what
we
also
have,
which
is
like
the
the
use
case
write-up,
that
Hank
was
working
on
basically
last
week,
like
judging
from
the
many
commits
he
submitted,
so
that
that's
also
great,
and
if
we
jump
back
to
that
use
case
Hank.
What
do
you
think
is
missing,
like,
besides
the
sort
of,
and
how
did
you
phrase
it-
sort
of
misbalance
between
some
of
the
use
cases
in
terms
of
writing
style
but
like
where
do
we
go
from?
Can.
H
A
H
D
A
H
D
So
when
I
was
writing
my
document
just
just
bring
down
some
of
my
thoughts.
The
one
thing
I
I
question
is
whether
there
should
be
some
statements
of
negative
use.
They
could
be
very
easy
to
use
a
a
this.
This
product
is
no
longer
under
support.
You
should
go.
You
use
the
new
one
and
charge
you
a
5.95
for
the
next
version.
Do
we
have
want
to
make
any
statement
of
saying
hey?
This
should
not
be
used
for
marketing
purposes
or
to
drive
forever.
D
D
D
Well,
it's
a
question
of
I:
don't
want
to
be
used
as
a
way
to
drive.
Revenue,
like
you
realize
version
two
you
shouldn't
be
able
to
say:
hey
version,
one
is
is
no
longer
safe.
You
must
use
version
two
and
chart
force
you
to
use
to
spend
money
when
there's
something
nothing
wrong
with
the
last
version
like
it
would
be
basically
a
what
do
we
want
by
convention
to
do.
G
I'm
I'm
on
a
different
topic,
but
I
think
here
I
think
we
are
mixing
actually
the
the
topic.
That
is
that
my
brought
up
is
mixing
use
case
to
run
with.
What's
the
policy
on
how
to
how
the
whole
specification
text
is
used
in
where
we're
created,
yeah
and
and
I
think
both
both
are
kind
of
in
that
realm
I,
don't
know
we
have
to
talk
more
about
that.
G
G
So
this
is
an
interesting
chaos
session,
so
please
bear
with
us.
Situations
will
improve
and
having
back
China
conferences
that
basically
oh
101
explain
how
this
works
is
one
thing
to
do.
We
can
also
set
up
a
a
training
session
and
then
screen
share
around
that,
so
that
I
think
that's
absolutely
fine
to
do,
especially
when
we
are
approaching
up
to
the
Christmas
days.
Maybe
the
schedule
is
a
little
bit
less
strained
and
we
have
time
for
like
a
like
a
test
session.
G
Whoever
wants
I
need
some
introduction
and
guidance
whatever
so
I
I
wanted
to
actually
reply
to
harnesses.
Our
question
that
was,
do
you
think
is
anything
is
missing
here
and
I.
Think
yes,
at
the
very
least
I
think
missing
is
because
the
consumer,
in
all
the
use
cases,
is
literally
what
we
would
intuitively
see
as
a
consumer
software.
Here
the
customer
buying
something
installing
something
we
have
another
consumer.
G
That's
the
auditor
I
think
there
must
be
at
least
one
auditing
use
case
and
and
somewhere
that
and
and
and
I
personally
think
we
sometimes
have
interesting
problems
like
not
only
that
things
have
to
be
auditable
after
the
facts.
So
that's
an
auditor,
maybe
one
or
two
auditor
use
cases,
but
also
we
have
an
infrastructure
use
case,
especially
in
a
high
critical
systems
that
air
gap
scenarios.
How
do
you
validate
something
when
everything
goes
through
a
service?
G
Do
you
have
to
be
online
all
the
time
or
can
we
mitigated
somehow
I
think?
That's
that's
a
very
especially
from
critical
infrastructure
that
say
they
want
to
all
the
all
accounts.
Abilities
shall
be
there,
but
oh
no
online,
it
shall
not
be
I
must
have
it
with
me
here
right
now,
so
there
must
be
this
air
gap
problem,
sometimes
and
I.
G
Think
there's
no
use
case
for
that
at
the
moment
and
I
think
that's
strongly
related
how
to
get
all
the
data
that
we
we
want
to
produce
here
and
I
think
that
that
might
yield
some
interesting
requirements.
Also
so
yes,
I
would
say
there
are
one
or
two
auditor
use
cases
missing
and
one
infrastructural
one.
G
B
A
Lot
of
positive
things
regarding
the
use
cases,
of
course
it's
not
complete
yet,
but
any
other.
Any
other
comments
like
like,
maybe
some
yeah
like
Ori,
have
you
had
a
chance
to?
Well,
you
have
looked
at
earlier
versions
of
the
use
cases,
but
probably
not
the
ones
that
Hank
was
working
on
most
recently
right.
B
B
I
know
you
know
at
any
point
with
GitHub.
You
have
a
full
history
of
the
provisions
of
the
document
and
when
you
do
a
full
read
through
you
could
you
know,
object
to
content
that
had
been
added
and
file
an
issue
and
we
could
discuss
it
as
a
group,
but
I
think
you
know
at
the
early
stages
of
a
document
like
this.
It
would
be
helpful
to
merge
a
little
bit
more
frequently
just
so
that
we
can
get
some
basic
structural
in
place,
so
that
would
be
I
I.
B
E
So
one
other
use
case
I'd
hope
we
can
get
to
at
some
point.
I
will
entertain
Hank's
help
with
this
is
using
an
app
store
use
case
where
you
can
use
a
skit
registry
to
check
the
trustworthiness
of
an
app
before
installation
that
that's
another
case,
and
we
see
a
lot
right
now.
Of
course,
Tick
Tock
is
getting
a
lot
of
attention
due
to
the
lawsuit,
that's
underway
with
Apple
and
Google,
but
I
think
this
is
another
potential
use
case
which
has
a
has
a
solution.
Thanks.
E
Yeah,
here's
the
deal
K.
So
when
you
go
to
an
app
store
and
you
do
a
search
and
you
get
a
list
back,
you
don't
know
which
of
those
apps
are
trustworthy,
and
so
some
indicator
of
trust
would
be
very
helpful
and
maybe
just
a
button
that
says:
go
to
skit
the
skit
registry
and
tell
me
if
there's
any
trust
for
this
app.
That's
the
scenario
I'm
thinking
about.
E
So
people,
you
know
if
any
people
use
the
like
button,
but
you
can
imagine
where
something
like
a
notary
function
would
examine
an
app
and
then
file
a
trust
declaration
for
that
happiness.
Get
registry
which
we
could
link
to
the
app
stores
so
that
anyone
could
say
looking
at
an
app
press,
a
button
and
say.
Is
there
a
trust
declaration
in
this
trust
registry
for
this
app
thanks?
G
Yeah
I
just
want
to
reply
to
Ori.
We
click
and
see
I,
hear
you
at
the
moment
I.
So
that's
where
I'm
coming
from
I'm.
Coming
from
the
point
that
I
inherited
APR
from
yogesh,
it
was
I,
I,
I'm
purely
German,
very
polite,
so
I
did
not
mess
with
it
I
branched
from
yogis
abroad.
So
this
is
a
branch
of
Abram
and
yeah.
I
can
pull
everything
back
together
into
Maine.
If
we
find
a.
G
If
there's
nobody
is
like,
like
like
objecting
yeah
I
I
think
that
it
doesn't
have
to
be
a
consensus
call
on
the
list
because
we're
all
offers
I
just
was
too
hesitant
to
mess
with
things
that
yoga's
left
and
he
comes
back.
Everything
has
changed,
you
know,
but
if
it's
for
readability
it's
easier,
we
can
I
can
pull
sorry
I
can
merge
my
Branch
into
yoga's
Branch
or
merge
that
into
Main,
and
then
we
can
go
from
there
again.
That
is
not
an
issue.
G
B
A
A
Yeah,
well,
we
don't
need
to
so
like
this
is
not
a
working
group
document
at
this
point
in
time
like
we
want
to
get
it
into
the
state,
so
so
I
think
it's
totally
fine
to
agree
in
this
call.
Since
there
weren't
there
was
positive
feedback,
so
I'm
happy
that
Hank
spent
all
the
work
to
clean
this
up
and
to
get
it
to
sort
of
the
next
level.
B
C
A
A
H
We
can
okay,
beautiful
yeah,
so
I
guess
Ori
stated
it
I
think
pretty
well
I
agree
that,
whether
it's
an
app
store
or
whatever
the
individual,
you
know
end
user
use
cases
the
specifics
of
it.
We
I
think
we
do
have
it
captured
in
the
use
case
document
right
now,
and
we
could
probably
generalize
to
the
point
that
we
need
to
and
again
I
think
or
he's
got
a
pretty
good
point
about.
H
E
I'd
like
to
add
that
I
put
into
the
chat,
essentially
the
use
case
that
I'm
describing
described
by
our
one
of
our
FCC
Commissioners
in
in
the
Apple
Google
antitrust,
lawsuit,
that's
going
on
with
Tick
Tock
right
now,
so
this
is
actually
a
really
good
example
of
a
supply
chain
issue
that
we've
seen
from
the
App
Store.
So
this
is
not
theoretical.
This
is
something
that
is
real
today
and
it's
it's
causing
problems
and
the
solution
is
is
in
order.
Thank
you.
A
A
A
G
A
A
But
that's
excellent
news
in
so
Monty
is
not
here,
so
we
can't
discuss
his
specific
firmware
use
case
that
he
had
in
mind,
but
maybe
we
should
also
spend
a
few
minutes
talking
about
of
what
to
do
in
the
upcoming
meeting,
but
specifically
to
focus
on
because
there's
always
we
need
to
I
need
to
send
out
the
agenda
ideally
today
latest
tomorrow,
and
so
that
people
can
actually
prepare
and
get
sort
of
read
into
well.
Who
is
whoever
is
driving
the
discussion?
F
A
A
A
B
A
So,
okay
case,
what
we
could
also
do
is
like
we
had
received
the
request
from
the
six
store
people
about
the
liaison
and
to
invite
them
to
one
of
those
meetings
to
have
a
discussion
with
us.
So
a
better
person,
a
presentation,
maybe
an
update
on
where
they
are
just
to
sort
of
like
talk
about
their
stuff.
I.
Think
that
would
be
also
used
for
time
spent.
F
F
F
A
To
get
that
material
and
Etc,
so
the
the
other
thing
like
we
have
now
Hank
submitted
the
architecture
document
as
a
serious
serial
working
group
document.
So,
needless
to
say
that
there
are
a
lot
of
issues
open
doing
a
round
of
review
and
and
making
some
progress
on.
The
architecture
document
would
of
course
be
useful
as
well,
because
that's
kind
of
lays
out
the
foundation
and
specifically
having
a
better
understanding
of
the
use
case.
Double
checking
in
the
architecture
is
going
to
be
useful.
F
B
F
A
A
Good
point:
the
terminology
is
also
something
we
we
had
a
discussion
the
other
day
and
I
I
got
the
impression
like
for
some
of
the
terms.
We
are
a
little
bit
all
over
the
map,
but
for
others
it
looks
pretty
good.
So
if
they
do,
you
think
it's
about.
There
is
a
possibility
to
actually
drive
some
of
those
terminology-
discussions
home,
maybe
even
a
mailing
list.
Let's
say
the
next
week.
A
A
G
G
So
you
can
always
open
my
PR
on
any
type
of
document.
We
have
here
visible,
adapted
or
not.
It's
all
reflected
on
on
iitf,
skid
or
iitfwg
skit
at
some
point.
I
actually
don't
know
yet
I
put
ietfwg
skit
as
a
reference
into
for
GitHub
organization
into
the
architecture
Africa
for
example,
but
I
haven't
checked
for
it
now,
if
that's
actually
existing,
so
it
might
just
be
programming
at
the
moment
so,
but
having
said
that,
no
I
think
we
can
focus
if
we
have
a
primary
focus
on
the
software
use
cases.
G
So
if
you
the
guidance
where
to
focus
on,
go
to
the
software
use
cases
and
and
if
you
find
something
weird
in
the
terminology
or
want
to
clean
that
up,
I
think
there's
still
this
there's
the
sequence
of
how
we
refine
messages
from
from
the
actual
products
we
are
talking
about
and
then
there's
again
that's
none
of
these.
These
this
thing
that
you
talk
about
the
product
and
you
sign
it,
and
then
you
make
it
more
visible,
transparency
and
integral
services.
G
So
so
these
These
are
where
we
are
circling
or
always
a
little
bit
all
these
terms.
If
we
can
set
those
better,
then
I
think
early.
Other
texts
will
be
also
more
consistent,
so
I
have
to
agree
with
Roy
here
that
there
are
some
things
we
really
should
settle
on
the
verifier
and
distinguishing
it
from
rats
verifier.
D
Sure,
I
suspect,
I
think
we
want
to
make
another
round
on
the
use
case.
I
would
sure
love
to
see
another
use
case
to
try
and
pull
out
some
commonality.
I've
stated
this
before
having
one
use
case
kind
of
doesn't
tell
us
where
we're
going
to
have
conflict.
We
understand
the
the
rats
one,
but
the
use
case
ones
are
concerning
to
me
that
we
go
off
and
Reserve
words
that
are
going
to
cause
US
problems
later.
A
But
but
I
also
liked
case
idea
of
like,
like
already
now
like
Reviving
some
of
the
requirements
and
seeing
like
did
we
did
we
are
we
actually
capturing
everything
like
specifically
going
forward
like
we,
we
work
on
the
various
Solutions
like
what
is
there
something
missing
coming
out
of
those
software
use
cases,
and
maybe
there's
not,
then
that's
great.
That's
a
that's
a
positive
confirmation
that
the
stuff
that
was
worked
on
previously
on
the
on
the
architecture
document
is
just
covers.
It.
F
A
B
D
D
A
Yeah
we
I
would
I
would
put
the
requirements
for
the
for
the
building
blocks,
not
for
everything,
because
because
otherwise
we
have
a
list
of
requirements
which
we
are
then
basically
have
to
display.
Declare
outside
the
scope
of
the
work,
but
having
requirements
for
the
technology
that
already
described
in
the
architecture
document
would
be
good
as
a
confirmation
of
how
this
works
and,
in
some
sense,
like
there's
this
kit
document
does
this
that
we
talked
about
also
like.
There
are
a
couple
of
examples.
A
A
G
A
Foreign,
okay,
then,
then,
maybe
that's
what
we
should
put
on
the
agenda
for
next
week
this.
How
should
I
leave
these
additional
use
cases,
and-
and
we
can
pick
up
a
first
step
and
and
or
various
people
who
who
raise
their
hands,
can
give
it
a
try
and
see
how
that
works
out
and
whether
they
have
some
some
text
that
we
could
discuss.
Obviously,
since
they
haven't,
nobody
has
seen
them
before.
A
So
there
may
be
some
some
discussion
and
thanks
for
watching
I
I
saw
that
you
posted
the
link
of
the
the
document
now
in
the
in
the
chat
window,
which
leads
to
some
nice
rendering
so
I
hope
that
that
will
give
others
also
a
chance
to
to
read
through
it,
maybe
print
it
and
then
read
through
it.
Yeah
looks
looks
good
to
me.
F
A
Okay,
it
was
a
bumpy
start,
this
meeting,
but
I
hope
next
time.
First
of
all,
you
are
joining
and
because
we
had
planned
these
meetings
with
just
using
different
tools
beforehand.
Now
we
use
a
new
tool,
not
a
big
deal
and-
and
we
just
tried
to
make
some
progress
before
we
all
disappear
in
in
what
many
of
us,
not
probably
not
everyone
India
vacation
time,
any
other
things.
Anyone
wants
to
race.
I
Hey
honest,
so
I
shared
the
the
meetings
link
that
that
you
had
sent
out
like
on
on
Friday
right
with
all
the
skid
working
group
meetings.
I
just
put
it
on
the
chat,
you
can
go
and
add
your
that
meeting
to
your
calendar
so
that
you
know
next
time
you
you
can
you'll,
have
a
reminder
on
your
calendar.
Yeah.
A
No
I'm
saying
I'm
like
I'm,
going
to
update
the
agenda.
I
hope
that
this
is
then
immediately
reflected
into
the
list
that
Kieran
sent
around.
So
you,
if
you
click
on
it
of
course,
or
not,
of
course
I
actually
I
should
check.
So
if
I
update
it
and
you
may
you
imported
that
beforehand-
I,
maybe
it's
a
link
to
the
agenda
or
it's.
If
it's
the
actual
agenda,
then
obviously
we
you
just
have
an
old
version
of
the
agenda.
That's
unfortunate,
but
yeah.