►
From YouTube: IETF 112 Plenary
Description
The plenary session at IETF 112 will be held at 1330 UTC on on 3 November 2021, providing the usual updates on various administrative and operational topics.
A
A
If
you
have
a
headset,
you
can
use
one.
I
do
have
one,
but
I
prefer
not
to
that's
why
I
asked
whether
the
audio
is
okay
and
there's
some
more
details.
If
you
get
really
bored
during
this
plenary,
you
can
click
on
that
link
or
copy
that
link
into
your
browser.
If
it's
google
and
look
at
that
all
right,
I
think
it's
a
couple
minutes
past
3
30.
A
My
time,
which
is
in
finland,
so
for
me
this
is
a
great
time
zone,
my
apologies
and
condolences
to
all
of
you
for
whom
it's
the
middle
of
the
night.
I
was
in
your
shoes
last
time,
it's
not
fun,
so
thanks
for
making
it
anyway,
if
you
didn't
make
it
anyway,
if
not
you
listen
to
the
recording.
I
guess
next
slide,
please
I
should
probably
say
my
name
is
liz
eggert,
I'm
the
itf
chair
since
march
of
this
year.
A
We
have
a
reasonably
short
agenda,
this
time,
which
means
we
have
lots
of
time
for
open
mic
or
we
can
have
a
really
short
plenary.
As
you
wish,
we
have
the
usual
round
of
updates
from
the
various
bodies
and
roles
all
of
them
have
published
or
in
the
process
of
publishing,
longer
written
reports
that
are
mostly
linked
to
from
the
itf
report
that
I
shared
earlier.
So
you
can
find
them
from
there.
A
A
First
off,
I
really
want
to
thank
erickson
who's,
the
meeting
host
for
this
meeting.
They
were
very
excited
to
host
us
in
madrid,
which
was
where
we're
all
going
to
be.
I
had
kovit
permitted
us
to
do
so
and
they
graciously
kept
their
commitment
up
when
we
decided
to
move
this
meeting
to
a
fully
online
meeting.
So
so,
thank
you
very
much
for
that.
It's
it's
really.
A
Please,
and
also
thank
you
to
all
of
you,
who's
involved
in
making
this
happen,
this
sort
of
starts
and
stops
with
the
secretariat,
but
there's
also
other
teams
meet.
Echo
is
doing
a
great
job
running
the
system.
For
us,
the
knock
is,
as
always
great
in
getting
our
infrastructure
running
for
this
meeting,
the
llc
signs,
the
checks,
the
tools,
teams,
write,
the
tools
and
and
they've
been
very
busy.
We
have
a
little
bit
of
an
update
on
that
later
on
and
the
hackathon.
A
I
hear
has
been
going
great
and
the
support
team,
for
that
is
doing
a
good
job,
as
always,
so,
thanks
to
all
of
the
people
involved
in
making
this
meeting
success,
success
next
slide.
Please
right.
My
chair
report
next
slide
is
very
short
this
time.
Basically
we're
going
through
the
usual
statistics
on
participation,
the
plan
for
future
meetings,
I'm
going
to
say
some
things
about
our
currently
running
experiments,
because,
as
we
put
together
the
report,
the
written
report,
we
realized
there's
quite
a
few
of
them
and
maybe
not
everybody's
aware.
A
A
Given
that
the
time
zones
work,
like,
I
would
say,
okayish
for
it
for
the
u.s
this
time
and
also
for
europe,
other
regions
of
the
world,
unfortunately,
are
a
little
bit
in
a
difficult
situation.
But
that's
why
we
rotate
and
we're
going
to
post
detailed
attendance
stats,
as
always
after
the
meeting,
especially
since
the
plenary
is
happening
before
the
meeting
week.
So
we
are
probably
going
to
pick
up
a
few
more
late
registrations
as
we
move
towards
next
week.
Next
slide
right
future
meetings
and
also
for
this
meeting.
A
If
you
have
any
issues
with
the
iatf
or
the
meeting
or
anything,
please
use
support
at
igf.org
as
the
one
stop
email
address
for
anything.
You
will
get
triaged
to
somebody
who
can
help
you.
If
you
want
to
specifically
talk
about
tools,
there's
a
mailing
list
that
you
can
join
also
to
be
kept,
the
best
of
what's
happening
on
the
tool
site,
which
is
tools
discussed
at
itf.org.
A
A
A
I
would
optimistically
say
if
you
don't
agree
put
that
in
the
survey
and
also
put
anything
else
related
to
this
plenary
experiment
and
the
story
that
jay's
gonna
send
out.
I
want
to
apologize
to
the
people
at
nanak.
We
dropped
the
ball
on
on
making
sure
that
we
wouldn't
conflict
with
anything.
I
thought
we
had
done
it,
but
apparently
we
didn't
and
we
missed
that
nano
is
happening
this
week.
A
We
also
are
doing
an
online
welcome
reception.
I
think
this
is
the
first
time
we're
doing
this
in
this
virtual
format,
which
happens
right
after
this
plenary
ends.
So
look
at
the
agenda
and
there
are
links-
and
I
think
the
last
slide
of
this
presentation
also
has
links.
This
happens
in
gather
dot
town
which
you
may
or
may
not
have
joined,
which
is
this
sort
of
virtual
forum
in
which
you
can
interact
with
groups
of
other
participants.
A
I
think
this
will
be
pretty
exciting.
We're
trying
to
sort
of
recreate
the
actual
welcoming
section
that
we
have
it
in
person
meetings
and
one
part
of
that
has
been
the
hot
rfc
session
that
aaron
fox
been
running
for
a
while
and
we're
bringing
hot
rfc
back
for
this
meeting
in
a
virtual
form.
It's
also
in
gathered
up
to
town
also
after
the
plenary
ends,
so
go
and
check
out.
A
A
We're
for
a
number
of
meetings
now
had
the
running
experiments
with
scheduling
the
buff
deadlines
a
little
bit
differently,
so
that
the
isg
and
iab
have
the
opportunity
to
give
feedback
to
the
people.
Preparing
buffs
in
sort
of
the
end
result
hoping
that
the
buff
will
be
better
planned
and
better
run.
A
A
A
Based
on
data
we
had
when
rfc
8989
was
written
and
rather
than
speculate,
we
decided
to
gather
more
data.
The
other
more
pragmatic
reason
is
that
we're
still
in
an
all
virtual
forum.
So
at
the
very
least,
we
have
to
keep
counting
virtual
attendance
or
attendance
to
virtual
meetings
as
noncom
eligibility
require
qualifying,
because
otherwise
we
have
trouble
sitting
in
nom
come
next
year
and
finally,
the
isg
has
decided
to
do
an
experiment
of
doing
sort
of
a
360
degree
reviews
for
ads
and
we
just
got
the
first
set
of
results.
A
Basically,
we
asked
each
other.
We
asked
the
iab,
we
asked
the
secretariat,
we
asked
our
chairs
and
document
authors
as
well
as
other
document,
also
that
we
balloted
on
to
sort
of
give
us
feedback
in
sort
of
a
set
of
short
web
forms.
We
got
some
interesting
feedback
from
the
community
that
we
should
revamp
the
questionnaire
if
we
do
this
again,
which
will
take
into
account,
but
I
still
think
we
got
some.
A
Personally
I
would
say
I
got
some
interesting
data
out
of
this,
so
the
idea
is
that
every
ad
gets
their
own
review
and-
and
it's
not
shared
with
the
rest
of
the
isg,
the
entire
isg
gets
sort
of
an
aggregated
view
which
averages
all
the
individual
feedback,
and
that
aggregate
view
we're
planning
on
publishing.
Since
we
just
got
it,
this
might
take
a
week
or
two,
but
you
can
then
all
see
what
the
feedback
was
on
on
the
isg
as
a
whole
and
that's
about
the
currently
running
experiments
next
slide.
A
Please
right.
We
had
zero
appeals,
which
is
great
as
usual,
and
we
published
one
isg
statement,
which
is
the
aforementioned
report
on
the
rfc
8989
experiment.
It
has
a
bunch
of
data
in
it.
So
if
you're
wondering
exactly
why
we
are
continuing
it,
please
give
that
a
read
if
you
haven't
already-
and
there
are
much
more
reports
that
I
go
into
detail
online
on
the
data
tracker
materials
page
for
this
meeting
and
as
always,
there's
an
itr
blog-
that
greg
is
filling
with
interesting
content.
A
So
if
you
wonder,
what's
going
on
that's
a
good
source
to
take
a
peek
at
as
well
next
slide,
please,
okay
about
tools.
So
there
was
an
announcement
in
may
that
the
services
that
are
currently
running
at
the
tools.itf.org
url
are
being
replaced
and
we're
going
to
wind
that
down.
It's
probably
going
to
happen
before
itf
113..
A
The
original
goal
was
to
do
it
before
this
itf,
but
it
was
a
bit
more
complex
than
was
anticipated,
and
so
we
removing
that
by
a
meeting,
there's
a
few
tools
that
are
sort
of
still
waiting
to
be
replaced.
Probably
the
xml
to
rfc
page
is
the
most
visible
of
those
there's
an
authors.idf.org
beta
that
you
can
take
a
look
at
which
is
intending
to
replace
this,
but
we
need
still
need
to
do
a
little
bit
of
work
on
the
bibxml
and
the
conversion
service.
Before
that's
fully.
A
There
there's
a
whole
slew
of
other
tools
that
were
made
available
under
tools.itf.org
for
almost
all
that
have
a
sort
of
sizable
community
that
uses
them.
We
have
a
transition
plan,
there's
a
github
url
here
that
that
you
can
take
a
look
at,
but
I
also
want
to
be
clear
that
we,
we
can't
maintain
all
tools
that
were
under
tools.itf.org
going
forward,
because
we
have
limited
resources
and
some
of
the
tools
specifically
written
oftentimes
for
a
very
small
community.
A
I
think
we
have
one
or
two
tools
that
were
specifically
written
for
one
participant
and-
and
I
hope
it's
clear-
that
we
are
not
going
to
be
able
to
maintain
those
going
forward,
but
we're
going
to
try
our
best
and
if
you
have
feedback
on
on
the
plan,
please
go
to
that
github
page
and
open
issues
or
send
emails
to
tools.
Discuss
next
slide.
Please.
A
Right,
there's
a
directory
called
imorder,
which
is
the
new
home
for
the
edgier
team
activities
and
also
other
mentoring
and
outreach
activities
which
has
been
chaired
by
karen
o'donnell
greg
wood
and
joey.
Salazar
and
joey
has
just
informed
us
earlier
this
week
that
she
unfortunately
needs
to
step
down
as
a
co-coordinator.
D
D
Yeah.
The
full
ie
report
is
already
uploaded
to
the
proceedings
where
you
find
all
the
admin
stuff
and
all
the
information
you
might
need,
and
as
always,
I
can
say
now
for
the
last
couple
of
meetings.
We
will
also
have
an
ib
open
meeting
next
week
during
the
regular
agenda,
which
will
be
on
thursday,
so
the
the
iab
open
meeting
is
really
focusing
on
technical
work.
The
iab
is
doing
and
giving
the
community
a
chance
to
to
give
us
feedback
and
to
have
some
discussion
with
the
iap
so
happy.
D
D
So
one
is
about
a
workshop
that
the
iab
is
holding
end
of
november
and
this
workshop
is
focusing
on
analyzing
ietf
data.
So
what
we
want
to
do
here
is
to
bring
together
the
researchers
and
engineers
that
are
working
already
on.
Looking
at
like,
for
example,
participation,
trends
and
or
author
trends
or
author
groups,
and
these
kind
of
things
and
bringing
everybody
in
the
room,
understanding
what
we
know
about
the
ietf
already
and
what
else
we
can
learn
from
the
data.
D
I'm
sure
there
will
be
some
interesting
insights
about
what
happened
during
the
last
two
years.
What
changed
during
the
pandemic
and
so
the
workshop
the
call
for
position
tape
is
already
over.
So
the
workshop
is
kind
of
moving
forward,
but
we're
planning
to,
of
course,
record
the
sessions
and
putting
them
available
after
the
workshop,
and
also
nice
thing
about
this
workshop
is
that
we
are
planning
for
having
discussion
sessions
on
monday
and
thursday
and
then
actually
have
some
time
for
hacking
in
between.
D
So
maybe
we
can
actually
come
back
with
some
nice
results
after
the
workshop
and
report
back
at
the
next
itf
meeting
afterwards,
so
yeah
looking
forward
to
that
next
slide.
Yes,
also
an
important
thing,
and
we
have
the
rfc
editor
future
development
program.
So
this
is
a
little
bit
of
special
iab
program
because
it's
it's
actually
driven
by
the
community,
and
I
have
reported
about
this
already
last
time.
So
maybe
you
know
about
this
already.
The
important
news
this
time
is
that
they're
basically
done
with
the
work.
D
So
the
main
document
which
is
describing
the
new
rfc
model
is
currently
in
program
last
call
and
if
you
haven't
looked
at
the
document,
yet
it's
the
right
time
to
do
so.
So
please
reach
out
read
the
document
provide
feedback.
The
program
last
call
is
open
until
november
5th,
but
we
will
also
try
to
reach
out
further
in
the
community
to
get
as
many
reviews
as
possible
before
we
finally
finally
published
this
document
and
there's
also
a
session
from
the
program
next
week
on
wednesday.
D
D
His
term
will
end
in
february
next
year
and
we
probably
have
another
chance
to
thank
him
at
the
next
meeting
in
march
and
hopefully
in
person,
but
I
already
want
to
say
very
much.
Thank
you
to
adrian.
I
think
he
has
done
a
great
job
in
this
position
by
trying
to
to
make
sure
that,
like
all
voices
are
heard
in
our
community
and
discussion,
is
ongoing
and
like
also
I
talked
to
him
and
he
said,
he's
kind
of
also
working
a
lot
with
newcomers
and
providing
it
right
advice
to
them.
D
D
As
I
said,
I
think
this
is
a
very
important
position
in
our
community
and
I
think
it
can
also
be
very
interesting.
Of
course,
there
is
a
little
bit
of
work
here
to
do,
but
if
you're
interested-
please
let
us
know-
I
think
adrian-
is
also
available
to
talk
to.
If
you
want
to
learn
more
about
this,
because
he
has
all
the
first-hand
information,
I
can
probably
only
point
you
to
the
rc,
where
this
role
is
defined.
D
D
D
There
is
a
little
bit
of
news
about
the
saw
management,
so
john
clenson
has
served
for
many
many
years
in
the
position
of
the
laser
manager
for
iso
isotc46
he's
already
retired
for
a
while.
So
he
asked
us
a
while
ago
actually
to
step
down
in
this
position,
and
we
finally
managed
to
find
somebody
so
big
thanks
for
for
john
serving
in
this
position
so
many
years
for
all
the
experience
he
brought
in
from,
like
both
organizations
and
all
his
knowledge.
D
So
far
richard
bruns
was
serving
in
this
position
and
he
reached
his
term
limit
after
six
years.
So
thanks
a
lot
richard
for
serving
in
this
position,
so
we
are
looking
for
a
new
candidate
again.
This
is
the
position
that
has
a
real-time
commitment
and
but
it's
also
very
interesting
position.
I
think
you
learn
a
lot
about
what's
what's
happening
in
isoc
and
you
can
actually
also
impact
there
and
we,
as
the
iab,
serve
as
the
interface
to
isoc.
D
So
we
actually
do
get
a
lot
of
input
about
what
isoc
is
doing.
I
personally
find
it
very
interesting.
I
don't
have
all
this
knowledge
about
the
politics
behind,
but
it's
always
good
to
understand
what
what's
happening
in
policy
and
and
what
other
views
are.
So
this
is
really
definitely
something
where
eyesock
is
important.
D
We
are.
We
are
really
looking
for
you
to
put
your
name
in
last
time.
We
had
a
very
good
set
of
candidates.
I
think
we
had
like
eight
or
ten
candidates,
but
diversity
of
that
set
of
people
was
really
really
low,
so
it
was
really
just
people
from
the
u.s.
It
was
only
male
people
and
it
was
only
white
people.
D
So
icelock
is
discussing
diversity
a
lot
and
they
try
to
fill
their
board
with
a
diverse
set
of
people,
because
isaac
has
like
all
the
chapters
very
international
as
well,
but
I
think
we
should
also
support
them
in
trying
to
to
provide
them
a
more
diverse
candidate
than
we
had
in
the
past.
Maybe
so,
I'm
I'm
really
looking
for
people
to
nominate
their
self
or
maybe
think
about
people
who
would
serve
very
well
in
this
position
and
ping
them
try
to
convince
people
to
put
their
name
in.
D
I
would
definitely
like
to
see
more
women
applying
and
I
think
we
should
also
figure
out
how
to
get
more
people
from
other
regions
interested
in
participating
in
this
work.
So
the
call
just
opened
yesterday
it
will
be
open
until
january,
and
please
put
your
name
in
and
please
think
about
other
people
who
could
be
qualified.
E
E
So
we
what
multiple
awards
per
year.
We
typically
do
six
awards
per
year
and
we're
making
three
of
these
awards
at
the
upcoming
ietf
meeting
next
week,
and
these
will
go
to
thomas
vertigon
for
his
work
on
extend
extensibility
of
bgp,
implementations
and
routing
protocols,
and
this
is
the
the
xbgp
paper
they'll
go
to
x,
exercise
for
her
work,
studying
the
effects
of
third
party
service
dependencies
in
the
internet
and
they'll
go
to
kevin
bach
for
his
work.
E
So
if
you
know
of
any
good
applied
networking
work,
if
you
know
of
any
people
whose
work
that
should
be
highlighted
to
the
community,
then
please
do
consider
making
a
nomination
and
that
the
website
irtf.org
slash.
A
nrp
is
the
site
where
you
combinations,
and
it's
got
all
of
the
details
of
how
the
prize
works.
E
So
pl,
please
do
consider
nominating,
and
please
do
consider
self
nominations
if
you
think
your
work
is
appropriate
for
the
price
and
the
deadline
for
nominations
is
in
a
couple
of
weeks
on
the
19th
of
november
next
slide.
Please-
and
that's
essentially
all
I
have
to
say
this
time,
look
out
for
the
irtf
talks
coming
up
next
week.
The
the
research
groups
highlighted
in
blue
in
slide
are
going
to
be
meeting
next
week
and
if
you're
not
familiar
with
the
work
of
the
irtf
and
how
we
differ
differ
from
the
ietf.
E
F
Myriad
told
you
about
the
rfc
editor
evolution
program,
which
is
wrapping
up,
I'm
holding
the
fort
until
it
on
until
we
until
we
appoint
whatever
whatever
bodies
and
people
will
replace
the
former
rfc
editor.
So
I'm
I'm
sort
of
I'm
keeping
keeping
the
documents
flowing
next
document,
please
next!
Yes,
next
page,
please
we
have
been
publishing
rfcs
and
xml
for
a
year
and
a
half
we
publish
461
of
them.
F
The
process
is
working
pretty
well,
I
mean
there's
some
nits,
the
pdfs
page
breaks
still
aren't
beautiful,
but
the
html
and
text
versions
are
working
pretty
well
and
again.
Since
the
since
the
process
is
the
xml
is
canonical
and
the
rendered
versions
are
not
as
we
improve
the
rendering
we
can
fix
it.
F
It
took
a
while
for
the
production
people
to
learn
the
ins
and
outs
of
xml,
but
they
have
done
so.
We
are
back
to
the
service
level
agreement
that
we
had
before
and
they're
meeting
the
service
level
agreement.
So
so,
although
they're
putting
more
work
into
it,
they
stepped
up
so
that
rfcs
are
now
being
published
as
fast
as
they
were
before
we
switch
to
xml
next,
please.
F
What
I'm
still
trying
to
work
on
are
the
tools
I
mean.
The
a
lot
of
drafts
are
still
being
being
submitted
in
version
2
xml,
even
though
v3
is
what
we
publish
in
and
v3
is
in
fact
stable
and
usable.
Some
of
the
tools
aren't
complete.
I
have
the
discussions
about
like
do
we
need
to
do.
We
need
an
xml
diff.
Do
we
need
other
tools
to
make
it
to
make
us
svg
work
better
and
things
like
that?
We
we're
also
having
a
lot
of
discussions.
F
I
mean
a
lot
of
people
write
stuff
in
markdown.
Do
we
want
to
do?
We
want
to
support
markdown
tools
that
have
an
entire
markdown
tool
chain,
we're
also
doing
some
experiments
in
auth
48.
Anybody
who's
done
an
rfc
notice
that
in
in
in
auth
48,
there's
a
great
deal
of
email
back
and
forth
between
the
authors
and
the
editors
confirming
the
changes
and
and
and
approving
stuff
that
there's
clearly
room
for
automation.
F
F
F
So
if
you
use
the
vocabulary
described
in
rfc,
7991,
that's
valid
that
will
work
when,
when
we
back
out
some
of
the
postal
changes,
I
this
is
something
I
need
to
discuss
with
the
community,
but
I
would
like
to
reissue
the
xml
changing
the
codes,
not
the
text,
but
the
codes
so
that
all
of
the
canonical
xml
actually
matches
the
final
version
of
the
vocabulary,
and
we
also
have
a
lot
of
issues
with
svg.
It
turns
out.
F
We
backed
the
wrong
horse,
the
diver,
the
the
profile
of
svg
we
use
is
one,
that's
it's.
Nobody
uses
it's
abandonware
and
the
tools
have.
We
have
trouble
producing
xvg
that
matches
our
profile
and
the
question
is:
do
we
need
to
change
the
tools
or
change
the
profile
or
something
so
we're
talking
about
that,
so
the
svg
subset
will
likely
change
too.
But
again,
this
is
a.
This
is
a
minor
evolution.
You
know,
if
you
lots
of
people
have
produced,
got
reproduced
rfcs
with
perfectly
good
svg,
both
line
diagrams
and
equations.
G
So
I
have
a
very
short
presentation,
only
three
slides
of
which
two
really
are
content.
The
first
and
foremost
is
I
need.
We
need
feedback.
There
was
a
recent
call
for
community
feedback
that
I
sent
out.
This
is
a
continuation
of
that.
We
need
feedback.
Here's
a
very,
very
easy
way.
Go
to
this
link
on
the
data
tracker,
non-com,
slash,
2021,
slash
feedback.
G
You
click
on
that
you'll
see
the
names
of
all
the
nominees.
You
can
click
on
all
the
names
or
the
names.
You
know
better,
provide
feedback
on
them.
There's
also
a
quote:
unquote:
topics
at
the
very
bottom
of
that
page:
don't
miss
it.
If
you
have
feedback
that
is
not
specific
to
any
given
nominee,
you
can
provide
it
there,
but
be
mindful
of
the
scope.
G
G
G
So
of
course
again
don't
think
that
the
general
or
topics
capability
is
a
it's
a
general
discussion
for
that
you
can
go
to
other
venues
like
you
know
the
itl
mailing
list
or
wherever
so
please
help
us
reflect
the
community
give
us
feedback.
I
would
be
remiss
if
I
didn't
mention
what
rfc
8713
already
calls
out
for.
Please
give
us
feedback
on
the
incumbents.
You
have
worked
with
them.
You
have
seen
them
in
their
positions,
sadies
or
llc
members
or
whatever
the
case
may
be.
G
G
Final
thing,
I
need
to
say
is
thank
you.
Thank
you.
Thank
you
to
all
the
nominees
and
I
wish
to
also
include
the
quote-unquote
almost
nominees,
because
I
know
there's
folks
who
were
considering.
I
had
discussions
with
some
of
you,
who
were
very,
very
convinced.
You
were
going
to
go
forward
with
the
process.
For
some
reason
you
know
life
happens.
I
understand
not
everybody
who
intended
to
made
it.
G
Finally
as
a
as
a
nominee
so
but
you
you
considered
it,
and
I
thank
you
for
that
and
we
have
30
nominees
and
we
have
32
nominations,
because
two
of
those
nominees
are
buying
for
two
positions,
each
so
a
huge
thanks
for
all
those
nominees
and
almost
nominees,
and
please,
if
you
don't
get
selected
this
time,
please
offer
your
service
next
time.
We
need
many
nominees
for
non-comp
to
do
its
job
next
slide.
Please
here's
some
pointers.
You
can
use
these
to
get
in
touch
with
us.
G
We
have
office
hours
this
week,
they're
in
the
agenda.
Please
look
for
those
they're
on
gather.
There
was
one
yesterday
one
this
morning,
one
tomorrow,
one
next
week.
If
those
don't
work
for
you,
please
let
us
know
send
me:
emails
send
email
to
nom
com.
We
can
arrange
a
meeting
through
webex
zoom,
whatever
the
case
may
be
phone
just
contact
us
give
us
feedback.
Thank
you
very
much.
That's
it.
H
And
next
slide
again,
please
so,
yes
thank
you
to
ericsson
and
to
gonzalo
in
particular
for
making
this
happen.
So,
as
lars
said,
erickson
stuck
with
us
twice
now,
when
we
have
cancelled
in-person
meetings
and
move
them
fully
online
and
continue
to
sponsor
us
and
also
offer
to
sponsor,
should
we
when
we
go
back
to
in-person
meetings,
so
this
has
been
very
helpful
of
them.
Thank
you
very
much
next
slide.
H
Please
thank
you
to
cisco
juniper
for
and
the
the
webex
part
of
cisco
for
their
equipment
services
sponsorships.
We
receive
a
lot
of
equipment
from
both
cisco
and
juniper.
That
really
helps
us
with
running
the
network
for
the
in-person
meetings,
so
we'll
begin
to
start,
seeing
that
usually
and
hopefully
next
year,
next
slide.
Please.
H
H
And
to
our
silver
diversity
and
inclusivity,
sponsor
huawei,
and
to
our
bronze
sponsors,
comcast
and
donuts,
and
to
our
running
code,
sponsor
cnn
nick
as
you'll
see
our
new
set
of
sponsorships
bring
about
a
substantial
amount
of
ongoing
support
from
these
companies,
because
I
think
we've
managed
to
get
the
point
where
we're
aligning
with
the
values
of
these
organizations
well
and
people
are
comfortable
supporting
us.
Thank
you
next
slide.
Please.
H
So,
thank
you
to
the
many
generous
volunteers
who
make
this
happen.
We
had
a
code
sprint
last
week
focused
on
performance
of
the
data
tracker
and
we
had
lots
of
people
involved
there
looking
hard
at
that
stuff.
So
thank
you
very
much
for
that
and
thank
you
to
the
knock,
who
continued
to
provide
our
significant
support,
such
as
during
this
meeting,
and
thank
you
particularly
to
their
employers,
who
provide
their
time
to
us
for
free
for
us
to
for
them
to
work
on
ietf
related
things.
That's
very
generous
of
them
next
slide.
Please.
H
So
I'm
going
to
go
through
all
here,
but
I've
listed
out
all
everyone
who's
part
of
the
team
that
hasn't
been
thanked
so
far,
so
we
have
the
secretariat
team.
We
have
the
not
contractors
meet
echo,
which
is
obviously
crucial
for
us.
We
have
the
llc
staff,
which
have
grown
a
little
bit
and
we
have
the
contracting
members
of
the
tools
team.
So
thank
you
very
much
for
everyone
for
making
this
a
success.
H
Next
slide,
please
so
ietf113
we
are
close
to
negotiating
a
new
venue
for
this.
All
I
can
tell
you
so
far
is
that
it
is
going
to
be
in
europe.
We
have
had
to
move
away
from
bangkok
due
to
the
covert
situation.
There
we've
been
unable
to
find
any
other
alternative
venue
in
asia
due
to
largely
restrictions
on
travel
and
in
some
cases
due
to
the
state
of
the
pandemic.
H
There
we've
also
similarly
had
to
rule
out
north
america
due
to
travel
restrictions
and
we've
therefore
been
working
on
europe
for
some
time
now.
Of
course,
it's
likely
by
march
that
many
of
the
travel
restrictions
will
have
changed
for
those
other
regions,
but
that's
not
something
we
can
take
the
risk
on.
H
Given
the
reluctance
that
some
people
will
still
have
to
travel
and
the
practical
difficulties
that
some
people
will
still
feature
still
struggle
with
and
then,
but
then
we're
going
to
ramp
up
again
for
the
middle
of
the
year
and
later
in
the
year
for
the
meetings
to
enable
us
to
get
back
to
normal
sized
meetings
again
relatively
soon.
We
hope
next
slide.
Please.
H
And
so
finally,
thank
you
to
all
of
our
global
hosts,
so
our
global
hosts
make
a
commitment
to
us
of
generally
six
years
where
they
agree
to
fund
us
throughout
those
six
years
and
to
sponsor
one
or
to
be
the
host
meeting
host
for
at
least
one
meeting
or
two
meetings
during
that
period
of
time.
So
these
people
have
made
long-term
commitments
to
us,
and
many
of
them
have
been
making
some
years
having
renewed,
at
least
once
so.
Thank
you
to
cisco,
comcast
ericsson,
huawei,
juniper,
nbc,
universal
and
nokia.
H
So
this
is
all
we
have
so
far
about
the
future
meeting
locations
and
venues.
We
we
are
we
as
you'll
notice.
We
have
a
number
of
slots
open
one
in
2022
in
november,
we
are
close
to
negotiating
somewhere
for
that,
the
asia
slots
in
116
itf
one
or
six
we're
also
close
to
negotiating
someone
there
that
the
reason
we
haven't
done.
H
Those
is
that
generally,
we
need
to
do
site
visits
and
we
need
the
hotels
to
be
up
and
operational
and
functional
for
us
to
do
business
with
them,
and
the
hotels
have
really
only
started
coming
back
on
stream
in
the
last
few
months.
So
that
has
been
problematic
until
now
and
for
mike's
comment
in
the
chat
to
know
the
dates
haven't
changed.
Those
are
still
the
same
dates.
H
We
did
look
at
changing
the
dates
to
see
whether
that
helped
availability,
but
there
was
no
reason
to
do
that,
and
so
no,
we
haven't
changed
that
and
then
looking
further
you'll
see
that
we've
rebooked
vancouver
later
on
and
my
tf-119
of
course,
we've
had
an
asian
cancellation
that
we're
looking
to
try
to
rebook
as
well,
so
this
schedule
should
hopefully
fill
up
quite
soon.
Thank
you
next
slide.
Please.
H
H
H
So
this
is
now
the
full
complement
of
llc
staff.
There's
yours,
truly,
the
handsome
man
on
the
left,
greg
wood,
director
communication
operations,
lee
berkeley,
shaw,
who
I'll
be
introducing
shortly
who's,
our
director
of
development,
working
on
raising
money
for
our
endowment,
kasara
and
nick
giard
are
our
two
senior
developers.
They
have
slightly
different
job
titles
because,
where
nick
works,
the
lives,
the
word
engineer
is
regulated,
and
so
we
couldn't
use
the
word
engineer
for
him.
H
I
I
As
such,
I'm
very
pleased
to
announce
that
we
have
a
new
gift
to
the
ietf
endowment
as
of
september
of
this
year.
Lachnik,
the
internet
registry
for
latin
america
and
the
caribbean
has
made
a
hundred
thousand
dollar
gift
to
the
endowment.
This
is
a
first
time
gift
for
them,
we're
so
pleased
and
they
join
aaron
and
ripe
as
key
donors,
and
their
gift
will
be
matched
two
to
one
by
the
internet
society.
I
This
is
really
exciting
and
we
hope
this
will
be
the
first
of
many
gifts
coming
down
the
pike.
Our
special
thanks
go
to
oscar
robles
and
the
entire
board
of
laknik
for
their
contribution,
and
I'd
just
like
to
say
if
you
want
to
learn
more
about
the
endowment
as
an
individual
or
on
behalf
of
your
organization,
I
encourage
you
to
reach
out
I'll,
be
and
gather
throughout
all
next
week
and
I'm
happy
to
catch
off
catch
up
offline
with
you,
anytime,
you'd,
like
I
think
that
about
covers
it
jay
anything
you
want
to
add.
H
H
That's
in
gather
we've
deliberately
made
gather
space,
smaller,
more
cozy,
so
we're
all
pushed
together
and
have
to
start
interacting
and
talking
so
come,
join
the
fun
and
gather
afterwards,
so
that
we
can
them
at
least
see
each
other
in
person,
even
if
we're
not
able
to
meet
in
person
at
all
and
now
over
to
you
jason.
Thank
you.
J
J
J
We
also
completed
a
consultation
on
the
llc
role
requirements
that
we
send
to
the
nom
com.
That
was
some
feedback
that
we
had
received
from
the
prior
years
in
oncom,
and
so
we
put
that
out
to
community
comment
over
the
past
few
months
and
then
sent
the
updated
requirements
over
to
the
nom-com
in
august.
I
don't
think
there
were
any
major
changes
there.
Perhaps
just
these
minor
tweaks
item
number
three.
J
This
is
an
interesting
one
that
just
came
up
one
or
two
board
meetings
ago.
You
know:
we've
only
just
adopted
an
investment
policy,
but
our
advisor
goldman
sachs
has
recommended
potential
changes
to
those
and
we'll
be
considering
those
we've
started
to
look
at
their
their
recommendations
and
we're
going
to
at
the
next
board
meeting
in
december
have
an
independent.
J
J
You
know
the
different
technical
vendors
to
see
what
we
need
to
do
to
get
ready
for
our
first
hybrid
meeting
in
march
again
nice
to
have
a
bit
more
time
than
when
the
pandemic
first
struck
to
have
that
transition
to
online.
Only
so
you
know
some
some
work
is
going
in
there
mostly
around.
You
know
the
contracting
and
support
for
any
technical
investments
that
might
be
needed
next
slide.
Please.
J
So
this
is
the
view
of
the
current
operating
budget.
Really.
The
notable
thing
here
is
that
the
current
net
income
is
solely
a
result
of
the
isoc
funding,
the
timing
of
that,
and
so
that
investment
comes
in
december.
I
believe
so.
You
know
the
numbers
look
better.
What
we'll
plan
to
do
next
year
is
to
account
for
that
a
bit
differently
in
the
budget
so
that
it
it
doesn't
show
up.
J
J
J
In
april
we
proposed
a
high-level
process
for
this
and
a
timeline,
and
you
know
asked
for
feedback
starting
then,
in
june
we
began
the
consultation
process
by
first
releasing
a
draft
document
for
comment,
asking
a
bunch
of
very
specific
questions,
as
well
as
general
ones,
and
then,
in
the
june,
to
september
time
frame.
We
made
a
number
of
revisions
to
that
assessment
based
on
community
input
and
then
we've
just
released
a
final
report,
and
so
you
can
take
a
read
through
that
lots
of
details
in
there
we'll
touch
on
some
of
them
here.
J
J
J
So
we
had
63
specific
enumerated
requirements:
61
of
those
were
rated
as
achieved
or
on
track.
Two
we
were
noting
here
as
partly
achieved
or
in
progress,
and
those
specifically
were
requirements.
Number
50
and
61.
so
improve
the
ietf's
technical
environment
and
develop
a
sustainable
funding
model
next
slide,
please!
J
J
Not
only
is
there
a
lot
of
technical
debt,
but
the
community
is
really
in
the
midst
of
a
transition
to
you
know,
maybe
newer
and
updated.
You
know,
tool
sets
or
technical
workflow
processes
and
so
we're
here
to
support
that
and
resource
it.
However,
we
can,
but
you
know,
certainly
there's
you
know,
maybe
a
higher
rate
of
change.
You
know
over
the
next
few
years
than
perhaps
the
past
five
so
ongoing
in
process
next
slide.
Please
so
requirement.
61
is
developing
a
sustainable
funding
model.
J
We
feel,
like
there's,
been
a
lot
of
progress
here,
but
clearly
you
know
this
is
an
area
of
continued
focus.
So,
first
and
foremost
we
were,
you
know,
pleased
to
have
the
new
funding
agreement
last
year
with
isak,
with
the
great
matching
program
that
lee
berkeley
mentioned
a
moment
ago
and
of
course,
thanks
again
to
lachnik
for
their
new
contribution.
We
really
really
appreciate
that
and
the
leadership
they've
shown
we've
revised
the
sponsorship
program.
You
know
so,
for
example,
we
have
different
types
of
sponsorships
that
organizations
can
make
some
new
opportunities
for
that.
J
J
You
know
that
agreement
framework
with
isoc
and
that
you
know
you
know
lee
berkeley
has
just
been
hired.
So
you
know
we
didn't
feel
like.
We
could
mark
that
as
complete
by
any
means.
We
think
that
we're
making
substantial
progress,
but
we've
got
more
work
to
do,
and
this
is
where
there's
a
lot
of
board
focus
next
slide.
Please.
J
You
know
in
doing
it
once
a
decade
in
a
much
more
disruptive
fashion,
so
we
recommend
doing
that
every
three
years
and
that's
something
that
the
llc
will
be
scheduling
and
driving.
Two.
We
recommended
making
a
couple
of
modest
financial
planning
adjustments,
one
during
the
annual
budgeting
process,
just
updating
the
target
for
reserve
funds
and
annually
reviewing
the
investment
policy
which
we'll
be
doing
again.
J
But
it's
not
possible
anymore
in
the
way
that
the
insurance
for
those
issues
work
to
increase
that
policy
coverage,
and
so
that
really
is
one
of
those
issues.
That's
potentially
driving
a
change,
and
we
really
just
identify
that
this
is
a
potential
issue.
I
think
the
trust
totally
agrees
and
they're
going
to
go
off
and
work
on
a
consultation
about
what
that
might
look
like,
and
you
know,
lead
that
discussion
with
the
community
next
slide.
D
Yes,
so
that's
me
again,
I
believe
we
have
a
next
slide
where
we
have
photos
of
everybody
right.
So
no
not
everybody
has
to
turn
on
the
camera.
At
the
same
time,
you
can
see
all
the
faces
and
names
here.
That's
the
iab
loves.
You
can
stay
here.
If
you
want,
you
don't
have
to
disappear.
That's
right!
Yeah!
We
have
the
iab.
We
have
lars
here
and
we
also
have
colin
and
john
with
us
for
any
questions.
D
K
K
D
Okay,
thanks
for
your
question,
you
were
breaking
up
a
little
bit,
but
I
think
you
are
talking
about
rc.
That
says
that
the
user
intent
should
be
considered
when
designing
protocols,
and
the
question
was
if
you,
if
the
ib
did
something
to
implement
this,
I'm
inviting
other
ib
members
to
add
a
an
opinion
here
and
like
even
the
authors
of
the
draft
who
are
not
on
the
ib
anymore.
But
like
from
my
point
of
view,
this
is
the
advice
given
by
the
iab
for
the
ietf
community.
E
M
D
A
Yeah
thanks,
so
this
is
of
concern
right
and-
and
it
was
a
joint
topic,
we
had
a
recently
had
a
little
workshop
with
the
iab
and
the
llc
board,
where
this
was
what
one
of
the
sessions
right
we
we
are
monitoring
sort
of
the
sort
of
activity
of
the
itf
and
we
reported
on
it.
I
think
at
the
last
meeting
a
little
bit
more
detail.
We
we
do
see
that
sort
of
currently
chartered
work
is
sort
of
progressing.
Okay,
I
want
to
say
there
is
a
like.
A
I
think
everybody
is
sort
of
finding
it
difficult
to
socialize
a
topic,
especially
something
that's.
Maybe
a
bit
controversial-
or
you
know-
requires
some
some
more
shaping
in
this
virtual
format,
and
we
know
also
by
anecdotally
from
a
few
people
that
basically
are
waiting
with
their
proposals
until
they
get
to
be
back
in
person
and
can
present
to
a
room
rather
than
online.
A
M
Now
was
something
that
I
hadn't
heard
and
I'm
wondering.
Is
there
a
way
to
sort
of
share
some
visibility?
If
those
things
are
out
there,
you
know
I
mean,
maybe
that's
not
an
accurate
assessment,
maybe
it
is,
but
still
I
I
think
that,
from
a
from
an
organizational
point
of
view,
it
would
be
reassuring
to
know
there.
This
is
that
this
is
a
a
temporary.
A
So
so
I
agree
all
signs
that
we
see
point
to
this
being
solely
based
on
on
the
pandemic
and
not
being
able
to
meet,
and
so
one
thing
that
I
I'm
actually
happy
about
is
hot
rfc.
So
thank
you
again
for
that,
because
I
think
that
is
actually
a
pretty
useful
vessel
in
which
people
can
bring
sort
of
at
least
the
nugget
of
an
idea
for
new
work
and
expose
it
and
get
some
private
feedback,
and
maybe
that
private
feedback
can
be.
M
So
I
I
don't
want
to
believe
in
the
quote,
but
let
me
just
make
I
I
feel
like
we're
we're
completing
two
slightly
different
topics.
One
is
sort
of
I'm
suggesting
that
when
you
say
something
like
all
signs
are
pointing
to
the
fact
that
this
is
temporary,
I'm
suggesting
that
it
would
be
helpful
if
those
signs
could
be
collected
together
and
shared
with
the
community,
so
that
we
can
all
develop
that
assessment
that
what
the
actual
signs
are.
D
So
maybe
let
me
say
one
thing,
I
think-
and
this
is
a
topic
we've
been
discussing
very
often
before
and
during
the
pandemic.
I
think
we
do
have
generally
a
problem
to
on
board
new
work
in
a
good
way
to
find
the
right
contact
person
and
to
bring
people
to
the
right
stage
right.
So
it's
not
like.
I
think
the
ihg
is
actually
exposed
to
much
more
of
this.
These
ideas
on
new
work.
D
What
we're
also
seeing
is
that
and
we're
all
seeing
that
that
there
are
components
of
an
in-person
meeting
that
we
can't
replicate
in
a
virtual
environment,
and
these
are
simply
missing,
and
a
lot
of
this
was
was
where
you
actually
talk
to
people
about
new
work
and
so
on,
and
we
can't
replicate
this
and
we
don't
just
don't.
Have
it
right
and
I
think
what
the
signs
that
we
are
looking
at
is
just
the
numbers
that
everybody
can
look
up
from
the
data
tracker
or
the
email
is
like.
D
D
D
O
Yeah,
thank
you
I
I
may
be
talking
to
the
okay.
So
two
two
questions,
the
the
comment
about
work
being
considered
to
be
controversial.
Do
you
have?
Were
you
actually
saying
that
that
was
the
people
proposing
the
work
were
concerned
that
it
was
too
controversial
or
someone
else
was
concerned
that
was
too
controversial?
A
O
P
D
D
N
It's
quite
different
like
go
to
the
hackathon
yeah
you're.
Welcome
and
you
know,
have
your
team
have
your
table
and,
and
you
just
move
forward,
it's
much
harder
in
the
itf
side
and
of
course
I
understand
some
of
the
reasons
why
I
understand
that
many
proposals
are
also
all
over
the
place
and
not
very
easy
to
add
up
to
any
standards
organization,
but
I
I
think
we
should
at
least
recognize
that
this
is
an
issue.
It's
it's
difficult
and
right.
You
have
to
do
these
new
things.
D
H
H
H
P
Q
Yeah
hi,
I
just
wanted
to
follow
up
on
the
community
survey.
I
think
that
was
mentioned,
and
I
note
that
it's
both
the
llc
and
esg,
I
think
both
that
are
covering
it.
I
just
wanted
to
see
if
you
had
any
more
follow-up
on
it
in
terms
of
the
actions
from
it.
I
know
that
you
have
a
whole
year
that
you're
going
to
review
it,
but
any
any
information
would
be
great
thanks.
H
So
there
I
won't
go
into
the
details
of
what
was
discussed
because
that
hasn't
yet
been
written
up
and
agreed
properly
yet,
but
it
certainly
was.
There
was
an
understanding
that
some
things
there
are
important
that
need
to
be
tackled
by
all
of
us,
and
this
considerable
effort
was
put
into
thinking
about
how
we
might
tackle
those.
So
I
think,
that's
probably
all
we
can
say
unless
lars
wants
to
add
anything
to
that.
O
Yeah,
I
I
just
wanted
to
take
a
a
minute
to
thank
you
all
on
camera
and
live
for
the
work
that
you
all
are
doing.
I've
been
following
at
a
distance,
you
know
the
work
that
you
all
have
been
doing
in
the
current
environment,
and
this
is
this
is
the.
I
think
this
is
the
itf
meeting,
where
I
finally
realized
there's
no
possible
way.
I
could.
I
could
even
contribute
to
this.
So
thank
you
for
the
work
you're
doing.
I
know
it
is
not
easy
and
I
know
it
really
matters.
O
We
have
to
you
know:
we
have
tools
now
that
we
that
so
I'm
not
talking,
I'm
not
talking
to
you
guys,
I'm
talking
to
you
guys
and
the
community.
We
have
tools
that
now
that
we
could
use
more.
So
the
hot
rfc
thing
was
kind
of
shut
down
during
the
pandemic,
and
it
took
us
a
while
to
figure
out
that
we
could
actually
do
that
in
a
virtual
meeting
or
in
a
hybrid
meeting.
O
One
of
the
things
that
I
note
is
that
gather
is
yeah
and
I
didn't
realize
this
for
a
while,
but
gather
is
up
between
itf
meetings,
so
you
know
anything
that
you
could
do
and
gather
you
know
today
or
in
the
in
the
coming
week.
You
could
do
in
february
also
and
that
that
that
that
does
actually
have
the
ability
to
have
audio
visual
conversations,
and
things
like
that.
O
O
But
if,
if
gather
is,
is
capable
of
supporting,
you
know
the
small,
the
small
meetings
that
we
kind
of
visualize
assigned
meetings
that
may
be
a
that,
may
be
a
good
thing
as
well.
You
know
it
it's
that.
I
think
it's
important
for
everyone,
especially
the
community,
to
remember
that
bots
have
never
been
a
required
part
of
this.
They
were
just
a
convenient
way
of
us
of
us
evaluating
new
work
proposals
when
the
community
gathered.
R
I
think
the
idea
of
having
a
high
quality
idea,
not
going
for
a
formal
buff
to
directly
kind
of
chartering,
is
a
very
viable
kind
of
path.
That
is
one
of
the
outcomes.
That's
sometimes
recommended
at
a
sec
dispatch
that
the
idea
seems
baked
enough.
There's
enough
kind
of
discussion
on
it.
Let's,
let's
do
a
little
more
mailing
list
discussion
to
get
charter
language
firmed
up.
O
O
As
a
reminder
to
me,
almost
all
the
areas
have
some
form
of
dispatchy
function
these
days,
don't
they
and
I
wonder
whether
I
wonder
whether
being
able
to
do
something
with
those
kinds
of
groups
where
they're
you
know
where
it's
more
formal
than
a
side
meeting
together,
but
less
formal
than
a
buff
request
being
able
to
do
that
on
an
ongoing.
You
know,
like
once
between
ietf
meetings,
say
as
an
example
just
so
that
people
aren't
waiting
four
months
to
have.
O
You
know
see
how
things
go
with
the
ietf,
the
you
know
the
thing
that
jason,
that
jason
was
talking
about
with
the
llc
of
you
know,
looking
at
stuff
more
frequently
than
we
have
been
looking
at
things.
I
think
that
you
know
I
think
that
may
be
a
good
model
for
the
technical
work
as
well
as
you
know,
to
say
what
what
are
we
gonna?
What
are
we
gonna
wish?
We
had
a
good
proposal.
O
You
know
had
approved
a
proposal
for
at
the
next
ietf
meeting,
and
I
always
say
you
know
you
guys
you
guys
would
know
better
how
to
do
that
on
the
with
the
current
structure
and
in
the
current
environment,
but
I
did
I
did
want
to
respond
to
that
as
well.
I
think
I
think
you
know
I
think
you're
digging
in
the
right
hole.
C
S
So,
first
off
apparently
warren
says
we
should
be
wearing
hats,
so
I
thought
I'd
join
in,
but
I
wanted
to
follow
spencer's
topic
a
little
bit
because
it's
an
important
one-
and
you
know
it's
definitely
easier
to
have
new
work
when
you
can
get
together
and
do
it
in
person,
but
we're
not
going
back
to
fully
online
or
fully
in
person
for
a
while.
I
mean
if
we
just
heard
earlier
that
you
know
we
expect
march
to
be
sort
of
half
attended
and
so
hybrid
meetings.
S
You
know,
may
still
mean
less
incoming
work.
Unless
we
can,
you
know,
find
other
solutions
that
you
know
allow
us
to
continue
bringing
in
new
work,
even
when
some
of
the
potential
participants
can't
actually
make
it
to
the
meeting
because
they're
in
an
area
where
travel
may
be
restricted,
for
example,
so
it
would
really
benefit
everyone
to
concentrate
on
reaching
out
and
helping.
You
know
through
some
of
the
existing
tools,
I'm
very
happy
that
spencer,
you
know
mentioned
gather,
for
example,
as
being
around
in
between
meetings.
S
I
will
admit
myself
I
haven't
joined
gather
as
much
as
I
as
I
should,
and
I
should
I
intend
to
make
a
concentrated
effort
to
do
that.
But
just
you
know
even
responding
to
email
or
helping
out
with
the
guides
program,
or
something
like
that
you
know,
would
greatly
help
bring
in
new
work.
It
feels
really
good
when
you
actually
manage
to
you
know
help
somebody
take
a
document,
walk
them
through
the
ietf
process
and
then
later
find.
S
You
know
that
that
new
member
that
brought
in
new
work
to
become
a
active
member
of
the
ietf
community
and
there's
been
a
couple
of
cases
over
the
past.
I
want
to
say
five
to
ten
years
where
I've
helped
somebody
come
in,
and
you
know
now,
they're
now
they're
actually
writing
more
mail
than
I
can,
because
I
really
am
not
great
at
keeping
up
with
email.
But
so
you
know
final
point
is
really
try
and
make
a
concentrated
effort
to
help.
S
A
Thanks
yeah,
that
was
a
good
point,
so
I
actually
got
matched
up
with
somebody
through
mentoring
that
was
trying
to
bring
new
work.
I
think
it
was
to
transport
and-
and
that
was,
I
think,
a
pretty
interesting
engagement
for
both
sides.
In
terms
of
you
know,
you
could
really
sort
of
help.
Somebody
explain
you
know
what
should
you
focus
on
when
you
first
present
this?
M
Yeah
so
before
we
break
the
the
sort
of
the
general,
the
comment
to
everybody
capabilities
and
gather
are
a
little
bit
limited,
and
so
I
want
to
take
a
minute
and
just
sort
of
talk
about
the
hot
rfc
structure.
If
that's
okay
with
you,
okay,
so
so
we
have
a
space
and
gather
for
hot
rfc.
The
the
links
on
the
on
the
agenda,
page
and
notewell
is
the
password
to
get
in.
M
If
you
go
in
there,
you'll
see
where
you
enter
and
after
you
decorate
your
avatar
there's
directions
on
the
floor
to
take
you
to
the
hot
rc
space.
It's
laid
out
like
a
poster
session,
and
so
each
talk
has
a
little
essentially
a
private
room
and
gather
where
folks,
who
are
in
the
room
can
talk
to
each
other.
M
A
Thanks
aaron
that
was
useful
and
yeah.
Thank
you
all
for
joining
the
plenary.
I
know
it
was
early
for
some
of
you,
but
I
think
we
had
pretty
good
attendance,
probably
only
the
same
order
magnitude
as
the
the
last
few
that
we've
done
so
that
that's
a
good
sign
for
this
experiment
and
I'll
see
you
all
over
and
gather
now
and
then
next
week
in
the
working
group
sessions
enjoy
the
itf
bye,
guys.