IETF Logo Mail Archive

Re: [OAUTH-WG] What to do about 'realm'

Brian Eaton <beaton@google.com> Fri, 16 July 2010 20:16 UTC

Return-Path: <beaton@google.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 527493A6849 for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 13:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.911
X-Spam-Level:
X-Spam-Status: No, score=-102.911 tagged_above=-999 required=5 tests=[AWL=1.066, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 6Dsr5Mgqark4 for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 13:16:15 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 4C2103A6848 for <oauth@ietf.org>; Fri, 16 Jul 2010 13:16:14 -0700 (PDT)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id o6GKGOIq010873 for <oauth@ietf.org>; Fri, 16 Jul 2010 13:16:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279311385; bh=ykOaVWTX42K7FgTWGZ+8e8ylVEc=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=j+u+N4+V+6UpJ8FqYxBzrelKZdgBdm0vItZn504ElfshXwzB41iSdNAGGmobmTySU WCtZXHwBpZw7dPWgzUGGg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=NlfuLQDCh8S30p1Hj8D0kBVClUf/OroHf2XFpsHwiOMjD9LTThDqM2GSqi3rfPivz KSzBzuv198JTYeWql6XTA==
Received: from pwi10 (pwi10.prod.google.com [10.241.219.10]) by wpaz24.hot.corp.google.com with ESMTP id o6GKGNIG023419 for <oauth@ietf.org>; Fri, 16 Jul 2010 13:16:23 -0700
Received: by pwi10 with SMTP id 10so1587118pwi.20 for <oauth@ietf.org>; Fri, 16 Jul 2010 13:16:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.171.7 with SMTP id t7mr2136319wfe.48.1279311382903; Fri, 16 Jul 2010 13:16:22 -0700 (PDT)
Received: by 10.142.193.19 with HTTP; Fri, 16 Jul 2010 13:16:22 -0700 (PDT)
In-Reply-To: <7C01E631FF4B654FA1E783F1C0265F8C5F998076@TK5EX14MBXC113.redmond.corp.microsoft.com>
References: <AANLkTil8wp2A6JN_td7hwSAttPH6dG_U6PPakb6-vlsb@mail.gmail.com> <C85FDA20.3701A%eran@hueniverse.com> <7C01E631FF4B654FA1E783F1C0265F8C5F991033@TK5EX14MBXC113.redmond.corp.microsoft.com> <AANLkTimlZowDSwOoOgVStDYAJnRdYB1jtH9OdDVagxqE@mail.gmail.com> <7C01E631FF4B654FA1E783F1C0265F8C5F998076@TK5EX14MBXC113.redmond.corp.microsoft.com>
Date: Fri, 16 Jul 2010 13:16:22 -0700
Message-ID: <AANLkTikP0oCBfqD-ixDfDiq_uQvl7jME2eMGoR9LLTFk@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Yaron Goland <yarong@microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] What to do about 'realm'
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: Fri, 16 Jul 2010 20:16:17 -0000

On Fri, Jul 16, 2010 at 11:21 AM, Yaron Goland <yarong@microsoft.com> wrote:
> That's my point. The spec says " 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]." But since RFC 2047 is a dead letter as a practical matter the only safe way to move non-ASCII content in a HTTP header is to use some form of ASCII encoding. So, for example, we couldn't use UTF-16 because it produces characters that aren't safe in ASCII.

Of course, JSON does support unicode escapes, which will work just
fine in an HTTP header.

v2.35.0 | Report a Bug | By Email | System Status