►
From YouTube: CNF WG Meeting 2021-06-21
Description
CNF WG Meeting 2021-06-21
A
B
B
Are
we
talking
about
the
weather,
yeah
weather
and
I
guess
it's
texas
electrical
stuff.
C
C
D
C
D
C
B
B
B
At
the
meeting
notes
been
posted
in
the
zoom
chat,
they're,
also
in
slack
and
the
calendar,
if
you
have
it,
it's
listed
on
the
cncf
public
calendars
of
events,
and
this
call
is
recorded.
If
you
didn't
get
the
zoom
message,
I
think
everybody
gets
them
now
when
you
join.
These,
so
is
recorded,
will
be
posted
to
the
cncf
youtube
channel.
B
I
guess
one
thing
to
note
at
the
july
5th
meeting
so
not
next
monday,
but
the
monday
after
is
going
to
be
canceled.
It's
a
public
holiday
in
the
u.s.
B
And
upcoming
events
kubecon
in
a
october
o
nes
the
cfp
submissions
closed
yesterday,
the
20th,
if
there's
some
interesting
ones,
I
guess
if
you've
had
acceptance,
I
don't
know
if
it's.
If
those
have
come
through
for
kubecon,
then
let
people
know
we
could
post
them
on
here
ahead
of
time,
so
that
folks
can
be
aware
of
this,
and
if
there's
some
interesting
stuff
for
o
nes,
then
keep
those
in
mind
for
when
they
get.
B
If
you
get
accepted,
let
everybody
know
in
the
group
so
right
now
it
looks
like
all
we
have
is
some
items
from
the
pull
request
and
I'm
gonna
refresh
that
page.
I
don't
see
anything
new
there,
no
new
discussion
items.
Does
anyone
have
anything
they
want
to
add
agenda.
B
B
Cool,
I
think
you
had
some
changes
on
the
staples.
F
B
F
Yeah
and
I
made
those
over
the
weekend,
so
I
don't
think
there's
any
open
issues
left.
I've
made
a
type,
a
change,
I
think.
Is
it
pancaj
put
a
comment
yeah,
which
I
updated,
which
was
the
introduction
of
the
basically
the
statement
that
he
made
about
the
glossary
state
being.
F
I
just
took
the
text
as
as
written
and
then
change
the
existing
one
to
be
types
of
states,
because
that's
basically
what
it
was
all
right.
So
I
don't
think
there's
any
reason
why
sorry.
F
F
B
Yes,
sorry,
I
should
have
brought
it
up
a
little
different,
so
I
I
actually
just
expanded
this
funky.
This
has
been
resolved
so
we'll
go
and
take
a
look
at
the
changes.
Would
that
be
and
the
yeah.
B
E
F
Of
states
but
yeah
those
the
ones
I
talked
for.
F
Okay,
I
don't
think
there's
any
other
comments
left
over,
so
I
guess
we
either
need
more
people
to
review
it
or
we
accept
it
as
it
is,
and
then
iterate
like
we've
done
on
other
things,.
F
F
Thanks
peter
yeah,
there
was
yeah.
I
did
a
couple
of
minor
adjustments
previous
to
the
last
meeting,
to
clarify
certain
things
so
yeah,
that's
all
good
yeah.
We
just
need
a
couple
more.
I
think.
F
Yeah,
that
was
the
only
change.
All
of
the
changes
were
prior
to
the
previous
meeting.
B
B
Okay,
so
this
is
we're
trying
to
get
more
use
cases
in
here
with
the
purpose
of
having
context
for
taking
these
are
looking
at
them
and
using
them
as
reference
for
best
practices,
so
there's
stuff
that
we've
started
talking
about
for
best
practices
on
state,
like
probably
from
databases
and
stuff.
B
The
point
is
to
get
these
in,
so
that
we
can
reference
and
discuss
them.
We
can,
it
doesn't
have
to
be
perfect,
so
is
there
can
we
get
some?
I
guess
some
plus
ones
and
get
this
merged?
D
B
C
H
I
F
Checker
and
I
think
it
checked
the
whole
repo,
I
think,
let
me
have
a
look.
I
Yeah
but
or
maybe
the
status
is
not
considered
as
a
healthy
service
like
because
it's
returning
like
429
http
code,
so
probably
I
don't
know
we
have
to
modify
the
checker
to
also
consider
that.
I
Because
the
the
url
is
fine,
I
mean
don't
check
it
and
it's
it
is
there.
I
If
you
click
on
that
it
is,
it
is
working,
it's
opening
the
repo,
but
maybe
this
tattoo
code
that
is
he's
getting
that
429
yeah.
Consider
like
I
don't
know
if
we
have
to
modify
the
company
file
or
something.
B
B
B
C
Should
probably
use
relative
links
because
then
they
become
tied
to
the
commit
branch
as
well,
rather
than.
B
B
I
think,
as
she's
came
on
like
for
a
couple
of
calls,
but
I've
been
out
for
a
bit
and
I
don't
see
them
on
the
call.
B
B
B
I
B
I
B
B
B
But
this
is
a
suggestion,
I
guess
so
that's
one
thing
to
keep
in
mind
just
pointing
this
out
and
I'm
not
looking
at
the
rest
of
context
for
the
use
case,
but
in
a
use
case
we're
not
trying
to
communicate
a
best
practice,
but
this
is
kind
of
suggesting
what
people
should
do
it
should
maintain.
B
So
that
may
need
to
be
adjusted.
I
don't
know
if,
if
anyone
wants
to
take
this
over
because
I
haven't
heard
from
ashish
in
a
while,
has
anyone
else
heard
for
machis.
I
B
B
So,
if
you're
interested
in
these
take
a
look
and
we
can
reach
out
to
a
sheesh,
but
if
they
don't
respond,
then
we'll
need
to
go
through
and
and
look
if
we
want
to
take
this
over.
I
think
on
the
timing
was
the
one
that
had
the
most
interest
and
that's
why
we
ended
up
with
a
discussion
and
I,
if
we
go
back
and
look
at
the
notes,
there
was
some
comments
there.
E
E
B
This
one's
been
open
for
a
while
too
tal
have
you
gone
through
and
looked
at
some
of
the
stuff
for
being
able
to
commit
merge
in.
B
We're
talking
about
mine
specifically
well
yeah,.
C
B
This
pr
there's
a
bunch
of
oh
yeah.
I
guess
part
of
the
thing
is
because
it's
such
a
a
large
set
of
changes,
then
they've
had
a
lot
of
requests
for
changes
to
that
or
I
won't.
B
C
So
I
I
really
thought
we
it
it's.
The
comments
are
a
discussion
right.
I
I
don't
feel
like.
I
we
reached
a
final
decision
on
anything
really.
I
think
it's
worth
discussion
discussing
here.
This
is
why
we're
doing
this,
I
yeah-
I
I
don't
know
we
re.
If
we
reached
a
complete
alignment,
there
were
a
few
good
ideas,
but
I
don't
think
we
as
a
group
as
a
whole,
agree
on
some
of
the
court
terms.
C
C
I
suggested
cn
nf
cnnf
with
the
dash
being
an
emphasis
that
this
is
well
we're
talking
about
an
operational
perspective
on
a
network
function
rather
than
a
technological
perspective,
which
is
things
like
vnf
and
cnf,
which
refer
to
how
the
network
function
is
deployed,
with
the
point
being
that
a
containerized
network
function
is
not
necessarily
a
cloud
native
function
and
a
cloud
native
function
could
be
a
virtualized
network
function,
and
I
I
don't
know
if
that's
the
suggestion
I'm
throwing
out-
and
I
know
it's
a
big
one
and
it
really
changes
even
the
name
of
of
this
group
work
group
and
what
it
means.
B
B
H
B
That
right,
I
understand
what
you're
saying
tal.
With
regards
to
the
confusion
on
containerized
and
other
stuff,
I
don't
think
within
cncf
in
the
kubernetes
community
there
is
confusion,
that's
it
is
about
cloud
native,
so
it
would
be
presenting
itself
outside.
But
from
the
group
standpoint,
whatever
the
acronym
is
we're
talking
about
cloud
native
networking
applications,
that's
right,
correct.
C
I
I
don't
think,
there's
any
confusion
about
that,
I
think
and
if
we
would
make
a
suggestion
to
the
cncf
we
we
are
trying
to
align
with
the
industry
right
and
provide
best
practices
for
the
intercity,
and
the
glossary
is
an
important
contribution
too
right.
These
are
terms
that
we
can
all
agree
with.
C
The
fact
is
right
now
that
the
industry
as
a
whole
are
is
not
using
cnf
in
the
way
that
we
are,
if,
if
we
mean
cnf
to
mean
cloud
native
network
function
and
we've
been
using
it
that
way
so
far,
I
think
it
creates
confusion
in
the
industry
at
large.
So
I
mean
we
can
do
whatever
we
want.
That's
true,
but
I
think
I
want
us
to
be
helpful
and
not
add
to
the
confusion
so
like
it
or
not.
C
Cnf
in
many
parts
of
the
industry
and
many
documents
and
many
presentations
that
are
given
refers
to
cloud
native
network.
Sorry
refers
to
containerized
network
function,
sometimes
specifically
on
kubernetes,
but
not
always
and
yeah.
It's
an
unfortunate
aspect,
the
this
confusion.
So
I
I'm.
B
Trying
to
make
a
suggestion,
one
of.
C
B
B
Second,
frederick
one
thing
that's
been
suggested
and
I'm
gonna
bring
it
up
now
is
break
this
pr
update
into
smaller
chunks
so
that
we
can
get
some
of
them
that
are
agreed
to
merged.
So
just
on
your
glossary
update
the
pr
in
general
and
then
around
cloud
native,
I
think
that
needs
to
be
put
for,
probably
not
in
a
pr
but
a
discussion
so
create
a
discussion.
B
I
I
think
there
might
actually
yeah.
There
is
one
that
jeffrey
put
in
here,
so
you
could
put
it
in
here
or
put
it
in
a
new
discussion
and
what
I
would
recommend
is
creating
like
a
a
spreadsheet
or
a
link
show
a
big
list
of
here's
all
of
the
there's
when
we
do,
google
searches
or
whatever
you
have.
Eighty
percent
of
the
people
say
containerized
and
here's
20
that
are
using
that.
So
do
this
as
like
a
discussion
for
itself,
and
we
can
deal
with
that
separately,
but.
B
C
I
think
I
think
you're
you're
jumping,
I
think,
there's
a
confusion
here.
The
the
issues
were
were
discussion
right.
I
don't
know
if
I
would
treat
them
as
comments
necessarily
ian
raised
a
few
points
and
we
we
discussed
things.
My
original
pr
is
not
related
to
that
issue.
I
mean
I
am
treating
cloud
native.
I
am
treating
cnf
as
cloud
native
network
function,
so
the
discussion
might
be
separate,
but
I
think
the
pr
as
itself
yeah.
C
I
I'm
not
sure
if,
if
any
of
the
comments
would
affect
it,
so
I
I
think
the
pr
could
be
merged,
as
is,
and
that
discussion
I
agree,
is
separate
and
we're
having
it
in
separate
places,
and
there
could
be
a
future
pr
to
fix
to
fix
that.
But
right
now
it
absolutely
adheres
to
our
original
definitions.
That
is
cnf
means
cloud
net
cloud
native
network
function.
I
I
did
not
change
that.
B
Okay,
let's
well
frederick,
I
don't
know
if,
if
you
had
a
comment
or
would
just
move
forward
to
try
to
close
this
out
without
talking
more
about
cnf,
but
go
ahead,
frederick.
H
It
was
just
a
little
bit
of
context
just
on
the
history
of
cnf,
so
the
actual
term
was
actually
created
through
collaboration
with
the
cncf
itself,
so
there's
an
individual
who
doesn't
want
to
be
named,
who
came
up
with
the
term
cnf?
H
H
Despite
the
the
efforts
that
went
on
to
to
define
what
what
a
cnf
is.
So
it's
it's
definitely
very,
very
acute
issue.
That
would
be
good
to
get
some
form
of
resolution
on,
but
I
I
I
don't
see-
I
I
don't
see
an
easy
path
towards
towards
any
of
that.
I
do
agree,
though,
that
the
community
at
large,
within
the
cncf,
does
does
agree
that
it's
cloud-native
network
function
and
we've
done
a
good
job
in.
E
H
Environment
at
the
community
of
large
is
definitely
taking
their
own
interpretations,
and
I
think
they're
going
to
do
this,
even
if,
even
if
the
term
containerized
ever
function
did
not
exist.
A
lot
of
people
think
that
cloud
native
is
explicitly
equal
to
containerization.
So
I
think,
even
if
we
change
the
terms
around
we'll
still
run
into
this
issue
of
people
saying
well
we're
running
a
cloud
native
thing.
H
Despite
the
fact,
it's
just
a
containerized
workload,
one
last
thing
as
well
of
aligning
the
cncf
to
the
industry
is
definitely
an
important
thing,
but
simultaneously
the
opposite
is
true
as
well.
Aligning
the
industry
to
cloud
native,
I
would
argue,
is
equally
as
important
in
the
sense
that
we
are
trying
to
have
an
effect
on
on
the
industry.
So
we
should
not
forget
the
goal
of
it
is
not
to
say
we're
aligning,
but
also
to
have
a
positive
influence
on
on
the
rest
of
the
community,
but
yeah
anyways.
H
I
just
want
to
toss
that
out
not
to
try
to
cause
any
significant
discussion,
but
just
to
put
some
some
thoughts
into
people's
minds
on
on
how
we
got
here.
C
B
We
can
do
it
now
and
if
there's
no
objection
yeah,
let's
just
see
where
we
can
get
with
it
talent
and
then
there's
so
there's
there
are
suggestions
to
update
in
here
that
I
guess
any.
This
is
for
everybody.
If
you,
if
you
put
a
pr
in
here,
everyone
can
help,
of
course,
but
it
is
coming
from
your
branch
or
you
know,
probably
your
own
repo.
B
B
But
some
of
these
would
be
like
this.
It
looks
like
it
may
be.
A
style
thing
bill
that
you're
noting,
and
this
would
be
something
cal
that
we
could
go
through
and
go
okay.
I
see
that
you're
just
making
a
suggestion
that
I
can
accept.
I'm
not
sure
if
you
have
to
pull
it
back
into
your
branch
or
whatever,
but
these
would
be
items
that
you
could
resolve
and
that
would
help
clear
out
the
cues
so
that
we
can
get
it
merged
faster.
C
C
B
You
put
this
in
because
it's
based
on
the
cncf
style
guide
for
what,
how
to
say
cloud
native,
I'm
I'm
supposing.
But
this
is
your
comment.
E
B
C
E
Yeah
this
is
like
the
debate.
This
is
what
was
chosen
at
like
the
beginning.
I
mean
this
is
quite
an
old
document,
so
that's
just
I
guess
how
cncf
chose
to
do
it
before
I
showed
up
so.
B
They
definitely
had
some
british
english
speakers
on
it,
so
I'm
sure
it
got
debated
across
the
board
for
people,
but
okay,
so
is
this
something
you
can
commit?
I
don't
know,
or
I
can
just
do
a
plus
one
for
me.
Tal
now.
C
I'll
commit
it
actually
bill
there.
There
are
other
places
that
I
use
cloud
native
with
a
hyphen,
so
I'll
change,
those
as
well
you'll
come
at.
E
H
Sure,
thanks
yeah,
the
the
heuristic
that
I
that
I
tend
to
use
which
may
not
align
with
the
cncf,
is
if
it's
a.
D
H
I
do
not
put
the
iphone
if
it's
a
adjective
I
do
which,
which
is
like
the
common
english
approach,
but
they
are
using
cloud
native
as
a
as
a
brand,
so
it's
possible
that
they,
they
don't
include
the
hyphen.
That's
with
speaker
for
that
reason,
but
yeah
these
are
conversations
way
above
my
head
in
terms
of
how
they
want
to
represent
their
brand
yeah.
C
Well,
I'll
just
be
consistent
because
bill,
you
noticed,
you
made
a
change
that
you
forgot
one
hyphen
to
remove.
That's
basically,
it.
C
Well,
yes,
but
but
we
are
saying
that
a
network
function
is
a
cloud-native
application
right,
cloud-native
design
principles,
I
think
refer
to
applications.
So
yes
in
our
world,
we
don't
call
them
applications.
But
if
you
want
to
talk
about
design
principles,
then
it
is
an
application.
C
C
D
B
Oh
other
places.
C
H
B
Yeah
I
I
would
prefer
to
go
with
the
common
and
then
if
we
have
a
real
world
example
where
it
it's
off
and
we
need
to
change
it
or
add
an
exception.
Then
we
do
that
versus
theoretical.
B
So
I'm
I
I've
been
using
applications
because
we're
talking
about
well,
primarily,
we've
been
talking
about
on
kubernetes
platforms
and
it
aligns
with
that,
but
even
on
non-kubernetes,
if
we're
just
saying
networking
software
that's
running
and
from
an
end
user
perspective,
so
that
could
be
like
a
service
provider
running
this
they're.
Thinking
of
the
the
application
running.
H
Yeah
and-
and
I
think
workload
in
I
know
in
the
kubernetes
documentation,
they
specifically
scope
it
down
in
general,
a
workload
can
be
either
physical
or
or
virtual,
but
an
app
but
application
itself
is,
is
clearly
or
I
guess
my
mind
is
clearly
software,
although
others
may
have
a
different
definition
for
it,
but
yeah.
I
think
it
really
comes
down
to
we
want
just.
How
do
we
want
to
scope
it?
Do
we
want
to
talk
about?
H
Do
we
want
to
talk
about
hardware
as
part
of
the
cnf,
or
do
we
want
to
say
the
application
itself
is
a
cnf
while
at
the
same
time,
even
if
we
take
the
software
approach,
we
still
acknowledge
that
there
may
be
hardware
integrations
that
we
may.
B
H
D
So
applications
are
typical,
typically
have
end
users
that
utilize
them
network
functions,
on
the
other
hand,
are
components
that
go
into
and
they
may
be
form
part
of
or
provide
traffic
through
which
applications
interface.
B
B
Well,
it's
that
said
most
of
the
world
would
say
a
dhb
server
is
an
application.
You
happen
to
be
using
it.
As
a
you
may
say:
it's
like
underlying
or
making
this
larger
network
that
everything
else
then
runs
on.
So
it's.
What
are
your
your
end,
users,
and
because
we
run
this
dhcp
application
as
part
of
our
infrastructure,
networking
that
then
stuff,
like
oh
you're,
your.
B
And
stuff,
but
even
say
this
vbng
so
or
broadband
network
gateway.
What's
special
about
this,
it's
it's
pushing
packets
between
this
side
and
this
side.
But
you
have
this:
you
have
the
same
functionality
from
layer,
4,
layer,
7
type
of
packet,
routing
things,
but
we're
calling
this
something
different,
because
it's
it
may
be
underlying.
You
may
have
an
application
on
top
that
does
layer,
7
routing
that
goes
on
top,
so
to
speak,
to
the
bng.
D
H
I
I
think
it's
a
good
suggestion
and-
and
I
think
part
of
it
comes
down
to
again
how
we
want
to
scope
it
down
and
how
we
want
to
interpret
it.
This
is
probably
something
that
should
absolutely
go
into
the
glossary,
though,
to
specifically
say
that
if
we
use
the
term
application,
we
we
should
make
sure
that
we
state
that
this
that
it's
not
just
end
user,
but
we're
talking
about
it
as
a
software.
Just
so
that
we
can
be
clear
about
it,
because
there
is
some.
H
There
are
some
differences
between
how
a
significant
portion
of
the
industry
uses
the
term
application
versus
when
you're,
when
you're
in
enterprise
versus
it's
very
common
for
for
people
to
mix
the
buffalo.
So
I
have
an
application
that
which
they
mean
that
you
have
a
demon
or
they
have
a
server
running
or
some
software
running.
But
then,
when
you're
in
the
telecom
space,
the
definition
may
be
much
more
precise.
H
B
All
right,
let's
try
to
move
the
pr
forward
so
tell
it
looks
like
this.
One
is
not
changing
anything.
I
don't
know
if,
if
the
suggestion
was
to
not
even
have
this
line
that
says
tbd
just
remove.
C
B
C
C
It
could
be
that
could
be
a
separate
pr.
You
know
I
didn't
remove
things
that
were
already
there.
I
tend
to
agree,
I
think,
there's
a
new
pr
from
alook
that
that
adds
a
whole
bunch
of
other
things,
including
filling
that
out.
So
we
can
maybe
deal
with
that
separately.
C
B
Right
now
we're
leaving
it
alone
we're
not
adding
a
definition
for
cube
right
that
wasn't
part
of
what
I
was
trying
to
do.
Okay,
so
resolve
it,
I'm
gonna
resolve
it.
C
B
Okay,
I'm
working
my
way
up
so
kubernetes
network
function,
a
clarified
network
function
deployed
on
kubernetes
note
that
k
nf
is
not
necessarily
a
containerized
network
function.
There
are
ways
to
employ
virtualization
and
containers
and
kubernetes,
indeed,
to
run
full
virtual
machines.
All
right,
that's
a
lot
of
extra
you're,
not
wrong.
C
C
It
could
just
help
us
in
discussions.
I
think.
B
So
that
we're
being
specific
on
that,
the
networking
application
that
someone
is
talking
about
so,
if
you're,
giving
an
example
and
a
best
practice
or
use
case
that
it's
explicitly
running
on
kubernetes
without
saying
it's
in
a
container
but
you're
saying
this,
networking
application
is
running
on
kubernetes,
correct.
B
C
B
C
C
Oh,
did
you
do
it?
I
did
not,
but
I
pushed
something
else,
so
you
know
what
let
me
just
do
it
on
my
end,
all
right.
B
If
you
just
press
on
the
right,
it
might
show
it
correctly.
Oh
I've,
I've
already
refreshed,
but
I'm.
B
Okay
and
then
this
one
is
exp.
This
is
kind
of
a
similar
one
where
we're
trying
to
at
least
call
out
that
we
recognize
that
if
something
is
only
in
a
container
that
we
could
say
that
because
like
as
said
in
this
one,
you
could
have
a
cloud
native
vm
running
on
kubernetes
and
you
could
have
a
containerized
network
function
that
doesn't
follow
any
cloud
native
standards.
I
guess.
I
B
C
E
B
I
think
frederick
made
this
point
earlier,
or
maybe
it
wasn't
a
comment,
but
does
this
help
us?
Why
are
we
putting
a
term
in
like
the
term
should
help
with
something
that
we're
discussing
versus
theoretical
discussion?
So
is
this
something
that
we're
already
referring
to
clarified.
H
B
H
I
think
this
may
relate
that
the
term
itself
is
new
to
me,
but
but
I
think
the
intention
may
have
come
from
conversations
that
that
ian
was
also
involved
with
some
of
the
conversations
we
had
was
what
what
does
it
really
mean
for
something
to
be
to
be
cloud-native
and
for
it
to
be
like?
H
How
are
we
using
the
term
and
how
are
we
describing
things
and
one
of
the
areas
that
we
found
that
there
was
some
contention
around
was
if
I,
if
I
was
in
a
if
I
was
in
a
cloud,
and
I
created
an
api
within
within
a
cloud
that
allows
you
to
let's
say,
create
a
firewall
on
demand
or
create
a
vpn
on
demand.
H
Is
that
being
considered
to
be
cloud
native
because
it
only
runs
in
the
cloud,
and
so
I
I
think
it,
the
term
very
likely
came
out
as
a
result
of
of
those
discussions,
though
I'm
not
sure
where
the
actual
queen
itself
was
was
termed,
but
that
that's,
my
guess
is
that
is,
is
it
has
to
do
with?
How
do
we
mean
cloud
native
which
is
very
specific
versus?
H
This
is
something
that
can
run
in
the
cloud
or
even
it's
provided
as
infrastructure
that
that's
part
of
a
cloud
or
designed
to
to
run
in
a
cloud
which
may
not
be
a
cloud
cloud
native
in
a
way
that
we
describe
it
as
being
something
you
can
horizontally
scale,
et
cetera,
et
cetera.
So.
C
Just
yeah,
that's
exactly
it
yeah!
I!
The
problem
is
that
in
some
conversations
with
people
who
are
not
on
board
with
don't
know
everything
that
the
cncf
is
about
and
think
that
it's
you
know,
it
just
means
running
things
on
kubernetes.
We
need
to
distinguish
these
things
and
say:
okay,
you
brought
your
cnf,
you
brought
your
network
function
to
kubernetes,
but
that's
not
enough.
If
you
want
to
be
classified
as
a
cnf.
That
means
following
our
best
practices
and
the
design
principles
for
cloud
native.
C
C
Well,
we
can
scroll
to
the
vnf
definition
definition
too
yeah.
We
had
some
discussion
about
that
as
well.
D
C
Well,
the
way
I
defined
it,
it
talks
about
the
technology
and
it
actually
doesn't
mention
the
word
cloud
at
all.
You
can
have
virtual.
C
It
mentions
containers
also,
while
I'm
mentioning
that
virtualization
technologies,
so
virtualization
does
not
have
to
be
specifically
with
a
virtual
machine.
Virtualization
right
agreed
agree.
D
H
H
I
I've
had
I've
had
significant
discussions
with
people
through
set
through
cnt
back
when
it
was
still
before
it
was
part
of
anakin
and
similar
about
this
exact
phrasing.
This
exact
term,
and
so
I
think
this
is
one
that
we
need
to
be
really
really
careful
with.
Is
you
know
in
terms
of
redefining
vnf,
because,
like
re,
defining
cnf
like
we
came
up
with
the
term,
but
the
term
vnf
originates
from
etsy
and
has
a
very
specific
meaning
within
etsy
that
that
will
end
up
fighting.
H
So
we
want
to
be
careful
that
we
don't
conflict
with
that
definition.
We
we
could
say
if
we
wanted
to
restrict
our
usage.
H
I
think
it
would
be
okay
to
say
that
when
we
describe
dns
we're
explicitly
talking
about
virtual
vm
based
systems,
but
also
make
it
clear
that
we're
that
we're
not
aiming
to
to
derail
the
the
etsy
term,
I
I
think
we,
I
think
we
should
be
very
careful
on
how
we
approach
that.
B
You
can
go
back
through
and
try
to
respond
to
as
many
of
these
as
possible,
and
then
I
think
the
one
that
I
can
see
that
may
not
be
in
here
is
what
is
the
definition
of
cloudify
and
that
that
would
expand
on
this.
So
clarified
network
function,
but
that's
the
only
one
I'm
seeing,
but
if
you
can
just
go
through
and
then
we'll.