►
From YouTube: IETF114 EMODIR 20220727 1615
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
A
I
need
to
be
left
okay,
we're
going
to
go
ahead
and
get
started,
how's
that
that's
louder
right,
excellent.
So
if
you
can
go
ahead
and
get
your
lunch
and
come
on
and
sit
down,
also
a
reminder,
even
in
this
session
we'd
like
you
to
go
ahead
and
scan
the
qr
code,
if
nothing
else,
that
will
help
us
plan
for
lunches
in
the
future
and
also
I'd
like
to
know
who
you
know
roughly
how
many
people
are
attending.
A
You
know
when
you
finish
eating
put
your
masks
back
on,
but
I
guess
in
this
particular
session,
masks
will
need
to
be
off
for
a
little
while
we
are
also
going
to
use
the
queue
we
do
have
some
remote
participants.
So
please
please
do
that.
A
So
this
is
our
agenda.
For
today
we
have
an
update
from
our
ombuds
team,
an
update
from
our
tools
team
and
an
update
on
some
of
the
work
that
has
been
ongoing
to
help
improve
some
of
the
chairs,
training
and
materials.
We
will
have
an
open
mic
at
the
end.
We
do
need
to
end
promptly
at
12
45,
and
then
we
will
need
to
quickly
clean
up
and
exit
the
room
because
other
meetings
come
in
after
us.
A
So
with
that
pete.
B
A
C
I
think
I
am
sufficiently
loud
to
speak
through
a
mask,
so
we're
just
here
to
give
our
every
so
often
ombuds
team
reminders
we
being
me
today,
because
both
alison
and
melinda
are
off
remote.
C
So
I
got
to
be
the
stuck
e,
we're
mostly
here
to
remind
you
that
the
ombuds
team
is
here
to
help
and
are
absolutely
willing
to
help
chairs
out.
We
are,
if
you
would
like
to
come
to
us
for
advice
either
in
person
at
the
meeting
or
drop
us
some
email.
C
We
are
glad
to
advise,
as
we
can,
we've
even
been
invited
by
one
ad
to
come
to
speak
to
a
particular
working
group
that
was
having
some
issues
with
people
sniping
at
each
other
and,
and
you
know
we're
glad
to
even
do
that
in
a
sort
of
non-official
capacity.
C
But
we
wanted
to
remind
you
more
importantly,
of
the
division
of
labor.
Here
we
are
not
the
behavior
police
you'll
notice
that
the
way
that
our
rfc
is
written,
we
do
everything
behind
closed
doors,
lots
of
confidentiality.
C
We
are
not
here
to
get
up
at
the
mic
and
say
stop
doing
that.
That's
not!
Our
purpose.
Shares
have
the
ultimate
responsibility
and
authority
in
rfc,
2418
and
bcp
25
generally.
If
you
haven't
read
it,
please
do
to
address
disruptions
in
working
groups.
You
have
the
ability
to
disallow
someone
from
going
to
the
mic.
You
have
the
ability
in
different
circumstances
and
with
different
mechanisms
to
stop
people
from
posting
to
mailing
lists.
C
It
is
your
job
to
stop
behavior
that
is
being
disruptive
to
the
work
of
the
working
group.
That's
not
an
ombuds
team
responsibility
like
I
said
we
are
absolutely
happy
to
advise
you
on
how
to
do
that
and
and
work
you
through
the
process
if
you
need
that
help
we're
all
old
hands
at
the
ietf
processes,
but
please
do
not
expect
that
the
answer
to
this
person's
being
a
jerk
is
oh,
go
talk
to
the
ombuds
team
about
that.
C
When
it
comes
to
things
like
harassment,
and
and
by
that
I
mean
you
know
something
more
interpersonal
and
direct
someone
making
disparaging
comments
about
groups,
someone
doing
something
off
list
harassing
someone
behind
the
scenes.
That
is
something
that
we
want
to
hear
about,
and
please
do
bring
those
kinds
of
issues
to
us.
But
overall,
if
it's
happening
on
the
mailing
list
and
it's
disrupting
the
working
group,
we
expect
you
to
take
up
dealing
with
that.
C
C
The
way
we
generally
handle
things
is
if
it
comes
to
the
ombuds
team,
address
we'll
assign
one
of
the
three
of
us
to
deal
with
it,
so
that
only
one
person,
especially
if
it
becomes
a
true
ombuds
team
issue,
so
only
one
person
is
dealing
with
the
confidential
information
and
with
that
I'd
just
like
to
open
up
the
mic.
If
anybody
has
any
questions
or
problems,
they've
encountered
glad
to
talk
about
them.
Here.
D
Yeah.
Sorry,
because
computer
and
food
and
sorry
introduce.
D
Richardson
here
so
thank
you
for
for
reminding
us
that
and
to
the
topic
of
this
group.
I
still
don't
feel
we've
done
some
work
in
the
past,
but
I
don't
still
feel
don't
chairs,
don't
have
the
training
and
experience
to
deal
with
problem,
and
I
took
a
training
course
sometime
during
the
pandemic.
It's
all
vague
on
street
harassment
called
from
I
hauler
back.
D
I
highly
recommend
it
to
everybody.
It
does
have
things
that
apply
to
what
you
just
said:
disruptive.
It
was
more
about
cat
calling
in
the
streets
and
what
people
can
do.
That's
the
kind
of
training
that
I'm
after
okay,
because
it
puts
us
in,
gives
us
specific
tools,
even
words
and
sentences
that
we
can
use
in
those
contexts
when
we
see
them
as
opposed
to
oh
something,
bad's
happening.
What
do
I
do
now
right?
D
C
Start
in
that
direction
and
the
ombuds
team
is
happy
to
help
out
with
that
training
and
and
find
resources.
C
But
yeah
folks
are
interested
in
that,
and
I
think
it's
a
good
idea
to
give
you
all
some
tools
and
maybe
come
up
with
some
specific
ideas
about
you
know
for
ietf
context:
how
best
to
handle
that
stuff
right.
Good.
A
I
I
think
greg
greg
wood
will
be
giving
us
a
little
bit
of
an
update
on
the
working
group
chairs
training-
that's
planned
for
this
year.
That
might
touch
on
some
of
that.
But
if
you
have
specific
other
additional
specific
session
suggestions,
please
feel
free
to
send
it
to
the
emo
door
mailing
list.
E
Hi
this
is
hank,
so
what
I
heard
over
the
course
of
the
past
days
is
about
the
encouragement
of.
E
Enticing
people
to
become
new
blood
chairs,
new
influx
of
pool
of
cherish,
and
I
love
the
notion
that,
if
you're
afraid
of
being
a
chair
so
to
speak,
try
shepherding
first
so
that
but
something
I
would
actually
actively
do
in
all
chat
working
groups.
I
will
talk
about
the
quickly
talk
about
the
possibility
to
be
a
chair,
but
if
you
are
not
used
to
that,
we'll
boil
down
to
the
become
a
shepherd.
E
We
have
a
lot
of
documents
and
any
chapters,
and
then
they
learn
all
the
processes,
we'll
be
there
for
you
as
the
chairs
and
happy
with
that,
and
I
think
that's
an
excellent
way,
a
segway
into
the
actual
share
duty
and-
and
I
love
the
idea
and
therefore
yeah,
I'm
an
absolute
in
favor
of
promoting
that.
Thank
you.
C
And
to
you
know
be
more
directly
on
this
topic
if
you
do
bring
in
shepherds,
which
I
think
is
great.
Remember
that
your
shepherd
does
not
have
the
same
authority
that
you
have
as
chair.
So
please
do
hold
hands
of
shepherds
and
make
sure
that
if
they
are
shepherding-
and
someone
is
getting
out
of
hand
that
you
are
the
one
to
you
know
say
to
the
person
to
the
other
person
you're
interfering
with
the
progress
of
this
working
group
by
misbehaving-
please
don't
abuse
the
shepherd,
etc
and
so
forth.
A
Next
we
have
robert
sparks
robert.
You
want
to
go
ahead.
F
F
Hopefully,
you've
noticed
there
have
been
rather
large
changes
to
the
look
and
feel
of
the
data
tracker
since
the
last
ietf
meeting-
and
I
expect
the
velocity
of
those
changes
to
continue-
we've
moved
all
of
our
source,
control
and
issue
tracking
into
github
under
an
organization
called
ietf
hyphen
tools,
if
you've
not
been
there
yet,
please
go
visit
it.
F
Everyone
is
welcome
to
join,
they
are
open,
they're
recorded
the
sessions
are
available
afterwards
at
youtube.
F
We
are
keeping
our
notes
in
minutes
in
the
notes.itf
site
and
in
the
slide
deck
that
I
sent
a
link
to
to
the
chairs
list.
Yesterday
I
pointed
to
one
of
the
recent.
F
The
things
that
I
wanted
to
call
out
during
this
meeting
was
to
remind
everyone
that
we're
very
near
the
end
of
the
tools.ietf.org
transition,
you're
expecting
to
start
redirecting
tools.ietf.org
completely
the
week
after
this
meeting,
and
I
fully
expect
that
when
we
start
that
redirection
some
new
and
unexpected
things
are
going
to
break,
please
use
tools
discussed
to
to
help
us
identify
those.
F
F
Those
of
you
that
have
been
doing
a
lot
of
draft
work
have
probably
run
into
issues
if
you've
had
references
using
cram
down
in
particular
or
v2
to
anything
in
the
oidc
section.
Sorry,
not
all
adc,
the
oid
section
that's
being
resolved
now.
Hopefully
we
will
be
resolved
before
we
get
into
the
redirection
when
we
when
we
get
when
we
start
the
redirection
next
week.
F
So
I
guess
one
last
reminder
you
run
into
issues
reporting
things
at
github
is
great
mail
to
tools.
Discuss
is
great
if
there's
something
urgent
like
you're
at
this
meeting,
and
you
can't
log
into
the
data
tracker
for
some
reason.
E
Hi
sorry,
this
is
hank
again,
that's
actually
not
a
question,
but
something
when
I
was
preparing
for
a
working
group
came
up.
It's
a
feature
request
and
it
will
issue
something,
but
I
want
to
maybe
communicate
it
here
right
now,
every
year
we
are
sorry
every
measure,
every
session
meeting
session,
where
we
are
going
to
do
the
diff
of
how
the
state
of
the
data
tracker
of
our
working
group
with
respect
to
the
id
state
changed
to
the
last
meeting.
E
E
I
know
we
should
all
know
this
from
the
top
of
our
head,
but
sometimes
we
don't
so
so
and
and
when
we
were
doing
the
the
the
chair
slides
where
I
was
realizing,
what
would
be
probably
easy
to
implement-
maybe
I
don't
know
would
be
like:
what's
the
diff
to
the
last
meeting.
F
E
H
Hi
lou
burger.
Sorry,
I
didn't
get
into
queue,
but
wasn't
fast
enough
on
that
phone
chris
hopps
wrote
a
tool
that
does
that
it's
in
you
can
just
do
pip.
I
think
it's
working
group
stats,
wg
stats
and
you
can
just
install
it
and
I
don't
think
he's
in
the
room,
but
maybe
I'll
send
it
to
the
list.
But
I.
I
Dave
theater,
so
I
hadn't
thought
about
this,
but
I
think
hank
is
exactly
right.
I
think
there's
actually
two
different
things,
I'm
not
sure
which
one
hank
is
thinking
about,
but
I'm
guessing
it's
the
first
one,
which
is
the
draft
status
like
the
data
tracker
for
a
working
group,
says:
here's
all
the
working
drafts
and
here's
the
status
and
so
on,
and
so
that
would
be
like
the
mature,
slides,
there's.
I
Also
a
similar
thing
that
I
do
when
I
present
a
particular
draft
to
a
meeting
is,
I
want
to
know
the
draft
diffs
between
a
particular
meeting
and
another
meeting
right.
So
right
now,
there's
a
bunch
of
work
to
say
which
version
of
the
draft
was
it.
That
was
the
past
meeting
right,
because
your
diff
one
and
diff
two
links
are
the
current
draft
against
the
previous
version
right.
I
But
the
last
meeting
could
have
been
four
versions
back,
try
to
figure
out,
which
is
the
version
as
of
the
last
meeting
and
then
generate
the
diff
url
between
that
one
and
this
one.
That's
actually
what
I
do
when
I'm
preparing
slides
for
a
presentation:
okay-
and
that's
actually
not
easy
to
do
with
a
bunch
of
clicks
right
now,
there's
a
lot
of
manual
work
right
now.
I
think.
I
That's
the
other
point
that
I
think
is,
as
a
draft
presenter
to
say,
is
there
an
easy
way
to
get
a
diff
between
the
current
version
and
the
version
that
was
presented
last
meeting
and
again
only
the
end
points
right,
which
would
be
the
same
thing
as
as
the
the
the
diffing
utility
right
now
is
great.
Once
you
get
the
right
url
right,
it's
just
getting.
What's
the
url
that
says
this
version
to
that
version
is
a
bunch
of
extra
manual
effort
right
now.
G
I
At
the
expense
of
suggesting
an
implementation,
if
you
could
enter
a
date
to
say,
show
me
the
diffs
between
this
date
and
today,
that
might
be
a
way
of
implementing
it,
because
you
can
look
up
what
which
draft
was
posted
most
recently
before
that
date
so
being
able
to
enter
a
date.
Because
then
you
don't
have
to
know
what
meeting
it
was
or
whether
it
was
an
interim
meeting
or
a
design
team
call
or
whatever
just
enter
a
date.
Generate
me,
the
diffs.
F
Yeah
yeah,
as
as
don
pointed
out,
there
are
links
down
in
the
history,
but
you
have
to
manually
compute
when
the
meeting
was
and
go
find
it,
and
I
think
that
we
could
make
that
a
little
faster
and
more
intuitive
so
that
you
don't
have
to
do
the
middle
calculations.
A
All
right
thanks
robert,
I
see
greg's
making
his
way
forward.
So
the
next
subject
is
information
updates.
K
Yeah
hi
greg
wood,
ietf,
llc
staff.
I've
been
working
on
a
number
of
things
related
to
chairs,
so
I'm
really
pleased
to
be
able
to
give
a
quick
update
on
the
three
of
them,
which
I
don't
have
in
my
head,
but
I
think
I'll
cover
them
all.
So,
first
on
working
group
chairs
training,
as
you
probably
saw,
we
had
training
last
year.
K
If
you
were
around
then-
and
it
was
pretty
well
received-
and
we
learned
a
lot
and
so
we're
after
some
discussion
in
the
emoji
group,
we're
going
to
be
doing
a
version
of
it
this
year,
it's
going
to
take
what
we
learned
and
build
on
that
so
we're
the
format's
gonna
be
slightly
different.
K
We've
also
assembled
a
group,
as
we
had
last
year,
to
give
us
advice
on
how
to
best
structure
the
training
or
the
content
of
the
training,
and
we
have
engaged
the
same
experts,
training
experts
to
help
develop
the
content
and
deliver
the
training.
So
expect
some
more
news
about
that
in
the
next
couple
of
months.
K
The
second
thing
that
we
were
talking
about
is
the
chairs
at
itf.org,
again,
just
just
to
remind
folks
that,
based
on
input,
we
had
we've
combined
content
from
the
www.itf.org
site
that
was
focused
on
chairs
and
also
the
content
on
the
old
chairs.
Wiki
enrolled
it
into
a
new
wiki
style
platform
at
chairs.itf.org.
K
So
now
there's
a
single
source
for
all
the
information
that
you
might
want,
as
chairs
always
open
to
suggestions
about
how
best
to
organize
that
and
content
that
we
might
want
to
add
to
that
so
feel,
free
again
to
send
suggestions
along
and
one
of
the
areas
that
we're
working
on
there
right
now
is
to
make
figure
out
a
way
to
make
sure
that
that
content
on
a
regular
basis
gets
updated
and
stays
relevant.
K
So
what
we
found
with
the
old
chairs
wiki
is
that
a
lot
of
the
content
there
just
had
not
been
updated.
So
we
we
want
a
single
source
of
information
that
is
always
up
to
date,
and
so
that's
what
we're
working
towards
there
then
finally
and
related
to
chairs
that
it.org
and
also
chairs.
K
In
general,
we
have
stood
up
a
new
wiki
itf
wide
wiki
at
wiki.etf.org,
and
this
past
saturday
we
held
a
what
we
call
the
content
sprint
and
the
idea
there
is
to
figure
out
all
the
details
that
we
need
to
figure
out
to
get
content
from
the
old
track,
wiki,
which
will
be
going
away
relatively
shortly,
so
that
we
can
get
content
from
there
onto
the
new
wiki.js
platform.
So
the
the
content
spent
went
really
well
actually
exceeded
expectations.
K
I
think,
and
we'll
write
up
a
summary
of
that
and
provide
a
further
update
about
what
that
means
for
chairs
of
research
and
working
groups
as
part
of
the
con
as
part
of
the
sprint,
we
actually
moved
over
a
number
of
working
group
chair,
I'm
sorry
working
group
wikis
from
from
track
to
wiki.edf.org
and
yeah.
So
that
was
that
was
really
great.
K
L
Okay,
yeah
charles
eckel,
thanks
for
that
update
so
for
the
the
hackathon
we
make
extensive
use
of
the
wiki
as
well,
and
I'm
wondering
if
you
know
the
format
of
that's
going
to
be
different,
probably
than
what
each
working
I
haven't
looked
so
much
at
the
working
group
once.
But
do
you
think
the
strategy
you're
looking
at
would
also
be
able
to
bring
that
over?
K
Yeah,
so
that's
a
great
question,
so
all
the
wiki
content
on
various
track
instances
is
expected
to
move
either
move
to
the
new
wiki
platform,
which
is
sort
of
what
we'd
like
to
do
for
all
active
content,
which
we
will
do
for
all
active
content.
So
that
includes
the
hackathon
wiki,
which
obviously
we'd
work
with
you
and
barry
and
other
folks
on
moving
over
and
also
things
like
the
meeting
wiki.
K
So
the
itf
each
ietf
meeting
has
a
wiki
and
we
one
of
the
things
we
did
is
sort
of
set
up
the
test
version
for
115,
but
yeah.
Just
to
answer
your
question
all
the
track.
All
the
content.
That's
now
on
a
track,
wiki
needs
to
move
to
wikijs
or,
if
it
in
the
case
that
it
hasn't
been.
L
And
then
you,
you
touched
on
my
second
question
for
ietf
115,
the
meeting
wiki
and
therefore
probably
the
hackathon
would
be.
Should
we
plan
on
that
being
in
track,
or
is
there
a
plan
to
kind
of
switch
the
meeting
wiki
over
for
115?
You
know.
K
L
B
Spencer,
dawkins
and
I
want
to
try
to
say
quickly,
two
nice
things
greg.
I
have
really
been
impressed
every
time.
I've
talked
to
you
in
the
past
couple
of
years
about
how
helpful
you
have
been
knowing
things
about
the
way
things
work,
and
especially
the
best
way
to
get
things
in
front
of
the
community
like
when
we
were
doing
when
we
started
back
up
with
the
hot
rc
talks
that
were
meet
echo
only
and
things
like
that.
B
I'd
just
like
to
encourage
other
people
to
seek
you
out
because
you're
a
wealth
of
information,
the
other
the
related
thing
there
probably
is
that
I
wonder
if
there's
a
good
way
to
get
you
doing
a
report
like
this
in
front
of
a
larger
audience
when
that's
when
that's
appropriate,
just
because
you
know
like
the
work
you've
done
getting
youtube
organized
for
us.
B
I
had
no
idea
until
you
know.
I
said
something
stupid
on
a
mailing
list
and
you
said
but
spencer.
You
know
it
now
works
this
way.
So
you
know
you:
do
you
actually
do
things
that
are
very
valuable,
just
to
think
about
the
best
way
that
the
broader
community
could
know
about
those
things
before
we
already
needed
to
know
that?
K
Well,
thanks
spencer,
I
was
expecting
the
two
nice
things
and
then
maybe
one
suggestion
for
improvement,
but
I'm
also
happy
to
talk
to
anybody.
So
thank
you
for
making
a
point
of
that
and
suggestions
for
improvement
are
always
welcome
as
well
yeah.
So
we
want
this
all
these
things
to
work
well
for
the
community
and
to
and
like
emodure
just
make
the
ietf
work
easier
and
better
for
for
everybody.
A
F
So
I
wanted
to
call
attention
to
some
words
that
charles
used
in
his
question
that
I
think
greg
reshaped,
but
I
want
to
reiterate
the
reshaping
charles.
You
asked
greg
how
deep
he
planned
to
go
or
the
team
that
he
was
running
planned
to
go
on
content
migration,
and
the
answer
is
that
he
and
his
direct
team
have
no
plans
that
line.
What
is
active
has
got
to
come
from
the
subject
matter:
experts
for
each
group
for
the
things
that
are
being
moved.
F
So
the
the
answer
to
the
the
question,
as
you
stated
literally,
is-
is
that
that
that's
your?
You
need
to
figure
that
out
and
find
people
to
help
greg
in
the
migration
to
to
figure
out
where
that
line
is
and
what
content
is
is
actually
still
active
versus
what
is
archival.
A
So
we
whipped
right
through
those
three
topics.
At
this
point
we
are
in
open
mic.
Does
anybody
have
anything
they
want
to
raise
to
the
working
group
chairs
in
general?
Go
ahead,
put
yourself
in
the
queue
or
stand
at
the
queue?
If
that's,
you
can
go
ahead
to
the
microphone
since
you
waved
at
me.
M
M
M
You
can
converge
on
more
than
one,
and
you
know
this
is
really
not
a
thing.
That's
unique
to
idea.
You
know,
I
think,
we've
seen
this
in
other
working
groups
such
as
spring
and
other
places
as
well,
so
I'm
not
going
to
go
into
any
specific
details
about
the
headaches
and
just
talk
about
the
more
general
details
and
see
what
people
think
about
it.
M
The
issue
that
we
tend
to
have
in
terms
of
our
processes
is,
we
want
to
have
technical
discussion
move
and
ideally,
we
converge
on
a
single
solution,
because
the
majority
of
time
it's
a
healthier
thing,
for
you,
know
the
industry
and
the
people
using
the
stuff
that
we
produce
the
challenge
that
we
have
is
that
sometimes
you
know
the
there's
multiple
incentives
for
us
to
not
converge
on
a
single
solution
and
eventually,
if
things
are
left
alone
for
long
enough,
you
know
the
divergence
into
multiple
solutions
gets
the
multiple
deployments
and
there's
really
not
a
chance
to
do
that.
M
M
M
So
the
topic
I
started
about
a
q
is:
what
do
people
think
about
this
idea
that,
as
a
mechanism
to
try
to
sort
of
head
off
this
sort
of
disagreement,
let's
you
know
sort
of
encourage
people
to
have
this
discussion
at
upfront,
maybe
discourage
allocation
of
code
points.
You
know
that
allow
these
things
to
happen.
A
Okay,
so
I'm
guessing
the
next
two
people
in
queue
are
not
on
this
subject.
So
is
there
anybody
that
wants
to
comment
on
this
specific
subject.
G
So,
apologies,
I'm
the
other
one
of
the
other
idr
chairs.
Let
me
put
a
bit
of
weight
on
that.
We've
spent
the
last
month
and
a
half
trying
to
work
on
it.
Our
email
is
what
oh,
it
doesn't
work
that
way.
Okay,
sorry,
you
got
a
lot
more
work.
If
you
don't
take
that
approach,
we
found
it
was
lots
of
work
and
apparently.
E
A
I
think
it
would
be
useful.
I
don't
I
don't
remember
exactly
who
suggested
the
link
to
the
external
training
for
conflict
resolution.
I
think
that
might
be
helpful
and
I
also
think
the
training
that
greg
is
giving
is
is
going
to
address
that
topic.
So
at
least
parts
of
that
topic.
It
won't
address
specifically
what
you're
talking
about
jeff,
but
maybe
we
should
have
some
follow-up
offline
conversation
on
it.
L
Okay
and
if
I
can
share
my
screen
too,
I
think
it
might
be
a
little
more
helpful
because
I
wanted
to
ask
this
charles
eccle.
I
wanted
to
point
to
or
call
out
just
one
of
the
many
cool
features
that
have
been
added
to
the
the
data
tracker
and
I
don't
know
how
many
of
you
are
familiar
with
it.
L
I
mentioned
it
in
the
hackathon
and
I
have
a
couple
slides
that
that
I
can
send
to
the
list
if
we
don't
get
them
up
here,
but
under
in
github,
you
can
sorry
in
the
data
tracker
you
can.
L
Just
a
second
while
I
try
to
share
my
slides
here:
okay,
great
I'll,
make
it
so
in
the
data
tracker.
There's
this
field,
it's
kind
of
a
little
small
there,
but
additional
resources,
and
if
you
click
on
it,
one
of
the
things
you
can
do
is
you
can
add,
related
implementations
and
just
to
give
you
an
idea,
this
again
is
small.
It
should
go
forward,
hasn't
advanced
yet
up
there,
but
you
know,
in
addition
to
attaching
a
github
repo,
you
can
also
attach
a
related
implementation.
L
That's
weird
that
it's
not
working!
Sorry
about
that.
So
we
try
to
use
this
in
the
hackathon
and
encourage
people
hey
if
you're
working
on
some
code
related
to
a
working
group
draft
or
an
rfc
or
an
individual
draft,
please
go
ahead
and
and
add
it
using
this
related
implementation,
so
people
are
able
to
find
it,
and
but
one
of
the
challenges
is:
if
it's
not
an
individual
draft,
they
actually
can't
do
it
themselves.
L
You
know
that
keeps
them
from
doing
it,
so
I
don't
know
how
much
that's
happening,
but
in
any
case,
as
a
working
group
chair,
if
you
can
encourage
people
to
use
this
functionality,
maybe
when
someone
brings
a
draft
in
an
individual
draft
or
something
when
it
gets
added
to
your
your
working
groups,
list
of
things,
if
you
can
ask
them
hey,
is
there
any
code
associated
with
this
and,
if
so,
help
them
to
get
this
field
set
up?
I
think
it'd
be
great,
and
so
just
thanks.
B
Spencer
dawkins,
I
got
up
to
say
something
else,
but
I'd
like
to
agree
with
what
charles
just
said
and
and
say
I'm
seeing
now.
You
know
now
that
we're
meeting
in
in
person
in
hybrid
meetings,
I'm
I'm
more
aware
of
new
participants
who
are
bringing
concrete
proposals
to
the
ietf
with
code
behind
them.
I
can
imagine
for
a
new
participant.
B
The
idea
of
asking
working
group
chairs
to
do
anything
might
be
kind
of
intimidating.
They
will
be
less
intimidated
soon,
but
just
like
I
say
just
adding.
That
is
a
another
reason
for
charles
to
say
you
know:
have
the
working
group
chairs
encouraging
people
to
do
that?
B
In
a
hybrid
meeting
environment,
one
of
the
conversations
I
was
having
in
jabber
with
the
people
from
mock
was
you
know.
Can
you
ask
who
in
the
room
agrees
with
this
and
we
get
up
and
say
roughly
the
same
thing
so
that
they're
not
having
to
chase
plus
ones
all
over
the
place?
But
you
know
just
to
ask
a
question
like
that.
B
N
Wes
hertika
uscisi
and
one
of
the
guides
leads
spencer.
I
want
to
follow
your
note
with
another
one
saying
you
know
it's
really
important
that
working
group
chairs
figure
out
how
to
help
newcomers
get
involved,
but
but
even
to
a
bigger
area.
One
of
the
things
I
realized,
especially
for
the
buff
I
ran
yesterday,
is
a
lot
of
times.
We
have
newcomers
coming
to
the
ietf
to
bring
their
work
and
their
ideas,
and
we
have
this
notion
in
the
ietf
sometimes
of
well
that's
an
area
that
we
don't
work
in.
N
Well,
how
does
the
ietf
expand
if
we
don't
figure
out
how
to
add
new
topics
in
new
areas?
It
may
not
be
things
that
we
work
in,
but
we
have
sort
of
the
expertise
to
help
them
bring
that
in
right
and
that
this
happens
a
lot
for
for
especially
new
boss
that
come
in
that
that
are
entirely
new
areas
of
work,
and
then
we
should
figure
out.
J
Paul
valkos
emodia
reviewer,
apparently
so
this
quick
question,
I'm
not
sure
what
an
emoji
reviewer
is.
I
guess
it's
an
artifact
of
being
part
of
the
emu.
J
That's
secretary,
sorry,
I
just
noticed
that
it
says
emudia
reviewer
behind
my
name
and
west's
name,
and
so
I'm
assuming
that
it's
just
being
part
of
the
emo
director,
because
we
don't
do
reviewing
right.
J
Sure
I
know
that
that's
not
why
I
was
coming
to
the
microphone
I
was
actually
I
wanted
to
talk
a
little
bit
about
the
previous
topic
of
the
implementation
section.
We
do
have
an
implementation
status
section
in
the
draft.
O
Yeah,
I
want
to
talk
about
issues
besides
meetings
that
we
have
this
week,
so
outside
meetings
we're
trying
to
be
remote
friendly
and
it's
really
challenging.
So
I
don't
know
if
this
is
the
right
forum
to
discuss
this
or
talk
about
this,
but
I
was
wondering
if
there's
a
way
to
kind
of
help,
us
kind
of
enable
that
meeting
to
be
remote
friendly,
not
asking
for
full
support
from
me
deco,
but
somehow
to
allow
us
to
easily
allow
remote
participation,
because
it
was
really
kind
of
challenging
this
week.
A
Durov,
I
I
do
think
to
the
issue
of
side
meetings
and
open
participation
inside
meetings
is
something
that
could
probably
use
further
discussion.
I
didn't
I'm
just
not
sure
what
the
answer
is
at
this
point.
A
All
right
with
that,
oh
wait!
I
see,
I
guess.
O
A
I
I'm
not,
and
I
mean
it
it's
to
a
certain
extent,
it's
a
resourcing
issue.
So
I
I
don't
know
how.
M
P
We'll
see
if
we
have
the
same
answer,
this
is
alexa
my
closer.
P
Is
that
it
is
an
isg
decision,
and
so
this
is,
this
needs
to
be
taken
up
with
the
isg
who's
been
they've
been
pretty
clear.
They
don't
want
to
provide
a
lot
of
support
for
side
meetings,
formal
support,
but
it's
something
that
should
be
raised
with
the
isg.
Q
Queue
barry
levi,
I
can
say
something
that
lars
told
me
the
other
day:
okay,
that
they're
working
on
getting
a
different
skin
on
the
on
meat
echo.
That
would
make
it
clear
that
this
is
a
side
meeting
and
not
an
ietf
meeting,
and
that
that
might
be
the
way
forward
with
this,
so
that
they
could
then
provide
meat
echo
for
that,
but
that's
early
stages.
Right
now,.
C
This
is
pete
par
part
of
the
issue
is
that
the
more
side
meetings
get
official
recognition
by
the
ietf
lots
of
other
procedural
things
start
to
kick
in,
so
the
iasg
has
always
been
of
the
mind
that
you
want
to
keep
these
things
very
separate.
The
initial
idea
was
we're
providing
room
space
only
because
it
was
available
anyway,
and
so
that
would
be
convenient.
But
if
you
start
doing
well,
we
want
the
ietf
tools
available
in
the
room
with
audio
support
with
remote
participation.
R
Just
one
more
point
about
that
is,
it's
you
know.
I
think
we
can
hear
that
you
know
please.
We
would
like
some
help
with
side
meetings.
What
would
be
a
lot
more
helpful
than
that
is
specifics
about
exactly
what
kind
of
help
would
be
most
helpful
like
what?
What
exactly
are
the
pain
points?
And
then
you
know,
maybe,
as
pete
said
they
can
be
addressed,
or
maybe
they
can't
be,
and
you
can
you
know,
talk
in
the
mic
or
put
any
email
to
iesg
at
or
whatever
works
for
you.
B
B
Do
you
want
implement
or
something
like
that?
I
think
that
trying
to
have
that
same
mindset
for
side
meetings
may
be
very
helpful.
Also,
you
know.
Is
this
a?
Is
this
a
general
knowledge?
Sharing
thing
is
this:
you
know
we
want
to
work
on
a
charter
together,
whatever,
but
just
to
say
what?
What's
the
ask
for
people
who
come
to
the
meeting.
O
Sorry,
the
ask
is
the
ask:
is
a
I
want
to
be
able
to
allow
remote
participation,
I'm
not
asking
for
full
support
for
miteiko,
maybe
that
the
idea
of
a
light
miko
meat
echo
is
is
the
right
answer,
but
I,
instead
of
me
dealing
with
the
audio
not
working
mute,
this
unmute
that
took
10
15
minutes
just
to
figure
it
out
if
we
can
have
that
setup
at
least
no
again
not
asking
for
full
support.
Maybe
that
that
the
me
take
a
light
is
the
right
answer.