Not sure what I'm supposed to send please be detailed in the instructions please unblock my stake.us account though I can no longer log in using sign in through my Google
On Thu, Feb 15, 2024, 3:01 PM <oauth-requ...@ietf.org> wrote: > Send OAuth mailing list submissions to > oauth@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/oauth > or, via email, send a message with subject or body 'help' to > oauth-requ...@ietf.org > > You can reach the person managing the list at > oauth-ow...@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OAuth digest..." > > > Today's Topics: > > 1. Re: FW: Call for consensus on SPICE charter (nada...@prodigy.net) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 15 Feb 2024 11:36:20 -0800 > From: <nada...@prodigy.net> > To: "'Tom Jones'" <thomasclinganjo...@gmail.com>, "'Roman Danyliw'" > <r...@cert.org> > Cc: "'oauth'" <oauth@ietf.org> > Subject: Re: [OAUTH-WG] FW: Call for consensus on SPICE charter > Message-ID: <07e701da6046$40e704b0$c2b50e10$@prodigy.net> > Content-Type: text/plain; charset="UTF-8" > > 1) Do you support the charter text? Or do you have objections or blocking > concerns (please describe what they might be and how you would propose > addressing the concern)? > > Not sure I support at this point, I understand the need for an > architecture document with patterns and definitions, etc. > > There is a lot of work going on outside the IETF in this area such as the > mDL work in ISO that already has patterns and definitions along with > credential formats (mdoc) and transports (ble/http/nfc). I don?t believe > the IETF should ignore these efforts since most of the driving licence and > passport communities/companies are adopting this as one of the standards > that issuers and verifiers will use. The same is true for W3C WebAuthn. > > The architecture, patterns and definitions should be free from technology, > I don't know why W3C is mentioned in the introduction as the only > technology, this should not be in the introduction but along with other > technologies such as mDL/mdoc, webauthn, etc when describing profiles. As > the goal would be for interested parties to produce profiles of other > technologies to fit the architecture document with patterns and definitions. > > I believe that the WG if formed should also think about holder > verification and patterns and attestations that can be used. Also there > needs to be a notion of a "reader/wallet/etc" that can potentially store > credentials (not necessarily the user or verifier) and release/store > credentials upon "user" consent. > > There are other models than the 3 party that VCs use, so these also need > to be considered in the architecture, patterns and definitions documents > to enable profiles for other technologies. > > I believe in the 1st 3 items in Goals but I don't believe it would be in > the best interest to define a metatdata protocol, as this sounds like this > would be a protocol for obtaining DID documents, there are already many > protocols out there for metadata retrieval, not sure there is a need for > another one, if one is needed for DIDs then that may be better done in W3C > as this does not seem to fit well with the charter > > This charter seems to be very scoped to W3C technology, I understand that > interested parties will have to contribute if they want to have other > technologies included but the charter in general does not seem to allow > this, so removing specific technology will allow this to happen. > > I would be happy to give provide specific text changes to the charter. > > > 2) If you do support the charter text: > > > 3) Are you willing to author or participate in the developed of the WG > drafts? > > yes > > ? Are you willing to review the WG drafts? > > yes > > ? Are you interested in implementing the WG drafts? > > I'm willing to see how we can use these outputs with the other industry > technologies. > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > > ------------------------------ > > End of OAuth Digest, Vol 184, Issue 24 > ************************************** >
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
