Message-ID: <4C285291.2060501@pidster.com>
Date: Mon, 28 Jun 2010 08:43:13 +0100
From: Pid <pid@pidster.com>
Organization: Pidster Inc
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB;
 rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: OAuth WG <oauth@ietf.org>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3EC84ADE@P3PW5EX1MB01.EX1.SECURESERVER.NET>
 <269A7D01-CB98-46F3-9D17-C0AAA31041E4@gmail.com>
In-Reply-To: <269A7D01-CB98-46F3-9D17-C0AAA31041E4@gmail.com>
OpenPGP: id=62590808
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="------------enigBCAA1212E7CFD94CE6F762C6"
Subject: Re: [OAUTH-WG] What to do about 'realm'
Precedence: list
Reply-To: pid@pidster.com

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigBCAA1212E7CFD94CE6F762C6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 28/06/2010 06:37, Dick Hardt wrote:
> I vote for (3) unless a good (4) is suggested.

Ditto.


p

> On 2010-06-27, at 6:51 PM, Eran Hammer-Lahav wrote:
>=20
>> Over the past year many people expressed concerns about the use of the=

>> =91realm=92 WWW-Authenticate header parameter. The parameter is define=
d in
>> RFC 2617 as required, and is allowed to have scheme-specific structure=
=2E
>> =20
>> We have a few options:
>> =20
>> 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 =96 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=
=2E
>> 4. Something else.
>> =20
>> Comments?
>> =20
>> EHL
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org <mailto:OAuth@ietf.org>
>> https://www.ietf.org/mailman/listinfo/oauth
>=20
>=20
>=20
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth



--------------enigBCAA1212E7CFD94CE6F762C6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)

iQIcBAEBCgAGBQJMKFKXAAoJEGoM2OGpOvr9bOgQAK7Etv6/gbOI2Bt9e7tw8PGJ
2vbms2PwFqRzDFrE/1w6fKGXbVszeuOO3l43/h4L8uKlmB8QdehVYE4wd0fYdHkW
y80xVmWy25qhCj2VgDs6qABF6Uo0il5XHJlqfmjRFts5rkChDFw5UaSG3w25pDX8
ctGRpogItDYoTrT8XJgV5u6idE6lzmpPy52hLV/4gu07k++7u4uAY2NbwgE605kQ
9vFTF60MU4ENfHU/Tp62L4cZYsrU2JLdcTUL/uRkAiBrBGJiOtifp6b9ThVRtV/p
bpzrde6GTbku/hRAhXfhaggb2dXO2a9+I9ee56X4FsoBDmsQEOBhB2n3W2qxTBvi
uv5pJok9eRwJm53zCfD5T76q27UqfzVBkQPesuHZs1hsyY7vyCBrGkwJEmeR7zyH
odchzlGojEL0zNMsBbyNdZZB02m/W5bUYnz3wHi03b95Upsq14iB+m+LGlPRrp2B
XHv8pjUVrm4j2KXXc1/j3Z7yV/Ho9ls/80ruFG4DAmgUNUetbFrr3FeMF7J4kFBL
2alE2YwnWRFlAxVoOX5CL2z3K3LXqcuWE+sSQx8wjEbuEnRYNeK56YSyJTYGoTVE
O6Uv5Q3xaIEitUDtTD6IQY780owQz1bXBj5KEO7mhImlfniC/uQOGBeEqvaQHb9A
YU33QeqhQ9FEuGeREfEK
=i15Y
-----END PGP SIGNATURE-----

--------------enigBCAA1212E7CFD94CE6F762C6--