►
From YouTube: IETF109-CALEXT-20201119-0900
Description
CALEXT meeting session at IETF109
2020/11/19 0900
https://datatracker.ietf.org/meeting/109/proceedings/
B
B
A
And
there
we
are
all
right,
welcome
everybody
to
the
virtual
video
conferencing
technology.
Everything
is
fine,
bangkok,
2020,
ietf
meeting.
A
A
If
you
have
any
questions,
please
do
ask,
I
know
I'm
being
very
flippant
about
it,
but
it
is
really
important
that
we,
we
have
guide
rails
around,
how
we
behave
and
that
we
all
behave.
I
just
told
people
that
discussion
is
very
respectful
in
this
working
group
and
they
should
come
here
rather
than
some
of
the
others,
so
you're
in
the
right
place.
Well
done
with
that
said,
this
is
the
agenda
that
I
put
together
based
on
what
it
looks
like
our
work
is
from
the
queue
of
documents
we
have.
A
D
Can
you
hear
me
yep
yeah?
Well,
that's
marvellous!
Okay,
if
you've
got
my
slides
and
can
you
drive
them,
I'm
not.
D
B
A
A
We're
not
going
to
spend
that
long
on
the
submitted
documents
just
wanted
to
quickly
talk
about
where
we're
at
with
them.
No,
I
didn't
actually
bring
that
up,
which
I
probably
should
have,
but
that's,
okay.
I
can
easily
just
go.
A
That's
right
yep!
So
if
we
glance
here
at
these
documents,
we
can
see
event
pub
is
the
first
one.
It's
it's
been
waiting
a
while
and
barry.
What
have
we
got
here.
E
Yeah,
I
just
the
changes
in
the
security
considerations.
Look
pretty
good.
I
just
sent
a
response
about
an
hour
ago
or
two
hours
ago,
or
I
don't
know
something
like
that.
It's
the
times
are
weird
right
now
to
michael,
so
my
discuss
is
almost
ready
to
clear
and
I've
pinged
ben
cadek
asking
him
to
have
a
look
at
at
the
version
16..
So.
A
A
E
Well,
yeah,
the
delays
have
mostly
been
getting
responses
back
and
forth.
You
know
it's
taken,
michael
a
while
to
respond,
and
then
it
takes
the
ads
a
while
to
respond,
and
you
know,
and
then
when
you
go
back
and
forth,
so
I
guess
the.
What
I
would
suggest
is
that
the
document
shepard
needs
to
to
be
a
shepherd
and
start
running
around
in
circles
and
barking
when
things
don't
happen
quickly
enough
all
right,
I'm
looking
forward
to.
C
I
I
believe
that
one
of
the
issue,
the
issue
we
have
is
that
when
I
mean
when
the
ad
is
providing
comments,
I
mean
we
should
try
to
respond.
Let's
say
in
the
two
three
days:
otherwise
the
id
is
switching
context
and
then
it
takes
a
lot
of
time
to
bring
it
back.
So
I
guess
in
the
case
of
ben
now
it's
a
little
bit
we're
a
little
bit
in
that
situation.
Is
it
has
to
and
in
to
switch
context,
then
that's
that
takes
a
lot
of
time,
so
yeah.
E
Correct-
and
he
he's
been
particularly
busy
in
recent
months
as
well,
so
some
of
some
of
us
other
ads
have
picked
up
some
of
his
documents
to
move
forward
so
that
his
working
groups
wouldn't
languish
while
he
tried
to
through
everything.
So
it's
you
know,
there's
no
one
person
is
causing
the
delays.
It's
just
yeah
as
different
people
get
involved
the
delays
mushroom
and
having
somebody
actively
chasing
that
down
and
saying
hey,
it's
been
a
couple
of
weeks
and
there's
been
no
response
to
this.
Can
you
go
check
again?
Can
you
give
a
response?
D
That
was
the
relations
draft.
I
think
oh.
D
Yeah
yeah
and
I
think
I'm
as
responsive
as
anybody
else.
I
I
guess
a
little
bit
of
oddly
enough.
You
know
I've
had
a
few
standards
go
through
the
process.
I
wasn't.
It
wasn't
actually
clear.
In
my
own
mind,
I
should
I
should
look
at
this
the
outstanding
stuff
in
the
data
tracker.
I
was
so
relying
on
the
mailing
list
more
than
the
data
tracker
and
perhaps
a
pointer
back
into
that
to
say
to
remind
people
to
check
it
and
see
what's
outstanding.
E
D
E
We've
we've
actually
talked
about
that
with
the
tools
team
and
it's
questionable
how
some
of
us
would
love
to
have
the
data
tracker
send
us
reminders
that
hey
this
has
been
hanging
out
and
nothing's
happened.
E
Other
people
get
very
irritated
when
the
data
tracker
starts
automatically
reminding
them
of
things
so
yeah,
but
we
are
working
with
the
tools
team
on
coming
up
with
a
good
answer
for
this
and
having
some
flag
in
the
data
tracker
for
who
has
the
action
whether
the
action
is
on
the
author
or
the
ad
or
the
yeah
or
whatever.
E
E
Yeah,
in
any
case,
I
I
think
we're
we're
nearing
the
end
of
the
event
pub
extensions.
I
hope
something
like
this.
A
Excellent,
I
I'm
very
glad
all
right
so
that
answers
that
one
next
one
is
js
calendar,
which
is
similarly.
E
Well,
so
that
one
I
just
need,
I
have
it
up
in
my
browser
and
I
am
ready
to
click
the
approve
thing
on
it.
If,
if
that
is
the
right
thing
to
do
right
now,
I
just
it
looks,
it
looks
ready
to
me.
I
think,
we're
good.
I
just
want
to
make
sure
that
the
document
shepard
agrees.
E
A
Great
awesome,
thank
you.
Next
is
the
alarm
extensions.
I
believe
we're
still
waiting
for
ipr
confirmation
from
apple
yeah.
C
So
for
the
gs
calendar
it
means
we
need
to
wait
for
an
isg
till
a
chat.
C
C
C
E
A
C
C
No,
I
I
was
wondering
what
that
would
be.
I
mean
cyrus
is
going
to
provide
them.
I
guess
at
some
point
so
and
and
it's
not
him
so,
but
I
was
wondering
because
it's
a
common
situation
that
I
mean,
for
example,
author
is
not
responsive,
and
so
I
mean
we
don't
know
what
to
do
with
this
ipr.
So
so
that
was
mostly
a
question
for.
C
E
E
Okay,
cyrus
should
not
be
checking
with
apple
legal
on
that,
so
maybe
you
can
ping
him
again
and
the
the
bcp
79
rules
say
that
it's
your
personal
knowledge,
you
do
you.
E
E
E
E
E
E
So
I
you
know,
I
don't
know
what
the
situation
is,
but
I
I
guess
the
thing
is
to
just
hound
cyrus
mercilessly
until
he
responds.
A
A
All
right
cool
our
next
slide
is
ical
relations.
This
isn't
working
group
last
call
I'm
the
shepherd
for
this
one.
The
last
calls
expired
and
I
just
didn't
get
around
to
dealing
with
it.
This
is
the
it's
my
fault
bit.
D
E
That
sounds
quite
delightful
and
I
will
have
something
to
read
tomorrow.
A
I
guess
awesome
j
calendar.
I
can't
I
don't
have
any
slides
for
this
one,
but
it
was
mostly
mike
working
with
robert
on
making
sure
that
it
was
complete
and
accurate.
What's
left
there.
D
Well,
I
I
it's
like.
I
guess
a
lot
is
down
to
me
at
the
moment
there
was
the
issue
over
handling
the
the
recurrence
id
in
in
you
know,
standalone
recurrence
instances
and
neil
came
up
with
suggestion,
which
I
guess
I
don't
think
I
responded
to
actually,
but
I
think,
it'll
work.
D
A
sort
of
a
side
issue
nothing
to
do
with
js
calendar,
and
I
can't
I
got
bogged
down
in
trying
to
upgrade
my
ical4j
library,
so
I
I
just
I
got
bogged
down
with
that
that
particular
issue
and
I'm
about
to
pick
up
on
this
stuff.
Again,
I
don't
think,
there's
anything
huge
outstanding,
I'm
hoping
that
it'll
be
relatively
plain
sailing
to
work
through
I've
done
all
the
js
calendar
eye
calendar
conversion.
D
I
was
working
on
the
I
called
it:
a
js
calendar
conversion
and
just
steadily
working
my
way
through
the
the
draft,
as
I
as
I
was
actually
implementing
as
I
went
along
so
hopefully
in
a
few
weeks,
it'll
be
wrapped
up,
hopefully
less
than
a
few
weeks.
C
Okay,
so
when
you,
I
guess
the
plan
is
when
you
review
the
document
and
you
agree,
we
should
start
working
with
lascal.
C
F
That
was
me
sorry
to
interrupt
daniel
yeah
there's
some
some
changes
still
pending.
Also
from
my
side.
First
of
all,
the
spec
still
includes
the
old
definition
of
the
fractional
I
calendar
parameter
that
we
want
to
introduce.
I
need
to
change
that
to
the
to
the
new
format
that
we
discussed
on
the
mailing
list.
Also,
I
think
we
should.
We
should
wait
until
also.
We
have
verified
the
js
calendar
to
I
calendar
translation,
for
example.
F
I'm
not
sure
we
are
covering
the
preservation
of
of
ids
yet
probably,
but
that's
something
we
might
need
to
add
for
cheaper
calendars,
spec,
then
so
yeah.
I
also
need
to
cross
check
this
back
with
what
we
are
currently
doing
at
fast
me.
So
a
couple
of
weeks
might
be
a
bit
too
eager,
probably
by
the
end
of
the
year
or
january.
I
think
it's
more
realistic.
D
Yeah,
it's
likely,
you
know
in
the
in
the
end,
much
as
I'd
like
to
see
it
go
faster,
given
that
it,
you
know
the
the
very
practical
nature
of
it.
It's
worth
having
at
least
a
couple
of
implementations
that
can
successfully
transfer
in
both
directions,
even
if,
with
only
themselves
it'd
be
great
to
test
across
more
than
one
service,
if
only
between,
say,
beadwork
and
and
and
fast
mail.
A
Yeah,
so
it's
sounding
to
me
like
we,
we
might
be
doing
the
working
group
last
call
for
this
one
in
the
lead
up
to
or
at
next
iatf
in
march
next
year.
That
seem
reasonable.
D
C
Or
what
we
can
do
also
is
have
a
long
working
group
last
call.
So
when
the
doc
is
when
the
specs
are
ready,
and
then
we
focus
on
the
implementations.
A
Yeah,
there's
probably
not
much
point
doing
it
while
we're
still
expecting
churn,
because
we
don't
want
too
many
people
to
to
review
it
before
it's
tested.
C
C
A
All
right
anything
else
to
discuss
on
this,
or
should
we
move
on
to
all
the
rest
of
mike's
drafts
with.
A
D
Well,
some
of
this
covers
some
of
what
we've
already
gone,
but
if
you
can
yeah
we'll
start
with
series
and
another
not
I
mean
I,
I
went
back
through
some
of
the
the
comments
there
weren't
as
many
comments
as
I
thought
there
were,
but
it
was
mostly
between
neil
and
martin,
but
I
think
I'm
gonna
have
to
make
a
few
significant
changes
to
the
draft
as
a
result
and
adding
some
sort
of
mastic
component
rather
than
there,
which
actually
makes
a
lot
of
sense,
because
then
the
generated
instances
will
stand
alone
and
be
and
things
that
don't
understand.
D
Any
of
this
will
just
completely
ignore
the
the
the
master
component
and
all
they'll
see,
is
a
bunch
of
generated
instances
which
look
like
real
events
anyway,
so
that
they
should
be
fine.
D
The
next
slide,
I
think,
with
the
the
other
part
of
the
argument,
was
about
whether
we
should
reuse,
r
rule
or
s
rule,
and
I'm
still,
I'm
leaning
on
these
on
having
an
s
rule
for
a
couple
of
reasons,
while
that
it
does
it
does,
it
does
allow
for
some
possibilities
that
that,
while
they're
more
they're
they're
sort
of
complex
in
a
way
that
you
don't
have
to
do
that
and
there's
also
the
issue
of
having
some
extra
parameters
and
things
added
to
the
s
rule,
which
I
think
just
it
just
makes
sense
to
have
it.
D
I
think,
as
a
separate
property,
it's
not
that
more
much
more
complex
if
at
all
more
complex,
it's
a
different
property
with
a
different
name,
but
almost
exactly
the
same
semantics
as
our
rule.
So
if
you
can
process
our
rule,
you
can
process
s
rule.
It's
just
there's
an
extra
few
parameters
that
are
legal.
A
I'm
inclined
to
agree
with
that
for
the
reason
that
it
is
always
easier
to
combine
two
different
things
that
behave
the
same
than
it
is
to
disambiguate
between
two
things
that
look
the
same
but
are
different.
D
Yes,
exactly
and-
and
I
I
quite
like
martin's-
I
hadn't
thought
of
the
of
the
issue
of
mixing
recurrences
and
and
and
this
series
that,
having
a
series
of
recurrences,
actually,
why
not,
if
you
want
to
have
it
then-
and
you
understand
the
complexity-
then
go
ahead
and
do
it
and
and
for
things
that
don't
even
understand
this-
it's
just
another
set
of
recurrences
that
happen
to
pop
up
regularly.
D
So
I
think
I
think
I'm
sticking
with
with
that,
and
so
mostly
it's
it's
a
matter
of
adding
in
the
issues
with
the
com,
the
new
components.
So
I
need
to
add
that
I'll
hopefully
get
a
new
draft
out
fairly
soon
without
him.
A
Cool,
I
guess
we'll
probably
want
another
implementation
as
well.
D
Oh
yes,
I
don't
want,
but
at
least
if
I
can
get
icarl4j
updated
anybody
who's
doing
java
can
use
that
and.
D
Not
yet,
I
guess
that's
something
to
to
stop
pushing
on.
D
B
D
D
A
A
D
Same
as
you
do
with
recurrences
and
generate
the
entire
lot,
if
it
if
it
makes
sense
to
do
so,
the
the
that
that
was
to
cover
some
thoughts
that
cyrus
has
had
over
the
years,
and
certainly
if
you're
booking
resources
as
well
through
this,
then
not
generating
any
further
than
there
is.
Then
you
can
book
in
the
resources
makes
sense,
but
yeah
there's
a
lot
of
business
logic,
probably
wrapped
around
yeah.
A
D
D
Yep
well,
we've
we've
something
did
come
up
in
on
the
list
in
event,
pub
and
and
and
most
of
the
issues
I
think
were-
is
julian,
who
sent
a
fairly
long
message
about
various
aspects
of
event
pub
which
mostly
typographical
errors
of
one
kind
or
another?
D
Can
you
move
on
to
the
next
slide
there?
I
think
I
can't
have
myself
where
we
were
so
yeah.
D
We've
already
dealt
with
this
yeah
we're
waiting
for
response
from
the
thing
and
then
that
message
from
dillian
and
the
question
was
he
had
on
the
next
slide
as
the
relevant
one,
and
he
had
some
comment
which
I
didn't
think
his
comment
was
termed
this
structured
data
thing
into
a
component
which
didn't
make
a
great
deal
of
sense
to
me,
but
it
did
make
me
think
that
recasting
the
structured
location
as
a
v
location
component
actually
made
a
lot
of
sense
in
that
it
dealt
with
some
of
the
issues
of
the
concerns
about
how
you
deal
with
things
like
the
the
v
card
reference
if
it
had
a
structured
data,
compo
property
inside
it,
which
referenced
the
v
card.
D
There's
a
lot
of
history
with
this.
What
it
was
trying
to
avoid
doing
was
essentially
transporting
all
of
the
v
card
properties
into.
I
calendar
it
just.
D
A
lot
of
sense
to
do
that,
so
one
way
to
do
that
was
to
reference
a
v
card
because
way
back
when
this
all
started
to
start
off
as
v
venue.
It
was
just
a
reflection
of
v
card
inside
I
calendar
and
that
didn't
make
any
any
real
sense
when
you
already
have
that
object.
At
that
time,
we
didn't
have
structured
data
as
a
as
a
as
a
an
idea.
It
was
cyrus
to
keep
with
that
much
later
in
the
life
of
this
whole
draft.
D
I
inherited
structured
data
from
cyrus,
and
it
does
make
a
lot
of
sense
to
to
turn
location
into
a
component,
put
structured
data
inside
that
which
could
then,
which
could
have
the
v
card
ref
as
a
as
a
data
uri
to
avoid
having
to
download
it
at
that
point
in
time.
D
A
D
Having
done
so
for
participants,
it
makes
it's.
It
requires
a
bunch
of
changes
to
libraries
which
couldn't
cope
with
with
multiple
depths
of
components,
but
having
got
over
that,
it
matches
better
to
what
we're
doing
with
say,
js
calendar
for
com
for
locations
where
they
are
essentially
a
component
rather
than
a
property.
C
Sorry,
I
I
don't
see
that
as
a
big
big
problem
to
change
that
I
mean
if
we
think
it's
a
better
approach.
D
I
think
I
can
do
this
fairly
quickly.
It's
it's
and,
and
probably
probably
within
what
day
is
it
today
within
a
few
days?
I
think
I
can
get
another
draft
out
with
this
with
this
in
it
it
it's.
D
You
know
if,
if
I'd
had
structured
data
from
the
start,
I
think
this
is
what
I
would
at
the
point
where
I
I
decided
to
go
with
participant.
I
think
I
would
have
done
this
from
the
from
that
point.
It
makes
such
an
it's
such
an
obvious
thing
to
do
in
the
end,
I
think-
and
it's
not
just
location,
it's
the
other.
It's
the
other
structured
resources
like
the
the
resource.
One
sorry
is
is
the
same,
is
the
same
kind
of
thing.
D
A
resource
is
often
referenced
as
a
v
card
or
whatever.
What
this
allows
you
to
do
is
to
put
the
is
to
put
multiple
structured
data.
If
you
want
in
there
which,
which
reference
the
thing
in
different
ways,
you
know
here's
a
here's,
an
html
rendering
of
the
thing
or
whatever.
D
So
so,
there's
there's
a
lot
of
advantages
to
to
doing
this,
and
I
don't
think
I
should
pass
it
up.
A
E
Then
I
mean
it's
you're
gonna
need
another
another
update
to
the
docket
to
the
draft
anyway,.
D
D
D
So
this
was
the
only
standout.
E
E
Yeah
I
mean
I
would
say
when
you,
let's
wait
for
get
this
queued
up,
but
wait
for
respond
to
my
response
and
make
whatever
change
that
you
want
to
make
for
that.
Wait
for
ben's
response
and
then
put
out
another
revision
of
the
id,
and
let's
see
where
that
takes
us.
Okay,.
A
A
See
it,
but
I
think
otherwise.
D
D
Okay,
I
can,
I
can
do
that
ahead
of
time
and
say
it'll
be
essentially
a
response
to.
I
already
sent
a
response
to
julian
on
his
comments,
but
I
left
this
sort
of
hanging
so
I'll
send
another
response,
saying
what
I'm
thinking
of
doing
with
this
this
particular
point
okay
moving
on,
then
I
guess
cool.
D
Oh
yes,
subscription
upgrade
this.
This,
I
think,
is,
is
actually
yeah
just
just
move
to
the
next
slide.
There
there's
no,
not
much
change,
it
was
it's
it
really.
I
think,
having
we
went,
we've
been
through
the
thing
and
I
don't
think
any
major
issues
have
been
raised
other
than
what's
what's
the
big
advantage
of
this,
and
I
think
the
big
advantage
we
we,
we
were
sort
of
highlighting
the
wrong
advantage
and
I
never
actually
incorporated
into
the
text.
D
The
big
advantage
seems
to
be
for
mobile
and
that
if
you
can
reduce
the
amount
of
traffic
going
on
network
traffic,
then
that
that
always
improves
battery
life,
and
that's
that,
I
think,
is
the
big
thing
with
with
this
I
mean,
if
you've
got
two
biggest
devices
touring
each
other
over
a
huge
network.
What's
the
difference
but
over
when
it's
a
mobile
device,
not
downloading
an
entire
multi-megabyte
ics
thing,
so
you
can
get
about.
One
percent
of
it
seems
to
be
a
good
deal.
D
So
I
think
that
I
I
just
need
to
change
the
finish
off
the
text
and
resubmit,
and
then
we
can
go
from
there
and
again
I'll
try
and
get
that
done
this
coming
week.
A
Cool,
I
think,
realistically,
I
should
just
call
a
working
group
last
call
on
the
new
draft
when
it's
uploaded.
I
don't
think
I
think
we're
basically
done.
A
D
And
the
I
think,
there's
there's
still
issues
with
this
draft.
As
regards
the
itip
interactions,
I
made
some
fairly
heavy
changes
to
it
to
replace
the
we
had
a
v-voter
component
in
there,
which
has
been
replaced
with
the
the
participant
component.
That's
in
the
event
pub
draft
an
extension
to
that.
So
this
relies
on
the
event
pub
thing
going
through.
D
This
is
a
much
better
approach,
because
it's
more
compatible
with
where
we
we're
going
with
js
calendar
and
and
things
so
so
I
think
it'll
make
that
easier
in
the
future,
and-
and
so
we
just
need
to
look
it
over
and
and
fix
up
our
implementations
and
make
sure
that
things
are
work
as
well
as
we
we
think
they
will.
I've
got
an
implementation,
ken's
gonna
try
and
get
his
going.
D
I
think
at
some
point
we
want
to
try
and
test
it
all
again,
but
I
think
it's
much
better
and
and
we've
had
the
eye
tip
issues
outstanding
for
a
while
they
need
tidying
up
is
make
sure
that
that
that's
that's
done
cool,
it's
a
big
document.
So
it's
quite
a
lot
of
work.
D
I
wouldn't
think
so:
there's
no
there's
no
there's!
No,
no,
no,
it's
not
gonna,
and
then
I
think
we
want
to
try
and
do
a
js
calendar
version
of
the
ambulance
as
well.
So
I
think
that's
it
on
my
part.
A
A
We
were
supposed
to
submit
the
alarm
which
is
still
waiting.
I'm
just
going
to
note
this
down
as
we
go
through
them,
so
v
alarm,
hopefully
to
december
js.
Calendar
has
been
submitted,
so
nice
done
scheduling.
Controls
is
waiting
on
me
and
I
haven't
done
anything
on
it
at
all.
I
guess,
since
we've
got
a
few
few
minutes
to
talk
about
that,
the
deal
with
this
document
is
that
it
just
adds
a
new
header
yeah.
There
you
go
I've,
let
it
expire
too.
A
But
the
main
thing
was
there's
an
options,
extension
to
say
that
we
can
do
scheduling,
controls
and
then,
given
that
you
can
then
say
whether
scheduling
is
all
non-internal
external
only
etc.
All
this
it's
probably
a
little
bit
more
complex
than
we
need.
The
main
use
case
for
this
is
to
say,
scheduling,
none
and
that's
when
you're
importing
data
into
a
caldav
server,
that's
come
from
somewhere
else,
and
you
don't
want
scheduling
messages
to
be
sent
out
for
it,
even
if
it
would
normally
schedule.
A
E
It's
always
great
when
I'm
on
a
call
with
alexei,
and
my
echo
thinks
that
I
said
it.
A
A
A
D
D
I
can't
remember
discussing
this,
but
apple
has
some
unpublished
draft
for
bulk
upload.
Does
this
have
any
relevance.
A
Yeah
bulk
upload
is
a
post
to
the
collection.
I
think,
and
you
can
do,
that
you
can
do
scheduling
yeah
ken
probably
knows
more
than
I
do.
B
Yeah,
I
was
going
to
say
that
there
they
would
be
compatible
with
one
another.
So,
yes,
you
could
use
apple's
bulk
import
and
use
this
header
so
that
as
you're
importing
all
the
various
events
you're
not
blasting
out
invitations
that
the
user
priority
has
sent
previously.
A
We
could
just
say
that
the
schedule
reply
header
applies
to
all
scheduling,
not
just
schedule
reply,
so
if
you
set
it
to
false,
then
the
server
should
ignore
it
for
all
things,
not
just
for
replies
and
that
would
that
would
mean
that
it
works
in
the
fallback
case
for
a
server
that
doesn't
support
any
of
this,
at
least
for
that
case.
So
you
wouldn't
have
to
send
two
headers,
but
it
would
for
a
server
that
does
support
suppressing
scheduling
it.
A
Would
it
would
allow
you
to
suppress
it
with
that
header,
even
for
things
where
you're
the
organizer,
but
it
doesn't
give
as
much
control
as
this
document
does,
with
its
internal,
only
external,
only
all
that
magic
that
allows
you
to
to
give
more
controls
over
scheduling.
So
I
don't
know
any
opinions,
one
way
or
the
other.
B
A
D
You
know
who
might
be
worth
engaging
this
is
is
hence
yoga
who
does
given
that
there's
this
this
big
push
in
in
the
eu
to
do,
allow
people
to
import
and
export
their
data.
D
I
think
standardizing
that
process
makes
a
lot
of
sense
and
it
may
not
just
be
a
I
mean
having
something
that
makes
sense
with
multiple
protocols,
or
you
know
that
at
least
the
semantics
are
the
same
makes
sense
you
you
want
to
pull
it
out
of
a
cal
diver
where
things
shove
it
into
a
js
calendar
thing.
Jay's
map
thing
it's
gonna
be
so
it
might
be
worth
engaging.
Hence
yoga.
That's.
A
A
A
Account
a
series-
hopefully
soon
so
I
can
leave
leave
that
for
december-
that
we
submitted
because
that's
pretty
much
done
subscription
upgrade
we'll
submit
in
december.
That's
pretty
much
done
server
side
subscriptions,
so
that
was
the
other
one
of
these
mike
did
you
have.
B
D
Yeah,
that's
that's
right!
Yeah.
We
and
I
think
we're
running
the
same
issues
as
anybody
else's
apple
aren't
talking
to
anybody.
A
Yeah
all
right,
I'm
to
bump
that
through
to
march,
I
hope
we'll
have
it
by
next
meeting.
C
A
I'm
I'm
hearing
a
great
deal
of
nothing,
in
which
case
we
get
to
finish
12
minutes
early.
That's
ridiculous!
Well
done!