►
From YouTube: IETF97-NVO3-20161116-1330
Description
NVO3 meeting session at IETF97
2016/11/16 1330
B
B
A
A
A
Right
I
want
to
talk
a
little
bit
about
the
meeting
logistics
first
up,
so
the
first
40
minutes
or
so
will
run
like
a
normal,
normal
IDF
working
group
meeting.
So
we
have
a
few
short
presentations
during
that
time.
The
final
50
minutes
will
be
taken
up
with
some
round
round
table
discussion
sessions.
We
don't
have
any
round
tables,
unfortunately,
but
I've.
So
some
topics
of
importance
to
the
working
group.
We
have
some
big
flip
charts
that
will
bring
out
we're,
not
sure
sure,
yet
exactly
how
to
to
best
run
this
session.
A
A
A
Okay
milestones,
so
we
need
to
update
the
milestones.
These
are
the
milestone,
proposed,
much
changes
to
the
milestones
that
we
discussed
in
the
virtual
interim
meeting
a
couple
of
weeks
ago,
and
if
there
are
no
comments
on
these,
then
we'll
make
the
changes
after
this
ITF
I
guess.
The
most
major
change
is
to
remove
the
security
requirements
milestone
because
I
think
those
consensus
in
the
working
group
to
split
security
requirements
and
the
implications
for
security
into
the
individual
solution
drafts
and
address
them
in
assertions
drafts
as
part
of
their
security
considerations.
A
A
Yeah
we
had
a
virtual
interim
meeting
on
the
twenty-sixth
of
October,
and
that
was
primarily
around
discussing
the
next
state
steps
in
the
data
plane
design
and
how
we
were
going
to
progress.
The
current
situation,
where
we
have
three
data
plane,
encapsulation
drafts,
with
very
little
technical
progress
being
made
on
on
each
one
of
them.
A
So
we've
drawn
to
the
design
team
to
take
one
of
these
three
three
existing
end
caps
and
enhance
it
to
address
concerns
that
were
discussed
on
the
list.
We
be
posted.
Some
questions
to
the
list
about
people
could
post
their
technical
concerns
about
each
of
those
three
drafts
and
the
output
of
that
will
be
a
standard
track
draft
for
adoption
by
the
working
group.
A
A
A
We
have
a
set
of
requirements
drafts.
I
think,
as
we've
stated
in
numerous
times
in
the
past,
we
plan
to
regresar
requirements
in
parallel
with
any
applicable
solutions,
rather
than
publishing
them
first.
So
if
there's
interesting
in
publishing
these,
you
know
when,
when
the
when
any
solutions
are
published,
that's
that's
fine,
but
we
won't
push
the
working
group
to
to
push
those
out
any
earlier
than
that.
A
We
have
a
couple
of
drafts
that
have
gone
through
last
call
and
we
really
need
to
send
those
to
earlier
so
I'm
afraid,
that's
as
myself
and
Sam
that
are
tasked
with
doing
the
write
ups
that
there's
the
multicast
framework
and
the
use
cases
draft.
So
we
will
we
promise
to
get
these
done
after
after
this
I
GF
yeah.
A
Okay,
finally,
roundtable
session,
so
after
we've
had
the
three
presentations
this
afternoon,
we
will.
What
we're
going
to
do
is
bring
out
some
flip
charts
and
we
have
some
facilitators
who
will
help
us.
What
we'd
like
to
do
is
to
break
up
into
groups
and
to
discuss
these.
These
three
topics
so
Pat
and
Greg
and
Benson
kindly
offered
to
help
facilitate
these
sessions,
and
we've
broken
this
down
into
three
high-level
topics:
OEM
control,
plane
and
data
plane.
A
All
kind
of
visibility
is
required,
end-to-end
in
the
in
the
MV
03
architecture
that
so
that's
at
all
points
in
points
and
end
points
in
the
architecture,
the
control
plane.
What
kind
of
standardization
worked?
We
really
need
to
do
in
the
DMV
to
mva
control,
plane,
a
management
plane
and
one
of
the
protocol
options,
since
there
hasn't
been
a
huge
amount
of
discussion
around
what
our
protocol
options
really
are
for
some
time
in
the
working
group,
what's
needed
from
young
models
versus
dynamic
control
protocols.
A
Now
there
are
also
some
questions
around
the
use
of
a
VPN
together
with
VX
LAN
and
the
implications
of
that
on
om
or
the
suitability
of
a
VPN
versus
centralized
control
planes
and
so
on
on
will
be
posted
to
the
list.
So
questions
like
that
could
be
used
to
just
hit
the
discussion.
Finally
data
plane,
so
we
would
like
to
you
know
there
was
a
lot
of
discussion
on
the
list
on
the
the
extensions
that
might
be
needed
for
an
env
03
encapsulation.
A
A
You
know
the
visibility
of
these
and
impact
of
these
on
nodes
in
the
network,
elements
in
the
network,
endpoints
and
midpoints,
and
what
kind
of
parsing
is
required
and
processing
is
required
at
those
points
for
the
encapsulation
and
the
impact
of
having
potentially
large
large
different
numbers
of
options
for
extensibility
in
the
encapsulation
on
implementation
so
likes,
you
think
about
really
what
the
what's
really
required,
rather
not
really
a
lengthy
to
wishlist
trying
to
narrow
this
down
a
bit
and
again
that
topics
covered
in
some
of
the
detailed
questions
on
the
on
the
list.
Okay,.
B
C
Pat
Taylor,
with
my
chair
of
the
I
Triple
E
802
dot,
one
data
center,
bridging
group
hat
on
okay,
so
we've
got
a
draft.
It's
a
very
early
draft.
Please
understand
that
when
you
look
at
it,
but
because,
basically,
what
we're
doing
is
adding
extending
our
existing
TL
v's
to
cover
the
the
needs
of
of
MV
03.
C
We
really
felt
we
needed
early
feedback
on
whether
we've
got
the
right
fields
on
and
and
and
whether
that
looks
like
that's
going
to
fill
the
need,
whether
we
need
to
adjust
anything
so
we're
making
this
available.
It's
a
point
0
for
draft.
It's
a
task
group
draft.
It's
not
for
working
group,
bad,
it's
not
considered
complete
or
so.
C
C
If
you
would
please
ask
your
chair
for
for
the
password
and
use
your
name,
we
don't
want
that
to
be
out
on
the
public
internet,
so
we
can't
send
it
on
the
reflector,
so
it
has
to
be
handled
via
emails
and
it's
it's
an
amendment
to
I
triple
a
standard,
802
dot1q
2014!
That's
that's!
Where
you'll
find
the
base
text
that
it's
amending
and
when
our
standards
have
been
out
for
at
least
six
months,
they're
available
for
free
from
on
the
get
802
website.
C
Our
editors
weren't
able
to
find
a
port
names
for
those
so
for
for
that
we
have
kind
of
special
names
for
all
our
ports,
so
we
can
say
it's
the
sport
of
that
portent.
With
the
NV
e
t,
MBE
and
NM
v,
we
didn't,
we
didn't
see
all
of
those
defined
so
we'll
be
working
on
the
terminology
and
trying
to
get
it.
So
it's
as
equivalent
as
possible,
though
it's
probably
not
possible
to
get
it
perfectly
equivalent,
but
just
so
we
can
describe
how
this
this
this
tlv
is
used.
C
C
D
We've
done
some
editorial
changes.
We
change
terminology,
because
what
is
proposed
in
the
document
to
use
a
mac
for
the
inner
and
ethernet
frame
and
first
it
was
referred
as
a
well-known
which
is
probably
not
the
best
term
and
because
we
are
requesting
iono
to
allocate
it
so
now
it's
referred
as
dedicated
mac.
D
Len
BFD
/,
v
expand
and
then
the
excellent
GP
will
be
a
discussion
for
another
document,
whether
it
be
a
separate
document
or
the
document
that
discusses
use
of
VFD
in
NV
03,
and
with
that
we
can
go
to
the
next
slide,
which
is
a
very
standard.
We
welcome
reviews,
comments
and
I
asked
chairs
in
the
working
group.
Consider
adoption
of
this
document.
Ok,.
A
A
Any
version
of
the
document,
actually
there
maybe
raise
your
hands.
If
you
read
one
of
the
last
couple
of
provisions
of
the
document,
ok,
then
you
got
two
or
three
people
for
I
am
I.
Think
it'd
be
good
to
get
some
more
more
review
of
the
document
on
the
list.
So
well
again
will
a
poster
a
note
to
the
list.
D
E
E
This
is
also
a
bunion
loader
and
24.
So
on
each
other,
like
configure
judge,
you
wish
in
protocol
for
the
West
nangi
side,
so
we
were
method
to
when
I
unto
you
I,
and
the
Nationals
anyway
changes
the
operation
of
the
regional
state.
So
next
up
eight
and
I'm
from
the
Chinese
from
the
changes
from
0
to
0,
1,
202
where'd,
you
find
the
control
panel
and
we
define
just
etiquette
lesson
antenna
for
in
20,
Jarrett
or
version,
and
we
also
define
the
operational
state.
E
So
next
page-
and
this
is
a
current
event
on
configuration
where
we
have
been
a
model
and
the
telnet
were
shut
down
network
container,
each
other
Ginobili,
neighbor
and
Western
an
instance
with
happy
instance,
and
instead
he
wears
Montana
and
European
instance
and
return
estate
group
for
pants.
So
we
were,
we
were
introduced
to
this
content
container
one
by
one.
Next
thanks.
E
So
this
is
a
Western,
an
instance
configuration
we
were
configured
to
Ginobili
enable,
and
we
will
have
the
new
lesson
when
an
instance
and
the
care
with
the
wealth
nonsense
is
the
Western,
an
ID
I
know.
We
also
have
the
description.
Noda
under
I
know
unique
asset
rope
and
the
feather
no
way
I
are
here
noda.
So
this
is
a
verse,
9
sensor.
Confrontation
nesa
is
a
weight
with
HEPA
with
heavy
instance,
so
wait
happened.
E
We
also
defined
nice
level
with
heavy
instance
on
okay,
with
having
instances,
though
we'd
have
ID,
and
we
also
have
a
deal
with
have
named
a
social
instil
a
social
interface
and
the
multicast
the
IP,
and
though
we
also
defined
that
you
know
when
I
hand
the
model
we
were
defendant,
johanna
model
georgette
would
have
silver
on
the
model
I'm
on.
We
also
have
the
unfinished
Europe
and
the
West
now
ID,
so
just
usually
afford
to
wait.
Happy
instance
with
two
abandoned
the
last
night
I
instance.
E
So
next
step
next
is
the
West
nine
control
pranay.
So
with
with
your
fan
too
or
would
have
a
control
panel
when
is
the
photostat
ago
was
an
internal
for
the
West.
None
was
that
here,
where
Stan?
Oh,
we
were
defender,
then
we
were
usually
slow.
Who
know
the
two
defenders
tell
her
western
antenna
and
decay.
Is
that
ten
idea
under
them?
We
defend
the
Tanner
name
and
address
family,
so
we
issue
the
own
support,
ipv4
and
ipv6
leases
for
that
kind
of
button.
D
E
So
so
you
have
olivium.
Protocol
is
used
to
for
the
last
90
set
decided
to
me
in
configure
editor
as
up
here
pipian
wrong.
She
wrote
her,
so
you
can
see
is
added
this
away,
should
augment
that
you
will
be
important,
so
I
I
love
the
real
with
you.
So
maybe
our
discuss
with
you
within
him
and
the
argument
that
the
configuration
of
the
elation
parameters
yeah
so.
G
You
see
my
way
for
photos.
The
VX
9200
this
we
type
somewhere
need
to
specify
this
empty
you.
What
the
the
maximum
the
frame
you
need
and
also
somewhere
need
a
specified
there's
a
ton
of
security.
What's
the
code
here,
you
are
supported
on
a
makyo
supposedly
for
this
color
I'm,
using
that
the
I
set
yeah.
So.
E
Thank
you
so
for
your
avian
we
were
augmented
to
awaken
and
moto.
So,
okay
next-
and
this
is
always
my
operations
data,
so
we
defend
her
to
show
the
lens
Nintendo
on,
so
we
were
shoot,
look,
I,
p,
remote,
IP
and
so
tan
idea
and
or
some
soon,
some
some
premiere
literal,
the
tannot
status
here
status
and
the
way
I
Stannis
so
so,
okay,
next,
okay.
So
this
is
my
reputation
for
topic.
So
can
we,
however
George
it,
and
so
this
is
a
third
hand
to
Virginia.
So
oh
come
on
our
walk,
to--for
doffing!
Oh.
A
Right
now
we're
going
to
move
on
to
the
to
the
discussion
roundtable
discussion
sessions,
so
this
is
this:
is
the
list
of
topics
oh
I'll
get
the
flip
charts
out
well,
I
suggest,
as
we
do
maybe
over
in
that
corner
over
there
by
Benson
on
that
side
would
do
control
plane
this
side
here?
Maybe
data
plane,
then
at
the
back
will
do
OEM.
H
So,
while
you're
all
putting
away
your
laptops
and
getting
up
to
move
to
where
the
roundtable
discussion
you
are
most
fascinated
by
is,
let
me
try
and
inject
some
energy
into
the
room,
because
that's
part
of
the
point
of
having
an
awesome
technical
discussion
in
person
where
we
can
do
high
bandwidth.
So
we're
going
to
have
three
roundtable
discussions,
one
as
he
said
on
control,
control,
plane,
data,
plane
and
OEM.
We've
got
some
detailed
questions
that
were
sent
out
to
the
list.
H
If
there
are
a
lot
of
people
interested
in
one
particular
topic,
that's
awesome
and
we
can
break
it
into
smaller
groups
or
facilitators
and
matthew
sam,
and
I
will
be
wandering
around
to
encourage
the
discussion.
Afraid
there's
not
going
to
be
a
lot
of
email
reading
this
time.
So
please
move
along
to
the
corner,
sharing
most
interested
in,
and
thank
you
for
coming.