►
From YouTube: IETF98-CCAMP-20170328-1450
Description
CCAMP meeting session at IETF98
2017/03/28 1450
A
A
B
B
So
this
time,
actually
we
have
very
busy
agenda
so
on
or
the
chairs
are
slot.
We
only
have
five
minutes,
so
I
would
go
through
some
general
information
where
quickly
and
so
for
the
Lots.
Where
information
I
can
you
know
it's
very,
very
and
its
usual?
We
have
the
you
know,
audio,
recording,
so
I,
please
speak
in
front
of
the
mic
and
state
your
name
before
speaking,
and
also
you
know
on
our
secretary
is
not
here
and
so
on.
It
will
be
appreciated
if
anyone
it
takes
a
minute
slowly
span.
B
Ok,
thank
you
and
we
also.
We
are
monitored
gem
balloon
to
see.
If
there
are
some
comments
from
the
gym
balloon
sessions.
We
have
two
sessions
at
this
time,
so
on
the
first
wine
stickam
only
and
the
second
one,
it's
a
joint
session.
Now
it's
our
MPs
and
the
peace
and
the
PCE.
What
includes-
and
it
will
be
on
friday
our
morning
so
and
also
you
can
get
the
slides
from
the
link.
B
B
C
D
C
C
Sent
to
the
iesg
the
ospf
available
draft
and
it
was
sent
back
to
the
working
group
because
we
decided
not
to
do
a
specific
encoding
for
that
document
of
what
we
decided
that
we
have
it
in
a
more
generalized
way.
We
submitted
the
documenter
to
the
kids
working
Luca.
We
asked
if
it
was
possible
to
have
the
first
part
of
that
document.
C
C
Working
group
/
drafts-
we
have
three
documents,
are
being
discussed
the
day
and
a
number
of
documents
that
they
will
not
be
disgusted.
We
received
the
Sun
updates
on
the
Middle
East,
but
and
just
summarize
them
here
so
the
flex
agreed
ospf
is
in
the
attic
of
you.
The
document
is
done,
roped
up
with
just
a
matter
of
doing
the
right
after
we
needed
to
take
a
decision
on
out
progress.
The
LMP
extensions
for
four
tracks
agreed.
C
The
document
has
been
around
for
awhile,
but
there
was
not
be
impressed
with
a
correctly
remember
from
the
last
meeting
on
the
document.
So
we
need
to
decide
how
to
progress
that
and
ospf
availability
extension
is
the
document
I
was
speaking
about
before.
It's
ready
to
move
forward
together
with
this
companion
document.
In
a
tease,
they
generalize
the
SCSI
extensions,
yeah
rsvp-te
bandwidth
availability
is
a
companion
document
of
the
u.s.
pfg
extensions.
C
It's
basically
stable
and
is
ready
to
move
to
move
on
after
the
USB
ft
is
ready,
and
then
we
have
the
dub
usana
impedimenta
wearing
for
model.
It
was
the
reason
recently
refreshed,
but
we
didn't
get
them
and
much
discussion
on
the
on
the
mini
vista.
Recently,
I
don't
know
if
any
of
the
authors
who
would
like
to
provide
the
shot
up
data-
maybe
you
know
who
was
the
editor
giovanni
gabrieli
run
the
VL?
Maybe
you
you
can
give
us
a
short
update
on
the
document.
E
F
So
good
afternoon
my
name
is
Judy,
cocoon
sadocha
telecom.
So
this
is
the
update
of
the
framework
document
for
control
and
management
of
signal
channel
optical
interfaces.
I
think
motivation
is
quite
clear.
We
presented
this
document
many
times
here
at
sea
camp.
So,
first
of
all,
what
we
want
to
achieve
is
interoperability,
and
for
that
kind
of
things
we
need
to
exchange
and
define
a
common
set
of
parameters
that
we
can
use
in
that
case,
and
the
second
topic
that
we
want
to
address
here
is
the
better
interworking
between
the
layers.
F
So
that
means
that
the
optical
and
the
transport
layer
yeah
could
be
work
more
efficient
in
a
more
efficient
manner
than
today,
so
that
we
addressed
here
in
this
document
and
the
scope.
I
present
it
many
times
as
well
as
on
requirements
and
use
cases.
We
described
a
lot
of
things
here
in
lot
of
use
cases,
and
this
document
should
be
as
well
a
guidance
draft
for
two
other
documents
that
are
mentioned
here
on
this
lights.
That.
F
A
F
So
if
we
look
on
this
new
version
04,
then
we
have
the
following
things.
So
we
update
the
DD
requirements.
Section
addressed
the
comments
of
the
chairs
and
yet
did
a
lot
of
rephrasing
and
error.
Correction
and
I
deleted
some
text
as
well.
That
is
not
really
necessary
and
helpful.
Yeah,
that's
what
we
did
and
yeah.
We
think
the
document
is
quite
stable
and
we
can
go
for
working
group.
Last
port.
C
Eat
I
really
like
that
they
removed
unnecessary
texture
very
much,
okay
and
well
actually
I.
Had
the
review
of
the
texture.
I
have
some
minor
comments
that
my
opinion
can
be
addressed
during
their
working
for
a
stroller
I,
don't
ever
and
eat
it.
Let's
see,
but
does
anyone
have
any
concern
with
moving
at
a
word
document
that
was
the
last
caller.
C
H
H
H
Yeah
and
then
we
kind
of
clean
up
a
node
attribute
pointing
to
the
right
augmentation,
because
the
problem
of
this
is
this
is
augmentation
model
from
the
apology
model
and
then
they
kind
of
my
great
themselves
to
augment
from
general
topology
model.
So
this
time
we
up
to
date
may
come
up
to
dated
augmentation
reference
and
then
again
added
operational
state
for
loaded
sugar
container
and
then
once
we
publish
this,
we
passed
the
PM
check.
H
But
later
we
were
informed
by
young
doctors
that
something
failed,
and
then
we
noticed
that
connectivity
made
tricks
from
topology
model,
they
change
name
to
connectivity,
matrices
and
then
they
have
connectivity
matrix.
So
I
was
told
that
we
need
to
change
to
make
sure
that
this
has
p.m.
test.
So
that's
something
that
we
are
going
to
do
in
the
next
update.
Hopefully
a
topology
will
be
stabilized
and
then
I
think
we.
Yes,
we
are
not
going
to
have
this
kind
of
problem.
C
Have
one
which
is
video
I,
don't
know
if
you
follow
the
latest
discussion
on
the
relationship
between
a
day,
I
forest
ecology
and
the
de
quito
politic.
The
fact
that
the
thing,
sir,
could
change
now
good
the
exchange
in
the
relationship
between
the
two
models
at
the
impact,
sir,
on
this
document
or
not.
H
H
H
Yeah
I
think
this
is
motivation
is
basically
we
have
technologies
specific
model.
This
one
addresses
flux
great.
We
have
generic
model,
I
tourettes
model
and
city
and
Douglas
and
young
model,
and
this
one
basically
provide
LexA
grade
based
on
76
98
and
it
extends
from
existing
generic
young
model.
What
that
means
is
a
theater
policy
model.
H
There
are
two
self
models
within
the
draft.
One
is
about
a
flexgrid
topology
model
and
the
other
needs
a
media
channel
model.
The
authors
made
a
decision
to
separate
into
two
young
draft
on
the
next
revision,
because
one
is
a
topology
obstruction.
The
other
one
is
tunnel
model,
so
you
don't
want
to
put
that
into
one
draft.
H
So
it's
going
to
be
two
separate
model
into
two
separate
draft
and
both
models
are
implemented
in
young
one,
that
one
and-
and
actually
this
will
surpass
the
pr
verification,
but
because
of
connectivity,
made
tricks
a
change
in
the
topology
model.
It
fails
again,
so
we
have
to
fix
that
in
the
the
later
revision.
H
Through
there
are,
you
know,
a
few
things
here,
future
work
we
are
going
to
separate
a
media
channel
into
augmentation
of
the
eternal
model
in
the
next
revision
is
a
separate
draft,
and
I
think
one
of
the
comments
from
d2
I
believe
he
want
to
use
application
code
instead
of
specific
modulation,
type
correct
yeah,
so
that
is
actually
consistent
with
the
CTN
working
group
in
gentle.
It's
time
to
sew
this
going
to
be
fixed
in
the
later
revision.
Weerakoon
0
is
the
problem
and
there's
one
more.
H
You
know
we
are
going
to
define
single
operational
model
actually
bit
for
occupational
transponders.
Instead
of
you
know,
making
complete
list
here,
we're
going
to
take
similar
to
open
config
approach
and,
as
I
said,
we're
going
to
split
into
two
draft,
and
although
this
is
first
time
we
present,
this
is
already
version.
5
and
I
know.
Some
of
you
have
read
and
I
would
ask
for
working
group
adoption,
because
this
is
important
extension
because
of
importance
of
flux,
great
work.
G
H
I
think
that's
some
proprietary
terms,
you're
going
to
take
it
out.
Okay,
yeah!
It's
not
I
to
Utley
defined
start
writing
some
a
European
Union.
This
is
actually
outcome
of
you
European
Union
research,
and
they
want
to
explore
that
with
that
particular
vendor
I
believe.
But
it's
a
proprietary
stuff,
yeah
I,
the.
J
J
H
K
H
H
K
J
So,
coming
back
to
the
argument
before
I
think
it
was
basically
responding
with
litter
to
divergent
things,
so
the
current
ideas
parents
do
not
support
application
codes
for
anything
which
is
beyond
10,
geek,
direct
detection
and,
if
T
or
her
gigahertz.
So
this
one
is
future-looking.
It
goes
to
a
flexgrid
but
you're,
saying:
okay,
we
are
using
the
application
codes
from
here
in
order
to
do
that.
So
what.
H
Does
that
mean?
No,
that's
not
my
point.
You
know.
Application
code
is
specific.
The
product
of
I
Tiote
yeah,
so
we
said
we're
going
to
add
application
code.
That
means
we
are
limited
to
whatever
is
defined,
which
is
50
gigahertz,
another
gigahertz,
but
not
flex
rate
yeah,
some
probably
our
application
code,
the
right
places
SS
on
young
model-
and
here
you
know
it
that
can
be
done
because
we
share
the
two
draft.
But
this
is
not
something
that
I
can
answer.
This
is
alone.
E
I
K
C
G
Dieter
again,
I
actually
commented
or
send
a
comment
to
the
sea
camp
mailing
list
on
this
draft,
where
I
was
proposing
that
we
should
follow
the
same
approach
that
open
config
is
using
in
their
young
models.
Instead
of
defining
a
long
list
of
transponder
characteristics,
I
think
they
defined
an
operational
mode,
and
this
allows
and
I
think
we
have
to
respect
that.
K
My
comment
was
that
basically,
it
is
would
be
very
good
to
look
into
what
other
people
are
doing
in
this
layer.
Okay,
so
open
config
'it's,
it's
one
thing
in
my
personal
preference:
it's
it's
a
better
way
to
do
that
open
the
rhythm,
but
nothing
precludes
also
to
look
into
open
the
rhythm
and
also
take
whatever
I.
If
I
you
find
it
useful
I
see
mindset
to
put
it
there
right.
So
basically
it
is
very
simple
to
say
you
know,
you
know
we'll
ignore
everyone
and
we
have
like
all
the
expertise.
L
Deborah
venis
ad:
this
is
the
current
problem.
We
have
that
often
we're
doing
work
that
I
to
hasn't
actually
standardized
its
mother's
and
of
course
we
don't
want
to
wait
for
the
long
window
of
time.
So
we
can
continue
to
progress.
The
document
and
the
chairs
could
have
answered
this
I
think
it's
a
we've
done
this
many
times
over
and
who
should
blaze
on
with
I
to
to
find
out
the
latest
status
and
if
it
seems
really
early
that
they're
not
ready.
L
L
B
A
guy
have
one
file
on
comment
to
the
OC
I.
Think
the
authors
could
double-check.
Are
you
frustrated
TT
and
young
models
you
to
augment
te
topology
all
covers
an
apology,
because
I
think
actually
on
this
fresh
grade
has
much
closer
relationship
with
stuff
some
rather
than
our
generic
collagen
right,
because
we
can
think
that
we
can
treat
the
sixth
grade
at
kind
of
special
case
of
that's
great
yeah.
M
Hello,
everyone
and
I'm
naming
from
poway
so
for
the
next
to
a
presentation
ever
give
update
to
just
place
a
framework
for
management
and
control
of
microwave
and
also
millimeter
wave
interface
parameters.
So
here's
our
author
list
of
anomalous
filled
actually
I,
don't
have
March
update
on
this
framework
draft
and
the
draft
has
just
been
adopted
by
the
working
group
in
last
December.
So
currently,
there's
no
open
topics
for
this
frame
drop,
and
so
our
design
team
short
set
up.
M
The
framework
dropped
is
already
done,
and
so
we
would
like
to
are
thinking
about.
We
could
move
it
towards
the
last
hope
and
another
quantity
that
we
are
I
will
further
tvoei
I
developed
the
young
models
and
we
were
based
on
what
hits
defined
in
this
framework.
Drought
and
we
didn't
receive
any
further
back
stance
adoption.
M
So
this
is
the
current
status
under
the
next
step
for
the
framework
draft
and
if
no
further
comments-
and
we
moved
to
the
next
one-
which
is
our
are
young
draft,
and
so
this
young
dropped
first
of
all
an
overview
just
a
several
hour
key
points.
The
first
one
is
that
we
follow
the
framework
which
is
just
mentioning
in
the
first
presentation,
and
another
point
is
that
it
will
argument
based
on
RC
1772
industry
and,
as
you
could
see,
gran
self
figure
on
the
top
right.
Yes,
L.
M
Another
point
is
that,
when
we're
developing
this
young
model,
we
take
a
two
important
inputs:
we're
in
the
fronds
are
draft
to
our
bug,
as
they
can
microwave
brick
building
and
that's
when
it's
the
only
f
microwave
model.
So
we
were
first
discussed
on
on
these
two
models
in
the
later
side
and
on
the
arm.
Baaton
baaton
are
right.
M
It's
just
two
layers
of
the
microwave
functions,
and
another
point
is
that
here
is
just
an
example:
you
don't
have
have
to
be
to
carriage
and
measuring
Easton
at
Winston's,
and
you
could
you
just
have
a
one
al
khair
recommendation,
so
update
fronts
are
0
0
and
we
have
a
new
coercer
from
NEC
koji
and
we
have
competitors
of
microwave
Yankees
a
model
because
in
the
first
region
we
just
defined
as
a
young
model
photo
gallery
termination
configuration
and
in
this
model.
In
this
version
we
have
completed
also
our
mr.
M
olympia
part,
which
includes
the
TDM
connection,
our
chicken
Fagan
state
and
also
city
states,
and
also
some
protection
are
expensive
and
my
mo
and
this
young
model
has
successfully
passed
the
PDM
validation,
and
so
the
right
part
is
just
a
arm.
Some
examples,
fronts
are
young
model,
which
is
this
just
shows
are
carried
him
nation
and
status,
and
another
con
is
that
in
the
latest
variety
of
general-
and
we
have
article
20
to
give
our
progress
and
what's
been
going
on
on
this
work.
It's
a
it.
Could
you
check
about
this
web
link.
M
Mistress
is
just
to
give
a
brief
example
on
how
to
use
the
model,
because
we
think
is.
This
is
quite
useful
when
we
are
developing
the
model
and
harris
shows
are
very
the
simple.
For
example,
the
left
one.
It's
sorry
left,
who
is
just
showing
from
the
microwave
note
of
view,
and
you
could
say,
there's
a
rage,
functions
and
then
connected
to
the
radio
link
activation
and
then
further
to
camera
termination
and
under
all
right
part
right
side.
You
will
see
how
it
will
be
showing
our
front
the
interface
and
the
interface
days.
M
So
that's
that's.
The
are
below
the
slides
that
shows
up
our
attributes,
value
for
each
relative
attributes,
for
example
the
ethernet
interface.
The
only
read
relevance
to
this
is
the
lower
larry
interface
with
linkage.
Hoods
are
our
TA
and
in
at
the
arch
in
our
lair,
you
will
see
confit
with
its
Elaine
and
it's
a
mold
and
also
how
the
arrow
key
Winkler
ways
the
camera
termination
and
as
a
carrot,
carrot
emulation
there.
M
So,
basically,
the
key
point
is
that
poster
information
model
and
a
data
model,
it's
just
to
define
the
management
objects
purpose
for
different
purpose.
Usually
the
information
model
is
defined
in
our
conceptual
level,
and
while
there
are
data,
mano
SI
have
a
more
literal.
Detailed
and
another
point
is
that's
helped
with
so
many
implementation
details.
M
So
another
point
fact:
we
found
from
our
sister,
21
and
98
is
that
there's
statements,
that's
a
data
model.
It
basically
is
a
real
rendering
of
an
information
model.
I
think
this
too
artsy
explained
very
well:
what's
the
relationship
between
the
data
model
and
the
information
mode,
and
another
fact
is
that
when
we're
developing
this
young
data,
modeling
IDF,
we
take
the
reference
bran
COF
information
model
as
a
very
important
input.
M
So
this
transmitters
among
open
discussion,
we
received
recently
received
a
very
good
comments
from
locating
and
its
include
someone
missing
an
ism
to
be
clarified
and
some
to
be
updated.
So
we
will
continue
to
have
the
discussion
with
looking
at
and
also
we
will
try
to
have
the
discussion
among
the
disk
among
the
list,
and
the
further
step
is
that
we
would
like
to
add
some
technology-specific
alarms
in
rem
data
model
and
then
there's
some
questions.
M
We
would
like
to
hear
from
the
working
group
such
as
whether
it's
valuable
to
include
the
examples
just
of
being
shown
in
the
previous
slides
to
be
including
heart
of
the
draft
and,
for
example,
into
our
appt,
endings
or
annex
which
is
worse
well,
because
I
personally
think
it's
a
very
worthwhile
because
that
will
help
to
clarify
how
to
use
the
model.
And
another
point
is
that,
should
we
add
the
capability
into
the
model,
this
is
a
question
regarding
to,
for
example,
if
the
model
defined
function
with
a
B
and
C.
M
Well,
this
particular
Network
elements
only
can
support
a
be
so
sure.
The
network
elements
to
report
that
my
crib
lady
is
already
to
a
B
and
which
is
not
allowed
to
config
c
or
another
way
is
that
if
I
receive
the
configuration
on
the
function,
C
I
just
a
returning
with
an
arrow
message-
then
it's
done
so
I'm.
Not.
We
are
not
quite
sure
about
our
which
proach
will
be
better
and
then
stolen.
Topic
is
about
the
protection
part
when
you
include
the
protection
young
model
in
our
radio
link,
Yamato
but
I.
M
Think
just
some
generic
apart,
especially
for
this
protection.
So
we'll
put
a
wonder
to
know
if
there
is
a
further
interest
to
put
this
protection
into
a
even
more
general
dropped.
So
that's
the
open
discussion
and
the
next
step.
We
would
like
to
resolve
the
comments
and
also
are
those
open
discussions
and
well,
where
I
reserved
this
comments
and
questions
ago.
I
think
you
were
thinking
that
I,
it
will
be
better
to
ask
for
our
working
group.
M
B
C
C
Taking
into
account
of
what
is
being
done
in
not
internet
and
the
providing
us
with
the
clarification
between
the
information
model,
the
data
model,
what
is
done
here,
what
is
done
there,
but
this
is
really
pretty
good
number.
Thank
you
and
I
think
we
could
try
to
sense
the
temperature
see
if
the
working
group
is
interested
in
using
this
document
as
the
starting
point
for
a
for
the
working
group
work.
So,
first
of
all
how
many
of
you
have
read
the
draft.
C
O
O
What
is
the
charter
of
our
work
is
that
we
are
looking
around
all
the
many
IDF
young
models
that
are
being
developed
and
try
to
understand
whether
they
are
applicable
to
the
transport
network
and
whether
there
are
some
gaps
in
the
current
models
that
have
to
be
fixed
by
the
designers.
What
we
are
doing
now,
we
are
looking
at
some
use
cases,
so
we
have
to
discuss
the
with
many
people
from
also
outside,
as
do
so.
O
The
idea
is
to
understand
what
are
the
use
cases
that
we
need
to
turn
the
support
in
the
transport
network.
Take
into
account
many
workers
been
dying
on
fnn
EF
and
we
are
analyzing
how
and
we
started
to
analyze
how
the
existing
your
mothers
can
be
used
to
address
and
support
those
use
cases.
The
working
method
were
the
way
we
work
with
a
design
team.
A
list
where
we
exchanged
the
discussion
and
ideas
we
have
a
weekly
conference
calls
every
wednesday
at
3pm
european
time.
O
Sometimes
we
skip
based
on
the
content
and
we
have
a
github
area
where
we
track
documents,
input
material
minutes
and
open
issues.
What
we
have
done
so
far,
we
have
published
a
documentary
at
a
use
case
document
revision
number
one,
which
is
covering
the
description
of
one
use
case
with
a
single
domain
and
single
layer.
O
We
look
at
how
the
net
we
have
developed
an
example
of
a
reference
network
of
this
fat
and
how
this
network
can
be
controlled
and
which
type
we
have
assumed
some
topology
obstruction,
for
example,
that
for
a
single
network
the
pnc
can
provide
all
the
details
to
the
mdsc,
and
we
start
to
describe
a
few
executive
assistant
at
work
can
provide.
For
example,
the
idea
do
do
transit,
so
I
note
you
that
is
starting
and
ending
outside
of
our
network
and
test
across
our
network
or
EPL
or
other
trying
to
obtain
client
services.
O
O
We
want
to
discuss
something
about
the
multi-layer,
assess
a
multi-function
access
links
when
we
have
a
link
which
can
be
configured
as
an
10,
gigabit,
eternal
ink,
sm64,
o
or
o
TN,
depending
on
the
service
configuration,
and
we
have
a
other
use
cases
when
we
want
to
see
single
domain
a
multi-layer.
What
you
domain
single
layer,
a
multi-domain
multi-layer,
got
input
for
all
of
them
and
we
have
to
describe
all
of
them
and
we
have
to
prioritize
a
bit
since
huge
number
of
cases
that
we
have
to
consider.
O
We
started
also
to
do
some
analysis.
The
analysis
just
started,
so
we
have
no
any
drafts
ready
for
submission
so
far
and
we
have
analyzed
how
do
you,
transit
service
can
be
implemented
in
the
use
case?
Number
one
from
this
and
I
still
get
many
details,
comments
and
questions.
We
have
already
started
to
discuss
with
the
models
authors
of
the
T
tunnel
and
we
got
some
changes
to
the
T
tunnel
model
to
clarify
and
to
support
the
use
case,
and
the
next
steps
is.
O
We
have
still
many
open
issues
to
address,
so
we
want
to
address
all
of
them
and
we
want
to
complete
the
analysis
of
this
use
case
and
continue
the
analysis
of
the
other
use
cases
on
contribution
basis
and
okay.
This
is
a
quick
overview.
What
is
use
case
number
one.
We
have
a
network,
a
transport
network
which
is
provide
interconnection
for
different
routers,
and
we
assumed
that
we
have
a
transfer
PSC
exporting
via
a
transport
MPI
information
about
the
network
to
the
mdac
and
the
MDS
is
providing
a
p+
optical
coordination.
O
We
are
making
assumption
about.
We
are
a
really
sexy
mi.
There
is
an
app
empi,
but
this
is
out
of
scope
of
our
work.
We
have
just
assuming
that
something
is
happening,
but
we
don't
care
about
how
this
is
done,
because
it's
outside
of
our
stalker.
We
care
about
what
information
needs
to
carry
over
this
interface
and
the
example
of
the
audio
tonight
set
up.
O
So
we
have
a
ready
state
apology,
which
is
a
started
at
the
NPI
and
in
order
to
have
annoyed
you
that
starting
from
hotel
number
one
goes
through
the
number
three
and
transit
the
network.
From
this
in
English
and
egress
points,
we
need
to
create,
at
eternal
with
the
first
little
element
pointing
to
this
ftp
and
the
Last
Theorem
elements
wanted
to
like
this
ftp
and
we
and
that
that
would
be
a
segment
of
an
end-to-end
tunnel.
So
we
have
analyzed
the
Indy
case.
O
All
the
attributes
I
need
to
be
set
up,
these
lights,
I
will
go
very
quickly,
is
describing
all
the
elements
that
needs
to
be
provided
them
and
some
questions
that
we
got
them
and
we
have
a
law
allowing
a
set
of
open
issues
that
we
need
to
discuss.
Some
have
been
already
addressed,
but
this
one
are
still
pending.
So
when
we
look
at
the
euro
element,
Omar
Sandahl
af-,
1-1,
okay,
so
we
have
some
in
the
tunnel
mode
that
the
euro
is
saying
who
that
IDK
phys
ed
in
the
tito
polish.
O
We
don't
have
rooted
at
the
interface
ad.
So
how
do
we
get
this
information?
We
have
an
assumption,
the
Rueter
ID.
Isn't
he
know
that
the
energy
phys
ed
is
a
TTP
ID,
but
we
have
to
die
validate
that
with
the
authors
of
the
two
drafts.
We
have
some
discussion
about.
How
do
we
configure
the
ole
you
two
time
slots
on
the
assess
link,
so
whether
it
is
selected
by
the
NDS
see
whether
there
is
some
negotiation?
O
There
is
some
suggested
label
coming
up
from
the
from
the
PNC,
and
this
is
still
a
discussion
on
going
girl.
Then
that's
the
also
the
possibility
to
have
some
suggested
label
and
negotiation
depends
on
the
restaurant
operations.
When
you
create
a
tunnel
and
you
get
an
answer,
is
the
tunnel?
Okay?
Is
the
tunnel
already
set
up
or
is
just
your
request
is
accepted?
And
then
how
do
you
know
if
the
tunnel
has
been
set
up
or
not?
O
We
have
also
some
discussion
to
be
done
about
the
other
draft
on
the
transport
control,
not
young,
whether
it
is
applicable
to
all
various
cases
or
not
depends
also
on
applicability
on
cmin
mpi.
We
need
to
talk
with
the
authors
of
this
raft
and,
as
you
have
seen
when
we
start
documenting
the
how
the
model
is
used,
we
can
use
a
power
point
which
is
easy
to
write
them,
but
is
much
more
difficult
to
put
in
a
little
draft
doing
in
text.
But
text
is
complex
to
write
the
order
England.
O
So
we
would
like
to
see
some
tools
well
passer
and
this
ongoing
discussion
on
how
to
do
that.
And
then
we
have
a
some
issue
about
the
scope
that
we
got
a
question
whether
we
have
to
analyze
in
terms
of
analysis,
so
otherwise
do
llamadas.
Our
current
assumptions
that
the
use
cases
that
we
work
through
our
should
be
the
super
set
up
for
the
use
cases
from
all
day
as
the
AUSA.
But
the
analysis
should
be
focused
on
the
IDF
in
our
model,
since
we
are
in
IDF
and
of
course,
with
our
document
is
open.
O
So
we
appreciate
your
father's
do,
can
take
our
use
cases
and
analyze
their
Andhra
llamo
does
how
they
support.
They
use
the
superset
of
the
use
cases
that
we
have
and
then
what
document
analysis.
So
the
idea
now
is
to
have
a
different
graph
for
analysis
and
to
split
the
use
case,
which
is
independent
from
the
model.
From
the
analysis
that
is
saying
how
the
model
is
addressing
the
use
cases,
and
we
ever
got
a
question
about
the
tech,
not
just
specific
commendation,
and
we
we
have
seen
some
individual
drafts
of
OT
an
augmentation.
O
O
J
So
I
think
I
ever
goes
on
that's
an
email
on
the
floor
about
the
usage
of
of
layering
some.
Maybe
you
can
just
go
back
to
the
picture
with
the
road
and
over
there
that
one
yet,
so
I
think
there
was
something
let's
say:
lose
some
loose
wording,
at
least
on
the
email
but
layer.
So,
for
example,
if
you
look
at
this,
where
is
the
transponder?
The
next
picture
seems
to
assume
there's.
Responder
is
in
that
the
rectangle
boxes
in
the
middle
right.
The
previous
picture.
O
Assumption
here
is
that
the
oldies
I
wrote
you
cross,
connect
electrical
cross-connect,
oscillation
traffic
at
your
new
layer,
and
this
is
the
agency
ideal,
new
layer,
and
we
don't
see
in
our
use
case
in
this
case,
which
is
single
layer
yeah.
We
don't
want
to
control
the
Year
Zero,
which
is
below
the
later
on
which.
J
Is
fair
again
if
you
go
back
to
the
previous
one,
so
there's
there's
a
kind
of
a
mixture
of
saying
okay,
what
what
do
you
redefine
in
your
use
case
has
to
be
a
layer?
Is
it
a
kind
of
what
previously
has
been
settin
loosely
said
to
be
a
control
layer,
so
you
have
a
vm,
pls,
say
TDM
or
ODU?
Is
this
your
layer
you're
really
caring
about
it?
We
already
go,
let's
say
on
itu
layers
and
have
a
controller
for
each
individual.
O
J
O
Q
Hi
Lou
burger
you're
using
the
transport
MPI
as
the
reference
for
this.
Is
that
correct?
Yes,
this
one
yeah?
Okay,
so
where
you're
getting
your
requirements,
because
I
heard
you
talking
about
that,
there's
a
mismatch
in
some
models
versus
the
requirements.
So,
where
you're
getting
your
requirements,
he
said
that
you
needed.
You
said
no
tidy
for
something
else.
Oh
yeah.
O
Q
O
Yeah,
look
at
all
the
use
cases
and
we
say
well.
We
have
a
use
case
where
we
have
an
audio
network
which
is
providing
a
OT.
You
started,
we
have
an
end-to-end
owed,
you
from
puter
12
Rooter
tree,
which
has
to
cross
98
neural
network
am
so
so
the
end
to
end
audio
is
clearly
seen
by
the
MDS
see
because
the
MDS
see
controls
everything,
but
on
this
interface,
what
you
need
to
ask
is
in
audio
segments
that
is
entering
the
networker
from
this
point
and
leaving
the
network
from
this
point.
Q
I'll
get
there
to
say
so,
I'm
trying
to
figure
out
how
you
went
from
your
require
your
stated
requirements
to
worrying
about
something:
that's
pretty
low
level.
Without
that
larger
work
have
been
having
been
done.
So
I
guess
we
can
go
through
a
couple
things.
First
of
all,
there's
a
requirements
document
alright
for
actn.
Did
you
look
at
that?
Not
we.
O
O
Q
Q
Q
O
Don't
think
all
right,
we
have
not
fine
missing,
we
find
something
which
is
not
clear,
for
example,
for
example,
what
we
said.
We
noticed
that
when
you
look
at
the
tunnel
model,
the
euro
is
other
than
node
or
the
label.
So
and
then
we
read
the
clarification
that
we
have
to
put
you
you're
awesome
14.
They
know
the
more
for
the
node,
so
this
clarification
were
not
very
good.
We
didn't
know
that,
so
we
got
that
feedback
from
the
teet
apologize
versa,
and
we
are
continuing
on
doing
that
analysis
and
it
is
yeah.
Okay,.
Q
O
K
K
K
P
K
E
Good
morning
mr.
Bergeron
Betty
speaking
and
presenting
the
LMP
draft
Jeff
of
the
auto
first
of
all,
I
should
apologize
weedeater,
because
I
didn't
update
the
company
name
and
second,
because
data
actually
is
not
taking
part
of
the
text.
Interface,
LMP,
work
and
I
will
fix
a
bit
of
you.
So
the
consideration
for
this
to
draft
are
related
to
implemented
Olympic
protocol
and
define
all
the
parameters
that
an
interface
located
on
the
client
can
share.
With
the
with
the
network.
E
E
E
While
the
second
flex
interface,
LMP,
is
the
first
time
I'm
presenting
so
can
be
considered
as
a
0-0.
Here,
okay,
we
are
dealing
here
about
LMP
I,
just
to
state
to
clarify
NP
between
the
client
interface
that
are
on
on
located
on
Deck
on
the
external
of
DW
meter
in
d
WN
network
and
their
own
inkay
in
the
DWDM
interface
LMP.
We
have
defined
as
agree
in
the
last
ITF
meeting
to
manage
the
the.
E
Application
code
only
as
I
to
the
recommendation,
plus
Delta
power
and
the
current
input
power.
These
are
all
the
parameter
that
are
enough
to
let's
say,
tell
the
the
network
what
kind
of
interface
with
in
SS
wine
extension.
We
have
a
bunch
of
parameter
for
sake
of
time,
I!
Think
I,
don't
I,
don't
comment
all
those
parameters,
but
I
suggested
or
I
asked
you
to
look
at
them.
The
draft
that
is
an
experimental
draft
is
not
a
normative
and
give
us
feedback.
E
C
P
E
P
Ok,
what
is
the
problem
so
in
the
existing
G
709
version
2012?
It
actually
defines
the
otn
capabilities
and
the
signaling
and
routing
extensions
to
cover
that
are
already
specified
in
the
RFC's
mentioned
over
here
in
2016
version
of
the
g
709
beyond
100
G's
capabilities
or
otn
capabilities
are
introduced.
So
since
those
functions
are
not
addressed
from
the
routing
and
signaling
perspective,
so
here
I'll
be
talking
about
in
the
framework.
For
example,
what
are
those
new
requirements?
Are
new
capabilities
and
then
the
corresponding
routing
and
singling
extension
quickly.
P
So
I'm
not
going
to
go
through
this
all
the
gory
detail,
but
here
in
essentially
this
summarizes
some
of
the
new
capabilities
which
are
defined
in
g
7
a-9,
for
example,
OD
UC,
n
signal
beyond
100g
rate
and
the
corresponding
or
you
CN,
as
well
as
the
transport
of
the
OD
UC
n
over
flexo
in
turf,
is
mapping
of
different
these
signals
on
to
these
new
containers
and
if
another,
important
new
thing,
which
is
introduces
a
five
gig
granularity.
But
you
know
times
are
energy.
P
P
So,
okay,
so
in
the
framework
document,
we
also
list
some
of
the
use
cases.
If
you
remember
in
the
last
ITF
actually
I
think
you've
got
to
remember
so
some
of
the
use
attic
was
presented
there.
So
this
actually
extends
some
of
the
use
case.
The
list
we'd
like
to
actually
focus
to
take
a
look
and
give
a
comment:
if
there's
some
something
is
missing,
so
it
actually
talks
about
mix
of
different
otu
links,
the
traditional
otu
links
and
also
there's
a
multihop
concept.
P
Okay,
that's
scored
all
those
cases
and
based
on
those
use
cases,
we
think
the
solution
needs
to
be
des
all
those
use
cases.
When
the
solution
comes
up.
Please
take
a
look.
If
you
see
some
use
cases
incorrect,
give
us
a
feedback
or
something
is
you
know
when
you
need
to
add
more
using
its?
Let
us
know:
ok,
so
then
another
one
is
based
on
the
use.
Cases
actually
identifies
some
whatever
it
is
mean
what
solution
we
need
to
look
for.
So
some
of
the
things,
for
example,
is
from
the
routing
perspective.
P
We
need
to
be
able
to
advertise
the
encoding
type,
the
switching
and
determination
and
multiply
multiplexing
capabilities
for
this
new
links,
because
eventually
these
links
cannot
be
going
to
the
cat
topology
database,
and
then
you
need
to
make
a
path
computation
and
then,
from
the
signaling
perspective,
also
the
different
signal
types,
granularity,
l,
a
VPN
allocation
and
then
basically
also
the
reduced
reduced
rate
Flinx.
So
all
those
functionality,
the
signaling
solution-
should
be
able
to
address
okay,
keeping
all
these
implication
or
the
requirement
solution
of
primers
in
mind.
P
I'll
just
briefly
go
over
some
of
the
signaling
and
routing
extension.
What
we're
proposing
here?
Ok,
so
somebody
off
the
routing
extension.
So
as
we
just
mention
that
we
need
to
extend
the
developing
ospf
traffic
engineering
capabilities,
so
here,
for
example,
we
summarized,
as
captured
in
bullet
number
two,
then
we
need
to
extend,
for
example,
SC,
switching
capability,
specific
information
field
and
also
the
is
CD.
Ok,
these
these
this
message,
so
here
is
providing
a
some
brief.
P
C
P
Fine,
so
I
think
the
framework
I'm
covered,
I'm
just
going
to
quickly
flash
through
this
one
then
so
here
is
the
solution.
I'm
not
going
to
talk
about
it,
but
this
is
thus
eccentric.
People
can
look
in
the
draft
and
similarly,
for
the
say,
are
signaling.
There's
a
solution
proposed
and
then
short
of
time.
I'm
not
going
to
talk
here,
so
I'm
going
to
them
for
the
last
one.
So
if
there
any
comments,
yeah.
G
P
P
So
actually
I,
actually
maybe
I
can
just
just
since
you
asked
the
question,
so
you
see
this
built
at
TNS
field.
So
what
we're
saying
is
the
field
must
be
set
to
want
to
indicate
terminated
and
then
s
must
be
set
to
0
to
sit
non
switchable.
So
there's
some
example
shown
in
the
draft
and
also
in
the
slide.
We
actually
show
some
different
example
how
this
dl
we
will
be
used
for
different.
You
know
different
multiplexing
cases,
but
short
of
time,
I'm
not
going
over
it.
Also
in
the
graph.
They
are
covered,
John.
D
Sedlar
a
couple
of
comments
with
respect
to
it
not
being
a
switching
layer,
it's
not
clear
what
the
need
for
signal
type
assignment
is.
We
don't
have
a
signal
type
assignment
for
VMS
layer
and
SDH,
so
it's
not
clear.
They
need
here
like
to
see
that
developed
further
in
the
framework
draft
I.
Do
you
think
there
are
some
use
cases
for
it,
but
anyway
some
some
development
there
would
be
good.
Second,
is
there
is
a
restriction
on
the
number
of
TP
ends
allowed
per
link
I'm,
not
seeing
that
strongly
talked
about
in
the
draft
either.
D
D
D
Flexo
work
in
itu
hasn't
been
published,
yet
it's
still
work
in
progress,
so
we
need
to
coordinate,
make
certain.
We
don't
get
ahead
of
their
activities.
There.
Yes,
I,
agree,
it's
work.
That
needs
to
be
discussed
here,
but
it
might
be
good
to
actually
separate
the
extensions
for
that
just
so
we
can
get
ya.
P
P
I
do
to
use
yet
well
I
think
it's
quite
well.
They
actually
in
the
family.
You
right
in
the
framework
document
we
are
saying,
is
TBD
under
discussion,
but
I
think
it's
something
at
in
a
use
case.
We
need
to
actually
identify,
because
this
is
reuse
of
like
our
electrical
interfaces,
which
are
existing.
You
cannot
reuse
those
interfaces,
for
example,
for
the
audio,
see
and
enjoy
a
short
reach
right
right
under
so
yes,
so
no
I'll
send
my
comments
to
listen,
send.
D
J
It
is
good
and
I
pecially
was
my
comments
already
own
list,
so
I
find
the
framework
to
offer
you
well
written,
there's
only
one
use
case,
I
kind
of
amazing,
because
there
was
a
lot
of
work
here
related
to
protection.
Switching,
no
data
point
I'm,
just
recording
signaling
and
everything.
I
think
that
would
be
worth
to
be
added
as
well,
so
because
there
are
other
indications
based
on
the
new
layering
secretly
send
you
comes
on
the
list.
I
did.
N
Okay
good
afternoon,
everyone,
this
is
how
men
and
I'm
going
to
introduce
a
couple
of
through
Jesus
ml9
draft.
Also,
so,
basically,
we
will
have
one
framework
draft
and
one
signaling
exterior
work.
Actually,
the
other
routing,
if
they
can
work,
is
also
ready,
but
it's
not
on
the
agenda
at
this
time.
So
I
will
try
to
also
incorporate
the
some
of
the
content
of
this
presentation.
N
So
here
are
some
the
overview
of
the
history
draft,
actually,
the
Liberata,
based
on
the
refugee
definition
of
the
OT
o
CN
and
the
addition
5
of
2009
consider
about
the
beyond
100
people
data
plan,
and
we
assume
that
the
corresponding
control
plane
work
need
to
be
addressed
in
the
sea
camp
working
group
and
the
in
the
draft.
We
took
a
brief
review
of
what
is
going
on
for
Jesus
ml9
with
5
and
including
including
how
this
crime
signal
is
mapped
into
audio
CNN.
N
So
the
in
the
version
5
of
the
adidas
ml9,
the
new
scenes,
including
a
one
new
signal
type
that
is
audio
CN
and
there
is
also
a
separate
Magnus
out
you
see,
of
em,
which
is
not
a
integral
time
of
the
100-acre.
And
another
new
issue
is
a
new
skill
tree.
Sloth
final
energy
has
been
defined
as
the
five
pika
and
for
ODU
CN.
N
The
member
of
the
tributary
slot
is
always
tan,
hiep,
x,
n,
so
in
the
2009
version
5,
it
is
also
described
on
how
the
oto
seen
will
its
work
together
with
all
UK,
so
the
your
Lizzie,
the
client
signal
will
be:
firstly,
must
act
to
the
audio
k
and
then
carried
by
the
audio,
see
it
or
hear
it
see
it.
So
it
is
not
a
switching
for
the
OT
OSI
layer
and
it
will
always
go
to
the
audio
k.
First.
N
So,
by
analyzing
this
kind
of
features
we
try
to
address
this
kind
of
signaling
implications.
The
firsts
there
are
totally
five
issues.
We
need
to
address
you,
the
signal
extension.
The
first
one
is
to
support
the
New
York
signal
type
of
UCM.
We
will
add
a
new
signal
hype
and
second,
one
is
to
support
the
new
to
be
dressed
up
and
granularity,
which
is
five
people,
and
we
will
also
add
one
more
section
444
this
granularity.
N
The
third
one
is:
we
need
to
support
off
the
RSP
set
up
for
the
audio
seein
containers
and
though
we
are
going
to
extend
the
should
generalize
the
label
to
support
this,
and
we
will
also
extended
the
TPM
allocation
together
with
the
supporting
off
co,
toc
n/m
and
for
the
routing
implementation.
So
we
also
need
to
extend
the
highest
city
to
describe
to
you
how
to
express,
link
multiplexing
and
how
to
advertise
the
five
key
to
preserve
start
granularity
and
also
how
to
advertise
fee.
N
We
separate
out
your
CRM,
so
what
we
are
trying
to
give
an
open
discussion
here
is
I
think
we
need
to
first
confirm
with
all
the
experts
here
about
the
scope
cause
we
notice.
There
are
some
ongoing
works,
including
some
effects.
Oh
and
slacks
ethernet
some
kind
of
this
work,
which
are
highly
related,
wizard,
you
seein,
and
we
need
to
confirm
whether
this
kind
of
so
and
the
fact
eternity
is
even
in
the
scope
or
I'll
have
scope
of
this.
N
This
draft,
because
both
of
these
are
part
of
the
trees,
are
several
nine,
but
we
can
address
this
kind
of
work
separately.
You
separate
graphs,
and
the
second
issue
is
about
a
separate.
The
OTO
CNN
is
a
kind
of
appendix
so
which
can
be
included
or
okay
should
be
excluded
in
the
draft
and
for
the
use
case.
So
we
will
will
try
to
add
more
informative
use
case
according
to
the
decision
of
the
previous
Lascaux
discussion.
N
So
there
is
a
other
works,
that's
the
present
hit
by
iftikhar
and
we
are
trying
to
coordinate
and
work
together
with
our
other
property
and
try
to
convert
as
soon
as
possible.
After
that,
we
are
going
to
ask
for
a
preferred
option
and
we
can
then
dropped
for
a
single
thread
off
so
the
solution
rather
than
competition.
C
I
guess
most
of
the
comments
of
the
previous
event,
a
presentation
also
apply.
This
is
one
example
is
open
question
on
the
flex,
Oh
factor
that
needs
to
be
out
of
this
book
of
the
document.
Thank
you.
We
all
agree
with
happy.
I
would
suggest
also
to
keep
a
flexi
dammit,
which
has
a
scope
of
of
these
documents
and
the
address
it.
Maybe
in
another
conference,
yeah.
N
C
P
I
think
yeah
I
think
we
are
contested.
We
cannot
come
up
with
one
one
document
and
also
from
the
from
the
last
idea
meeting.
I
think
the
chairs
emphasize
the
solution.
So
that's
by
the
way.
That's
one
of
the
reason
we
kind
of
speed
it
up
this
solution,
part
because
it
was
emphasized
that
ok,
let's
not
worry,
less
less
worried
about
use
cases.
Let's
talk
about
the
solution,
so
that's
why
I
speeded
up
so,
but
we
are
alignment
whatever
the
strategy
we
need
to
take
here.
Yeah.
B
I
agree
actually
I
read
all
the
solutions.
Johnson
I
think
this
extension
quite
really
simple
and
straightforward.
Those
kind
of
solution
could
be
you
know,
based
on
on
Jesus,
I'm
on
my
way
straight
jobs
actually
to
find
find
both
Cheers.
So
I
think
actually
we
can
spend
more
time
on
the
solutions
and
not
spend
too
much
time
on
framework.
Here's.
K
P
C
A
E
There
is
something
in
G
872,
but
is
not
one
hundred
percent
clear
to
me
and
we
refer
also
the
existing
RFC
for
the
SSN,
so
the
76
98,
where
there
is
a
definition
of
a
media
channel
and
also
the
OTS
I
that
can
be
associated
to
the
subcarrier
and
also
this
worker
can
standard
the
signal
Inga
and
the
76
98
and
7690
7790
to
the
scope.
They.
E
Let's
say
the
reason
we
want
to
F
distension
is
because
between
the
client
interface
that
are
located
in
a
router
audience,
which
or
whatever
and
the
road
important,
we
might
have
a
single
channel
or
a
let's
say,
a
media
channel
that
is
populated
with
multiple
carriers.
How
we
can
signal
those
carriers
around
the
network
can
be
is
needed.
E
E
B
B
E
G
E
O
You
little
boozy
from
away
is
a
second
the
comment
about
why
what
we
are
doing
here
is
we
are
configuring
something,
but
we
have
still
don't
know
how
the
data
plane
can
interoperate.
As
far
as
understand
from
people
in
question
6
is
that
defining
the
optical
parameters
to
ensure
interoperability,
the
optical
a
list
is
not
an
easy
process,
so
we
are
going
too
fast,
but
we
are.
Are
we
going
to
the
right
direction
because
the
the
attributes
are
not
known
by.
O
E
E
O
R
Generic
just
trying
to
join
the
discussion
has
tell
you
what's
mentioning:
there
is
some
interoperability
appearing
at
least
when
you
split
the
line
on
the
transponders,
so
you
don't
have
full
interoperability
between
transponders,
but
alien
wheels
cases
are
becoming
mormon.
Common
on
this
is
typical,
has
written
a
drive
for
the
uni
meaning
between
the
transponder
on
the
line?
You
need
this
kind
of
work
to
start
the
the
progresses
so
starting
a
single
burner
with
experimental
is
a
way.
R
C
P
Yeah
so
I
think
this
is
good
enough,
so
I'm
just
going
to
give
us
a
status
update,
so
I'm
going
to
skip,
for
example,
what
what
is
Lexi
with
the
problem
just
give
us
status,
so
we
met
since
assault,
so
we
actually
identified.
These
are
the
things
which
needs
to
be
done
so,
for
example,
revised
abstract
review
the
use
case
event,
update
requirements,
provide
more
content
in
the
framework
and
architecture,
section
analyze
the
existing
solution
and
start
working
on
that
one
so
since
n.
So
this
is
what
had
happened
so
we
did
revise
the
abstract.
P
We
agree
on
the
use
cases
actually
and
work.
We
had
several
meetings,
including
one
conference,
call
and
a
lot
of
discussions
on
the
email,
and
we
have
added
information
on
the
framework.
Section,
publish
the
device
framework
as
version
2,
and
we
have
started
initial
discussion
on
the
existing
solutions
and
then
that's
where
we
are
so
we
are
following
what's
happening
in
other
s,
Toews
and
then
what
are
they
can
new
use?
Cases
like
you
know,
as
we
discuss
coming
up
you're
keeping
an
eye
on
those
and
what
are
the
next
steps?
P
So
the
next
step
is
released
to
start
focusing
on
the
solution
and
by
the
next
idea.
Hopefully
come
up
with
the
Rajah
billing
solution,
converged
consensus
solution
and
complete
the
architecture.
You
know,
framework
document
and
start
may
be
discussing
on
the
yank
yank
models
and
get
a
feedback.
Any
questions
comments
so
just
going
to
be
a
separate,
especially
when
you
have
people.