Regarding this issue in particular, the reason why I am saying that SQL client/server communication is out of scope for this, is because the ISO specification addresses how that is done in several different scenarios, including embedded and direct methods. Hypothetically, if such communication were to use HTTP with this media type, then the charset parameter would be used instead. Yakov On Wed, Jan 23, 2013 at 11:37 PM, Yakov Shafranovich <ietf@xxxxxxxxxxx> wrote: >> > Regarding the charset issue, you are correct in that when > communicating between SQL clients and SQL servers, the encoding maybe > specified inline via a SQL command, or out of band via driver or > session parameters. HOWEVER, this media type is not intended for that > type of communication, rather it is intended for a more mundane things > like exchanging SQL files via an HTTP connection, or in an email > message. In those cases, I do not see any other way of specifying > encoding. >>