►
From YouTube: CNF WG Meeting 2021-05-10
Description
CNF WG Meeting 2021-05-10
A
B
B
B
B
B
B
B
The
different
groups
and
people
that
care
about
these
things,
which
will
be
helpful
when
we're
talking
and
collaborating
with
other
groups
so
that
they
can
say
who's
involved,
and
how
does
this
relate?
So
please
add
yourself
there.
I
think,
there's
a
pr
to
add
some
reasoning
at
the
top,
but
I'm
not
seeing
it
here.
So
I'm
not
going
to
worry
about
that.
B
If
you
have
been
working
on
some
of
the
prs,
then
you
may
have
seen
the
checks
that
are
happening.
There's
multiple
types
of
checks,
including
linting,
and
the
pr
process,
has
been
updated
to
say
at
the
moment.
We
would
prefer
that
everything
passes
lenting,
but
there's
been,
as
we've
been
going
through
the
whole
repo
a
lot
of
little
updates.
So
it's
not
a
hard
requirement.
B
D
B
D
D
B
A
E
B
All
right
where
I
can,
I
can
work
with
you
and
get
all
those
in.
Let's
see
what
what
else
do
we
have,
though,
on
this
one,
because
this
is
one
that
we've
had
open
for
a
while?
Are
we
at
a
point
other
than
those
I'll
say,
minor
lending
issues
we
could?
Even?
I
would
call
that
one
minor,
those
type
of
things
is
minor
and
we
can
always
come
back
and
do
a
second
pr.
F
B
F
What
I
would
say
is
if
we're
getting
lint
failures,
we
don't
actually
like
very
much,
then
I'm
sure
we
have
control
over
what
lint
rules
the
thing
applies.
So
if
we
want
to
basically
get
rid
of
rules
because
they
cause
us
problems
and
have
no
benefit,
then
that
is
a
perfectly
acceptable
approach.
That's
one
thing.
A
F
You're,
not
the
only
one.
I
had
the
same
problem
when
I
was
looking
at
this.
I
got
to
the
end
of
it
eventually,
but
realizing,
firstly,
how
to
find
that
a
file
has
failed,
and,
secondly,
that
that
message
is
just
a
summary
and
there
is
more
clues
higher
up,
basically
giving
you
indications
of
what
the
failure
is
that
one
itself
was
a
bit
a
leap
of
deductive
reasoning
that
took
some
doing
and
it
sounds
like
you're
doing
exactly
the
same
on
this
call
that
you
know.
F
B
D
C
B
Is
it
we're
not
really
looking
at
like
an
entire
pass
fill
for?
I
don't
I
don't
care
about
all
the
positives.
It's
which
ones
actually
didn't
pass
all
right,
but
we
can
do
that
off
and
maybe
just
to
take
it
and
do
a
round
of
adjustments
on
that.
We've
heard
a
lot
of
the
same
feedback
other
than
lenting.
So
what
are
the
other
things
luke
that
we
can
work
through?
I'm
saying
some
stuff
here
is:
is
this
something
for
this
ticket
or
I
mean
pr?
Do
you
want
to
open
something
new.
D
B
D
B
Yeah
absolutely
and
best
practices
could
point
to
more
than
one
use
case,
of
course,
since
they
can
be
used
in
more
than
one
use
case.
So
this
one
may
be
as
you're
saying,
like
an
umbrella,
larger
one,
and
then
we
may
have
a
best
practice
that
also
points
to
a
more
focused
small
use
case
that,
for
example,
test
case
even
if
it
gets
down
to
that
all
right.
So
I'm
trying
to
find
the
one
that
you're
saying
there's
still
one.
B
B
B
D
B
D
B
B
I
B
D
B
Second,
all
right
we'd
just
like
to
get
this
one
in
since
it's
it's
been
open
for
a
while
and
over
we
keep
approving,
and
then
there
will
be
weeks
later.
Someone
will
have
another
comment,
and
what
we
really
want
to
do
is
those
type
of
things
should
be
another
pr
or
ad
comments
to
the
existing
stuff,
rather
than
keeping
it
open
for
forever.
B
F
B
G
B
G
B
G
H
B
B
Meeting
stuff,
so
if
people
are
trying
to
encourage
people
to
come,
then
where
the
meetings
are
happening,
getting
involved
from
issues
first
issues,
this
is
about
the
lenting
stuff
saying
that
how
to
do
it,
including
the
make
file
that
victor
mentioned
earlier,
if
you
want
to
run
it
local
and
then
the
main
things?
Okay,
I
don't
know
why
this
is
not
visible.
I'm
going
to
skip
that.
B
Okay
links.
Okay!
Here
we
go
so
the
main
reason
this
pr
is
in
place
was
this
top
portion.
So
what
is
interested
parties
about
so
expressing
an
interest
in
these
topics?
Then
add
your
name,
an
organization
and
a
pr
and
then
communicating
that
it
could
grant
you
some
rights,
including
capabilities
to
vote
if
you're
listed,
but
it
doesn't
imply
any
obligation
to
you
or
the
organization,
including
legal,
just
to
make
sure
if
people
need
that
from
your
side,
we've
added
that
and
I
think
the
rest
are
kind
of
like
links
and
typos.
B
A
B
B
H
B
H
B
I
think
it
would
be
good
to
try
to
work
with
the
global
as
much
as
possible.
I'm
I'm
actually
supposed
to
have
a
call
with
katherine
and
this
katherine
and
jason
right
here,
jason
morgan,
who
are
leading
on
this.
They
had
a
talk
during
kubecon,
so
I
wanted
to
get
some
feedback
on
what
they're
doing
and
talk
with
them
about
the
cloud
native
principles,
papers
and
stuff.
But
I
I
think
it'd
be
a
good
idea
to
try
to
push
as
much
upstream.
So
it's
global
to
all
of
cncf.
H
Yeah,
I
think
if
we
disagree
with
those
terms,
or
we
don't
feel
they
go
far
enough,
we
should
be
this
group
should
kind
of
advocate
across
the
cncf
holistically
to
get
like.
You
know
our
thoughts
once
desires
out
there,
but
then
it's
a
lot
less
work
on
us
and
we
don't
have
to
deal
with
conflicting
points
of
view
if
our
glossary
is
as
cnf
specific
as
possible,
and
we
just
adopt
terms
where
it
makes
sense.
B
B
So
then
what
is
a
cloud
native
application
and
there's
some
of
that
over
here?
What
is
this
is
a
cloud
native
app.
So
what
is
a
cloud
native
application
and
then
we
go
on
to
be
explicit
and
say
it's:
this
application
is
implementing
network
functionality,
so
there's
lots
of
applications
out
there,
and
this
one
is
about
network
functionality.
B
This
still
could
be
good.
Jeffrey
I'd
like
to
hear
your
thoughts,
because
we
are
talking
about
best
practices
and
they're,
not
really
getting
into
best
practices,
so
we
could
say
that
we're
expanding
on
what
they
have
so
taking
advantage
of
cloud
resources
and
scaling
capabilities,
and
all
these
other
things
and
then
how
to
do
it.
This
would
be
the
best
practices
and
thinking
cube
native.
B
J
H
H
H
At
some
point,
though,
I
do
think
we
should
be
more
explicit,
like
I
like
the
glossary
definition,
it's
kind
of
the
stuff
that
ian
always
harps
on
around
it
runs
in
a
cloud
which
is
good
like
at
a
broad
level,
but
then
you
know
what
is
the
cnf
itself
just
saying
it's
a
network
function
that
runs
in
a
cloud
I
mean
that
is
technically
an
accurate
definition.
I
don't
know
if
it's
a
useful
definition,
though.
J
H
Yeah-
and
I
mean
I
agree
that
maybe
it
talks
about
the
verbage
could
be
cleaned
up.
Maybe
maybe
we
don't
approve
this
right
now
or
we
do
we
approve
it,
and
then
we
do
more
stuff,
but
maybe
it
could
be.
It
should
be
more
instead
of
consists
of
one
or
more
microsoft
can
be
consumed
as
a
microservice
right,
and
but
I
mean
things
like
loose
coupling.
I
mean
that
it
doesn't
say
that
your
services
inside
have
to
be
loosely
coupled.
H
J
H
J
J
I
didn't
I
in
terms
of
accepting
this
pr
or
not
I'm
actually
in
favor
of
accepting
a
lot
I
we
can
always
add
more
and
more
prs
later
I
my
advice
would
be
to
iterate
quickly
and
keep
adding
more
and
more
iterations.
So,
even
if
I
don't
I'm
not
entirely
happy
with
what
I
see
here,
I
would
still
approve
it
and
think
of
it.
Okay,
this
is
a
contribution
and
it's
a
good
contribution
and
we'll
keep
moving
forward.
J
F
B
F
J
H
Well,
I
just
say
like
it's
good,
to
discuss
this
stuff,
though,
because
I
mean
I
just
pulled
that
out,
I
mean
yes,
I
like
helped
build
that
originally
in
the
jug,
but
I
agree
that
it
does
force
architectural
opinion
in
there.
So
maybe
we
just
move
all
of
the
specific
references
out
of
there
like
microservices,
loosely
coupling
or
declarative
apis,
and
we
just
boil
it
down
purely
to
it
follows
cloud
native
principles
and
those
can
be
discussed
off-site
and
that
I
do
think
that,
it
being
you
know,
a
repeatable
deployment
process.
F
F
B
So
it's
a
work
in
progress,
the
new
definitions,
not
the
def,
the
main
cncf
definition
doc
at
the
top
level.
This
glossary
project,
I
think,
is
the
reference,
but
we
have
never
really
talked
about
this,
because
this
is
brand
new
and
it's
I've
already
had
multiple
people
that
are
working
on.
This
say
that
it's
just
a
start.
It's
not!
E
Tal
I
like
what
you
said
earlier
about
iterating
quickly.
You
know
when,
when
kind
of
picking
apart
this
definition
or
what
jeffrey
gave
right
is
it,
it
could
be
argued
that
if
you
take
an
example
like
a
control
plane
network,
essentially
like
calico
or
psyllium,
or
something
like
that,
that
is
comprised
of
microservices.
E
J
Yeah
right,
so
I
I
I'll
add
another
point
specifically
about
the
the
other
gloss
theory.
That's
a
work
in
progress
taylor,
as
you
said,
I
I
think
it's
good
for
us
to
define
cloud
native
for
the
terms
of
the
work
group,
so
I'm
actually
not
necessarily
I'm
in
favor
of
referencing,
maybe
the
other
glossary,
but
I
think
in
terms
of
defining
what
a
cnf
is.
J
We
can
define
what
cloudv
cloud
native
means
for
specifically
for
cns,
because
it's
not
just
a
regular
application,
and
I
wonder
I
wonder
too,
you
know
I'm
thinking
out
loud
here
that
it
it
could
be
a
matter
of
degree
right,
there's,
not
a
there's,
not
a
clear.
Suddenly
you
look
at
the
network
function.
Okay,
this
is
a
true
cnf,
or
this
is
partially
cloud
native
or
it's
cloud-native
in
some
ways
and
not
very
cloud-native
in
other
ways.
J
So
maybe
the
definition
should
be
about
criteria
even
a
list
of
criteria
that
that
would
work
in
terms
of
okay.
You
know
we.
We
either
cover
all
the
criteria
for
a
network
function
or
not
and
to
an
extent
it
could
be
aspirational
in
terms
of
becoming
a
very
good.
A
very
cloud
native
network
function.
Right,
I'm
not
sure
myself,
I'm
thinking
out
loud
and
and
maybe
I'll
turn
my
thoughts
into
a
pr
as
well.
So
we
could.
J
H
Scroll
down
taylor
yeah,
so
on
that
I
I
took
a
bunch
of
stuff
out
real
quick,
I'm
I'm
a
fan
of
the
move
fast,
but
I
also
don't
want
to
just
put
junk
in
there.
So
I
stripped
a
bunch
of
stuff
out
with
the
hopes
of
us
having
a
more
neutral
starting
point.
We
can
just
put
more
prs
against
it.
I
don't
know
if
this
helps.
D
It
definitely
helps
I
mean
it's
probably.
We
are
writing
definitions
and
some
documents,
but
we
are
still
on
the
github
and
if
you
look
at
how
the
code
evolution
happens,
actually
it's
exactly
the
iterative
process.
The
first
commit
is
always
something
that's
maybe
half-baked,
and
then
it
gets
expanded
by
community,
but
it
doesn't
prevent
it
from
being
a
commit
or
being
pushed.
D
J
J
J
J
B
B
Some
of
these
properties
are
stuff
that
are
listed
when
we,
if
you
dig
through
the
glossary
the
definitions
over
here,
they
have
all
sorts
of
stuff,
including
talking
about
microservices
and
loose
coupling
and
immutable
infrastructure,
is,
is
all
part
of
this,
so
these
would
be
properties
that
you
would
see.
It
doesn't
mean
that
I
guess,
if,
if
you
had
a
single
well,
actually
these
are
all
high
level,
so
you
may
not
use
every
best
practice
and
I
guess
it
may
not
have
every
property
if
it's
not
actually
part
of
it.
B
B
H
Gotta
take
in
mind
like
scope
and
audience
so
when
we
wrote
this
for
the
tug
it
was
when
we
were
trying
to
intentionally
opinionate
and
provide
context
with
the
definition
versus
I
don't
know,
I
mean
I,
I
know
why
you
want
them
in
there.
My
hope
would
be,
though,
that,
like
the
best
practices
that
feed
off
of
this
would
be
where
we
we
have,
you
know
best
practices
that
show
you
should
be
loosely
coupling,
but
I
mean,
unless
we're
giving
a
very,
very
verbose
definition
in
trying
to
shape
opinion
within
the
definition
itself.
H
You
know
it's
like
the
news.
Are
we
reporting
the
news,
or
are
we
giving
a
syndicated
opinion
on
something
kind
of
deal
like?
What
is
our
goal
with
this
glossary?
Is
it
to
just
provide
baseline
context,
or
is
it
to
kind
of
shape
influence
opinion
from
those
outside
of
our
small
collective
here?
When
they
come
in
and
read
this
stuff,
I
actually
would
prefer
kind
of
more
the
just
generic
news
standpoint.
H
You
know
now
that
I've
had
time
to
stew
on
this
and
then
let
the
best
practices
try
to
guide
people
towards
loose
coupling
immutable
infrastructure
etc,
and
I
did
leave
cloud
native
principles.
You
know
as
a
development
consideration
in
there,
which,
I
think
should
also
kind
of
I
don't
know
imply
that
some
of
these
things
are
followed.
B
B
C
J
I
believe
so
I
I
want
to
add
a
point
to
what
you
said
jeffrey
about
you
know,
reporting
the
news,
and
it
goes
back
to
a
point
very
early
on
that
shane
made
where
you
know
he's.
We
had
this
big
argument
if
cnf
really
means
container
right
and
we
all
agree
that
it
doesn't,
but
we
also
have
to
acknowledge
that
people
use
the
term
cnf
already
very,
very
widely,
and
often
it
simply
means
a
network
function
running
in
kubernetes.
That's
it.
J
It
doesn't
talk
about
if
it's
running
in
a
good
way
or
if
it
works
correctly,
with
kubernetes
or
or
anything
else.
So
so
I
guess
I'm
saying
that
for
for
our
purposes
it
should
be
descriptive
right
and
should
describe
how
people
are
actually
using
it,
and
then
we
can
say
well
how
do
you
build
a
good
cnf
and
that's
not
part
of
the
glossary?
That's
one
of
the
goals
that
this
whole
work
group
is
aiming
for.
I
think
right.
B
I've
committed
that
change.
It's
I
don't
know
where
I
cut
out,
but
it
sounded
like
your
approach.
Jeffrey
was
to
tackle
all
of
the
properties
that
would
be
part
of
cloud
native
applications
and
the
best
practices
as
those
are
going
on
the
way,
those
get
added
immutable
infrastructure
and
everything.
So
do
you
want
to
have
something
like
this
cloud
native
application,
a
link
there's
a
reference
to
linking
like
that.
H
So
real
quick
too,
before
we
do
this,
let's
chat
with
the
group
here
is:
do
we
want
to
do
in-band
links
like
that
or
if
the
the
main
thing
you
know,
we
put
a
little,
it's
gonna
say
glossary,
but
this
is
the
glossary
little
index
at
the
bottom.
You
know
linking
like
for
like
the
kubernetes
definition.
I
go
my
link
to
kubernetes.org
their
docs
and
stuff
just
to
show
people
that
I
didn't
create
my
own
definition
for
kubernetes.
H
H
J
B
B
E
K
K
K
E
K
K
F
B
F
B
F
F
H
H
H
B
J
Still,
you
know
not
all
cnfs
are
developed
with
cloud
native
principle,
we're
kind
of
stating
what
a
cnf
should
be
at
best.
But
again
this
glossary
support.
Glossary
is
supposed
to
be
useful
for
us
right.
So
it's
a
lot
of
times
we're
going
to
be
talking
about
cnfs
that
might
not
be
developed
using
cloud
native
principles
very
well,
but
they're
still
part
of
our
deployment
and
we're
still
working
with
them.
J
F
D
J
J
B
J
B
J
A
A
B
J
A
B
B
B
We
have
enough
approvals,
I'm
going
to
I'll,
send
this
to
everybody,
but
I'll
make
the
change
for
the
capitalization
to
be
consistent
and
have
that
in
the
commit,
and
then
I
think
we're
good
the
next
time
we're
here.
Maybe
we
can
talk
with
folks
about
the
new
use
cases,
so
we
have
a
stateful
and
a
5g
use
case.