IETF Logo Mail Archive

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

Robert Sayre <sayrer@gmail.com> Tue, 13 July 2010 23:00 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 D4F313A6833 for <oauth@core3.amsl.com>; Tue, 13 Jul 2010 16:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level:
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[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 k+A12P6u+67b for <oauth@core3.amsl.com>; Tue, 13 Jul 2010 16:00:36 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 0F6543A67EE for <oauth@ietf.org>; Tue, 13 Jul 2010 16:00:35 -0700 (PDT)
Received: by qyk2 with SMTP id 2so5113762qyk.10 for <oauth@ietf.org>; Tue, 13 Jul 2010 16:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=vYx7K9FY30vhFQTyi6b8t5+YcvIWk3KIkl7YgT1qXVs=; b=TyA5giaTv8etD2RzKxE2V9Epwib1prg8EMroFVT1lEu9apUYVxhaq8SHRWQKg/jsZr /UifUZEb/Ej3iy4abd4rQEA83jqNe9HKn599upndhmsbDnOsE/qWT0I25nURhFcH4O6g twWmO4Q+eyQNqXAnT3+gQ8KblUtx0w/lKEs7s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XuR02RGewMjS/b2uMeAscwWoxZ+ywFmrb5b6Sc8H/uduQC2u+IX9StOr0fn/0+EU+E q4DPvHHNIVkEGgvz6P5ZdjJNSEGuZiXVwL3QcW0koL970Epl081nmzaYmfCgFL8IfsO7 wIb8Y1wycwfYlQNCQVZB+sENUz/lDhrYtn+JU=
MIME-Version: 1.0
Received: by 10.224.37.137 with SMTP id x9mr9279179qad.155.1279062041628; Tue, 13 Jul 2010 16:00:41 -0700 (PDT)
Received: by 10.229.83.130 with HTTP; Tue, 13 Jul 2010 16:00:41 -0700 (PDT)
In-Reply-To: <7C01E631FF4B654FA1E783F1C0265F8C5F991033@TK5EX14MBXC113.redmond.corp.microsoft.com>
References: <AANLkTil8wp2A6JN_td7hwSAttPH6dG_U6PPakb6-vlsb@mail.gmail.com> <C85FDA20.3701A%eran@hueniverse.com> <7C01E631FF4B654FA1E783F1C0265F8C5F991033@TK5EX14MBXC113.redmond.corp.microsoft.com>
Date: Tue, 13 Jul 2010 16:00:41 -0700
Message-ID: <AANLkTimlZowDSwOoOgVStDYAJnRdYB1jtH9OdDVagxqE@mail.gmail.com>
From: Robert Sayre <sayrer@gmail.com>
To: Yaron Goland <yarong@microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"
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: Tue, 13 Jul 2010 23:00:36 -0000

On Tue, Jul 13, 2010 at 9:46 AM, Yaron Goland <yarong@microsoft.com> wrote:
> As defined in section 4.2 of RFC 2616 the only characters legally allowed in a HTTP header are a fairly small subset of ASCII.

I don't think that is correct. The definition of the TEXT rule in
section 2.2 allows most octets. It also references RFC 2047, but I
don't think many implementations actually support that RFC.


-- 

Robert Sayre

"I would have written a shorter letter, but I did not have the time."

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