We did add a diagram but have not published that version yet due to the freeze
on document updates prior to the IETF meeting this week.
in sec 4.1 we recommend using a 32 octet (256bit) random number that is
base64url encoded to create a 42 octet string with the correct URLsafe
character set.
Hi Eduardo,
I have accepted all the "Suggestions" in the forthcoming
version. You can see my private editing copy at
https://bitbucket.org/Nat/oauth-spop/commits/f0f8599
to see how it has been incorporated.
Best,
Nat
On Wed, 03 Sep 2014 01:57:31 -0600
Eduardo Gueiros wrote:
> -BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Review of draft-ietf-oauth-spop-00
Gentleman, here are some notes on the OAuth SPOP Draft.
Review Summary
A few grammar errors, no major flaws, some suggestions that could
possibly make some passages clearer. Some questions as well.
Also, providi