►
From YouTube: IETF108-CCAMP-20200728-1300
Description
CCAMP meeting session at IETF108
2020/07/28 1300
https://datatracker.ietf.org/meeting/108/proceedings/
A
A
Okay,
you
mean
okay,
let's
start
yeah,
yes,
okay,
perfect
so
good
morning,
good
afternoon
or
good
evening
to
all
of
you
so
welcome
to
our
sig
cam
session.
So
you
know.
Actually
this
is
our
second
online
second
walking
group
meeting.
I
mean
formal
working
group
picking
next,
please.
A
A
And
then
this
time
this
meeting
we
have
only
one
session
with
15
minutes.
So
this
is
quite
you
know
short
weekend
and
and
also
we
have
you
know,
a
plan
on
the
internal
meeting
in
the
future,
which
will
be
scheduled
in
september
and
in
this
interpreting.
A
A
So
this
agenda,
so
we
know
actually
this
meeting
is
quite
short
and
but
we
only
have
three
jobs
to
be
presented
for
discussion,
so
I
I
think
we
should
have.
You
know
enough
time
for
discussion
next.
A
And
you
know
on
this
time
we
are,
we
are
all
using
the
mid
echo.
So
please,
I
think
you
all
know
how
to
use
the
with
echoes
and
also
you
can
get
more
information
from
the
link.
But
there
are
some.
You
know
important
icons
that
you
should
be
aware.
For
example,
if
you
are
going
to
speak,
you
have
to
click
the
third
icon,
which
means
that
you
are
going
to
end
the
queue
to
speak,
because
you
know
for
the
online
meeting.
A
We
do
not
have
the
physical
micro
q,
but
we
have
the
virtual
virtual
mic
q.
So
in
this
way
we
can
keep
the
meeting
more
efficiently
and
also
we
have
a
kind
of
new
tool
which
is
about
harming
children.
A
So
if
we
are
going
to
polling
post
something,
I
think
we
can
use
the
harming
tool
and
then
we
can
see
how
many
people
are
support
or
object
to
something.
Yeah,
okay,
go
ahead.
A
A
A
A
So
this
very
important
you
know
reminder
about
ipr
process.
A
So
we
know
if
a
job
working
group
draft
it's
going
to
move
to
the
next
step,
invoke
group
process,
so
the
chairs
will
send
out
the
ipr
napoleon
and
then
the
authors
and
the
contributors
you
know
have
to
respond
to
the
polling
as
soon
as
possible.
Otherwise
you
know
it
will
delay
your
job
to
move
forward
next.
A
Another
remand
on
main
list.
I
think
we
as
cheers
always
encourage
people
to
use
the
melodies
as
much
as
possible
and-
and
we
can
discuss
anything
you
know
within
the
scope
of
the
sikkim
working
group.
For
example,
we
can
discuss
some
open
issues
or
introduce
some
new
drafts,
or
even
some
potential
topics
in
the
camp
and
also
we
know
that
working
groups
consensus
should
be
determined
on
the
mailing
list.
So
even
though,
here
we
got
some
consensus,
we'll
be
bringing
to
the
list,
for
you
know.
B
Yes,
okay,
just
status
update
since
the
last
the
last
interim
meeting,
because
we
didn't
meet
at
itf
107..
B
This
is
basically
the
the
result
of
the
work
that
we
did
during
the
day:
entry
meeting
on
layer,
zero
types
and
w's
on
young
models.
Basically,
we
concluded
the
last
call,
and
now
the
the
drafts
are
in
the
isg
processing.
So
this
is
a
good
step,
good
step
forward,
as
fatigue
already
said,
I
mean,
since
our
previous
entry
meeting
was
extremely
fruitful.
B
B
B
This
is
something
that
is
a
sort
of
part,
so
I
don't
expect
any
major
update.
While
on
this
other
side
on
the
flexibility,
the
media
channel,
I
think
that
we
will
have
an
update
soon,
probably
done
I
was
working
on
this.
I
don't
know
if
done
is,
is
online.
I
would
like
to
comment
or
gabrielle.
I
don't
remember
who's
holding
the
pen
of
the
draft.
B
B
I
would
leave
a
sort
of
five
minutes
of
open
mic
if
the
authors
of
some
drugs
wanted
to
share
some
information,
the
plans
to
move
on,
etc.
So
if
you
want
to
enter
the
queue
and
share
some
information
with
us
with
us,.
B
B
B
C
Okay,
just
trying
to
summarize
the
progress
so
far
on
all
the
otn
layer,
one
modules.
Basically,
we
are
tracking
everything
on
the
github
and
we
receive
some
editorial
comments
which
has
not
been
addressed
to
the
latest
version.
Yet
we
believe
the
model
itself
would
be
stable
and
we
have
good
connection
with
young
doctors.
Then
the
next
step
would
be
update
the
editorial
ones
and
proceed
for
working
for
glasgow.
B
B
B
B
D
B
B
E
Yeah,
hello,
everyone
jimmy
just
trying
to
point
you
to
the
chat
gert
is
giving
he's
getting
some
help
from
mexico.
There.
D
B
Let's,
let's
move
on
so
regarding
these
drafts,
the
itf
c
camp
client
signal
young
model.
Actually,
there
is
no
technical
change,
no
change
to
the
module.
There
were
some
corrections
and
to
to
to
naming
to
so
it
was.
It
was
just
a
validation,
evaluation
issue
regarding
the
flexi
grid,
young
model.
B
This
work
has
been
restarted,
with
some
editorial
changes
and
formatting.
So
I
mean
this
is
something
that
we
would
like
to
do
progress
in
the
in
the
in
the
next
months,
because
I
mean
this
is
a
completing
our
set
of
optical
optical
drafts.
There
are
still
some
open
issues,
open
issues,
the
rbnf
needs
to
be
updated
and
some
alignment
is
needed
on
on
the
young
on
the
young
model
and,
as
we
agreed
in
the
previous
discussions,
the
transponder
part
will
be
removed
from
from
the
topology
topology
droughts.
B
On
the
other
side,
the
nbi
applicability
statement
these
there
were
very
minimal
updates
on
the
draft.
So
this
is
something
that
can
be
considered
as
a
ready
for
working
group
lascala,
and
this
is
something
that
we
will
work
on
soon.
B
So
this
is
it
for
for
the
introduction.
B
C
C
C
Yeah,
okay,
before
getting
to
the
technical
details,
we
would
still
like
to
briefly
introduce
the
model
motivation.
C
In
itf
and
basically
the
objective
of
this
module
is
to
monitor
the
performance
parameters
which
has
been
configured
during
the
client
signal
configuration
in
the
client
signal
young
module.
It
includes
the
ethernet
client
signal
and
also
the
transparent
client
signal
like
sdh
and
fiber
channel
and
so
on.
C
So
the
kind
of
performance
monitoring
is
is
deployed
on
the
on
our
spawn
of
the
controller
and
all
the
client
signals
are
configured
on
the
given
tunnel
like
otn,
but
the
performance
monitoring
the
monitor
can
be
set
at
one
side
of
the
origin
tunnel
or
on
both
sides,
so
they
are
separately
colored
by
red
and
and
blue.
So
for
the
red
we
call
it
merit
by
loopback
and
only
p1
would
be
needed
to
set
as
a
monitor.
C
So
we
also
use
the
term
single
ended
because
only
tp1
is
involved
and
for
the
red,
sorry
for
the
blue
dashed
line,
so
it
means
okay,
we
monitor
the
performance
from
p1
to
p2.
Then
we
set
both
the
monitoring
on
p1
and
p2,
and
this
would
allow
the
p2
to
understand
the
kind
of
one-way
performance.
But
we
call
this
the
dual-ended
performance
monitoring,
because
both
physical
ads
are
evolving
in
the
performance
monitoring
and
regarding
the
parameters
to
be
monitored.
C
We
have
a
list
here,
including
the
latency
br
packet
laws,
bandwidth
cheater
so
also,
first
quite
general,
and
we
just
try
to
use
construct
a
comprehensive
model
that
can
express
the
real
time
or
historical
value
of
the
client
signal
already
configured
next.
C
Please,
okay
and
we
have
been
changing
compared
with
the
previous
version
in
the
pm
module
because
originally
we
have
two
client
signal
model,
one
for
ethernet
and
one
for
transparent
client
signals.
So
in
previous
version
we
also
have
two
pm
models,
but
they
are
quite
similar
with
each
other.
So
in
this
version
we
successfully
manage
them
to
combine
them
into
one,
and
we
also,
as
stated
in
in
the
previous
page.
We
also
add
the
measure
methodology
to
specify
how
to
do
the
pm.
Basically,
we
call
it
measured
by
loopback
or
measure,
but
as.
E
C
And
okay,
as
we
also
combined
the
ethernet
and
the
transparent,
transparent
client
signal,
so
we
also
reformatted
the
pm
structure.
Here
we
are
using
the
perform
parameter
name
as
a
key
to
perform
to
represent
the
performance
data.
It
includes
potential
identities
like
delay
b,
are
all
parameters,
and
we
have
the
value
lift
to
express
the
numerical
value
and
we
have
a
value
unit
to
give
the
corresponding
units
of
the
value
and
the
start
time
and
end
time
allows
people
to
understand
what
is
the
right
time
interval
for
the
performance
monitored.
C
And,
moreover,
we
have
also
additional
oam
functionality
being
configured
in
in
the
pm
model,
because
this
is
a
typical
way
to
do
the
to
do
the
oam
or
a
given
service
configured
in
the
networking.
So
we
augment
to
the
performance
monitoring
module
by
setting
the
source
and
destination
node
to
do
the
oam,
so
the
oem
related
parameters.
So
we
are
referencing
to
ieee,
802.1
q
or
y.1731.
E
C
C
Okay,
so
this
is
not
the
first
time
we
present
this
working
group,
but
we
didn't
hear
any
feedback
yet,
but
now,
besides
the
the
the
solution
or
the
model
shape,
we
would
like
to
start
from
the
very
beginning
saying
that
looking
for
the
feedback
from
the
group
is
this
the
problem,
a
valid
problem
to
be
solved
in
secant
and
does
it
match
the
current
scope
of
the
camp?
So
if
yes,
I
think
people
may
have
different
ideas
on
how
to
manage
the
performance
monitoring
and
we
can.
We
are
open
to
comments
on
this
discussion.
B
C
F
Yes,
I
think
you,
you
have
defined
a
measure
loopback
or
something
like
that
in
the
in
a
in
the
young
code.
Right.
F
And
I
think
yes
well,
I
think
in
the
description.
I
think
you
should
probably
describe
better
what
that
means,
because
a
lupe
can
be
anywhere
and
usually
I
think
you
mean
here
the
that
the
loop
is
closed
on
the
remote
end
of
the
tunnel
right.
C
F
C
F
C
B
B
G
G
We
just
do
some
refreshing
to
avoid
taking
the
changes,
and
this
draft
is
normally
referenced
by
the
transport
mba
applicability
draft,
because
it's
needed
for
discovery
of
the
uni
links
next
type,
please,
okay,
this
is
somehow
I
think
there
was
some.
Can
you
some
animation?
G
In
addition
to
that,
we
want
to
provide
additional
information
on
the
asset
links
about
what
are
the
capabilities
they
can
support.
So
what
what
type
of
green
and
classification
operation
we
can
do,
and
we
want
to
configure
the
value
profiles
used
on
these
assessments,
which
are
the
two
items
which
are
addressed
by
this
document?
Next
item
and
okay
click
again,
there
should
be
some
animation.
G
This
is
also
supports
the
case
where
the
time
that
they
suppose
a
service
is
also
an
iterative
tunnel
or
lsp,
and
in
this
case
we
need
to
associate
the
asset
link
with
the
internet
ttp,
and
we
also
need
to
report
the
iterative
topology.
What
are
the
internal
notes
and
eternity
links
which
can
be
used
to
to
pack
computation
and
pass
it
up
of
the
eternity
tunnel?
G
Okay,
so
for
the
access
link
discoveries,
where
we
have
some
debates
at
this
moment
in
time.
Okay,
we
this
model
is
currently
augmented
at
etopology,
and
the
reason
is
that
the
t
topology
already
supports
the
discovery
of
the
asus
links,
whether
they
are
uni
or
intel
domain
nni
is
the
same,
and
this
mechanism
is
almost
independent
of
whether
the
underlying
network
is
a
t
or
an
t
network.
So
it
tells
us
with
the
plugin.
We
know
what
are
the,
which
is
the
uni.
G
In
addition
to
that,
for
the
case
where
the
underlying
network
is
the
the
point
gives
us
the
same
on
the
same
entity,
which
is
the
ltp
the
information
which
allows
us
to
understand
what
are
the
interlayer
relationship
with
the
seven
layer
ttp,
this
is
clearly
t
specific
next
slide.
Please
and
the
approach
that
we
follow,
which
is
inherited
from
the
t
topology,
is
definitely
by
being
based
on
the
same.
Common
model
is
consistent
with
what
we
have
in
the
otn
topology.
G
So
when
we
look
at
the
network,
we
will
see
that
some
asus
links
which
are
otn,
for
example,
if
you
have
a
an
otn
line
card
on
a
router,
and
you
want
to
set
up
otn
thunderstrimet
in
your
transport
network.
You
have
to
model
this
as
an
otn
link
between
you
and
the
router,
or
an
otn
link
between
two
otn
domains.
They
are
both
type
of
links
are
reported
as
part
of
ltn
topology,
as
ltps
with
plug
id.
G
Container
that
tells
you
that
the
the
ltp
is
carrying
a
client,
transparent,
client
and
then
what
we
do
for
the
internet,
client
services
link.
We
report
them
as
part
of
the
internet
topology
and
if
you
can
have
some
unis,
which
are
able
to
operate
both
as
layer,
1
or
l2.
We
can
report
them
on
both
ethernet
and
otn
topologies
and
we
will
see
within
the
same
interlayer,
lock
or
transitional
link
how
they
relate
with
a
several
layer
tunnel
and
next
slide.
Please.
G
G
Okay,
so
when,
after
after
the
discussion
we
already
made,
we
had
some
offline
talks
with
the
people
and
we
got
us
a
better
understanding,
and
our
view
is
that
the
competition
is
not
between
our
draft
and
the
uni
draft.
But
it's
more
between
the
the
draft
of
gondio
and
the
t
topology
draft.
G
The
reason
is
that
the
the
draft
in
observer
working
group
is
trying
to
find
a
solution
which
is
generic
for
discovering
unis
when
the
underlying
network
is
t
or
non-t,
and
then
the
t
topology
is
the
one
that
provides
this
information
and
for
us
provides
additional
information
which
is
needed
for
the,
for
only
for
the
case
when
the
underlying
network
is
the
network,
so
we
may
need
in
our
application.
G
But
this
is
additional.
Information
is
a
cytoscope
of
draft
of
this
rafter
because
it's
generic
and
you
also
draft
organdio,
because
it's
not
related
to
t,
which
is
the
interlayer
lock,
and
what
we
do
in
this
document
is
something
which
is
outside
the
scope
of
both
draft
organdio
and
of
the
topology,
which
is
reporting
what
are
dividend:
classification
and
operation
capabilities
on
the
uni,
to
configure
the
access
link,
venue
profiles
and
to
configure
and
to
report
the
topology
for
eternity
technology-specific
augmentation
of
the
topology.
G
And
then
we
let
the
ts,
working
group
and
observer
working
group
to
understand
what
should
be
the
common
model
for
united
apology
discovery,
and
then
we
can
align
our
model
to
what
is
the
output
of
the
solution,
the
the
major
the
vast
majority.
Almost
all
the
code
will
be
untouched
by
this
decision.
It's
just
how
you
implement
it,
because
it's?
How
do
you
get
the
information?
Where
is
the
uni
rather
than
how
do
you
report
the
united
capabilities
that
will
change
by
by
this
decision?
G
A
Yeah,
thank
you.
So
actually
you
know
the
title
of
your
draft
is
a
young
data
model
for
ethnicity
topology,
but,
looking
at
the
you
know,
file
name
of
your
draft,
it
says
just
cam,
client,
topology,
young
and
also
looking
at
the
sec
introduction
section.
It
seems
you
also
are
discharged.
It's
just
you
know
a
topology
beyond
of
the
is
net.
So
my
question
is
that
it's
your
job
to
only
focus
on
the
that
topology
or
beyond
of
the
eastern
technology,
including
this
map.
G
It
is
currently
focused
is
focusing
only
on
ethernet
topology,
so
maybe
we
can
rename
the
draft
or
in
the
title,
if
it
is,
if
it
is
adopted,
I'm
okay.
A
And
also
some
you
know,
description
should
be
modified
in
your
draft.
For
example,
some
text
in
intersect
introduction
section
and
also.
G
A
You
order,
you
know
a
text
of
your
job.
H
Hi
so
I'll
be
quick,
because
I
think
we
are
four
minutes
about
time.
So,
just
to
let
you
know
what
was
the
purpose
of
the
draft
and
it
was
to
complement
existing
drafts
with
the
concept
of
the
service
attachment
point
at
the
uni
reference
point,
so
we
can
have
a
place
or
a
placeholder
to
put
independently
whether
the
underlying
network
is
t
or
norte,
a
point
to
say:
hey
from
here.
You
can
start
a
service.
H
E
H
H
Okay,
so
the
suspension,
the
discus
the
what
we
have
is
the
service
attachment
point.
We
add
a
augment.
We
have
made
the
the
node
directly,
so
it
is
not
http
is
not
a
link
termination
point.
We
can.
It
need
a
data
reference
to
a
line
termination
point,
but
right
now
it's
a
separate
concept,
so
it
is
more.
We
can
see
it
more
like
a
inventory
in
the
sense
that
what
we
are
exposing
is
okay.
These
are
the
p
nodes.
Are
these
are
the
points
from
where
services
can
be
instantiated?
B
Thank
you
thanks
thanks
a
lot,
and
thanks
a
lot
for
for
the
analysis.
I.
E
D
Yes
good:
this
is
a
young
model
for
the
sinker
5.
The
fight
can
be
a
ethernet
or
otn
see.
Next,
please.
D
The
linkage
can
be
a
ethernet,
rtn,
sdh
and
so
on,
and
the
signal
is
transferred
using
the
master
to
sliver
mechanism,
and
the
final
signal
can
be
traceable
to
a
external
prc
such
a
primary
reference
clock.
D
One
feature
of
this
synchronization
is
in
the
when
the
link
between
the
master
and
the
sleeve
clocker
fields,
the
equipment
will
still
be
able
to
maintain
the
hold
over
or
the
terminal
frequency
precision
within
some
prescribed
performance
limits,
such
as
10
seconds.
D
D
D
As
you
can
see
on
the
right,
the
core
network
have
some
primary
reference:
clock,
which
provides
a
high
precision
frequency
and
on
the
left,
is
a
mobile
network,
which
is
the
young
network,
and
the
frequency
of
the
face
clock
can
be
provided
front
right
and
step
by
step
transporter
of
the
clouds.
That's
the
transporter
network,
to
the
left
side
and
on
each
step.
D
The
clock
signals
are
are
transferred
across
a
network
from
from
one
node
to
the
next
node
and,
at
the
same
time,
the
ssm
message
with
the
quality
level.
Information
are
also
transported
in
the
network.
D
D
The
northbound
interface
is
to
the
upside,
which
will
interface
with
software
mod
blog
such
as
sync
continue,
and
the
second
tool
will
manages
two
blocks.
One
is
a
system
clock
and
another
station
clock
wherein,
on
the
left
side
is
a
mult
power.
D
D
So
I
said
the
selection
between
which
support
is
used
as
the
time
timing
source
is
under
the
control
over
the
system,
clock
or
under
the
station
clock.
So
this
is
a
cool
idea
of
the
control
and
the
monument
of
the
thinker
node.
B
D
Yeah
cannot
go
any
longer,
yeah,
some
couldn't
start.
They
use
this
id
and
the
next
day
is
the
young
tree
telegram.
So
I
will
not
give
some
details.
The
final
one
is
yeah.
We
will
enhance
this
in
idea
when,
with
any
imp,
progress
in
itt-
and
I
will
update
it
according
to
our
workgroup
feedback.
D
B
B
E
Great,
so
hello
again,
so
this
is
julian.
I'm
about
to
present,
on
behalf
of
my
co-author,
the
extension
we
proposed
into
the
lvpt
signaling
for
the
transponder
mode
within
the
wdm
network.
So
what
is
the
problem?
We're
trying
to
address
nowadays,
more
and
more
transponders
or
transceivers
in
the
market
are
supporting
various
types
of
modulation,
formats,
borrate
efficiencies
and
so
on.
E
So
we
assume
that
the
routing
will
have
wavelet's
assignment
on
a
mod
selection
as
well
happen
before
the
the
signaling
leaves
the
the
first
roderm
along
the
pass,
and
we
use
that
messaging
to
carry
more
information
up
to
the
egress
transceiver.
To
make
sure
that,
on
the
other
hand,
of
the
past,
we
have
the
correct
set
of
transponders
that
are
put
on
provided
consistently
with
the
ingress
transponder.
E
So
some
parameters
may
be
sent
or
forced
by
the
operator
from
the
transponder
to
the
line
to
configure
to
end
up
to
the
egress
transponders,
or
some
may
be
dynamically
allocated
at
routing
on
reflect
at
time
on
time.
If
we
consider
that
the
first
rotom
of
the
line
is
in
charge
of
pass
computation,
whether
it
is
embedded
or
remotely
in
a
pc
and
when
this
problem
selects
all
the
parameters
relevant
to
the
pass,
it
sends
uses
the
drcpt
signaling
messages
to
carry
those
up
to
both
ends
of
the
wdm
pass.
E
E
E
It
assumes
that
the
pass
computation
entity,
whether
it
is
embedded
or
not
in
the
in
the
first
problem,
is
able
to
resolve
the
opaque
id
into
a
set
of
parameters
that
actually
define
the
mode
we
want
to
configure
and
that
the
pass
computation
entity
is
able
to
select
among
the
modes
with
a
clear
view
on
what
mod
id
refers
to
in
terms
of
detailed
parameters
and
can
use
this.
The
mode
to
refer
to
this
set.
E
E
A
given
set
of
mode
ids
are
referring
to
referring
to
a
given
set
of
optical
parameters,
and
everything
happens
at
selection
time
on
the
protocol
just
carries
alpha
kd
so
to
encode
that
we
will
use
a
similar
encoding
of
the
application
id
that
is
available
in
the
lmp
draft,
which
is
already
a
working
group.
Second
working
room
draft,
so
the
id
is
composed
of
a
field
that
is
the
vendor-specific
prefix,
and
then
we
use
two
fields,
the
transceiver
type
and
the
mod
id
that
refer
to
the
the
columns
in
the
rows
in
the
the
table.
E
E
Some
may
be
relevant
in
both,
depending
on
the
the
use
case
that
we
have,
but
we
consider
that
as
a
first
approach,
this
one
could
be
considered
as
an
interesting
first
proposal
in
the
draft,
all
the
more
it
is
already
proposed,
another
existing
internet
draft
within
the
working
group,
so
the
next
step
from
there
is
to
improve
the
level
of
consistency
with
other
existing
drafts
that
are
connected
to
the
the
topic
so,
first
of
all,
the
the
optical
implement
within
the
young
topology,
of
course,
also
dwdm
interfaces
that
are
so
far
tackled
in
the
specific
young
module.
E
E
We
addressed
a
couple
of
comments
that
we
received
from
private
discussions
with
a
couple
of
fellows
that
are
connected
today,
and
we
hope
that
we'll
get
new
feedback
from
the
working
group,
starting
from
today,
either
right
now,
either
using
the
the
mailing
list
as
soon
as
you
feel
ready
on.
E
A
Okay,
thank
you.
So
I
have
just
one
minor
comment,
so
I
think
I
really
like
this
draft
because
you
know
this.
This
draft
is
about
you
know,
project
extension
rather
than
young
models.
You
know
it's
really
boring
to
have
lots
of
the
young
model
jobs,
but
you
know,
but
you
know
back
to
this
draft.
I
think
you
just
mentioned
you
know
short-term
codings
and
middle
term
encodings,
but
actually
you
don't,
you
know,
have
the
long-term
inconvenience.
E
Yeah,
okay,
I
see
your
point
well,
actually,
my
wording
here
short
midterm,
isn't
in
the
draft.
The
draft
proposes
these
two
types
of
encoding,
the
opaque
one
on
the
detailed
one.
So
to
make
it
easier
to
present,
I
renamed
them
short
term
on
midterm,
but
in
my
understanding,
midterm
or
long
term
would
merge.
The
idea
would
be
rather
define
them
as
opaque
or
detailed.
Maybe
that
would
be
better
warning
to
reflect
was
actually
proposed
in
the
draft.
B
Okay,
I
just
I
just
learned
that
there
is
no
more
renard
to
stop
at
five
minutes
past
the
session,
but
we
will
take
it
just
a
tell
us
question
or
just
for
respect
for
the
people
that
wanted
to
take
a
break
before
the
next
the
next
session.
So
it
allow
up
to
you
and
then
we
close
the
session.
G
Thank
you
now
just
to
point
out
that
we
are
having
similar
discussions
in
the
context
of
the
young
model
for
transceivers
and
the
issue
about
what
information
is
needed
for
par
computation.
First
setup
may
be
similar,
so
may
be
good
to
have
an
alignment
in
the
approach
between
this
draft
and
the
other
draft,
at
least
in
terms
of
what
are
the
attributes
that
are
needed.
So
we
don't
have
too
much
confusion
on
the
terminology.
G
E
You
know
it
hello,
I'm
evolving.
Those
on
I
fully
agree.
The
idea
is
not
to
propose
a
different
model.
The
idea
is
to
bring
the
model
that
we
define
in
other
places
into
our
zpt.
So
with
you,
consistency
is
at
stake
here,
and
this
is
the
target.
B
Very
good
thanks
a
lot
everyone
for
participating
and,
as
we
said
before,
we
will
schedule
an
interim
meeting
in
september
when
we
will
leave
a
lot
of
room
for
discussion
for
for
each
draft.
Thanks
a
lot.
Everyone
and
goodbye.