►
From YouTube: CNCF Telecom User Group Meeting 2019-11-07
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
CNCF Telecom User Group Meeting 2019-11-07
A
A
This
call
is
a
continuation
of
the
twice-monthly
calls,
specifically
continuation
of
monday
stockholm
user
group.
Call
if
you
could
add
your
name
to
the
attendees
list
in
the
meeting
notes.
So
that's
never
would
be
great
rather
than
having
an
open
agenda.
Our
main
focus
is
on
the
white
paper.
That's
fing,
written
and
I'll
paste
that
into
the
zoom
chat.
A
We're
looking
to
get
any
agenda
items
that
folks
would
like
to
talk
about,
and
ideally
volunteers
for
presenting
on
a
topic,
lightning
talks.
A
couple
of
minutes
get
up
and
get
discussions
going
and
if
you're
up
for
talking,
please
add
something
and
if
there's
just
something
and
really
like
to
hear.
Please
add
that
is
12
the
brainstorming
items
in
that
wiki
page.
A
So
for
folks
who
are
not
familiar
with
this
white
paper
and
there's
been
several
F
different
efforts
for
adding
content
and
that
could
go
towards
a
white
paper,
including
a
lot
of
effort
on
a
different
other
white
paper.
The
predecessor
may
be
to
this,
and
this
is
kind
of
a
combination
of
all
those
different
efforts.
This
is
chapter
one
of
what
we're
hoping
will
be
this
white
paper
on
cloud
native.
A
There's
a
lot
of
comments
in
this
document:
I'm
not
going
to
go
through
all
of
those,
but
one
of
the
particular
areas
that
were
looking
at
is
how
to
define
what
a
cloud
native
Network
function
is
and
there's
a
lot
of
different
definitions
and
ideas
on
where
we
could
build
from
including
references
to
Etsy
and
other
documents
and
standards
and
and
how
to
make
this
clear
and
and
that's
kind
of
what
these
are
I.
Don't
think,
there's
any
new
definitions
on
here
from
where
it
was
before.
D
A
D
D
My
preference
but
I'd
like
to
settle
on
a
see
enough
definition
I
think
it's
crucial
that
we
use
this
term
so
much
that
we
agree
on
a
definition
that
we
can
all
agree
around.
I
know
that
I
have
proposed
earlier
a
definition,
and
that
is
still
there
I
believe
as
alternative
5,
but
then
I
think
the
the
criticism
towards
that
was
that
it
contains
direct
reference
to
Etsy,
or
maybe
we
want
to
come
up
with
something
on
our
own
I,
think
it's
or
something
that
is
standalone.
D
D
C
Yeah
I
kind
of
second
that
this
is
probably
the
highest
priority
thing
from
me
as
well
in
terms
of
the
ones
I
contributed,
they
were
more
so
one
of
them,
I,
think
or
11.1.
We
were
essentially
building
on
the
original
one
that
you
created,
which
was
more
or
less
the
same
end
result
except
they
had
taken
the
wording
from
the
etsy
document
an
expanded
way
required,
rather
than
just
referring
this
to
the
NC
document.
C
Yeah
yeah,
which
I
think
then
then
leads
to
the
discussion
that
I
think
all
three
it
was
the
tailor
created
and
where
which
I
think
then
got
merged
a
little
bit
in
talked
1.2,
where
it's
a
bit
of
a
mixture
of
both
so
whether
you're,
an
existing
telco
person
with
knowledge
alexei
coming
to
this,
whether
you're
a
cloud
native
application
engineer
these
need
to
Toco
come
into
this
there's.
There's
descriptions
in
there
would
hope.
D
Iii,
like
all
of
these
fundamentally
I,
think
there
are,
there
are
bits
and
pieces
which
I'm
not
big
fan
of
I.
Think
I
know
that
there
has
been
a
lot
of
effort
in
previously
in
trying
to
figure
out
what
is
a
V
NFC
in
the
cloud
native
context
and
I
I'd
like
to
keep
things
simple
and
maybe
by
trying
to
do
a
mapping
between
VN,
FCS
and
micro
services.
We
are
a
little
bit
moving
out
of
the
domain
of
defining
the
the
C
and
F
and
and
trying
things
at
the
same
time.
D
I
think
I
think,
then,
that
the
question
is
the
fact
that
the
micro
services
are
a
little
bit
hanging
in
the
air.
Is
that
a
problem
or
not,
if
I
think
about
the
original
cloud
native
definition
by
C
and
C
F
I'm,
not
sure
if
micro
services
are
mentioned
there,
but
I
think
there
are
there
are
micro
service
is
mentioned
as.
C
C
So
old
5
is
the
original
one
from
the
first
white
paper,
which
was
CNF
is
an
implementation
of
V
and
F,
as
defined
by
l'a,
adheres
to
the
cnc
of
cloud
native
definition
and
and
the
feedback
in
tug
was
that
it
needed
to
to
either
create
its
own
wording
to
to
avoid
having
the
reference
to
the
HC
document
or
the
my
my
my
alternatives,
one
that
one
that
one
and
wanted
to
be
built
on
was
to
call
out
the
wording
from
that
document.
Instead,
I.
E
F
So
that's
why
it
calls
out
exactly
a
component
and
works
like
a
Vienna
and
of
the
NFC
one
of
the
scenes
that
going
back
and
forth
on
is
where
the
grouping,
and
where
is
a
single
service?
Where
does
that
line
that
looks
like
in
the
SD
doc?
The
component
is
more
of
something
that
would
map
to
the
single
service,
whereas
the
grouping
is
actual
network
function.
C
A
Then
that
would
be
quite
a
bit
different
from
what's
SC
and
I
guess
vnf
side
of
things
would
be,
the
mapping
is
different,
so
that
would
need
to
wouldn't
need
to
make
sure
that
that's
well
understood
and
then
all
four
is
kind
of
a
compromise
to
move
that
more
towards
what
they
similar
to
what
the
that's.
The
definition
of
virtualized
network
connections
are.
C
C
So
if
we
agreed
it,
that
means
that
that
behavior
faces
it
well
defined
because
they
are
they're
governed
by
industry.
Standard
specifications.
Then,
if
that,
if
that
kind
of
we
can
agree
on,
then
it
means
that
probably
old
fool
is
is
valid.
All
three
isn't
because
three
would
require
those
industry
standard
specifications
to
define
the
network
functions
as
very
simple
single
service
single
protocol
things
so.
E
I
think
I'll
I
have
a
trouble
without
so
because
the
current
information
about
is
implying
physical
device,
I
mean
I,
don't
think
when
we
talk
about
virtualization
and
writing
things
in
software,
you
will
have
a
functional
block.
One
single
function
block
would
extend,
it
will
define
external
interfaces.
This
is
not
biggest
the
new
world.
You
have
multiple
of
software
elements
working
together
to
fulfill
a
network
function,
and
this
is
why
I
think
if
we
use
all
to
us
as
the
basis,
it
might
not
be
my
view
at
least
aligned
with.
F
F
E
D
Not
at
all,
it's
just
I
think
Etsy
is
doing
their
own
mapping
and
definition
on
this
and
I
die.
If
I
remember
right,
that
is
not
finalized,
yet
so
I
think
it
would
be
wise
to
not
try
to
redefine
what
Etsy
is
defining,
because
we
might
end
up
with
a
different
definition,
and
then
people
will
get
confused
all
the
time
when.
D
D
G
D
D
D
G
D
D
A
D
C
I
D
D
A
G
A
G
A
E
So
going
back
to
Thomas
area
point
around
Asian
for
moving
out
one,
because
it
was
not
mentioning
any
of
the
cloud
native
principles
I'm,
but
that
is
cloud
native
function
is
a
credit
application.
So
it's
just
like
translating
the
water
with
water.
I
just
think
it's
not
much
in
this
definition
that
will
make
people
where
okay,
that's
that's
what
the
content
is.
It's
just
saying
cloud
native
function
is
a
bloated
application.
Only
thing
I
see
is
the
microservices
wrong,
so
I
don't
think
it's
enough
to
explain
what
is
make
loud
need
to
different
them.
C
A
A
What
I'm
not
gonna,
do
a
change
other
than
formatting
to
point
out
that
the
next
partes
is
referencing
but
not
necessary.
So
I,
yes,
for
what
you're
saying
1.2
was
supposed
to
mix
the
4
+
alt
1.1
I,
think
that
was
the
goal
yeah
all
right.
So,
let's
see
I
think
we
have
enough
fun
out
one
suggesting
removal
of
that
one
and.
D
C
E
D
I
D
Can
someone
this
tell
me:
why?
Is
it
a
bad
idea
to
talk
about
external
references?
I
I
hear
Taylor,
saying
that,
because
these
external
documents
might
change
but
I,
think
Etsy
standards
are
pretty
damn
version
control,
so
I
think
once
we
reference
the
right
version
and
copy
all
over
the
word,
so
one
doesn't
have
to
click
on
the
link.
I,
don't
see
a
practical
problem
with
referencing
at
sea.
Is
there
another
problem
with
referencing
axis.
E
F
E
I
was
going
to
say
in
my
personal
opinion,
I,
don't
think,
there's
anything
wrong
with
the
front
C,
it's
C
I
think
the
mapping
is
is
important
to
understand
how
that
illustrates
the
architecture
to
be
in
the
safe
side,
focus
in
to
not
worry
about
or
now
I'm
just
trying
to
define
cloud
neatly
respective.
Let's
see
what
is
it
accordingly
from
application
perspective,
what
features
do
they
have
and
a
letter
or
a
different
exercise,
trying
to
see?
Okay?
H
G
I
E
E
That
would
be
very
ambiguous
in
definition,
but
sometimes
ambiguity
is
good
thing,
because
that
will
remove
the
confusion.
This
is
one
approach
which
make
it
very
high
level
and
make
it
just
focus
into
what
my
cognitive
but
loud
native
I
think
this
is
a
starting
point.
If
we
start
digging
deeper
into
mapping
things
into
its
env,
we
will
miss
something
and
it
will
bring
more
misalignment.
I
would
say
so.
I
personally
think
if
we
just
stick
to
the
fit.
E
C
C
So
so
it's
a
cloud
native
application
that
implements
a
network
function
and
which
we
may
then
choose
to
add
a
link
to
which
is
a
we
were
talking
about
earlier
about
you
know:
do
we
agree
that
a
network
function
is
something
is
defined
by
an
industry
standard
specification
I
think
we
do
yep
so
I
think
if,
if
people
happy
with
for
dat
one,
then
we
can
simply
add
another
another
sentence
to
that
effect.
Maybe
that
makes
sense.
A
F
Yeah
so
as
far
as
like
interfaces,
so
when
iCloud
negative
there's,
a
heavy
emphasis,
part
of
the
definition
is
having
a
declarative
API,
and
so
we
keep
playing
around
with
adding
that
in
and
then
digging
it
out.
Not
wanting
to
deal
with
that
right
now.
As
far
as
the
definition,
but
if
we
put
in
something
that
says
interface
and
then
we
don't
talk
about
declarative
API,.
A
D
F
D
One
I
think
it's
important
to
differentiate
between
functional
architecture
and
implementation
architecture,
and
you
know,
network
functions
is
defined
by
3gpp,
with
their
interfaces
are
functional
architecture,
api's
and
backward
compatibility
on
api's
and
our
declarative
way,
because
that's
implementation
architecture.
So
this
should
we
should
stick
to
either
or.
A
Talking
about
up
tennis
protocols,
which
that's
not
something
that
we're
gonna
change
and
say
you
can't
run
MPLS
over
some
network
connection,
that's
set
up
or
whatever
else
you
want
to
say
so.
The
protocol
and
stuff
isn't
what
we're
talking
about.
It's:
how
to
create
the
connectivity
between,
say,
pods
containers,
multiple
nodes.
F
D
A
A
I
think
that's
the
confusion
there
when
we
just
say
interfaces,
because
the
pods
will
have
interfaces
so
that
that
word
is
too
generic
services
interfaces
connectivity.
So
we
need
something:
that's
not
talking
about
the
architecture
which
would
be
caught
native,
but
the
data
and
communication
that
goes
on
after
so.
D
A
A
I
think
that
could
be
good,
so
thing
we're
trying
to
do
is
get
that
kind
knowledge
with
folks
that
are
working
on
the
platform
side,
that
their
background
and
understanding
is
on
the
cloud
native
versus,
if
your
telco
in
there,
since
there's
a
lot
of
overlap
and
the
words
are
used
in
different
ways
based
on
the
context.
If
we
can
expand
those
words
and
have
the
definitions
in
there,
you
know
I,
think
collaboration
will
be
a
lot
easier.
I.
D
Think
the
question
is
how
much
we
want
to
bring
that
into
this
definition.
I
think
the
only
reason
why
we
are
bringing
in
the
same,
because
we
want
to
talk
about
network
functions
and
the
only
way
that
we
can
define
the
network
functions
themselves,
is
that
they
have
these
multiband
or
standard
defined
interfaces
between
them.
D
C
J
J
E
So
if
there's
any
ambiguity,
usually
the
rest
of
the
document
will
explain
that
so
I
think
personally,
I
think
it's
okay
for
the
definition
to
be
very
simplistic
to
the
point,
and
we
all
know
that
there's
a
definition
for
the
drop
function
y
tiene
be
there
are
interfaces.
The
functionality
is
defined
by
standards
at
loud
native
application
is
the
way
to
create
that
functionality
using
multimedia
services.
I,
don't
think,
that's
a
generic
definition
generic
enough
to
have
a
strong
basis
where
the
ratio
document
will
start
looking
at
different
aspects.
D
So
I
agree-
and
there
is
another
element
that
I'd
like
to
draw
in
which
sort
of
makes
me
like
1.3
more
after
all,
and
that
is
I'd
like
to
have
a
CNF
definition
that
I
can
use
internally
towards
my
organization,
to
you
know
to
beat
up
those
who
might
try
the
game
of
hey.
I
I
put
my
application
into
containers,
and
these
are
sort
of
microservices
storm
cloud
native.
When
it
comes
to
alternative
1.3.
D
F
A
D
Yeah
but
I
mean,
if
I
just
look
at
alternative
for
those
as
a
cloud
native
application
is
compost
or
of
one
or
more
micro
services,
which
is
true,
and
the
cloud
native
application
term
implies
much
more.
If
you
know
the
definition,
if
you
don't
know
the
definition,
then
you
might
jump
to
the
conclusion.
Okay,
so
to
be
cloud
native,
you
have
to
have
micro
services,
so
I
would
prefer
to
write
out
what
a
cloud
native
application
is
as
opposed
to
referring.
So
if,
if
we
are
now
writing
things
out,
then
we
should.