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

Lukas Rosenstock <lr@lukasrosenstock.net> Mon, 28 June 2010 07:14 UTC

Return-Path: <lr@lukasrosenstock.net>
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 F18E03A68F2 for <oauth@core3.amsl.com>; Mon, 28 Jun 2010 00:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 CfUGHrNWOfop for <oauth@core3.amsl.com>; Mon, 28 Jun 2010 00:14:01 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 50C3E3A67F1 for <oauth@ietf.org>; Mon, 28 Jun 2010 00:14:01 -0700 (PDT)
Received: by vws7 with SMTP id 7so1137996vws.31 for <oauth@ietf.org>; Mon, 28 Jun 2010 00:14:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.218.211 with SMTP id hr19mr2319782qcb.92.1277709248080; Mon, 28 Jun 2010 00:14:08 -0700 (PDT)
Received: by 10.229.236.130 with HTTP; Mon, 28 Jun 2010 00:14:08 -0700 (PDT)
In-Reply-To: <269A7D01-CB98-46F3-9D17-C0AAA31041E4@gmail.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EC84ADE@P3PW5EX1MB01.EX1.SECURESERVER.NET> <269A7D01-CB98-46F3-9D17-C0AAA31041E4@gmail.com>
Date: Mon, 28 Jun 2010 09:14:08 +0200
Message-ID: <AANLkTikb7bGq-7Y7V4h-pErpkwFJAQ0wZV-lE2hBWNvJ@mail.gmail.com>
From: Lukas Rosenstock <lr@lukasrosenstock.net>
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
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: Mon, 28 Jun 2010 07:14:03 -0000

+1

2010/6/28 Dick Hardt <dick.hardt@gmail.com>:
> I vote for (3) unless a good (4) is suggested.
> On 2010-06-27, at 6:51 PM, Eran Hammer-Lahav wrote:
>
> Over the past year many people expressed concerns about the use of the
> ‘realm’ WWW-Authenticate header parameter. The parameter is defined in RFC
> 2617 as required, and is allowed to have scheme-specific structure.
>
> We have a few options:
>
> 1. Leave it as required under the definition of RFC 2617 (i.e. provide no
> help, developers will need to ready 2617 and figure out what to do with it).
> 2. Update 2617 to remove the requirement – this is not going to be easy or
> possible to predict success.
> 3. Provide specific guidance as to what to do with the realm parameter.
> 4. Something else.
>
> Comments?
>
> EHL
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>



-- 
http://lukasrosenstock.net/