[Openid-specs-risc] Call summary

[Atul Tulshibagwale]

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

 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.

   Everyone introduced themselves.
   2.

   Resolved to move the call to the 10AM PT time, with the same bi-weekly
   schedule. Atul to send out the new calendar invite.
   3.

   Spec development: We resolved 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
   1.

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

   Bjorn explained the process other WGs in the OpenID Foundation use.
   There is flexibility, and different groups use branches differently, but
   the above described process is OK.
   5.

   Bjorn explained that SSE 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.
   1.

      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.
      2.

      Merging the two specs can be considered as a follow up milestone in
      the future.
      3.

      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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200317/96d35753/attachment.html>