During the IESG review of draft-ietf-oauth-v2, Sean Turner raised the following 
DISCUSS item (meaning, the specification is blocked until this is resolved):



> 0) General: I found the lack of ABNF somewhat disconcerting in that

> implementers would have to hunt through the spec to figure out all the

> values of a given field.  For example grant_type has different values based

> on the different kind of access_token requests - four to be more precise -

> but there's no ABNF for the field.  There are many examples of

> this.   It would greatly aid implementers if a) the ABNF for all fields

> were included in the draft and b) all the ABNF was collected in one place.  I

> had individual discusses for each field that had missing ABNF, but it was

> getting out of hand so I'm just going to do this one general discuss on this

> topic.

I don't have the time to prepare such text. Can someone volunteer to submit 
this text to the WG for review?

EH

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to