OAuth Core doesn't use HTTPbis. Many of these parameters are often used as URI
query parameters, so whatever encodings are specified must work there. What
syntax and encodings would you suggest for the OAuth Core parameters that need
to work with HTTP Basic as specified in RFC 2617?
Other suggestions are welcome as well.
Thanks,
-- Mike
-----Original Message-----
From: Julian Reschke [mailto:[email protected]]
Sent: Monday, June 04, 2012 3:37 PM
To: Mike Jones
Cc: [email protected]
Subject: Re: [OAUTH-WG] ABNF elements for suggested WG review
On 2012-06-05 00:03, Mike Jones wrote:
> RFC 2616 contains this restriction for the contents of TEXT fields:
>
> Words of *TEXT MAY contain characters from character sets other than
> ISO-8859-1 [22] only when encoded according to the rules of
> RFC 2047 [14].
TEXT is gone in httpbis.
> Therefore, I believe that for the elements using TEXT, the encoding must be
> specified as ISO-8859-1, since they are not always used in contexts where
> MIME encoding rules can be specified.
Again, the TEXT rule was only applicable while talking about
octets-on-the-wire. It wasn't used to define sequences of characters.
You will have to consider where the ABNF is used. Defining new protocol
elements that are constrained to ISO-8859-1 definitively will be a problem.
And anyway, it's gone from the spec.
> ...
Best regards, Julian
_______________________________________________
OAuth mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/oauth
