►
From YouTube: SONiC DASH Workgroup Community Meeting May 3 2023
Description
PR289 - Still needs volunteer - Dockerfile.saithrift-client has a static tag in the FROM instruction
SmartNIC Summit June 13 - 15 in San Jose, CA
PR336 - [ACL]: Optimize DASH ACL by introducing cluster tag
Continue “acl tag” convo
Q&A
PR346 - Change SAI submodule URL to opencomputeproject/master - pending
A
Community
called
today
today
is
our
67th
Dash
meeting
and
what
I'm
showing
on
the
screen
here
are
the
notes
from
last
time
and
so
people
who
attended
last
time
in
our
notes
for
anyone
new
on
the
call,
and
so
we
talked
about
the
quick
recap
of
the
P4
workshop
on
the
Intel
campus,
and
we
mentioned
that
the
smart
Nick
Summit
is
coming
in
June
in
San
Jose,
so
I
believe
I'm
planning
to
be
there.
Gerald,
I'm,
I,
know
I,
think
Chris
or
someone
had
planned
to
be
there.
A
So
we
could
talk
about
that
a
little
bit
and
then
I
know
Clark
from
Alibaba
wanted
to
talk
about
his
Nat
PR,
and
we
talked
a
little
bit
about
changes
to
psi
apis
and
some
ideas
around
that,
and
so
that's
what
happened
last
week
and
then
for
anyone
new
I,
usually
post
the
YouTube
videos
here
in
these
links,
just
the
community
call
the
high
availability
call
and
the
behavioral
model
call
if
we
have
those.
So
that's
what
was
happening
and
if
anyone
has
a
PR
or
something
they
want
to
discuss.
A
Let
me
know
today:
I
did
see
this
one
here
coming
through
this
week,
where
we
had
this
PR
350
merged,
and
it
was
a
pro
above
description
for
the
dash
appdb.
So.
A
Oh
more
questions
on
ACL
type,
okay,
all
right!
Maybe
we
should
start
that
first
then.
So.
Is
that
that
same?
That's
that
same
PR
from
last
time,
I'll
grab
it
336
I
think
it
is.
A
B
B
B
B
So
last
week,
sorry,
when
we
talked
about-
let's
say
you
add
an
IP
to
three
tags,
so
you
give
it
a
list
of
three
tags
and
let's
say
you
wanna
one,
two,
three
and
let's
say
you
want
to
remove
from
two
I
think
the
ID
was
well.
You
would
give
it
a
set
of
the
remaining
two
tags
that
IP
belongs
to
I.
Believe
that's
that's
what
was
proposed
last
week
to
make
this
work
to
make
a
remove
work.
B
However,
the
problem
is
the
set
taking
a
un32
as
a
tag
doesn't
allow
to
give
a
list
of
attributes
the
API,
the
Dashi,
the
PSI
API.
You
can
do
a
set
on
an
attribute
and
that's
it.
There's
no
attribute
count.
So
how
does
that
work?
It's
kind
of
similar
to
also
the
set
on
ECR
rules
where
we
cannot
give
a
list
of
port
or
anything
like
that.
B
So
to
me,
I'm,
not
sure
how
we're
going
to
do
the
set.
Unless,
like
is
your
rules,
we
basically
well,
we
will
see
our
rules,
we
would
create
a
new
set
of
rules
and
then
swap
on
The
View
on
the
eni
and
then
and
then
delete
the
old
stuff.
Well
here
it's
the
same
IP
as
a
key,
so
I'm
not
sure
how
we're
going
to
do
that
unless
we
remove
the
prefix
from
all
the
tags,
and
then
we
add
them,
we
add
that
prefix
to
all
the
exit,
the
remaining
tags.
B
A
D
Yeah
absolutely
so
I
think
the
32-bit
map
is
is
something
that
the
P4
is
currently
generating,
but
that's
not
the
actual
PSI
APA,
so
the
PSI
EP
will
I'm.
Thinking
like
it
must
be
something
like
a
big
Vector,
so
so
yeah.
D
It
can
be
a
big
Vector
of
let's
say,
based
on
the
hardware
capability
right,
but
it
can
be
say
256
or
512
or
whatever
the
big
Vector
that
that
can
be
supported.
B
Right
so
so
that's
you
know.
Let
me
let
me
think
a
little
bit,
so
there
is
also
this
there's.
No
there's
not
really
a
tie
for
at
least
well
there's
one
inside,
but
only
it's
a
list
of
whatever.
D
B
D
B
D
With
that
in
mind,
right
with
that
as
a
big
map
it,
it
will
be
like
essentially
like,
like
a
list
right
like
bitmap,
where.
E
E
B
D
So
if
it
is
a
bit
Master,
let's
take
the
say,
the
current
example
that
it's
32
bits
and
and
that
means
it
can
support
up
to
32
tags
right
and
and
if
there
is
a
change
we'll
the
application
can
reprogram
it
with
with
the
new
set
like
new
bit
bit,
set
right.
D
D
B
B
B
D
No
I
mean
I
think
we
can
it
for
the
scale
we
I
already
mentioned
right.
It
will
be
a
bit
mask,
it
will
be
a
two
sorry
bitmap.
It
will
be
a
new
data
type
inside
and
we'll
will
generate
the
PSI
headers
based
on
that
right.
It's
not.
It
will
not
be
the
32
bit.
F
D
D
4K
4K
tags
all
together,
but
I
I
think
that
scale
is
something
I
don't
know.
If
a
bit
map
can
be
of
that
size,
but.
B
Well,
but
okay,
it's
it's
a
significant
numbers.
Even
1K,
you
know
whatever
it
is
I,
don't
doesn't
really
matter.
So
all
I'm
saying
is:
okay,
that's
fine!
You
will
need
to
to
be
that
way
now.
My
question
is
the
timeline
and
is:
is
that
gonna
happen
ever.
C
F
D
E
D
Can
come
back
on
the
the
dates
on
when
this
this
headers
will
be
available,
I
yeah,
but
but
it
is
definitely
not
not
something
that
that
is
pushed
for
yeah.
We
will
be
trying
to
do
that
as
soon
as
possible.
Okay,.
B
D
B
We'll
do
all
right
cool,
so
the
answer
to
that
a
couple,
more
questions,
the
as
far
as,
for
instance,
as
far
as
ACR
rules
and
whatnot
I,
believe
the
the
the
algorithm
is
basically
as
soon
as
an
scl.
As
soon
as
a
group
is
assigned
to
is
applied
to
an
eni,
there
can
be
any
modification
of
HCL
rules.
B
If
there
are
any,
a
new
group
will
be
created
and
then
the
new
group
will
basically
be
set
on
the
eni.
Does
that
apply
to
tag
as
well
I
like
to
think
so,
meaning
that,
as
long
as
a
group
is
not
applied
to
any
ni,
if
a
rule
references
a
set
of
tags,
I
suppose
because
it's
a
mask
then
so
as
long
as
the
group
is
not
applied
to
the
dni,
we
can
add
prefixes
to
tag.
We
can
expand
the
tag.
B
D
The
rule
has
a
tag
bit.
That
also
is
a
bit
bitmap
right
so
in
in
the
rule.
If
you
set
a
tag
map
right
that
that
won't
change
after
the
the
rule
is
applied,
but
that
doesn't
matter
that
doesn't
mean
that
a
prefix
to
tag
map
will
will
never
change
that
I.
Don't
think
that
assumption
we
can
make.
D
So
what
I'm
saying
so
a
rule
has
a
tag
map
and
that
tag
map
will
will
stay
as
as
long
as
that
truly
started
to
a
group
and
the
group
is
bind
to
any
ni,
but.
B
B
What
you're
saying
so,
basically,
even
if
a
tag
is
active,
Chronicle
or
in
use,
you
can
basically
expand
its
list.
You
can
expand
this
list
of
prefixes
on
the
Fly,
while
the
ACL
is
being
used
for.
B
Okay,
yeah
I
mean
it
just
adds
complexity,
but
it's
it's
fine
I
had
to
ask.
Obviously
that's
not
great,
but
that's
just
the
way
it
is
do
we
need
to,
and
the
last
question
was.
B
Let
me
think
a
bit
an
ACL
tag
and
it
will
be
a
so
an
SEO
tag
is
part
on
the
NCR
rule.
Do
we
need
to
do?
We
need
to
assume
that
not
assume,
but
do
we
need
to
verify
the
style
layer
that,
when
a
tag
is
used
on
the
rule,
it's
not
empty.
D
B
D
So
so,
just
to
complete
that
conversation
attack
can
be
empty.
Also,
a
group
can
be
empty,
a
group
with
empty
Roots
right
that
can
be
bind
to
any
ni
as
well.
So.
D
If,
if
that's
not
clear,
then
I
will
I
will
update
the
hld
with
all
these
notes,
yeah.
B
I
think
the
actuality
different
needs
to
be
updated
with
the
the
fact
that
a
tag
while
being
in
the
program
in
a
rule
that
is
active,
you
know
the
group
is
applied
to
an
E
and
I
that
can
be
expanded
on
the
Fly
I.
Think
that's
an
important
factor,
because
that
changes
from
the
whole
ACL
not
being
modified
while
in
use
algorithm
right.
B
G
Yeah
I
had
a
couple
of
questions
and
Uncle
tags
too.
This
is
okay,
the
first
one
just
to
make
sure
that
everybody
is
on
the
same
page,
because
it's
a
bitmap
you've
done
is
that
understanding
that
the
rule
is
the
match.
If
any
one
tag
in
the
role
matches,
we
need
one
tag
in
the
prefix
derived
from
the
prefix.
D
E
D
B
B
B
I'm
trying
to
understand,
what's
now
it's
32-bit
prefix,
to
tag
bitmap
up
to
32
tags.
It
is
the
same
32-bit
map
program
in
DCR
rule.
Is
that
correct?
Okay?
So,
basically,
when
we
go
to
a
higher
scale
than
32,
both
of
those
not
only
the
tag,
programming
on
the
prefix
and
the
SEO
rule
we
have
to
change
is.
B
Okay;
okay,
because
for
this
your
rule,
the
tag
if
value
I
thought
it
was
just
like
it
was
a
tag,
value
that
you
could
Max
to
have
multiples,
but
the
algorithm
is
different
here:
it's
a
bitmap
of
tags;
yes,
yes,
okay,
thanks
for
interrupting
sorry,
for
that.
G
Yeah,
so
the
next
question
I
had
was
about
the
prefix
lookup
itself.
There
was
one
comment
on
the
pier
you
can
can
go
to
that,
which
is
the
the
Apple
tax
beer
yeah.
G
From
somebody
from
Intel
about
the
those
couple
of
lookups
ten
one
and
ten
one
slash
eight
and
one
slash
sixteen.
G
Yeah
I
guess
the
answer
at
that
time
was
that
it
should
I
mean
so
there
were.
There
were
two
different
tags
coming
from
one
from
ten
one,
slash,
eight
and
one
from
ten
one
slash
sixteen
yeah.
So
the
packet
has
packaged
and
matched
both
and
it
should
get
both
tags
or
something
was
the
response
I
believe,
but
my
understanding
was
that
it
should
be
an
LPM
based
lookup,
which
means
it
should
only
match
one
of
those
prefixes
right.
I
That
was
the
really
the
question
that
the
reference
BMV
to
model
actually
is
working
with
only
one
tag
right
at
that
point
of
time
and
the
the
question
was
that
how
do
we
expect
if
you
know
the
those
two
prefixes
you
mentioned,
you
know
if
there
is
a
match
to
multiple
prefixes
and
if
you
can
resolve
to
multiple
tags
and
I
think
the
response
was
that
okay,
that's
all
control
plane
work,
but
the
expectation
is
that
yeah,
if
you
are
matching
multiple
prefixes,
both
the
tags
are
really
matching
to
that
packet.
G
Correct
correct,
but
in
this
case
I
would
assume
only
one
one
tag
will
will
only
derive
one
tab,
because.
E
D
Expected
to
derive
both
tags
from
that
from
that
packet.
G
D
Sorry,
I
I
didn't
get
that
so
10.
G
G
D
G
G
G
Saying
the
PSI
API
would
only
would
provide
it
with
two
different
prefixes
and
the
implementation
has
to
combine
and
put
them
in
so
every
other
overlapping
prefix
has
we
have
to
aggregate
the
tags
so.
F
D
That's
the
expectation,
yeah
I,
don't
think
an
LPM
match
can,
because
here
the
actual
role
may
be
with
tag
one
or
Tag
2
right
from
this
example
on
on
Chetan
shoes
right
the
command,
but.
D
G
D
J
J
We
could
kind
of
roll
it
up
in
the
sense
that
if
there
is
there
is
a
Dar
16
anywhere,
then
any
of
the
lower
tax
are
useless.
We
can
always
put
it
to
the
slash
16
right.
Whatever
is
the
highest
tag.
No.
D
My
point
is,
there
will
be
a
rule,
one
with
let's
say:
Tag
2
match
and
some
action
rule
two
with
let's
say
tag
one
match
and
some
action,
but
your
packet
when
it
comes
I,
think
I
mean
if
I
I'm,
just
thinking
a
hypothetical
scenario.
But
the
point
is
the
the
packet
coming
and
and
all
the
tags
Associated
must
be
derived
for
any
rule
to
to
match,
because
if
you
only
rely
on
one
super
super
tag,
I
don't
know
how
the
rules
can
can
be
made
to
match
there.
D
D
K
D
G
J
J
Yeah,
you
could
only
simplify
it
to
that
prefix,
but
it
because,
irrespective
of
any
of
the
subnets
you'll,
always
derive
the
I.
H
See
I
think
there
should
be
a
configuration
example
that
makes
this
very,
very
absurdly
clear
in
a
case
that
that
and
and
this
should
be
a
pseudocode
description-
not
a
data
plane,
implementation
requirement-
this
is
a
behavioral
requirement
of
how
matching
works.
It's
not
how
you
have
to
implement
it
right.
H
If
a
data
plane
wants
to
do
a
single
longest,
previous
match,
look
up
and
get
17
tags
for
the
single
packet
and
look
up
all
17
tags
and
some
turnary
look
up
that's
up
to
it,
but
probably
most
won't
do
that,
but
that's
effectively
how
you're
describing
what
the
control
plane
wants
to
happen.
Logically,
right
behaviorally,
it
should
be
as
if
you
did
that
yeah.
G
H
Are
many
many
ways
that
all
give
the
same
answer?
There
are
many
ways
to
do
this
in
data
plane
that
all
get
the
same
answer.
I,
don't
think
the
dash
is
going
to
require
a
data
plane
to
implement
it
one
particular
way
as
long
as
it
does
a
correct
way,
but
they
need
to
clearly
Define
what
they.
The
correct
answer
is
for
matching.
K
H
B
H
Difference
yeah
an
example
with
overlapping
prefixes,
each
assigning,
different
tags
and
rules
matching
on
you
know
different
ones
of
those
tags
and
showing
subtle
cases
that
these
kind
of
would
answer.
These
kind
of
questions
would
be
ideal,
I,
don't
I,
don't
know
if
anybody
feels
comfortable
creating
such
an
example
it's,
but
it.
H
A
Right
right-
and
that
was
going
to
be
my
next
question-
is
who's
passionate
enough
about
this?
To
maybe
give
it
a
swing
for
us
to
look
at.
G
Yeah
I
had
one
last
question
for
the
Apple
tags
again
so.
E
G
So
the
stack
table
is
like
a
global
table
right.
So
it's
not
perfect
by
like
a
v-net
or
anything
like
that,
so
the
IPS
are
kind
of
global.
The
prefixes.
A
G
B
Global
is
a
global,
Source
or
Global
destination
because
desire
cannot
differentiate.
Those
so.
D
Yeah
but
in
the
Northbound
we
don't
differentiate
between
Source
or
destination,
but
it's
a
tag
to
prefix
match
prefix
map.
Sorry
right
here
so.
J
You
could,
then
we
could
most
probably
expect
the
prince
that
the
tags
will
either
be
on
the
source
side
of
the
axle
or
the
test
side
of
the
Ackle,
because,
with
the
dash.
G
J
Side
is
always
tenant
side.
Traffic
right
is
that
good,
so
it
would
probably
be
mostly
for
shared
services
kind
of
a
thing
where
either
the
tag
exists
in
the
tackle
rule,
either
on
the
source
side
or
the
destination
side.
Both
sides
don't
make
sense.
That
is
global.
Okay,
yeah.
A
G
H
H
A
A
A
All
right,
if
anyone
wants
to
take
a
look,
it's
350.
I'll,
put
the
link
in
the
notes
when
I,
send
them
out
or
I
can
take
a
snip
of
the
changes.
A
So
I
have
that
and
I
think
I
see
Vladimir
on
the
call
and
I
know
we
talked
about
his
it's
Vladimir's.
346.
A
are
you?
Are
you
here
Vladimir.
A
A
F
All
right,
but
that
breakage
of
the
170
1755,
is
being
looked
into
to
get
to
get
it
fixed
so
that
yeah
that
the
problem
is
that
the
dash
related
changes
in
the
video
went
in
and
then
this
PR
came
in
between
and
the
one
on
top
is
the
vxlan
fix
that
we
need
for
us
to
move
to
the
pointer,
to
move
to
that
instance
of
sign
as
a
sub
module
within
Dash.
So
we're
unable
to
move
to
the
vxlan
fix
that
we
absolutely
need
for
overlay
without
the
1755
picks.
F
So
that's
being
worked
upon
right
now.
F
A
I
was
curious,
does
someone
like
me
or
someone
else
in
this
group,
need
to
attend
the
the
PSI
calls
reshma
or
honey,
or
do
you.
F
Think
so
I
you
have
been
attending
these
days.
There
is
a
little
bit
of
conflict,
so
I
attend
off
and
on,
but
especially
when
we
have
Dash
related
PRS
being
discussed
there,
it
will
be
good
to
be
there.
A
Okay
or
like
if
someone
like
Vince,
has
a
dependency
on
dash
that
has
a
dependency
on
PSI.
You
know
Prince,
do
you
know
if
anyone
from
our
end
attends
those.
D
No
I
I
had
a
discussion
with
the
writer
on
this,
but
but
what
she
agreed
was
if,
if
our
community
here
agrees
and
the
changes
are
not,
you
know
majorly
impacting
the
rest
of
the
site,
then
then
we
can
make
the
call
to
merge.
D
F
That
otherwise
not
really
need
it.
From
the
dash
test
framework
standpoint,
we
actually
merge
into
ocp
side
main
repo,
not
in
experimental.
D
E
D
Yeah
so
it's
like,
we
have
started,
including
those
headers
and
those
things
right.
So
if
we
move
probably
going
to
break
the
implementations,
so
I.
E
F
F
To
be
hand
modified
amount,
and
then
it
will
be
good
to
move
like
a
standard,
but
we
can,
you
know
we'll
start
viewing
Dash
as
a
standard
when
we
kind
of
you
know
at
some
point
move
away
from
experimental
in
in
the
in
inside
as
well.
F
D
F
F
Right
sure
this
is
not
urgent,
but
you
know
to
think
about
it
at
some
time.
The
same
question
for
a
a
similar
question
for
metering
metering:
we
don't
have
the
PSI
apis
right
now,
so
the
implementation
cannot
be
completed
without
testing,
at
least
in
the
dash
test
hardness.
We
cannot
add
metering
part
without
the
sign
apis.
D
Yeah
I
think
metering,
maybe
AMD
team
can
chime
in
but
metering
the
plan
is
to
next.
The
next
plan
is
to
deliver
the
the
behavioral
model
for
me
tree
right.
So.
K
Yeah,
okay,
yeah!
That's
currently
work
in
progress,
so
I
think
the
before
changes
are
done
so
we're
having
some
looking
at
some
issues
with
the
same
API
generation
and
yeah
I'm
working
on
that.
So
it
should
be
out
soon.
Yeah.
F
A
J
I
think
Gohan
as
I'm
go
on
and
asked
if
I
can
raise
the
pr
of
week
or
two
week
or
week
and
half
back
I'm
working
on
that.
F
J
A
Let
me
know
if
I
can
help
yeah
sure,
yeah
and,
like
it
says
here,
if
anyone
has
this
open,
Computing
like
forward
it
to
me
just
so,
I
can
throw
it
on
my
calendar.
Listen
in
you
know
sure
I.
A
It
yeah
thank
you,
yeah
shifting
gears
a
little
bit
Clark.
Did
you
want
to
try
and
introduce
this
I'm?
Sorry,
sorry.
J
No
I
was
just
asking
if
the
gnmi
container
is
that
available
for
us
to
try
out
what
what
is
the
plan
for
that?
If
you
needed
to
do
it.
J
A
So
what
I
was
gonna
Yap
about
was
Clark.
I
know
wanted
to
I,
don't
know
if
you
wanted
to
talk
about
this
one
today,
Clark
or
if
you
wanted
to
just
introduce
it,
but
then
we
could.
Then
we
could
talk
about
Jane
and
my
Clark
did.
Are
you
on
the
ground.
G
Yeah
previously
I
I
want
to
add
the
code
for
this
net.
Hld
and
I
did
not
prepare
for.
G
Look
look
at
next
week,
maybe
I'm
trying
to
yeah
I'm
trying
to
join
the
and
tomorrow's
BM.
A
A
No
I
haven't
looked
at
this
one
and
I.
Don't
know
the
answer
to
that.
So
I
had
support
Gmail
interface
for
dash.
Add
support
so
hey
friends,
what's
what's
this
guys?
Is
this
gang
internally
I
have
trouble
synchronizing
the
names
yeah,
let's
see
what
he's
doing.
D
But
but
hold
on
so
this
one
is
for
the
new
protop
of
encoding,
but
there
is
already
the
gnmi
that.
A
D
That
in
this
repo
yeah
it's
in
the
Sonic
Ripper,
so
basically
Sanjay
was
it
Sanjay
I
was
asking
Christian
yeah
yeah.
E
D
So
Sanjay
the
the
sonic
gnmi
container
has
the
capability
to
program
the
app
DBS
right
like
directly
like
so
you
can.
You
can
basically
use
gnmi
to
set
or
create
any
entries
in
in
the
app
DB
and-
and
you
just
need
to
use
that
framework
to
program
those
Dash
entries
right
so
because
there
is
no
Yang
model,
validation
or
those
things
for
for
dash.
Yet
so
it
can
just
bypass
those
things.
Yeah
I.
K
See
but
okay
yeah,
so
it's
just
yeah.
D
Let
me
think
you
didn't
know.
D
D
One
only
dogs
and
is
it
config
updater,
maybe
scroll.
A
A
A
D
F
D
Oh
okay,
so
it's
our
Sonic
dog
management,
MGMT
in
the
dock,
yeah
I
think
it's
one
more
layer
of
indirection.
Yes,.
F
A
D
Here
there
are
examples
on
how
to
write
directly
to
appdb
right
and
then
we
use
the
the
schema
that
are
defined
in
the
Sonic
HRT
to
write
that
that's
I
mean
we
have
already
tried
that
internally
and
and
it's
working
as
expected,
so
nope.
B
We're
talking
about
Sonic
is
there
any
anything,
a
variable
for
Hardware
DB
Cindy
base
Sonic
the
dash.
D
B
B
As
far
as
the
side,
radius,
repo
itself,
like
code,
not
actually.
D
No,
that's
the
code
right
that
will
be
in
the
Sonic
repo.
That
Dash
report
is
mainly
we
have
all
the
documentations
there
and
and
the
the
P4
models
right,
but
the
actual
code
is
in
the
Sonic
report.
D
B
When
I
tried
to
integrate
to
sing
D
that
didn't
exist,
so
a
pull
side,
radius
and
updated
enough
of
thing
D
to
basically
be
able
to
yeah
the
size.
Reserve
yeah
the
side
changer,
to
write
the
app
Hardware
to
write
the
radius
database
so
that
it
can
be
fed
into
the
CD
and
call
my
style
layer.
So
that
worked.
E
D
Yeah
I
think
the
most
part
is
there,
but
Nvidia
is
also
adding
the
changes
on
on
to
sign
radius,
so
it
should
be
available.
Sometime
probably
this
week.
C
C
C
There
is
a
pull
request
in
the
draft
mode,
but
the
dash
API
changes
and
I
think
we
need
a
couple
of
more
days
to
finish
all
the
testing
and
it
will
be
ready
to
merge.
B
Yeah
that'll
be
good
thanks,
I
mean
there's,
nothing
like
I,
don't
need
in
a
week
or
so.
I
was
trying
to
understand
if
that
was
finally
coming
in
yeah.
A
Oh
sorry,
okay,
thank
you!
Cool
I,.
A
A
I
think
if
I
had
anything
else
again
we'll
be
down
in
California
for
the
smart
Nick
Summit,
so
you
guys
reach
out
to
me
if
I
apparently
I
have
an
exhibit
table
I'm.
Looking
for
like
a
banner
to
go
behind
the
table,
it's
a
short
notice
that
kind
of
scrambling
a
little
bit.
But
if
you'd
like
to
chat
with
me
offline
feel
free,
you
know
my
email
address
and
my
phone
number
I'll
put
them
in
the
chat
window.
So
anyone
have
anything
else.
A
Thanks
thanks
thanks
for
the
conversation,
have
a
good
day.
Okay,
thank.