[Openid-specs-risc] Discussion about subject identifiers - action requested

[Mike Jones]

Note that your reviews of https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-05 need to be sent to id-event at ietf.org<mailto:id-event at ietf.org> THIS WEEK, as the chairs established a deadline of Friday the 20th at 6pm Pacific Time to determine whether there’s interest in finishing the spec.  So yes, respond to Atul’s messages, but also send your own reviews.  Do it early this week.

RISC and CAEP need this spec to happen in the IETF – not SSE – because it establishes registries and only RFCs can do that.

                                                       -- Mike

From: 'Atul Tulshibagwale' via caep-discuss <caep-discuss at googlegroups.com>
Sent: Monday, July 13, 2020 9:30 AM
To: Openid-specs-risc <openid-specs-risc at lists.openid.net>
Cc: id-event at ietf.org; caep-discuss <caep-discuss at googlegroups.com>
Subject: [EXTERNAL] Discussion about subject identifiers - action requested

Hi all,

The SSE profile of SETs<https://docs.google.com/document/d/15zf0kwJhrrteDW-wA8iMwTVFQo2CK6kKK5kNq2IkLuM/edit?usp=sharing> being drafted in the OpenID SSE Working Group includes changes to the "subject identifiers" section of the previous RISC specification<https://bitbucket.org/openid/risc/src/master/openid-risc-profile-1_0.txt>. The subject identifiers section is being considered to be extracted as a separate specification in IETF.

Since we have already discussed this within the working group, it is important that we participate in the discussion within the "Security Events" working group within IETF<https://datatracker.ietf.org/wg/secevent/about/>.

I have created a single pull-request <https://github.com/richanna/secevent/pull/1> to the previous spec draft that captures all our changes, and also created individual email threads about specific aspects that the pull-request includes. It will help to do the following:

  1.  Review the individual topics in the archive<https://mailarchive.ietf.org/arch/browse/id-event/> of the Security Events working group mailing list.
  2.  Provide an opinion of whether the topic is important to you by emailing that list.
  3.  Provide feedback on anything that is being proposed needs to change by emailing that list.
If you subscribe<https://www.ietf.org/mailman/listinfo/id-event> to the SecEvents mailing list, it will help you keep up-to-date on the discussion.

Thanks,
Atul

--
You received this message because you are subscribed to the Google Groups "caep-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to caep-discuss+unsubscribe at googlegroups.com<mailto:caep-discuss+unsubscribe at googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/caep-discuss/CAMCkG5vk7xm8mxHuQ2Z3PELui63GkUpeHFt7%2B98pr%3Depb5-8bw%40mail.gmail.com<https://groups.google.com/d/msgid/caep-discuss/CAMCkG5vk7xm8mxHuQ2Z3PELui63GkUpeHFt7%2B98pr%3Depb5-8bw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200713/87740566/attachment.html>