Re: [OAUTH-WG] [kitten] OAuth Discovery and what the relying partyneeds to know

William Mills <wmills@yahoo-inc.com> Fri, 11 May 2012 15:08 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PhinUWweE634Ee6o/YEJiIaf3om4wCZEKm9Tanjz2XMlNauEn9+6lorMe9LrVUD4/jIOw22ZmrTlQFoADLNcMoUXjmBNZ6xTrVRap2NL7pEwnCWXPKvZSbfUS4sku2jLiiH9bU50Q0++PQdJdtjT63MFAqpxecchqtwjCVAXCt0=;
References: <40FC97F0-B72C-47F4-8206-590BA365997A@gmx.net> <5ECED997-49B8-4550-B79A-CF121FCD1AF9@ve7jtb.com> <9F541ABD-23C0-4592-BC8C-7B7E7CC620CB@gmx.net> <81091A66-03C3-4085-A840-BEC1BBF48161@ve7jtb.com> <A5BFAE4A-5FF2-4E0C-BE49-A04AA9AC9A98@cisco.com> <6E2A5AF6-F4D8-4FCA-A45F-7AE5032A82BE@ve7jtb.com> <4FABDBA2.20908@mitre.org> <6.2.5.6.2.20120511000851.0a735510@resistor.net>
Message-ID: <1336748911.21434.YahooMailNeo@web31807.mail.mud.yahoo.com>
Date: Fri, 11 May 2012 08:08:31 -0700
From: William Mills <wmills@yahoo-inc.com>
To: SM <sm@resistor.net>, Justin Richer <jricher@mitre.org>
In-Reply-To: <6.2.5.6.2.20120511000851.0a735510@resistor.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-125733401-1884177604-1336748911=:21434"
Cc: "kitten@ietf.org" <kitten@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] [kitten] OAuth Discovery and what the relying partyneeds to know
Precedence: list
Reply-To: William Mills <wmills@yahoo-inc.com>

Kitten is in the CC list because this applies to the discovery needs of the OAUTH SASL draft.




>________________________________
> From: SM <sm@resistor.net>
>To: Justin Richer <jricher@mitre.org> 
>Cc: kitten@ietf.org; oauth@ietf.org 
>Sent: Friday, May 11, 2012 12:19 AM
>Subject: Re: [OAUTH-WG] [kitten] OAuth Discovery and what the relying partyneeds to know
> 
>Hi Justin,
>
>[not sure why kitten@ is in the Cc.  Feel free to drop]
>
>At 08:15 10-05-2012, Justin Richer wrote:
>> "user@domain" represents a person. SMTP, XMPP, SIP, and other protocols have used this format successfully. OpenID made the mistake of trying to teach people that "http://domain/user"  could also stand for them, but people just don't think of themselves in terms of HTTP URLs. Webfinger came about to address this, and SWD adopted
>
>The strings industry probably have some reason to believe that people think of themselves in terms of domain names.  Some people think of the other person in terms of "what's your [insert social network]?".  There are several specifications which reference rfc822 identifiers.  The interesting point in the above is what will be people's expected behavior while taking into account the usual technical limitations.
>
>Regards,
>-sm 
>_______________________________________________
>OAuth mailing list
>OAuth@ietf.org
>https://www.ietf.org/mailman/listinfo/oauth
>
>
>

[OAUTH-WG] OAuth Discovery and what the relying p… Hannes Tschofenig
Re: [OAUTH-WG] OAuth Discovery and what the relyi… John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … William Mills
Re: [OAUTH-WG] OAuth Discovery and what the relyi… Hannes Tschofenig
Re: [OAUTH-WG] OAuth Discovery and what the relyi… Klaas Wierenga (kwiereng)
Re: [OAUTH-WG] OAuth Discovery and what the relyi… John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … Klaas Wierenga (kwiereng)
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … Justin Richer
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … John Bradley
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … SM
Re: [OAUTH-WG] [kitten] OAuth Discovery and what … William Mills