IETF Logo Mail Archive

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

Eran Hammer-Lahav <eran@hueniverse.com> Fri, 16 July 2010 21:26 UTC

Return-Path: <eran@hueniverse.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 D1D3A3A6B6F for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 14:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.478
X-Spam-Level:
X-Spam-Status: No, score=-3.478 tagged_above=-999 required=5 tests=[AWL=1.121, BAYES_00=-2.599, 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 EshnUDUyOb8J for <oauth@core3.amsl.com>; Fri, 16 Jul 2010 14:26:31 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id F1B313A6B2F for <oauth@ietf.org>; Fri, 16 Jul 2010 14:26:30 -0700 (PDT)
Received: (qmail 29386 invoked from network); 16 Jul 2010 21:26:43 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 16 Jul 2010 21:26:43 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Fri, 16 Jul 2010 14:26:42 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>
Date: Fri, 16 Jul 2010 14:26:30 -0700
Thread-Topic: [OAUTH-WG] What to do about 'realm'
Thread-Index: AcslLZYip0pw7EARS1e0FS7gY0e00g==
Message-ID: <56441EC7-DC70-4DEE-9DBA-0BF1B7F549A3@hueniverse.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> <AANLkTikP0oCBfqD-ixDfDiq_uQvl7jME2eMGoR9LLTFk@mail.gmail.com>
In-Reply-To: <AANLkTikP0oCBfqD-ixDfDiq_uQvl7jME2eMGoR9LLTFk@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 21:26:31 -0000

If you specify it. It is supported but not required. 

EHL



On Jul 16, 2010, at 16:16, "Brian Eaton" <beaton@google.com> wrote:

> 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.
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

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