Re: Mobile Stakeholders Meeting: Tuesday, 6 Oct at 10am ET

Hey guys, apologies I can’t make this due to a clash with an ISOC PC meeting and then a GSMA meeting which starts at 2pm UTC. Later this week is better, although timezones make things difficult.

Also, if we can advertise meetings in UTC time that would be fab. I’ll raise it at AC.

Natasha


Natasha Rooney | Technologist, Web and Internet, W3C & IETF | GSMA | nrooney@gsma.com<mailto:nrooney@gsma.com> | +44 (0) 7730 219 765 | @thisNatasha | Skype: nrooney@gsm.org<mailto:nrooney@gsm.org>
Tokyo, Japan


On Oct 1, 2015, at 7:08 AM, Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote:

Hello all,

I would like to organize the next call to hear perspectives from mobile operators:

  10am ET on 6 October (WebEx info attached).

Natasha Rooney has organized one call and updated the wiki based on discussion of
GSMA perspectives.
https://www.w3.org/Payments/IG/wiki/StakeholderPriorities#Mobile_Operators


I would like to be sure that others in the group have an opportunity to share thoughts
as part of building up to a discussion at the face-to-face meeting.

Although any IG participant may attend this call, I am keenly interested in the following
people (who have direct mobile interests or whom I am addressing for other reasons):

* Jörg Heuer
* Natasha Rooney
* Bryan Sullivan
* Laurent Castillo
* Lars Erik Bolstad
* Jean-Michel Rouger

Please let me know whether you can attend the call. The goal will be to hear from you
about mobile needs around payments, and to help us formulate the discussion within
the full Interest Group that will take place during TPAC.

Thank you,

Ian

--
Ian Jacobs <ij@w3.org<mailto:ij@w3.org>>      http://www.w3.org/People/Jacobs

Tel:                       +1 718 260 9447


<operators.ics>


This email and its attachments are intended for the above named only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this email or call +44 207 356 0600 and highlight the error.

Received on Monday, 5 October 2015 04:39:48 UTC