►
From YouTube: IETF-SCITT-20230522-1500
Description
SCITT meeting session at IETF
2023/05/22 1500
https://datatracker.ietf.org/meeting//proceedings/
A
D
Yeah,
it's
less
convenient.
This
thought
is
less
convenient
for
me,
but
I
was
more
concerned
that
I
had
screwed
up
my
calendar.
Okay,
because
there
were
some
problems
with
the
time
zones
with
the
upcoming
calendar
in
early
April
and
if
you're
using
Google
Calendar,
it
has
not
caught
up.
It
still
has
not
fixed
all
of
its
places,
really.
A
A
That
happens,
yeah,
okay,
yeah.
We
have
a
smart
group
today,
but
doesn't
matter
so
welcome.
Welcome,
anyway,
to
this
next
virtual
intro
meeting
for
the
skid
working
group.
As
usual,
official
intro
meeting
recordings
are
being
made,
the
all
the
IDF
rules,
Supply
IPR
rules,
Etc
we
last
week
we
talked
about
the
registration
policies
and
this
week,
as
I
distributed
in
the
meeting,
invite
in
the
updated
meeting
invite.
A
E
Oh
yes,
thanks
Hannah,
so
one
bit
of
agenda
hacking
just
arose
from
email
list.
This
week
is
a
quick
discussion
about
anybody
here
who
knows
the
t-trends
but
they're
going
for
chartering,
and
it
looks
to
me,
like
the
key
transparency
folks,
really
just
want
to
be
a
use
case
on
top
of
skit
and
if
they're
not,
then
it's
something
like.
We
really
need
to
make
sure
that
the
Primitives
are
aligned,
because
it's
really
really
darn
similar,
so
yeah.
B
A
Steve,
do
you
have
any
issues
that
you
would
like
to
I
know
you've
been
on
vacation
and
so
on?
So
probably
you
haven't,
spend
a
tremendous
amount
with
skit,
but
maybe
there's
something
because
you
created
a
number
of
the
open
issues
as
well
or
at
least
try
to
mix
well.
Actually,
you
did
create
many
open
issues.
A
C
Mean
I
just
copied
I
did
the
copy
paste
authoring
of
them
so
they're
not
but
I'm.
Looking
I'm
clicking
through
the
pr
requests
and
the
issues
now
I
I
guess
it's
hard
for
me
to
have
an
opinion
because
I
don't
know.
What's
transpired
over
the
last
couple
of
weeks,
I
had
literally
just
got
in
late
last
night.
So
what
I
see
the
Merkle
tree
proves
issue
45.
C
A
A
G
F
F
A
F
Okay,
I
get
rid
of
this,
yes,
so
so
yeah.
So
it's
something
we
discussed
that
at
many
places
and
the
meetings
but-
and
it
should
be
relatively
simple,
but
in
fact
the
details
are
not
that
simple.
When
you
look
at
them,
so
the
the
purpose
is
to
find
to
identify
what
is
the
standard
way
to
refer
to
a
producer
register
statement
and
that's
something.
That's.
F
F
G
Thank
you,
honest
yeah
this.
This
is
an
issue.
We
also
experience
with
our
own
sag
Center,
where
you
have
a
single
shot,
six
hash
value,
but
there
are
different
types
of
statements
or
declarations
that
may
be
posted
into
the
registry,
and
so
we
ended
up
creating
essentially
What's
called
the
Declaration
type
and
that
that
may
be
what
you're
referring
to
here.
Cedric
is
the
need
to
have
a
different
type
identified,
different
types
of
statements
for
the
same
exact
object
identified
by
a
shot.
256
hash
value
am
I
understanding
your
concerns
correctly.
H
F
Need
to
be
able
to
query
the
transparency
service
or
the
statements
registered
transparency
service,
and
for
that
you
may
you
may
have
a
more
advanced
query
language
that
says
I
want
to
know
what
is
the
latest
query
from
that
issue
for
that
purpose,
for
example?
So
so
here
the
goal
is
not
to
provide
the
Syntax
for
querying
the
the
transparency
service
in
general,
that's
more
to
identify
a
specifically
one,
previously
registered
Clan,
and
just
that
that
climate,
so.
F
Is
intensible
good
enough?
We
it's
not
meant
to
be
a
little
fast,
caring,
the
the
battery
transferences.
It's
meant
to
be
a
mechanism
to
authenticate
and
designate
when
specific,
transparent
register
statement
and
that
yes,
so
innocential
correct.
But
the
purpose
of
this
is
more
limited.
It's
really
identifying
a
register.
Transparency.
G
G
F
A
F
Okay,
so
so
what
argument
is
being
compact,
but
it's
not
just
it.
So
if
I
replicate
the
transference
statement
everywhere,
then
in
some
Advanced
attacks,
maybe
that's
a
transparent
settlement
that
was
not
actually
a
registered
of,
maybe
the
transparency
described
and
is
inconsistent,
and
so,
even
if
you
forget
about
compactness
in
terms
of
security,
being
able
to
refer
to
a
commitment
to
a
shared
transform
statement
is
arguably
more
transparent
and
more
secure.
So
there
is
that
transference
sharing
that
is
important.
F
F
Then,
in
that
case,
you,
including
it
would
I
think
defeat
the
purpose,
because
you
want
to
to
refer
to
something
that
is
registered
at
the
position
in
The
Ledger
or
not
not
to
it
as
a
value.
And
if
you
were
doing
it
by
value,
then
you
need
to
rebuild
the
full
story
of
all
the
firmware.
You
have
released.
I
Yeah
hi
everybody
so
for
being
late,
I'm
in
a
weird
place
in
Orlando
right
now
that
has
curious,
Wi-Fi
and
curious
doors,
and
so,
if
you
scroll
down
here
and
I,
think
Cedric
already
said
something
different.
If
you
scroll
down
yesterday
on
this
page
on
this
issue
and
F5,
this
page
you'll
see
a
comment
that
I
prepared
an
hour
ago,
but
only
said
press
send
when
I
was
arriving
in
my
room.
So
if
you
scroll
down
yeah,
oh
it's
already,
there
yeah,
wonderful,
it's
auto!
Updating,
wonderful,
so
I
thought.
I
When
I
read
this,
what
you
wrote
here
that
we
have
normative
text
about
that
in
the
architecture
I'm
not
going
into
the
depths
if
we
should
use
moment
of
language,
but
it
says
in
the
architecture
that
payload
content
may
be
encrypted
or
opaque,
which
in
essence
means
that
a
transparent
survey
is
basically
never
required
to
understand
it.
But
it
must
understand
this
metatar,
which
goes
into
the
cozy
header,
for
example.
I
At
least
you
know
what
the
semantics
are
to
some
extent
and
then
where
to
find
it,
how
to
resolve
it,
how
to
retrieve
it,
maybe
even
so,
with
the
scheme
and
authority
and
whatever,
and
so
thank
you
all,
and
so
my
assumption
again
to
a
long
story
short
to
me.
It
sounds
like
this
is
a.
This
is
a
few
of
the
statements
that
we
can
Define
actually
as
a
civil
structure.
Isn't
that
correct.
F
I
think
I
I
think
there
is
a
sometimes
I
I'm,
not
sure
in
particular
I
think
you
really.
Your
comment
seems
to
be
assuming
that
we
are
talking
about
the
payload
of
the
statement
and
that's
not
at
all.
We're
then
trying
to
do
there.
So
so
you
can
have
references
to
many
things,
including
to
the
the
payload.
If
you
want
to
do
the
detached
envelope
and
kind
of
things,
but
that's
not
what's
What's
Happening
Here.
F
F
I
F
To
to
to
elaborate
on
that,
so
so
those
references,
of
course,
the
transparency
service,
to
agree
on
the
contents.
So
it
may
make
sense
instead
of
a
bit
or
to
have,
instead
of
an
object
period,
to
have
references
to
other
statements,
yeah
the
menu
scales,
where
the
transformation
service
will
be
that
place.
If
we
include
references.
F
In
particular,
to
refer
to
a
police
blessing,
for
example,
or
to
some
transparent
statement
to
another
part,
so
we
are
building
this
kind
of
things,
and
so
the
the
use
case
I
think,
will
be
for
those
being
included
in
headers.
But
but
again
as
it
is
written,
the
reference
could
go
in
a
policy
in
the
payload
in
the
headers
anywhere
you
just
want
to.
We
don't
want
to
say,
okay,
what
they
consistent.
Okay,.
I
I
Why
not
so
especially
and
you're
correct
if,
if
that
would
include
the
receipt
you
can
now
refuse
this
reference
here
in
another
tree
that
might
have
different
algorithm,
layouts
yeah
and
still
would
be
able
to
use,
make
use
of
the
statements
stored
somewhere
and
I
think
that's
an
excellent
choice.
Yeah
and
this
can
go
anywhere
even
to
the
header.
Yeah.
Okay
got
it.
Yes,.
I
Now
in
hindsight,
documenting
things
with
Sketch
and
then
from
that
point
on
start
to
use
it
as
a
live
current
feed
so
to
speak,
then
you
you
pretty
much
would
be
obligated
to
fetch
all
that
from
the
Internet
or
from
other
Authority
or
for
the
source,
and
that
does
not
make
all
this
sense
also
size
and
scalability
and
usefulness
right.
So
so
I
think
we
need
to
deal
with
verification
processes
that
say,
oh
and
by
the
way
on
my
regular
I,
don't
know
safe
order.
Check.
I
I
am
unable
to
resolve
this
anymore,
and
maybe
there
could
be
I
know:
maintenance
processes
that
that
indicate
that
these
statements
are
now
I,
don't
know,
stale
to
some
extent,
I,
don't
know
how
that
would
work,
but
is
that
a
round
forward
that
that
there
would
be
I,
don't
know
intervals
of
safe
verification
that
the
verifier
checks
all
this
again?
This
is,
of
course,
hard
work
and
it
takes
a
lot
of
effort,
but
would
that
be
a
way
to
something
prune?
These
statements
that
are
not
available
anymore,
but
we're
true
at
some
point.
F
F
Statements
for
for
three
months
and
they
have
an
issue
that
needs
to
be
available
for
five
years.
Then
the
issue
I
really
like
to
point
the
verifier
to
a
star
that
is
going
to
keep
the
statement
for
five
years
as
opposed
to
the
original
construction
service,
and
we
don't
get
a
way
to
do
that.
I
think
that
can
be
done
by
putting
locators
and
as
interesting
information
elsewhere
in
the
envelope.
But
but
if
we
do
that,
then
we
need
to
agree
that
the
distance
outside
of
this
particular.
F
I
So,
just
sorry
for
just
another
great
question,
but
this
would
fall
in
the
registration
policy
bucket
then
so,
because
we
have
to
Define
who,
who
is
carrying
the
duty,
who's
the
burden
for
the
duty
of
checking
that
and
now
here
now
the
issuer
is
the
verifier
just
node
to
Rises
that
those
records
it
puts
it
into
the
append
Only
log
right.
So
so
the
the
responsibility
to
take
care
they're
there
for
five
years
is
on
the
issuer
side.
You
say.
F
F
For
example,
if
there
is
a
radar
that
says
persist
for
five
years
and
then
you,
the
translation
service,
accepts
it,
then
of
course
it
will
need
to
maintain
it
in
the
in
the
future,
but
that
would
be
the
semantic
of
a
specific
header
in
the
registration
information.
I.
Don't
think
that
would
be
attached
to
the
semantics
of
the
reference
itself.
F
H
F
H
F
H
H
F
Okay
thanks
so
so,
if
I
know
somebody
that
spout
of
the
discovery
ability,
so
you
think
discoverability
in
the
air
gap
system
or
in
many
systems,
is
going
to
be
to
be
broken.
What
I
was
suggesting
as
a
as
a
useful
patterns
for
that
is,
is
in
that
case
that
you
will
distribute,
distribute
the
statement
that
refers
to
statement
that
refers
to
state.
F
H
Do
we
need
compact?
That's
that's
I!
Guess
my
fundamental
heartburn
over
this
compact
isn't
necessarily
all
that
great.
If
you
want
you
know,
if
you
want
a
tool,
you
know
you
know
where
the
tool
is
but
you're
not
in
that
location.
You're
not
going
to
be
able
to
get
the
tool
and
I
think
that
you
know
these
are
not
gigantic
amounts
of
data
in
the
attestation
space,
so
I
think
they
should
be
carried.
You
know,
or
at
least
have
an
option
to
carry
them
in
full.
F
H
F
Yeah
I
think,
and
for
that
you
have
the
translation
and
I'm
assuming
you
lots
of
users
will
keep
the
response
balance
saved
on
for
about
team,
and
that's
that's
an
equal
thing
to
do
now.
I
guess
I
was
thinking
also
on
what
happens
on
the
on
the
transparency
service
side.
So
what
you
put
in
the
and
I
think
in
the
log,
putting
statements
that
include
full
copies
of
other
states
is
is
wrong
in
the
extreme.
F
G
H
F
B
Thanks
I
think
that
okay,
so
one
thing
is
I'm
resolving
a
little
bit
more.
What
the
use
case
is
for
the
selection,
data
situation
and
I
the
discoverability
and
the
reference
are
going
to
be
pretty
important,
I
think
because
this
data
is
going
to
be
developed
incrementally
and
so
there's
going
to
be
an
initial
say,
a
hunk
of
data,
it's
not
very
big,
which
is
the
list
of
all
the
public
keys
of
the
devices
and
that
needs
to
be.
B
You
know.
The
transparency
service
is
perfect
for
making
that
public
and
locking
it
down,
but
that
has
to
be
locked
down
earlier
than
you
know.
We
get
the
data
from
those
devices,
then
later
we
get
incremental
data
from
some
devices
and
not
others,
and
and
then
there's
this
Central
devices
that
are
that
are
and
we
we
would
like
to
get
that
data
incrementally
and
and
then
so
we
at
the
end,
we
need
to
have
a
way
to
either
as
part
of
the
skit.
B
B
That
will
allow
us
to
get
to
all
of
the
data
and
and
say
okay
for
this
particular
in
this
case
election
at
a
certain
District.
What
is
all
the
data
you
know
give
me
all
the
data
for
it
for
a
software
use
case.
It's
more
like
give
me
all
of
the
software.
You
know
stuff,
plus
all
the
tests
and
the
results
and
from
the
testing,
agencies
and
stuff
and
and
I
need
it
all,
and
so
there
needs
to
be
a
way
to
number
one
have
something
that
is
outside
of
the
Obscure
area.
B
If
you
want
to
use
it
and
then
a
way
to
say
to
for
for
for
the
submitter,
maybe
to
say,
I'm
I
want
to
group
all
this
together
like
maybe
maybe
we
can
have
a
fairly
simple
skit.
You
know
machine
that
doesn't
know
very
much,
but
the
users
of
it
can
know.
Okay
I've
submitted
all
this
stuff.
It
has
these
references
and
I'm
combining
that
all
together.
B
Finally,
into
this
one,
final,
submission
or
or
at
least
incremental
submission,
and-
and
here
it
is
and-
and
so
I'm
saying
my
new
claim-
is
that
these
other
submissions
are
all
part
of
this
larger
thing,
and
if
we
do
it
that
way,
then
we
can
kind
of
not
have
to
worry
about
the
discoverability
and
other
things
like
that.
We
kind
of
put
that
on
the
shoulders
of
the
users
where
they
they
would
know
what
they've
submitted
and
they
would
say.
B
B
Have
this
get
registry
be
incrementally
something
we
can
incrementally
submit
to
have
those
all
locked
in
and
then
have
some
way
of
having
a
final
submission
that
also
refers
to
the
incremental
ones,
because
we
want
to
be
able
to
say,
for
example,
that
that,
like
back
in
time
at
time
x,
we
did
submit
this,
and
this
is
exactly
what
was
submitted.
We
can't
rely
upon
a
new
submission
to
say:
okay,
now
I'm
submitting
a
new
and
by
the
way,
I
changed
everything
this.
So
it
complies
with
my
new
hacking
scenario.
B
F
Is
really
centered
on
the
transparency
service,
and
so
in
particular
what
we
got
a
statement.
It
really
is
the
unit
of
registration,
so
you
describe
a
providing
technology
that
are
about
what's
happening
and
so
I
think
from
the
transformative
each
time
you
register
something
and
to
to
make
it
transparent,
yeah.
It
is
a
set,
a
high
statement
and
I
think
that's
okay
in
particular,
it
means
the
transparency
that
is
not
know
about
this
meta
level.
Grouping
of
of
State
nodes
and
I
believe
that's.
F
B
B
Don't
know
how
you
would
do
that
if
you
have
obscure
statements,
unless
you
were
able
to
somehow
see
into
them
a
bit
more
and
find
that
airbag
or
or
that
you
know
library
of
in
the
bombs.
You
know
you
would
need
to
be
able
to
to
find
that,
and
so
the
some
of
the
functionality
of
looking
in
in
in
unless
you
you
somehow
could
I
just
that.
That's
the
part
that
I
think
is
a
problematic
with
with
having
a
you
know,
completely
obscure
submission
statements.
Then
how
do?
B
F
Thanks
yeah,
in
fact,
I
just
want
to
as
a
commenter
I
think
using
references
when
you
want
to
replace
statement
that
you
made.
This
is
a
very
good
use
case.
So
if
you
have
two
statements
signed
by
the
same
issue
for
the
same
purpose,
then
you
really
don't
know
which
one
follows
from
the
other.
Now,
if
you
have,
if
one
of
them
explicitly
refers
to
the
other
one
and
you
have
God,
then
you
clearly
you
can
compare
both.
B
Yeah,
okay,
so
let
me
give
you
an
example:
within
the
software
use
case,
let's
say
we
have
a
piece
of
software
and
we
have
let's
say
it's
a
something:
that's
critical
like
a
you
know,
self-driving
car
software
that
they
have
to.
They
have
to
submit
and
say
this
is
our
self-driving
car
software
and
it
was
tested
according
to
these
criteria
and
here's
the
test
results.
And
then
you
know
later
they
had
an
update
and
they
updated
and
fixed
stuff.
But
some
of
the
cars
were
still
running
on
the
old
stuff.
B
There
was
an
accident.
People
died
so
they're
in
court
and
they
want
to
find
out
what
version
of
the
software
and
what
is
it
tested.
So
not
only
they
need
to
go
back
and
find
out,
not
the
new
stuff
but
the
old
stuff,
and
what
the
test
results
were
there.
So
we
need
to
have,
as
you
can
see
there,
we
need
to
have
the
full,
like
even
the
older
results
that
they
can't
re.
You
know
we
don't
want
them
to
be
able
to
replace
that
and
and
never
and
or
change
it.
B
B
Sorry,
that's
a
bad
name,
because
it
implies
something
else,
but
say
a
number
of
entries
in
The
Ledger
that
refer
to
the
same
product
at
different
stages
and
different
releases,
but
they
all
need
to
be
kept
there
because
of
the
different.
You
know,
levels
of
functionality
and
whether
they've
been
tested
and
so
forth,
and
so
they
can't
replace
each
other.
But
now
we
need
to
find
them,
and
so
now
now
we
need
to
be
able
to
say
okay
now
for
this
product,
so
somewhere
there
needs
to
be
a
marker
of
I.
B
Think
that
is
not
obscure
for,
and
this
is
what
I
expressed
in
that
Sky
View.
We
need
to
know
who
the
manufacturer
is
and
what
the
product
is,
at
least
so
that
we
can
track
those
things
down
and-
and
maybe
there's
a
thing
where
you
can
say:
look
I,
don't
want
anyone
to
know
anything
going
in
and
so
I
don't
want
to
use
that
metadata,
but
I
think
most
of
the
time
we'll
say:
okay,
look
you're
going
to
have
to
identify
who
you
are
you're
submitting
this
and
what
your
product
is.
B
A
Yeah
two
issues:
one
is
and
that's
a
sort
of
question
to
Cedric,
to
or
request
to
Cedric
to
sort
of
fine
tune.
The
the
motivation
I
think
the
compactness
is,
is
it's
an
optimization,
but
it
also
obviously
has
some.
Some
disadvantages
makes
things
more
complicated,
Etc,
but
I
I
hear,
but
there
are
other
use
cases
from
the
discussion
so
far.
A
It's
just
the
difficulties
to
draw
the
line
between
referencing
and
a
query
language.
So
there's
there's
a
slippery
slope
here.
That's
the
first
point.
The
second
issue
is
more
technical.
One
I
believe
that
did
web
URI
scheme.
Here
is
not
what
you
should
be
using
for
this
purpose,
because
I
would
I
would
just
use
a
urine
and
Define
how
the
discovery
works,
because
they
did
that
at
least
that's.
A
F
F
F
A
F
G
I
think
we
can
flush
out
The
Core
Concepts
of
a
trans
Currency
Service,
using
a
very
simple
model
based
on
something
we
can
all
relate
to
and
I'll
give
you
a
very
quick
example:
Johannes
is
going
to
be
the
transparency
service,
that
registers
people's
weights,
all
people,
information
and
so
I
want
to
do
a
look
up.
I
want
to
say,
I
want
to
know
the
weight
of
Dick,
Brooks
and
I
need
to
get
it
from
harnesses
registry
transparency
service.
G
There's
two
things
that
come
right
off
the
bat
we
need
to
know
we
need
to
identify.
We
need
to
be
able
to
identify
the
transparency
service
entity
that
we
can
query
and
we
need
to
know
the
subject
that
we
want
to
submit
the
query
on
so
there
you
have
two
concepts
that
both
apply
to
software
as
well.
With
regard
to
this,
whole
concept
of
weight
weight
is
a
great
example
of
going
back
to
what
Hank
was
saying
earlier
about
staleness
and
freshness.
G
You
know
if
you
record
my
weight
from
today,
it's
very
different
from
my
weight
that
we
recorded
you
know
in
1979
when
I
got
married,
so
the
concept
of
freshness
and
Stillness
would
play
out
with
this
simple
use
case
as
well.
So
what
I'm
suggesting
is?
Maybe
we
can
just
start
with
something
simple
that
we
can
all
relate
to,
as
we
try
to
flush
out
what
this
transparency
service
thing
is
and
what
it
provides
and
I
think
the
just
using
that
weight
example
is
a
good
one
that
we
could
easily.
You
know
flush
out.
G
Some
key
Concepts
from
the
things
like
you
know,
for
example,
in
a
wake,
is
a
unit
of
measure
right,
so
that's
data
that
would
have
to
be
carried
in
the
receipt
there's
a
time
stamp
of
when
that
rate
date
rate
was
recorded.
You
know
so
there's
all
kinds
of
other
information
that
we're
going
to
the
statement
in
that
one
case,
so
you
know,
even
though
the
weight
one
is,
is
not
germane
to
what
we're
trying
to
accomplish
here.
G
F
So
I,
okay,
so,
first
of
all
I
I
agree,
that's
something
we
need
to
do.
I
I
think
that's
out
of
scope
in
this
particular
issue.
So
as
as
mentioned
a
few
times,
this
is
not
meant
to
be
a
very
long
wedge
and
what
you
are
I,
think
informally
asking
for
me:
what
are
the
most
natural
requirements?
What
made
up
what
may
have
about
statements
so
this
this
is
just
a
way
to
identify
and
refer
to
one
part,
one
specific
transfer
on
set
mode.
So
back
to
your
horizontal.
F
G
F
G
Yeah,
it's
it's
really
a
proposal
to
try
and
simplify
this
to
something
that
we
can
all
say.
Okay,
here
are
the
key
Concepts
that
we
know
we
need
to
capture
for
any
transparency
service.
That's
going
to
produce
anything,
but
you
know
if
that's
not
going
to
work
for
people
and
obviously
that
then
that
will
fly.
So
if
it's
not
going
to
work,
then
I
I
withdraw
my
suggestion.
Thanks.
I
Charlie
said
some
of
this
historicity
is
not
captured,
digitally
correct,
even
the
software.
Sometimes
this
is
in
a
very
weird
format.
That
is
that
we
wouldn't
call
it
digital
in
exercise.
I,
don't
know,
that's
not
post-processible,
effectively
and
or
weirdly
formatted,
and
then
and
then
we
have
this
weight
example
from
dick,
which
is
the
same
same
because
dick
is
recording.
I
This
I
know
in
his
own
EXO
sheet
again
so
so
now
we
have
skit
and-
and
now,
if
you
want
to
add
a
a
ancient
software
to
the
skid
Ledger
and
its
historicity,
there's
an
authority
doing
that
that
is
the
issua.
So
Charlie
highlighted
that
this
information
is
not
really
available
on
the
internet,
but
well
someone
issued
the
statement
so
why
that
statement
is
issued
by
the
issuer.
Now
this
issue
is
responsible
of
vouching
for
the
authenticity
and
the
rest
of
the
historicity
of
that
statement.
I
So
the
issue
is
doing
all
the
Providence
research
providing
his
historicity
and
then
then
issuing
that
a
statement
as
the
initial
statement
about
the
product
or
the
object,
and
then
we
go
from
there
right
so
I
think
it's
fine
as
long
as
we
burden
the
issue
with
that
responsibility
of
providing
that
data
in
statement,
format,
of
course,
and
and
then
go
from
there.
So
I'm
I'm
a
little
bit
surprised
that
this
this
perceived
as
a
problem,
because
now
the
issue
would
be
responsible
to
resolve.
A
B
H
I
H
I
I
Their
work
correctly
because
they
they
pass
the
registration
policy
of
the
transparency
service
I
mean
then
at
this
point
you
can.
You
can
believe
that
someone
was
at
this
point
of
of
of
making
it
transparent
at
least
providing
it
on
the
internet,
maybe
for
two
days,
I,
don't
know,
but
but
that
should
work
right.
I
H
H
G
A
F
A
F
Receive
two
statements:
two
transparent
statements,
one
referring
to
the
other
and
you
recompute
the
hash
of
the
sermon
statement
to
check
that
it
matches
the
one
in
the
first
state
mode,
so
that
you
know
that
the
visual
of
the
first
set
month
is
really
meant
to
refer
to
the
second
segment
that
you
have
it
on,
and
that
does
nothing
going
to
the
internet.
That's
something
you
can
do
on
your
own
or
as
soon
as
you
have
a
copy,
either
received
or
obtained
from
any
other
source
of
the
second
transform
claim.
So
the.
F
A
But
that's
only
half
of
the
story
Cedric,
because
because
in
in
your
write-up
you
kind
of
assume
that,
for
example,
in
this,
what
you
show
on
the
screen,
DS
dot
software.org-
is
that
there
is
some
that
this
is
at
some
place
right
at
a
transparent
statement
and
in
on
some
transparency
service
somewhere
on
the
internet.
At
some
point
in
time.
Right.
E
A
F
A
B
Well,
yeah
I
know
that
we're
out
of
time,
but
I
do
think
the
transparency
service
we'll
have
we'll
need
a
functionality
that
will
say
this
reference
I'm
give.
These
are
all
of
the
submissions
for
this
reference
that
I
have
and
there
are
no
more
and
there
are
no
less,
because
otherwise,
a
person
who
claims
to
be
honest,
emitter
can
say
okay.
This
is
this
is
all
the
information
that
we
have
about
this
and
we
didn't
do
anything
in
the
past,
even
though
they
did
so
anyway.
B
A
What
you
said
Rick
tries
to
accomplish,
with
with
your
proposal
and
thanks
for
the
details
right
up
and
for
the
explanations
today,
and
we
also
I
think
we
looked
into
some
additional
use
cases
or
more
advanced
use
cases
which
we
also
need
to
look
into
which
are
related
to
this,
but
obviously
not
the
same,
so
even
more
work.
So
we
went
out
to
solve
One
open
issue
and
we
created
an
extra
one.