Re: Organizing a PING / Auto WG call

Hi Christine,

I won't be able to make that time, when is your next call after that?

On Wed, Aug 2, 2023 at 10:25 PM Christine Runnegar <runnegar@isoc.org>
wrote:

> Hi Ted,
>
> Apologies for not getting back to you more promptly.
>
> Our next PING call will be on Thursday 17 August 2023 at UTC 16.
>
> We could set aside 15 mins at the start of the call for you, if that would
> be convenient.
>
> Kind regards,
> Christine
>
> On 14 Jul 2023, at 11:52 AM, Samuel Weiler <weiler@w3.org> wrote:
>
> Ted,
>
> Good to hear from you!  I've added the other PING chairs and the current
> PING team contact (PLH) to this message.  Hopefully they can help you.
>
> -- Sam
>
>
> On Fri, 14 Jul 2023, Ted Guild wrote:
>
> > Hi Christine and Sam,
> > While consent management is well outside of our current scope, to help
> address
> > privacy concerns around the W3C Auto WG VISS spec we've been discussing
> some ideas to
> > be able to accommodate consent handling and in doing so hope to
> encourage the
> > industry in that direction.
> > https://lists.w3.org/Archives/Public/public-automotive/2023Jun/0000.html
> We would appreciate a chance to discuss with PING at your convenience and
> get your
> > input.
> > On Thu, Jan 5, 2023 at 7:39 PM Christine Runnegar <runnegar@isoc.org>
> wrote:
> >      Thanks Ted.
> >
> >      The call link is here:
> >
> https://mit.zoom.us/j/823321737?pwd=cUs5QlVNVXJvZmFnanZjdmJEQWI4Zz09
> >
> >      We don’t use IRC. We take minutes in CryptPad.
> >
> >      Best,
> >      Christine
> >
> >      > On Jan 3, 2023, at 9:35 AM, Ted Guild <edwardguild@geotab.com>
> wrote:
> >      >
> >      > [correct current address for Ulf]
> >      >
> >      > On Tue, Jan 3, 2023 at 12:34 PM Ted Guild <edwardguild@geotab.com
> >
> >      wrote:
> >      > [adding Ulf - lead editor of VISS and dropping Sam]
> >      >
> >      > On Tue, Jan 3, 2023 at 10:48 AM Ted Guild <edwardguild@geotab.com
> >
> >      wrote:
> >      > Thanks Christine for reaching out and letting me know. I can make
> the
> >      19th at 17UTC and will inform others. If you can send along or
> point me
> >      to the call coordinates that would be appreciated so I can put them
> in my
> >      calendar.
> >      >
> >      > On Tue, Jan 3, 2023 at 10:45 AM Christine Runnegar <
> runnegar@isoc.org>
> >      wrote:
> >      > Hi Ted,
> >      >
> >      > With Sam out, the change of the year and everyone still coming
> back, we
> >      would like to do the call with you 19 January UTC 17 if that works.
> >      >
> >      > Best,
> >      > Christine
> >      >
> >      > > On Dec 2, 2022, at 7:57 AM, Ted Guild <edwardguild@geotab.com>
> wrote:
> >      > >
> >      > > Looking forward to talking on Tuesday. I can make 5 January as
> my
> >      recurring call's cadence is biweekly so we can try to get a few of
> us on
> >      that PING call.
> >      > >
> >      > > On Fri, Dec 2, 2022 at 10:35 AM Samuel Weiler <weiler@w3.org>
> wrote:
> >      > > On Thu, 1 Dec 2022, Ted Guild wrote:
> >      > >
> >      > > > This coming Tuesday the plan is for Isaac to present an
> alternate
> >      > > > authentication/authorization model ...
> >      > >
> >      > > I would be happy to join for that discussion.  Does the WG have
> >      anyone
> >      > > who's following the GNAP work in the IETF?  That's a follow-on
> to
> >      > > OAUTH and might be a better option than rolling something new.
> >      > >
> >      > > > I would be happy to attend a PING call and try to bring a
> >      contingency from
> >      > > > the Auto WG. 15 December at noon however I have a prior
> commitment,
> >      > > > coincidentally with an automotive cybersecurity research
> group I
> >      was trying
> >      > > > to form before leaving MIT, still involved in and have
> secured NSF
> >      funding
> >      > > > for the next three years. What is the cadence of the PING
> calls?
> >      > >
> >      > > 1st and 3rd Thursdays at noon Eastern, which puts the following
> one
> >      at
> >      > > January 5th.
> >      > >
> >      > > -- Sam
> >      >
>
>