ion from your document shepherd
>> or AD before posting a new version of the draft.
>>
>> Document: draft-ietf-oauth-v2-23
>>
>> Title: The OAuth 2.0 Authorization Protocol
>>
>> Reviewer: Henry S. Thompson
>>
>> Review Date: 2012-02-
ld tell me that retrieving
http://www.iana.org/oath2/access-token-types
will give me a page listing all the registered access token types, and
also
http://www.iana.org/oath2/access-token-types/bearer
will return the registration details for the bearer type.
This will then make all of (1)
for your patience, I hereby get out of the road on this point.
I'll reply to Eran's message wrt any other outstanding points. . .
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
piana" mailing list (
> https://www.ietf.org/mailman/listinfo/happiana ) and see if you can
> work with Michelle and the other IANA folks on it.
Indeed. I should have realised that that was the right level sooner:
as I said, thanks for your patience.
ht
--
Henry S. Thompson, School
" %x22 %s"M" %xc3 %xb6 %s"bius" %x22 "]"
>
> That is about as confusing as you can get, so please don’t do that.
Agreed.
> (You can write this JSON text as a JSON-encoded JSON text string data item
> while staying in ASCII:
> "[\"26bc4LT-ac6q2K
blem you've encountered arises when one tries to illustrate
UTF-8 byte sequences in an unambiuous way in, for example, an IETF
RFC.
My recommendation is to follow RFC 8259's lead, and use e.g. "%xC3"
for that purpose.
Hope this helps,
ht
--
Henry S. Thompson, School of
