[OAUTH-WG] Internationalization
Robert Sayre <sayrer@gmail.com> Tue, 20 April 2010 18:05 UTC
Return-Path: <sayrer@gmail.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A2773A67E5 for <oauth@core3.amsl.com>; Tue, 20 Apr 2010 11:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.74
X-Spam-Level:
X-Spam-Status: No, score=-2.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aL226QWMBtSl for <oauth@core3.amsl.com>; Tue, 20 Apr 2010 11:05:49 -0700 (PDT)
Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by core3.amsl.com (Postfix) with ESMTP id 4F58E3A67A5 for <oauth@ietf.org>; Tue, 20 Apr 2010 11:05:49 -0700 (PDT)
Received: by qyk11 with SMTP id 11so6844723qyk.13 for <oauth@ietf.org>; Tue, 20 Apr 2010 11:05:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:content-type; bh=W9GdarYd7L82dWvOC3j3vprql/w34yJ5HnG2osEk+YU=; b=oSDwKTy4bgIefA9z55zT51Otvpn3sPlV8fLeznDhF0Qy8ttOQkkYyvHZFD9csjhS2Y S1c2qprnOS8a7B6/0bTQs/d7MyNe10CMJKZV93l9EdXQHxrjvwHpiYbLUnEKRxExii5U D3y/+KRr+bBmuKlf/F2ENW9ohNZBX+1qiOlhs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JE7V0K5g3Uai39Jn6o3p7rcXGSeeNVazxsJDb6a11t7O8hrwqIlQAhl3Jn5lc0iJ5h 8eSegtIUYkiI0o3YI9080nSvKmtcjpsfeXCq8EyV12I1by5q0yMnKPQPsRxXczYHE33+ 0OmIcp7uLHUSZlnrJN80KXYgwMxTUu8DLa4rg=
MIME-Version: 1.0
Received: by 10.229.99.142 with HTTP; Tue, 20 Apr 2010 11:05:37 -0700 (PDT)
Date: Tue, 20 Apr 2010 14:05:37 -0400
Received: by 10.229.215.72 with SMTP id hd8mr60850qcb.43.1271786737386; Tue, 20 Apr 2010 11:05:37 -0700 (PDT)
Message-ID: <i2p68fba5c51004201105g88f8dadfqfb65f515da0c3e70@mail.gmail.com>
From: Robert Sayre <sayrer@gmail.com>
To: oauth@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [OAUTH-WG] Internationalization
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2010 18:05:50 -0000
Having examined the draft on github, it looks to me like the document should be much more specific about the character encoding of parameters that require internationalization. These include username, password, and realm. I see a UTF-8 reference in the footnotes, but it isn't used anywhere in the draft. RFC2617 really drops the ball on this, so we need to be careful when we reference it. Since this data needs to be passed over HTTP request lines and headers, it needs to be ASCII. That suggests specifying something like the text below for parameters requiring internationalization: > The username/password/realm/etc parameter is a character normalized UTF-8 string encoded as Modified Base64 for URLs. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."
- [OAUTH-WG] Internationalization Robert Sayre