[Openid-specs-risc] Call summary

[Stan Bounev]

Atul, thanks for the quick summary. I’m sorry I was not able to join.

Which spec is called CAEP spec?

Thanks,
Stan

From: Openid-specs-risc <openid-specs-risc-bounces at lists.openid.net> on behalf of Atul Tulshibagwale via Openid-specs-risc <openid-specs-risc at lists.openid.net>
Reply-To: Atul Tulshibagwale <atultulshi at google.com>
Date: Tuesday, March 17, 2020 at 3:48 PM
To: Openid-specs-risc <openid-specs-risc at lists.openid.net>
Subject: [Openid-specs-risc] Call summary

Hi all,
Here's a summary of the call. Also available in the Google doc here.

[Image removed by sender.] CAEP Weekly Sync<https://docs.google.com/a/google.com/document/d/1ZFwJJDwwSBNKX35VObClC1ctMbMMuHJtr5qY-7xsLW8/edit?usp=drive_web>

Call on 3/17

  *
  *   Jordan (Cisco)
  *
  *
  *   Rich (Cisco)
  *
  *
  *   Asad (Thales)
  *
  *
  *   Bjorn (Verizon)
  *
  *
  *   Michaela (BlackBerry)
  *
  *
  *   Atul (Google)
  *

Discussion Summary

  1.
  2.  Everyone introduced themselves.
  3.
  4.
  5.  Resolved to move the call
  6.  to the 10AM PT time, with the same bi-weekly schedule. Atul to send out the new calendar invite.
  7.
  8.
  9.  Spec development: We resolved
  10. that the CAEP spec development can happen in a branch, which can be eventually merged into the master after the spec has been agreed upon
  11.

     *
     *   We may have feature branches
     *   for development of specific documents such as the use-case document within the CAEP branch.
     *

  1.
  2.  Bjorn explained the process
  3.  other WGs in the OpenID Foundation use. There is flexibility, and different groups use branches differently, but the above described process is OK.
  4.
  5.
  6.  Bjorn explained that SSE
  7.  is the evolution of RISC to handle not just security signals but any signal related to authentication or access, which may be acted or decided upon by the receiver of the signal.
  8.

     *
     *   That said, the CAEP spec
     *   development will not at this time attempt to modify the RISC spec, but develop a profile on top of RISC.
     *
     *
     *   Merging the two specs can
     *   be considered as a follow up milestone in the future.
     *
     *
     *   Jordan had a concern with
     *   one of the event types in the current RISC spec needing an update, which he will propose as a pull request.
     *


Atul Tulshibagwale

Software Engineer

+14157613123 Mobile

1600 Amphitheatre Parkway, Mountain View, CA 94043


[Image removed by sender.]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200317/884f4645/attachment-0001.html>