[Openid-specs-risc] Agenda for RISC Meeting Today/ Notes from Jul 27

Adam Dawes adawes at google.com
Mon Aug 3 20:21:53 UTC 2015


Hi all,

Here's a combined agenda for today (3pm PDT) and notes from last week.

Aug 3

Agenda

   -

   Membership update
   -

   Sirtfi
   <https://docs.google.com/document/d/1IRLxqRkWoKAb6lXjgn2QUzcD_D5QSNU6BQc1gi8_L34/edit>
   effort
   -

   Strawman Spec Review
   <https://docs.google.com/document/d/1o1aB5INXE4xlixhANwiurHemg0_GB06Sf095GeigTyE/edit#heading=h.9q83cspgiqmx>
   -

      Adam results on Google abuse/hijacking systems. Internal
      conversations within Google.
      -

      Nat review of ISO 29100
      -

      Other comment review (John Lyle)


July 27

Attendees

Adam Dawes, Andrew Nash, John Bradley, Henrik Biering, Anton Taborszky, Nov
Matake, John Lyle, Alex Weinert, Vicente Silveira, Josh Aberant, Lev, Miguel

Agenda

   -

   Membership update
   -

      New member, Leif Johansson - SUNET. Have a proposal
      <https://docs.google.com/document/d/1IRLxqRkWoKAb6lXjgn2QUzcD_D5QSNU6BQc1gi8_L34/edit?usp=sharing>
      in the same space as RISC/STIX/TAXII
      -

      Josh Aberant from Twitter joining call. Twitter is finalizing IPR
      contribution.
      -

   Blog post completed
   <http://openid.net/2015/07/23/introducing-risc-working-together-to-protect-users/>
   -

   Continued Strawman spec review
   <https://docs.google.com/document/d/1o1aB5INXE4xlixhANwiurHemg0_GB06Sf095GeigTyE/edit#>
   -

      Alex- want to push forward specifically on the compromised case. For
      Microsoft, there is limited window between when account is tagged as
      hijacked and when session ends [mean time 12h]. So, from a signalling
      standpoint, sending the hijacked message is almost the same as
sending the
      “all clear” message.
      - Adam- Google works differently. There could be a long interval
      between when we mark an account as hijacked and when the user
      re-establishes their credentials. [AI: Adam to learn more about the
      specifics around Google’s account hijacking/recovery logic].


*Call in info*

1.  Please join my meeting.

https://global.gotomeeting.com/join/576653581

2.  Use your microphone and speakers (VoIP) - a headset is recommended. Or,
call in using your telephone.

United States: +1 (312) 757-3119

Australia: +61 2 9091 7603

Austria: +43 (0) 7 2088 0716

Belgium: +32 (0) 28 08 4372

Canada: +1 (647) 497-9380

Denmark: +45 (0) 69 91 84 58

Finland: +358 (0) 931 58 1773

France: +33 (0) 170 950 590

Germany: +49 (0) 692 5736 7300

Ireland: +353 (0) 15 133 006

Italy: +39 0 699 26 68 65

Netherlands: +31 (0) 208 080 759

New Zealand: +64 9 974 9579

Norway: +47 21 04 30 59

Spain: +34 931 76 1534

Sweden: +46 (0) 852 500 691

Switzerland: +41 (0) 435 0026 89

United Kingdom: +44 (0) 20 3713 5011

Access Code: 576-653-581

Audio PIN: Shown after joining the meeting

Meeting ID: 576-653-581

Weekly Notes
<https://docs.google.com/document/d/1XZi2p4A5LXLJD7sysQTg33mCtC_yYgdlwHMnmt-12Gk/edit>
[http://goo.gl/5Vt58K]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20150803/4210adb9/attachment-0001.html>


More information about the Openid-specs-risc mailing list