<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">I was wondering about
something like...<br>
<br>
OpenID Connect (HTTP Binding with normative references to OpenID
Connect Messages)<br>
OpenID Connect Session Management (with normative references to
OpenID Connect Messages)<br>
OpenID Connect Messages (contains all abstract messages both Basic
and Advanced)<br>
OpenID Discovery<br>
<br>
OpenID UserInfo <br>
<br>
If we need other profiles we can add them. Not sure if this breaks
the desired modularity, but from a developer perspective would be
easier for me to follow. I know what doc to start with and it can
reference another doc to provide message details as necessary.<br>
<br>
Thanks,<br>
George<br>
</font><br>
On 7/11/11 6:23 PM, Nat Sakimura wrote:
<blockquote
cite="mid:CABzCy2C9CK1mdBbVapRnnh2m1ZKbZ=JxdokaMXz-RoazfWLK-Q@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Tue, Jul 12, 2011 at 5:05 AM, Johnny
Bufu <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jbufu@janrain.com">jbufu@janrain.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 11-07-11 10:16 AM, Nat Sakimura wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
1. We should make sure to place HTTP Redirect Binding as
the Center Piece.<br>
This actually is the confusion that even Breno was
falling into. He<br>
was thinking that Core was something to be implemented.<br>
It is not. It is the HTTP Redirect Binding that the
developers<br>
should read. We may want to rename it to something more<br>
attractive and feel as the main spec. (Perhaps rename
core as<br>
"Messages" and let the HTTP Binding assume the name<br>
"Core" etc.?)<br>
</blockquote>
</div>
</blockquote>
<div><br>
</div>
<div>Just for the sake of the call: </div>
<div><br>
</div>
<div>Mike's suggestion: </div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Core
Messages</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Core
Bindings</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Framework
Messages</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>Framework
Bindings</div>
<div><br>
</div>
<div>My suggestions are </div>
<div><br>
</div>
<div> Basic Messages (for Connect)</div>
<div> Advanced Messages (for Connect)</div>
<div> Basic (HTTP bindings)</div>
<div> Advanced</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
<br>
</div>
I too feel that the current number of separate documents makes
it harder to get the big picture, even though I like modular
specs. I guess the modularization is not laid out in a way
that's easy to get. For example:<br>
<br>
- The separation between what is an "abstract" message and
what a binding is required/allowed to define is not very
clear.<br>
<br>
- ID Tokens are needed, one way or another (JWT encoded or
not) to complete a full OpenID-Connect authentication. I'd
rather learn about them from Core.<br>
<br>
- UserInfo endpoint seems to be covered by both UserInfo and
Framework specs.
<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
2. Short names are unpopular.<br>
</blockquote>
</div>
[...]
<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Here are my suggestions:<br>
inf -> userinfo<br>
idt -> id_token<br>
clm -> claims<br>
fmt -> format<br>
mxa -> max_age<br>
eaa -> iso29115<br>
nor -> unsigned<br>
sig -> signed<br>
enc -> encrypted<br>
aat -> auth_time<br>
loc -> locale<br>
opt -> optional<br>
</blockquote>
<br>
</div>
+1 if there's no clear technical reason that prevents using
these slightly longer names.<br>
<font color="#888888">
<br>
Johnny<br>
</font></blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Nat Sakimura (=nat)<br>
<a moz-do-not-send="true" href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>
<a moz-do-not-send="true" href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-ab mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Chief Architect AIM: gffletch
Identity Services Engineering Work: <a class="moz-txt-link-abbreviated" href="mailto:george.fletcher@teamaol.com">george.fletcher@teamaol.com</a>
AOL Inc. Home: <a class="moz-txt-link-abbreviated" href="mailto:gffletch@aol.com">gffletch@aol.com</a>
Mobile: +1-703-462-3494 Blog: <a class="moz-txt-link-freetext" href="http://practicalid.blogspot.com">http://practicalid.blogspot.com</a>
Office: +1-703-265-2544 Twitter: <a class="moz-txt-link-freetext" href="http://twitter.com/gffletch">http://twitter.com/gffletch</a>
</pre>
</body>
</html>