[Openid-specs-risc] Call notes

[Atul Tulshibagwale]

Hi all,
Pasting in the call notes here:
Call on 3/31

   1.

   Atul (Google)
   2.

   Asad (Thales)
   3.

   Tim (Microsoft)
   4.

   Adam (SailPoint)
   5.

   Marius (Coinbase)
   6.

   Rob (Ping Identity)
   7.

   Matt (SailPoint)
   8.

   Michaela (Blackberry)
   9.

   Stan (VeriClouds)
   10.

   Sergey (OneLogin)
   11.

   Peter (VMWare)

Agenda

   1.

   RISC and CAEP spec evolution
   2.

   Spec approval process
   3.

   Timeline for CAEP spec
   4.

   Subject identifiers discussion

Notes

   1.

   Proposed to rename the RISC profile spec to a “shared signals and
   events” profile, but keep the event types specs separate for RISC and CAEP
   2.

   Work on the renamed spec to address requirements of CAEP and RISC
   3.

   Need to look into the approval process. Marius to send email to the RISC
   list to clarify the approval process of specs
   1.

      also clarify the process of adding git permissions
      4.

   OIDF meeting is in the week of October 19. If SSE spec needs to be
   approved by then, it needs to be agreed to by the SSE WG by the end of
   August.
   5.

   Target the preliminary draft to be ready by May 1st.
   6.

   Successive revision with comments and input from the team by June 23rd
   7.

   Finalize and agree upon the spec by September 1st.
   8.

   Spec will contain:
   1.

      Combined SSE profile (including RISC and CAEP)
      2.

      CAEP event types
      3.

      Any modifications to RISC events types (if needed)
      4.

      Informative doc: Use-case document for CAEP
      5.

      Add the RISC use-case document as an informative doc to the repository
      6.

      Possibly a separate subject identifier specification
      7.
      9.

   Can we record the calls? Atul to check with Mike Leszcz.
   10.

   Review use cases to identify various subject identifier types and list
   them as subject identifiers to include in the spec. Also provide for a
   generic subject identifier type.
   11.

   One approach to developing the spec is to start writing the event type
   spec and extract the subject types as each event type is being written.


Thanks,

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/20200331/41784412/attachment.html>