►
From YouTube: IETF100-EXTRA-20171115-0930
Description
EXTRA meeting session at IETF100
2017/11/15 0930
https://datatracker.ietf.org/meeting/100/proceedings/
A
C
D
C
E
C
B
C
B
Have
one
of
these
things
totally
unreadable
the
note
world?
Everyone
has
noted
the
note,
well
excellent
I'm
done
by
the
way
we
have
three
people
remotely
on
media
co,
plus
a
very
small
crowd
in
the
room.
Here
we
have
an
hour
which
I
told
them:
I
don't
need
we're
a
brand-new
group
I'm
fairly
new
at
this
chairing
business,
and
nobody
has
come
back
to
me
with
requests
for
things
to
do
today.
So
I've
put
together
a
rather
optimistic
agenda.
I
doubt
we'll
need
all
this
time
for
all
the
things,
but
you
never
know.
B
Right
excellent,
if
your
uncover
than
not
somebody
else
will
send
us
an
email
awesome,
we
all
have
him
all
right.
Thank
you,
John's,
going
to
do
the
job
so
roughly.
What
we're
trying
to
do
here
is
extend
IMAP
and
sim
with
new
things
that
we
need
they're.
Already,
a
ton
of
extensions
I
for
something
completely
unrelated
was
looking
back
at
an
issue
a
couple
of
years
ago,
where
Microsoft
Exchange
implemented
the
move
extension
and
took
the
untag
response
to
be
don't
put
anything
in
front
of
the
response
at
all.
B
We
do
have
a
fairly
high
bar
to
get
to
the
clients
to
be
worth
clients,
implementing
anything
that
we
define
here,
because
it
has
to
be
perfect
or
there's
no
point,
and
even
then
they
need
to
support
both
the
old
and
the
new
until
every
servers
updated.
So
I
looked
at
what
the
three
things
that
would
justify
doing,
an
extension
are
I
think
either
the
world's
changing,
and
we
want
to
follow
up
which
the
64-bit
extensions
fourth
message,
sizes
are
getting
bigger
at
mailboxes.
B
Are
getting
bigger,
we
want
to
support
more
than
32
bits
and
architectures
now
support
bigger
numbers.
If
multiple
vendors
are
doing
the
same
thing
like
it's
been
the
message-id,
it's
worth
standardizing
that
so
that
everyone's
at
least
doing
the
same
thing,
the
same
way
and
finally
for
Joe
Maddon
compatibility
things
like
mailbox,
unique
ID
where
there's
an
ID
that
stays
to
the
mailbox
when
it
gets
renamed.
It
would
be
good
to
implement
that
in
a
way
that
can
be
seen
by
on
that
as
well.
B
B
Sure
so
list
my
rights.
When
you
do
a
list
command,
you
can
specify
extra
things
to
be
returned
and,
if
you
say
return,
my
rights
and
it
just
spits
out
as
if
you're
done
in
my
rights
on
each
mailbox
directly
after
the
list
command
convenient
for
clients
that
want
to
show
whether
a
mailbox
is
read-only
or
whether
you
can
write
to
it
as
part
of
their.
They
can
just
do
a
single
list
command
and
get
that
as
part
of
the
response.
B
We
actually
use
this
one
at
fast
mail
to
tell
whether
a
mailbox
is
writable
or
not.
It's
quite
trivial
to
just
add
one
more
item
to
the
return,
and
you
get
exactly
the
same
responses
you
get
to
my
rights.
It
was
very
easy
to
implement
sip,
FCC
and
sip
special
use,
I
believe
we
implemented
without
using
yet
and
I.
We
want
to
use
the
FCC
press.
Also,
we've
looked
at
it.
G
F
F
F
F
The
other
one
is
I,
I
thought
the
document
was
really
straightforward
and
then
somebody
went
and
did
overview
of
all
all
the
extensions
and
all
all
interactions
between
things
and
found
a
bunch
of
stuff,
so
I
went
through.
All
of
these
I
believe
I
incorporated
all
the
relevant.
A
BNF
updates
a
couple
of
comments.
One
is.
F
B
B
F
It's
actually
I,
don't
know,
maybe
even
like
10
years
ago,
Dave
cridlington
I.
Actually
we
had
a
quarter
update
draft
which
expired,
so
I
can
talk
to
Dave
and
bring
it
back
to
life.
It
doesn't
do
what
you
do
what
you
were
talking
about,
but
it
was
trying
to
add
a
bunch
of
other
type
of
quotas.
You
know
that
we
can
think
of.
Maybe
it
was.
B
B
B
F
F
Think
I
I
made
everything
I
can
think
of
as
being
63
bit
except
for
body
part
number
I,
don't
think
we
want
that
many,
so
I
thought
that
was
quite
safe
to
just
leave
it,
as
is
so,
but
if
I
missed
anything,
let
me
know
one
editorial
comment:
I
have
in
the
document
is
that
I
have
one
big
section
with
you
know
pieces
of
different
they'd
be
enough
updates.
Do
people
want
it
to
be
split
by
by
each
extension,
I
have
comments
in
there.
F
G
So
I
know
that's
you
don't
want
to
have
well
I've
collected,
not
summary
collected
grammar
at
the
end,
but
have
the
grammar
also
in
the
sections
that
it
applies
to
now.
I
know:
that's
it's
bad
to
have
the
same
thing
twice,
because
that
invites
having
them
differ,
but
so
I'm,
just
saying
and
I,
don't
feel
strongly
about
it.
In
this
case.
F
Yeah,
the
issue
is
that
most
of
the
things
are
reusing
message:
size
element,
whether
it's
in
a
pant
or
in
various
fetch
responses.
So
they
were
a
bit
of
Clinton.
You
know
generic
clean
up
to
the
mines
back
and
then
other
things
are
sort
of
separate
and
there
they
have
comments,
so
I
can
repeat
it,
but
for
the
you
know,
it's
only
like
four
pages
document
I'm,
not
even
sure
it's
worth
it.
B
B
H
H
In
the
current
image
world,
there's
only
the
date
at
which
the
message
was
received
into
the
mail
store
in
general,
and
if
you
copy
a
message
or
move
it
elsewhere,
that
date
is
retained
and
the
same
day.
This
is
date
where
the
message
is
stored
in
a
particular
folder,
and
you
could
use
that,
for
instance,
to
do
automatic
message
expiry.
So,
if
you
want
to
remove
messages
from
trash,
you
need
to
know
when
it
was
saved
in
to
threshold
or
not
when
it
was
first
received.
That's
the
main
distinction
between
the
two.
G
H
G
J
B
An
important
question
that
was
the
more
general
question
whether
it
becomes
another
fetch
item
or
whether
it
becomes
a
message
annotation
since
we
have
this
extensibility
feature
already
as
the
standard
should
we
be
using
it
or
should
we
just
be
adding
new
batch
items?
That's
a
more
more
general
philosophical
question
for
this
group.
Yeah.
G
H
Well,
basically,
you
can
query
the
size
of
of
a
mailbox
implicitly
in
the
in
the
in
the
list
command,
and
the
advantage
of
that
is
that
you
can
query
at
once.
If
you
use
the
list
extended
way
of
doing
things
and,
first
the
quota
extension,
you
cannot
query
the
size
of
a
particular
folder.
You
can
only
create
for
a
particular
quota
route,
so
that
doesn't
say
you
have
one
folder.
You
can
get
it
from
multiple
folders
as
a
total,
but
not
for
individual
folders.
G
H
F
J
Ya
know:
Jenkins
can
assign
any
way
similar
to
Lexy.
It
sounds
very
related
to
quota
and,
if
you're
making
changes
to
how
you
can
fetch
quota,
maybe
they
need
to
be
considered
together.
So
you
can
both
see
how
much
quota
you
have
and
also
for
each
of
those
things,
whatever
sister
statue
and
what's
being
used
now,.
F
Have
another
sort
of
extension
in
this
similar
to
status
size?
Some
clients
only
show
the
number
of
undeleted
messages.
There
is
no
work.
There
is
a
way
to
query
number
of
unseen
messages,
I
believe,
but
there
is
no
way
of
seeing
like
unseen
undeleted
messages
in
a
mailbox.
So
maybe
we
need
another
state,
but
then
it
goes
into
a
question
you
know:
do
we
ever
want
to
do
this
for
the
flags.
B
H
G
And
while
we're
getting
to
that
question,
it's
does
it
have
to
be
fast,
so
I
some
mailboxes
are
stored
in
one
big
file
and
you
immediately
know
the
size
I
used
to
have
a
server
where
each
message
was
stored
in
a
separate
file
and
computing.
The
size
would
take
a
while.
So
the
and
I
haven't
read
the
draft,
so
I
don't
know
if
it
says
anything
about
it.
But
if
it's
expected
to
be
fast,
the
draft
needs
to
say
that
so
that
implementers
don't
do
the
wrong
thing.
I.
B
B
H
B
So
the
other
things
that
I
put
in
notes
for
were
xgm
message,
ID
and
xgm
thread.
Id
multiple
servers
have
some
kind
of
concept
of
a
consistent
message:
ID
that
remains
with
a
message
when
it
gets
copied
or
moved
if
it's
the
same
message,
content
that
keeps
the
same
ID
and
many
servers
also
have
a
concept
or
a
thread
idea
where
they
have
calculated
that
messages
are
related
and
given
them
the
same
idea
of
some
sort.
B
The
last
time
we
discussed
this,
the
big
debate
was
whether
she
is
63
bit
numbers
and
have
the
server
do
magic
around
them
or
whether
to
use
a
longer
opaque
string
and
then
be
able
to
use
something
like
a
UUID
to
store
it.
I,
don't
know
whether
we
want
to
go
as
far
as
the
Microsoft
ActiveSync
protocol,
where
you
can
have
kilobytes
of
data.
That's
the
unique
ID
for
a
message.
F
J
Neil
Jenkins
again
came
up
there
strings
and
I
think
definitely
want
to
be
strings,
so
it
would
make
sense
to
me
if
that
could
be
the
same
across
both
more
easily.
F
J
B
G
B
F
F
F
Yeah
my
editor
hat
on
as
much
as
I
like
to
make
this
decision.
I
think
this
needs
a
discussion
of
the
working
group
of
so
there
will
be
some
iteration
on
things
to
hopefully,
what's
already
have
is
close
to
agree
agreeable
set
of
things
and
I
think
we
might
need
to
add
two
or
three
more
things,
little
things
so
like,
for
example,
sixty
four-bit
message
sizes
might
be
folded
into
it
right
away.
Just
because
it's
you
know
it's
nice
to
do
it.
If
we
are
doing
in
upgrade
anyway,
yeah.
G
G
B
B
B
G
Stefan
doesn't
step
up
to
the
speaker,
queue
I,
don't
know,
but
he
posted
I
will
channel
him
from
jabber.
Maybe
sieve
email
address,
internationalization,
savaris
RFC
predates
much
of
the
e
aĆ
work
possible
topic.
This
working
group
could
address
and
then
Ken
Murchison,
who
also
appears
to
be
in
Miyako
and
isn't
getting
in
the
speaker.
Queue
says,
with
respect
to
severe
CC
Ned
freed
was
opposed
to
allowing
FCC
to
be
used
with
reject
because
you're
essentially
lying
about
the
disposition.
Is
this
worth
discussing?
I.
F
B
C
F
Ada,
director
hat
on
I
need
to
double
check
whether
it's
within
charter
scope,
yeah
person,
I,
think
it's
a
good
thing
too
right
right
up
anyway,
so
write
it
up
and
we'll
decide
whether
it's
in
scope
for
the
working
group,
whether
we
want
to
do
a
small
tweak
to
the
Charter
or
just
process
it
as
individually
so
I
think
that's.
We.
B
F
B
H
B
H
G
But
do
we
want
to
address
it?
Do
we
have
the
knowledge
to
do
it
here?
I
see
John
is
on
Jabbar
or
is
on
Medeco.
So
there's
John
and
me
I,
don't
know
who
else
here
is
very
familiar
with
the
AI
but
John
John
yeah
and
John
and
Pete
in
the
room
so
yeah
I
guess
we
have
a
critical
mass
of
people
with
EA
I
clue?
Yes,
we
should
definitely
have
a
look
at
it,
but
not
until
we
deal
with
the
rest
of
the
dollar.
Okay,.