On 6/4/12 4:42 PM, Julian Reschke wrote: > On 2012-06-05 00:10, Mike Jones wrote: > >> Since *client_id* and *client_secret* are parallel to username and >> password, it would be inconsistent to use different character set >> restrictions for them. (On the other hand, Brian Campbell referenced a >> case where a client_id might be a URL, in which case colon would be >> required. That seems like a reasonable usage, so the syntax restriction >> on client_id probably needs to be relaxed. WG thoughts on the correct >> syntax? Should it just be TEXT?) > > No, please forget about TEXT. It's gone from HTTP- > > If you define new protocol elements, either restrict them to US-ASCII, > or find a way to encode all of Unicode. Restricting to ISO-8859-1 is a > non-starter.
+1 to that. Peter -- Peter Saint-Andre https://stpeter.im/ _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
