So it's not the protocol that's the problem, it's the documentation. For that I'm 100% with you all. However, I really don't think that the right response to that is "we'll just invent something new and incompatible with slightly different names" -- it's to document the protocol better.
-- Justin On Jul 30, 2013, at 12:57 PM, Paul Madsen <paul.mad...@gmail.com<mailto:paul.mad...@gmail.com>> wrote: I always think I pretty much understand OIDC until I see the specs list On 7/30/13 12:39 PM, Brian Campbell wrote: Yes, that. On Tue, Jul 30, 2013 at 4:46 PM, Richer, Justin P. <jric...@mitre.org<mailto:jric...@mitre.org>> wrote: Yes, I agree that the giant stack of documents is intimidating and in my opinion it's a bit of a mess with Messages and Standard split up (but I lost that argument years ago). _______________________________________________ OAuth mailing list OAuth@ietf.org<mailto:OAuth@ietf.org> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
