[Openid-specs-ipsie] Draft of the side car requirements doc

[Dean H. Saxe]

Yes, the idea is to avoid repetition by referencing this separate doc in
profiles.  Otherwise, we’d repeat common guidance about crypto keys, TLS,
etc.

​

-dhs

​

On Wed, 25 Jun 2025 18:49:07 GMT Dick Hardt wrote:

So the proposal is that we would require implementers to read this separate
doc in addition to a profile doc?
​
​The motivation being to not repeat language across profile documents?


​

On Mon, Jun 23, 2025 at 2:02 PM Dean H. Saxe via Openid-specs-ipsie <
openid-specs-ipsie at lists.openid.net> wrote:
​

IPSIE WG members,

​

I have published an initial draft of the side car document to collect the
common requirements that are spread across all of the profiles that we’ll
publish via the IPSIE WG.  Please find the repo here
<https://github.com/deansaxe/draft-saxe-ipsie-common-requirements-profile>
and the editor’s draft here
<https://deansaxe.github.io/draft-saxe-ipsie-common-requirements-profile/draft-saxe-ipsie-common-requirements-profile.html>
.

​

I expect we’ll discuss this on tomorrow’s call once I’ve put together the
agenda later this afternoon.

​

If you have any questions, feedback, or additions, let me know.

​

Thank you,

-dhs

​

--

Dean H. Saxe

dean at thesax.es

-- 
​Openid-specs-ipsie mailing list
​Openid-specs-ipsie at lists.openid.net
​https://lists.openid.net/mailman/listinfo/openid-specs-ipsie
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ipsie/attachments/20250626/2e7fc7be/attachment.htm>