> On 26 Feb 2019, at 12:15 pm, Tom Pusateri <pusateri@xxxxxxxxx> wrote: > > > >> On Feb 25, 2019, at 3:03 PM, Fred Baker <fredbaker.ietf@xxxxxxxxx> wrote: >> >> Puzzling about the CC line, and have reduced it somewhat. I am a paid attendee at IETF 104, and got a bounce from 104all@xxxxxxxx saying that mere mortals can't post to it. >> >>> On Feb 25, 2019, at 1:36 PM, Tom Pusateri <pusateri@xxxxxxxxx> wrote: >>>> On Feb 25, 2019, at 10:33 AM, Fred Baker <fredbaker.ietf@xxxxxxxxx> wrote: >>>> >>>> >>>> >>>>> On Feb 24, 2019, at 11:34 PM, Stewart Bryant <stewart.bryant@xxxxxxxxx> wrote: >>>>> >>>>> A better approach might be to ask people at registration what sessions they needed to attend. >>>> >>>> An even better approach, although it delays feedback by one meeting, would be to look into the IETFers Application data. People list what they want to attend for the purpose of calendar maintenance. That would inform the next meeting's agenda development. >>> >>> While a neat idea, it’s not currently possible because I don’t save any private data. And while no user is associated with that data, (I don’t even create users), it is something that could be collected anonymously in the future. There’s a lot that could be done with anonymous statistics or even creating actual users (like automatic blue sheet sign in using Bluetooth LE Proximity sensors or locating colleagues or subscribing to notifications), but I haven’t had time to think through the GDPR implications. >>> >>> Tom >> >> OK, I'm confused. There is this app, which runs on IOS or Android. I don't know where the data is stored, but I know I can tell it what WGs I care about and it will be displayed both on my phone, and on my laptop in a calendar called "IETFers". If it can get from my phone to my calendar on my laptop, it can get to somewhere else. I'm suggesting that the "somewhere else" might anonymize the data and summarize it in some useful way. > > You gave permission for IETFers to have read/write access to a calendar. Your other devices also have access to that calendar. In most cases, that calendar is private to you. In some cases, you may decide to share it with others. There is no access to that calendar information to the general public. And the IETF wouldn’t know where to look for it. And what I was trying to communicate is that while the app has access to that calendar, it doesn’t know who you are and that information never leaves the app so I can’t summarize it in any way. I’m thinking Fred is asking for the app to send the set of working groups selected somewhere (after asking). It would need some sufficiently large random token so that updates can replace old data. > Tom -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@xxxxxxx
