Putting the parameters in alphabetical order would make the page more readable, but other than that it seems fine.
On 8/7/12 6:52 PM, Dick Hardt wrote: > Would appreciate a few others checking to make sure the IANA entries are > valid. > > -- Dick > > Begin forwarded message: > >> *From: *"Amanda Baber via RT" <[email protected] >> <mailto:[email protected]>> >> *Subject: **[IANA #596671] Protocol Action: 'The OAuth 2.0 >> Authorization Framework' to Proposed Standard >> (draft-ietf-oauth-v2-31.txt) * >> *Date: *August 7, 2012 5:34:26 PM PDT >> *Cc: *[email protected] <mailto:[email protected]>, >> [email protected] <mailto:[email protected]>, >> [email protected] <mailto:[email protected]> >> *Reply-To: *[email protected] <mailto:[email protected]> >> >> Dear Author: >> >> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED >> >> We have completed the IANA Actions for RFC-to-be >> draft-ietf-oauth-v2-31 >> >> IANA has created the OAuth Access Token Types, OAuth Parameters, OAuth >> Authorization Endpoint Response Types, and OAuth Extensions Errors >> registries at >> >> http://www.iana.org/assignments/oauth-parameters >> >> >> Please let us know whether the above IANA Actions look OK. As >> soon as we receive your confirmation, we'll notify the RFC Editor >> that this document's IANA Actions are complete. >> >> Thanks, >> >> Amanda Baber >> ICANN/IANA >> _______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
