[Openid-specs-ab] [openid/connect] Client/server 2119 blurriness (issue #716)

Michael Jones issues-reply at bitbucket.org
Mon Jan 28 19:45:15 UTC 2013


--- you can reply above this line ---

New issue 716: Client/server 2119 blurriness
https://bitbucket.org/openid/connect/issue/716/client-server-2119-blurriness

Michael Jones:

A review of the use of the 2119 keywords is in order, per Tim's note below...

From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of Tim Bray
Sent: Monday, January 28, 2013 9:38 AM
To: <openid-specs-ab at lists.openid.net>
Subject: [Openid-specs-ab] Client/server 2119 blurriness

If this were in the IETF, you'd get pushback because in the basic/implicit client specs, there are loads and loads of places where it says MUST or REQUIRED but you're not doing normative-2119-stuff, you're instructing client authors what they can reasonably expect from the server; the MUST/REQUIRED applies to OP behavior not client behaivor.

The problem, if it's a problem, could be fixed by making a whole bunch of MUSTs into musts.  I’m not sure it’s really a problem, but as a reviewer of way too many IETF drafts, it did feel a little jarring.   -T




--

This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.


More information about the Openid-specs-ab mailing list