►
From YouTube: CNCF Reference Architecture - 2018-06-13
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
A
Okay,
can
I
I
think
we
could
go
ahead
and
kick
it
off
and
I
want
to
just
throw
out
a
proposal
here
that
I
think
any
kind
of
categorization
or
taxonomy
just
necessarily
is
limited
and
so
I
think
we
should
just
throw
them
all
into
the
same
bucket
together
and
just
say:
these
are
all
automated
sure.
B
B
Right
yeah,
definitely
as
I
want
to
kind
of
do
today
was
just
sort
of
you
know
kind
of
talk
a
little
bit
about
what
the
original
reference
architecture
came
from
back
before
Dan
actually
took
over
the
helm,
which
has
been
very
helpful
having
Dan
on
board.
We
had
this
really
ugly
diagram
in
our
Charter
that
just
looked
like
nothing
named
I
would
recognize
as
a
reference
architecture,
and
so
some
of
the
TOC
is
we
were
forming.
B
Deck
was
put
together
quite
a
while
ago
and
so
I
kind
of
draw
the
initial
end
user
reference
architecture
and
we
kind
of
what
we're
targeting.
You
know
very
simple
use
cases
of
you
know
what
is
what
does
a
cloud
native
stack
look
like,
and
so
we
spent
a
little
bit
of
time.
Looking
at
my
mouse
over
this
kind
of
a
at
the
top
of
that
stack,
you
know
what
it
means
to
be
containerized,
what
distributed
orchestration
and
management
means
and
what
micro-services
architecture
and
those
are
sort
of
the
three.
B
If
you
guys
remember
back
in
the
the
Charter,
you
know
what
are
the
the
three
things
that
make
something
cloud
native.
It
was
those
three
things,
and
so
we
try
to
sort
of
say
what
do
those
three
things
relate
to
in
a
end-user
type
of
reference
architecture,
and
then
we
sort
of
ended
up
developing
this
sort
of
a
model
where
we
we
want
to
kind
of
capture
at
the
bottom
that
there
is.
You
know
infrastructure
of
some
kind
underneath
this
reference
architecture.
B
A
A
What
one
more
piece
of
context
I
included
a
link
in
the
chat
window
to
the
CNCs
charter
and
I,
have
the
aspiration
in
the
next
month
or
so
to
get
the
governing
board
to
agree
to
delete
it
away
entirely
and
replace
it
with
that
two
paragraph
cloud
native
definition
that
the
TOC
just
occurred
last
week
right
and
so
when
you
can,
when
that
happens,
that
old,
out-of-date
like
three-year
old
reference
architecture
will
go
away
forever.
Yep.
B
Exactly
and
so
I
wanna,
you
know,
one
of
the
options
we
have
in
this
group
is
to
you
know,
come
up
with
a
new
reference
architecture
that
we
places
that
existing
one
we
also
I,
think
had
the
ability
to
kind
of
update
that
existing
user
reference
architecture,
taking
into
account
some
of
the
landscape
work
that
we've
done
and
the
CNCs
it
I'm
showing.
Hopefully
this
did
this
show
up.
B
Finally,
for
you
guys
to
you
see
it
on
the
screen
yep,
and
until
we
could
kind
of
update
the
we
could
add
two
different
architectures
one,
this
kind
of
an
end
user,
the
one
that
that
you
know
could
go
more
technical.
If
we
wanted
to,
we
could
just
we
had
that.
Just
that's
something
we
can
decide.
We
want
to
say
it
today,
but
what
I
liked
about
the
work
that
the
Dan
has
led
I'm
in
an
active
landscape?
B
Is
it
it
kind
of
you
know
leverages
if
you
look
on
the
left
hand
side,
it
kind
of
leverages
the
same
high
level
aspects
of
the
user
reference
architecture,
as
we
discussed
previously
and
things
in
the
next
level
down
right.
So
it
kind
of
talks
about
the
different
aspects
of
the
app
definition
and
development,
the
different
aspects
of
orchestration
management
and,
again
going
back
to
what
you
know
dan
was
just
saying,
with
the
new
definition
can
update
both
of
these
at
the
same
time,
right
and
then
what
I?
B
What
I
submitted
to
the
CN
CF
a
few
months
ago
was.
Was
this
right
sort
of
a
you
know,
high-level
picture
of
kind
of
you
know,
thinking
about
the
cloud
native
architecture
more
logically,
you
sort
of
get
this
model
of
there's
really.
You
know
these.
These
orchestration
pieces,
these
components
where
you're
trying
to
observe
and
and
and
monitor,
what's
going
on-
and
you
have
this
optimization
aspect
which
led.
C
B
You
know
kind
of
looking
at
maybe
this
as
a
logical
starting
point:
it
kind
of
pulls
together
the
reference
architecture,
the
the
end
user,
reference
architecture
and
the
interactive
map
right
to
sort
of
give
you
a
single
view
of
you
know.
These
are
the
three
main
components
that
make
up
the
logical
architecture,
and
you
know:
here's
how
they
sort
of
coil
way
to
these
different
aspects
that
are
captured
in
the
reference
architecture,
and
so
this
was
kind
of
like
a
where
that
would
be
a
good
starting
point
for
discussion.
B
Happy
to
you,
know
kind
of
open
up
to
to
discussion
now
and
sort
of
see
if
there's
any
any
thoughts
on
first
of
I,
guess
the
chart
of
what
we
want
to
do
in
this
working
group
and
then,
secondly,
we
can
get
into
you
know.
If
there
are
some
people
who
have
other
ideas
they'd
like
to
share,
we
could
start,
you
know,
collecting
those
ideas
and
communicating
them
when
we
meet
every
two
weeks.
E
D
B
I
really
think
this
logical
architecture,
a
starting
point
to
me,
is
more
of
hugging,
a
technical
audience
and
probably
wants
to
be
want
to
get
more
technical
with
what
the
architecture
looks
like
and
how
these
interfaces
work
together
for
cloud
native.
But
that's
just
my
opinion
open
to
like
what
other
people
think
of
you
know
one
or
two
views
of
an
architecture,
and
if
we,
you
know
need
to
go
more
technical,
we
need
to
go
more
marketing.
D
Yeah
I
mean
from
the
second,
when
we
had
discussed
this
logical
architecture
slide.
You
know
a
couple
months
ago,
I
think
the
the
impetus
for
sort
of
the
design
was
to
take
from
to
go
from
a
market
map
to
something
sort
of
more
functionally
in
capability
driven,
which
was
intended
to
give
people
sort
of
a
view
of
how
these
things
plug
into
each
other
and
importantly,
help
folks
as
a
decision-making
kasam.
D
In
terms
of
like
what
the
blueprint
for
a
cloud
date
of
architecture
could
look
like
and
the
the
challenge
I
have
with
market
maps
in
general,
you
know
either
as
an
investor
as
a
consumer
of
technology,
is
that
they're
they're
quite
noisy
and
there's
a
there's
a
lot
on
there,
and
so
by
cutting
it
from
a
sort
of
capability
driven
architecture
first
and
then
showing
that
really
you
know
these
are
these
are
taking
a
view
on.
These
are
the
few
things
that
matter
and
the
visa
technologies
within
those
buckets
are.
D
B
D
And
so
that
was
the
original
intention
and
I
still
yeah
I
still
think
like
having
a
it's
difficult
in
the
context
of
sort
of
like
a
competing
foundation.
I
think
because
you
know
I,
don't
know
what
the
appetite
is
to
take
a
view
on
putting
forth
like
one
or
two
technologies
is
first
in
front
of
pockets
of
technologies,
I'm
always
of
the
view
that
it's
good
to
sort
of
have
a
suggestion
or
a
recommendation,
but
I
think
for
me.
You
like
this.
Would
this
would
make
a
lot
of
sense
as
a
certain
point,
yeah.
B
So
just
I
mean
I
just
a
couple
real
quick
points
and
definitely
agree
with
I.
Think
that
that
was
my
view
going
into
this.
And
if
you
look
at
the
landscape,
you
know
we
do
have
like
CN
CF
incubating
CNC
have
sandbox
and
like
kubernetes,
the
CNC
F
graduated,
and
so
we
do
have
you
know
I,
don't
think
we
are
opposed
as
a
community
is
something
that
you
know.
B
Obviously,
I
can
now
take
back
to
the
TOC
at
our
next
meeting,
but
based
on
our
discussion
today,
I,
don't
believe
that
you
need
to
be
worried
or
constrained
to
whether
or
not
the
CNC
F
wants
to
get
more
technical
and
define
more
of
the
blueprints
and
the
components
and
the
architecture
on
how
these
things
should
connect
together
and
work
together.
We
don't
want
to,
basically
you
know,
select
other
than
the
projects
that
we
already
have
in
the
landscape.
B
We
don't
want
to
whether
in
the
community
we
don't
want
to
necessarily
select
one
as
the
winner
as
or
as
the
way,
but
you
know
like.
We
have
something
like
CNI
from
the
network
side.
That
is
a
reference
implementation
of
a
network,
interface
right
and
so
I.
Don't
think.
We
are
necessarily
opposed
to
saying
here's
the
way
we
see
that
architecture
coming
together
technically,
but
we're
not
going
to
sit
back
and
say
that
this
one
solution,
this
one
technology-
is
the
only
way
to
do
it.
If
that
makes
sense.
B
A
Just
the
previous
question,
I
feel,
like
the
architecture
in
the
form
of
the
landscape
has
had
tons
of
different
audiences,
so
actually
marketing
document.
We
have
legal-sized
printouts
that
were
giving
out
today
at
dr.
Khan.
We
had
the
trail
map
on
the
front
side
and
the
landscape
on
the
back
of
it.
I
also
think
it's
useful
as
a
technical
document,
where
I've
heard
from
well
I
guess
I
put
Brian
Grant,
who
has
both
time
called
it
useful
and
then
time
called
into
hellscape
that
they.
A
Here,
sometimes,
if
you're
trying
to
understand
an
area
like
key
management
or
secure
images
or
such
to
say
what
are
the
author's
here,
one
of
the
close
sorts
and
the
open
source
ones
and
the
comprehensive
nature
of
what
we've
done,
I
think
has
been
useful,
eaten.
The
overwhelming
aspect
of
it
I
feel
like
the
trail
map,
has
been
some
antidote
for
not
not
necessarily
a
perfect
one,
but
I
think
the
simplest
answer
is
if
this
architecture
work
has
a
variety
of
audiences.
A
I
would
probably
make
a
distinction
that
we
have
had
an
aspiration
over
the
last
year
or
so
within
CNC
app,
and
it
failed
so
far
to
delivery
of
doing
what
I've
described
as
pattern
work
where
rending
Burns
had
created
a
document
on
talking
about
different
cloud
native
patterns,
and
we
had
hope
to
have
a
series
of
blog
posts
around
eggs
and
illustrations
about
patterns
that
work.
Things
like
a
circuit,
breaker
or
nary
releases
or
psych
Park,
and
there's
really
dozens
and
dozens
of
them
over
time.
B
Yeah
I,
definitely
I,
guess
I,
guess
some
media
and
it
might
be
more
of
the
unusual
reference
architecture
goes
away
and
we
leverage
the
landscape
for
that
aspect.
Right
then,
but
we're
defining
there's
actually
the
world
reference
architecture
and
just
more
technical
down
below
this
that
make
me
might
make
a
lot
more
sense
because
you,
you
really
don't
need
a
landscape
in
use,
a
high-level
reference
architecture,
in
my
opinion,
but
again
I'm
open
to
others.
Other
thoughts
on
that
I'm
I'm.
C
A
hi
this
is
Paul
Fremantle,
I,
don't
I'm,
not
sure
I
agree
because
I
think
I
think
the
the
high
level
reference
architecture
is
really
what
a
customer's
reference
architecture
is
going
to
be
right,
right
and
I.
Think
that
that
you
know
these
projects
I
think
there's
a
need
to
address
it
from
the
customer
viewpoint
first
and
then
help
the
customer
see
how
to
fit
these
projects
in
and
I
think
that
the
the
landscape
is
sort
of
you
know,
because
there's
so
many
projects
hidden,
he
inevitably
has
time
a
product.
C
First
focus
in
a
way
and
I
know:
I
know
it's
not
really
that,
but
it
does
have
a
bit
of
that
and
I
think
that
I
I
think
it's
worth
at
least
exploring
what
a
what
a
enter
point
higher
level
enterprise
architecture
would
look
like
independent
from
this
and
then
going
into
the
details
of
the
enterprise
architecture.
Yeah.
B
F
B
B
Thought
that
I
know
Dan
introduced
himself
I'll
induce
my
self
quickly.
I
am
on
the
TOC
I
look
at
MasterCard
and
I
was
one
of
the
original
founding
or
even
call
like
founding
companies
when
I
was
at
Cisco
for
for
the
CNC
F
and
so
I've
been
looking
a
lot
of
different
projects
and
helping
Lobby
different
projects
mature
and.
G
Fine,
hey
Joe,
Carvalho,
Intel,
I'm,
a
senior
architect
and
the
software
services
group,
formerly
data
center
group
and
I've,
actually
been
a
part
of
the
San
CF
for
quite
a
long
time
back
when
Intel
actually
built
a
bare-metal
scale.
Cluster,
and-
and
can
you
and
I
were
on
a
on
a
panel
way
back
then
so
happy
to
be
back
in
this
conversation
and
to
be
a
part
of
this
effort,
yeah.
G
H
H
I
B
F
G
K
K
D
C
C
My
name's
Paul
Fremantle
and
I'm
the
CTO
at
wa2
we're
an
integration
vendor.
We
just
compete
with
with
Red
Hat
and
mule,
and
people
like
that
and
we've
been
I've
actually
been
over
the
last
few
months,
trying
to
develop
our
own
reference
architecture
around
what
and
how
kind
of
enterprise
architecture
is
evolving.
B
Make
deal
with
me
twice
so
I
thought!
No,
that's
right!
That's
gonna
make
sure
you're
on
here
twice
so
didn't
want
to
miss
it.
There
was
somebody
else
saying
with
that
radiation,
so
alright
cool,
so
I
apologize
for
the
introduction
it's
late,
but
I'm
not
used
to
I'm
used
to
like
run
around
but
not
fires.
These
days,
so
I'm
not
used
to
running
community
meeting.
So
oh
I'll
get
better
at
the
promise.
Okay,
it's
coming
back
to
me
slowly,.
B
B
And
so-
and
you
know
in
talking
with
with
Dan
and
then
Jacob
in
the
TOC,
we
seem
to
be
interested
in
kind
of
using
this
as
a
starting
point
and
I
guess
what
I'd
like
to
you
know.
You
don't
have
to
kind
of
go
into
a
lot
of
details
today.
This
is
kind
of
like
a
kickoff
meeting
in
a
way
for
what
we
want
to
try
to
do
with
this,
and
obviously
it's
gonna
take
a
few
meetings.
It's
sort
of
get
some.
You
know
momentum
and
you
know
start
making
some.
B
You
know
forming
some
opinions
on
what
to
do,
but
in
terms
of
these
areas,
you
know
you
got
sort
of
these
three
main
buckets
of
monitoring,
service,
communication
and
August
raishin
and
then
sort
of
the
the
components
that
make
up
different
parts
of
a
logic,
architecture,
security,
complaints,
I,
can
change
delivery
platform
management,
cloud
log,
analytics
account
management,
discovery
and
planning
for
services
in
the
container
registry.
Does
this
seem
like
you
know?
B
C
C
F
D
So
the
intention
of
this
was
to
present
a
logical
view
and
then
take
a
point
of
view
on
what
technology
is
really
differentiated
and
if
you
were
gonna-
and
you
know,
resources
are
limited
everywhere
and
so,
if
you're
going
to
invest
in
a
set
of
technologies,
the
new
with
that
reason
with
you
know
these
are
the
three
starting
points
and
then,
if
you
cook
everything
else
into
these
three
buckets
monomeric
service,
communication
negotiation,
everything
else
stems
from
there.
The
context
is
broadened.
D
I
think
this
is
originally
intended
solely
for
micro
services
and
we
really
meant
more
of
a
blueprint
sure
what
we
could
do,
and
but
the
intention
of
this
was
to
take
a
view
on
saying:
hey,
there's
really
only
so
many
things
that
matter
and
those
are
the
key
decisions,
and
if
you
get
those
right,
everything
else
will
follow.
But
I
agree.
I!
Think
that
you
know
it's
a
good
starting
point
by
the
golf
cart
I.
B
C
B
Always
working
with
my
developers
on
now
is:
how
do
you,
you
know,
get
metrics
and
understand
what
services
and
you
know,
associate
master,
got
really
worried
about
the
security
of
these
micro
services,
and
so
how
do
you
know
that
the
service
that
you
discovered
is
the
right
service
and
the
actual
service?
You
think
it
is.
B
That's
a
good
question:
to
date:
we've
sort
of
used
the
CN
CF
website
is
kind
of
a
way
to
to
have
a
clickable
drill
in
to
these
different
components,
and
so
it's
been
very
much
an
online
sort
of
view.
With
the
serverless
work
group,
we
did
do
a
white
paper
and
while
the
white
paper
is
still
available,
online
I
would
not
be
a
host.
B
B
And
these
you
know
me
I,
put
like
on
William
and
Cody
and
incriminates
on
this
original
one,
because
those
are
CNC
F
projects,
it
kind
of
fit
in
here,
I
I-
think
I
had
Prometheus
home
at
some
point.
You
know
what
happened
to
it,
but
you
know
I,
don't
I,
don't
I
was
just
kind
of
using
this
to
kind
of
help.
B
H
B
Yeah,
ideally
kind
of
like
we
did
with
the
user,
the
end
user
reference
architecture
and
the
landscape
I'm,
hoping
that
there's
a
pretty
obvious
mapping
of
you
know
what
the
reference
the
logical
architecture
provides,
what
sort
of
fits
into
that
and
then
where
there
are
gaps
that
we
have
identified,
that
are
still
needed
to
kind
of
your
point.
Annie
does
that
make
sense,
yeah.
B
We
ready
to
discuss
then
I
want
to
kind
of
just
make
sure
that
it's
easier
to
kind
of
see
how
they
fit
together
and
go
from
a
higher
level
here
at
the
different
set
of
projects
that
fit
inside
ecosystem.
Here's
a
kind
of
a
customer
reference
architecture,
view
of
what
you
should
be
thinking
about,
and
here's
a
logical
architecture
what
matters
the
most
to
get
started.
B
And,
of
course
you
know
all
three
of
these
should
be
living
didn't
use.
It
hasn't
really
been
updated
in
a
while
too
dense
point,
but
all
three
of
these
should
be
more
which
we
updated
on
a
regular
basis:
nine,
not
updating
just
to
update
them,
but
as
as
we
evolve
as
a
community,
we
should
be
updating
their
architectures
to
show
that
evolution
so.
B
Yes,
I
think
that's
that's
a
really
good
point.
I
would
love
to
take
this
high
level
layer.
We
talked
about
and
go
deeper
for
the
application
view
and
then
from
an
operation
view.
We
don't
really
have
that
caption
I
think
this.
This
logical
reference
architecture
we've
been
talking
about,
maybe
would
be
with
that
that
operations
discussion
would
happen
the
most
cleanly.
B
But
it's
you
know
the
point.
You're
bringing
up
I
think
is
sort
of
the
point.
We've
been
discussing
that
it's
difficult
in
a
concise
manner
to
kind
of
capture
the
the
customer
view,
the
application
view,
the
operations
view
and
the
ecosystem
community
view.
You
know
at
the
same
time,
and
so
I
think
you
know
to
your
attention
question.
Yes,
I
would
like
to
take
the
application
aspect
deeper
and
the
operational
aspect
well.
L
B
H
B
Anyone
like
to
take
a
stab
at
one
of
those
three
I'd
like
to
get
like
off.
Do
we
have
have
like
a
small
group
of
us
think
about
all
through
them
as
anyone
who's
interested
in
one
of
those
areas
more
than
the
other.
You
have
to
tell
me
now
to
send
me
a
note
and
what
start
maybe
I'll,
send
you
kind
of
like
a
template
that
we
like
to
use
in
the
CN
CF
to
kind
of
get
started
on.
B
B
A
A
List,
but
it
is
it's
a
public
list,
so
anyone's
welcome
to
participate,
I,
not
sure
if
you've
seen
the
email
that
I
sent
to
the
list
this
morning,
where
I
had
some.
B
A
Detailed
concrete
questions
or
proposals
about
the
existing
reference
architecture
and
how
it
fit
into
the
landscape,
and
so
I
guess,
I
I
was
interested
in
hearing.
If
you
were
comfortable
sticking
with
that
aspect
of
the
reference
architecture
such
that
it
would
make
sense
to
talk
about
some
of
our
existing
categories
and
whether
we
could
split
them
up
or
combine
them.
That's
a
what
of
additional
workflow.
We
can
look
at
the
group
I.
B
B
A
Can
I
am
kind
of
poor
Wi-Fi
here,
but
I
did
just
paste
into
the
chat
window
for
people
to
see
the
guts
of
that
message
where,
when
you
look
at
the
landscape
and
I,
think
most
folks
are
familiar
with
the
fact
that
you
have
this
interactive
version
of
the
landscape.
That
are
also
paste
in
the
link
to
that.
That
shows
this,
but
there's
there's
three
boxes
in
particular
that
are
quite
big
and
have
a
ton
of
content
there
and
I'm.
B
Not
only
you
know,
the
email
that
Dan
sent
out,
but
also
have
these
three
different-
do
usually
want
to
try
to
create
one.
It's
kind
of
the
app
developer
view
of
reference
architecture,
what
one
it's
kind
of
more
the
application,
DevOps
or
ops
view,
and
then
no
us
most
of
the
infrastructure
ops.
You.
B
And
kind
of
leveraging,
you
know,
I,
think
thinking
about
those
three
views
in
line
with
the
categories
we've
defined
in
the
the
interactive
landscape,
along
with
where
we
want
to
sort
of
condense,
those
into
a
smaller
subset
of
architectural
themes
that
we
then
define
more
specific
components
to
make
up
that
architecture.
For
that
end,
user,
that
we're
targeting
for
that
that
audience.
B
B
Anything
else
tan
you
want
to
to
raise
up.
A
No
I'm
just
happy
to
have
a
ongoing
email
conversation.
I
mean
we
were
a
little
slow
getting
this
meeting
slot
set
with
the
beautiful
and
then
getting
the
email
piece
revitalized,
but
I
mean
I'd
love
to
have
real
discussions
and
debates
ongoing
I.
Don't
think
any
of
this
is
necessarily
obvious,
so
variation
being
your
people's
feedback.
B
B
A
B
It
will
see
if
the
email
I
think
the
email
is
the
better
way
and
it
sort
of
start
making
progress
and
then
on
these
means
we'll
just
maybe
discuss
what
I
might
also
do.
Dan
as
I
might
I
might
work
with
Chris
on
this
I
might
create
like
three
I'm
I
might
create
three
separate
github
repos
for
each
of
the
reference
architecture,
types
we'd.
If
we
agree
on
and
then
we
can
kind
of
capture
those
architectures
didn't
get,
and
then
you
know,
discuss
them
and
do
poor
requests
as
needed
type
of
thing
to
find
issues.
B
We
definitely
all
good,
just
gonna,
take
it
so
I
think
to
get
to
that
point.
But
yeah
I
mean
that's
exactly
what
I
was
thinking,
what
you
just
described
with
the
Mike
downs,
eventually
we'll
start
with
slides
and
then
move
over
once
we
get
some
some
definitions
and
some
some
consensus
amongst
us,
I.
H
D
A
Just
for
we're
not
actually
an
official
working
group,
yet
working
groups
also
have
to
be
approved
by
the
TLC.
We
should
come
up
with
some.
You
can
wisdom
for
a
subgroup
or
BA
for
an
ad
hoc,
something
I
mean
if
we
felt
like
this
is
going
to
be
like
a
meaningful,
ongoing
activity.
We
could
charter
the
working
group.
I
just
didn't
really
seem
worth
the
trouble
to
create
a
charter
and
other
sort
of
stuff.
A
My
hope
is
that
we
can
create
these
documents,
get
some
consensus
around
them,
get
the
TOC
to
improve
them
and
then
kind
of
people
work
on
hiatus.
But
the
mailing
list
unfortunate
would
stay
around,
but
we
can
create
a
more
formal
structure
if
necessary,
but
the
key
thought
is
that
anything
we
do
no
matter
how
great
and
loves
it.
It's
not
until
five.
Other
team
members
agree
as
well
that
it's
a
fictional
ENT
about
yep.
B
B
And
we
will,
you
know
along
those
lines
and
I
think
you
join
a
lot
of
the
TOC
causes
where
they
are
open
cause
you
can
join
and
for
the
most
part
we
try
to
give
a
work
in
group,
and
this
isn't
a
working
group.
But
you
have
us
on
the
agenda
after
the
working
groups
and
so
there's
usually
a
slot
where
we
can
kind
of
give
a
quick
update
and
so
maybe
monthly
what
I'll
do
is
after
we
have
a
monthly
meeting.
B
Yeah
thanks
for
joining
that,
we
want
to
any
other
questions.
I
I
mean
kind
of
following
the
Google
mentality
of
any
my
meetings.
10
minutes
early
I,
like
college
I,
guess
so
any
other
I
don't
like
leave
questions.
Are
there
any
other
questions
feel
free
to
to
ask
him
now,
but
for
those
of
you
who
need
some
time
for
before
your
next
meeting
feel
free
to
drop
off.