The IETF I-D submission is closed at the moment, so I'm attaching a
draft extension to this email for now. It is my intention for this to
become a working group item, and am looking forward to discussing this
at IIW.
-- Justin
PS: This and the XML draft are my first time using the RFC formats, s
The IETF I-D submission is closed at the moment, so I'm attaching a
draft extension to this email for now. It is my intention for this to
become a working group item, and am looking forward to discussing this
at IIW.
-- Justin
PS: This and the instance draft are my first time using the RFC forma
I think that it would be good to have a writeup like this that describes the
differences and pros and cons of each approach. Perhaps on a Wiki page?
Some random thoughts:
One thing: host-meta is highly cacheable, so the # of round trips will
hopefully be comparable for large services with signif
JRD does not require an XML parser. If you want to talk about simplicity,
"engage" is simpler than "reinvent".
EHL
> -Original Message-
> From: Anthony Nadalin [mailto:tony...@microsoft.com]
> Sent: Friday, October 29, 2010 9:37 AM
> To: Eran Hammer-Lahav; John Bradley
> Cc: sa...@zxidp.
Like an XML parser
-Original Message-
From: Eran Hammer-Lahav [mailto:e...@hueniverse.com]
Sent: Friday, October 29, 2010 9:24 AM
To: Anthony Nadalin; John Bradley
Cc: sa...@zxidp.org; openid-specs...@lists.openid.net; the Connect work group;
oauth@ietf.org
Subject: RE: [OAUTH-WG] [Openi
Can you list those "quite a few more complex feature"?
XRD (and JRD) were carefully balanced over 3 years to produce a simple
specification that covers basic discovery needs without any unnecessary
complexity. It was coordinated with IETF, OASIS, OpenID, and W3C efforts, and
successfully adopte
I am agreeing using oAuth in that way is a good idea. It has been discussed
various places. I think Eve's UMA group is looking at some options for that.
You could however do the same thing with WebFinger/XRD.
It would have been better to have worked on this together over the last year
and a
I would not say that this is just a JSON version of XRD, as XRD has quite a few
more complex feature. What is being suggested here is being able to use OAuth
for the authorization/delegation to discovery information in a very simple
chunkable forward means.
-Original Message-
From: John
Can't really comment on product futures but Messenger Connect already has WRAP
support and ACS has Oauth 2.0 v10 support but there seems to be a trend here
-Original Message-
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of hank
williams
Sent: Friday, October 29
Mike,
Does this mean we can expect (or that it is already the case) that
microsoft will support oauth 2 in its mainstream products like
hotmail, mesh, etc?
Hank
On Thu, Oct 28, 2010 at 9:42 PM, Mike Jones wrote:
> I wanted to let people know who may not have seen the announcement, that
> Micros
If there is no authorization mechanism, then this is just a JSON version of
XRD.
Not that you couldn't add authorization to XRD.
We were planning on doing that as an option for a proxy resolution flow that
would look quite similar.
The way that the existing XRI resolver works is quite simil
Hello!
This draft is looking nice, the idea and specification is simple and
straightforward. I would like to draw the connection to other
discovery approaches.
The introductory example in the draft was this one:
GET
/.well-known/simple-web-discovery?principal=mailto:j...@example.com&service=urn:a
12 matches
Mail list logo
