[OIDFSC] Native application SSO Working Group
Nat Sakimura
sakimura at gmail.com
Wed Jul 17 22:56:41 UTC 2013
Hmmm, maybe it has fallen out of my plate. I just looked at the charter
proposal from the proposers.
I do not see anything but
http://lists.openid.net/pipermail/openid-specs-council/2013-July/000340.htmlin
the specs-council list and for that.
Maybe you are talking about
http://lists.openid.net/pipermail/openid-specs-council/2013-July/000341.htmlon
Wed Jul 3 21:25:51 UTC 2013 that was posted by you, Mike?
The proposed change were:
1. changed "in order to enable" to "to enable"
2. capitalize the first letter of the bullet points;
3. change id_token to ID Token;
4. changed OIDC to OpenID Connect;
5. changed "implementors" to "implementers" (BTW, neither "implementer"
nor "implementor" exists in OED, and I used to spell it "implementor". Is
it a Canadian thing?)
6. added "This specification will not make breaking changes to OpenID
Connect 1.0." to "out of scope" section, which is unnecessary since this is
a different working group than AB/Connect working group and has no power as
to OpenID Connect 1.0 to start with;
7. changed capitalizations such as "relying parties" to "Relying
Parties", etc.
8. changed "ie" to "i.e."
9. changed "&" to "and"
10. changed "And so" to "Thus"
They are all editorial.
I gathered that the scopes incorporating the comments were something that
is going to be approved on the first meeting of the Working Group. In fact,
that is the first agenda item of the working group as OpenID Process
Document mandates. If the changes proposed were technical in its nature, I
would have thought of otherwise, however, they were all editorial. Thus
resulted in my note.
Your late comment probably would be considered by the working group, but I
am not sure from the pure procedure point of view, you can actually block
it this way.
Best,
Nat
2013/7/18 Mike Jones <Michael.Jones at microsoft.com>
> Actually, per the rules, the working group **hasn’t** been approved yet,
> Nat’s note notwithstanding. I say that because you updated the proposed
> charter on 7/4, Paul, to reflect my comments and the two week auto-approval
> period if there is no action from the specifications council has not yet
> elapsed.****
>
> ** **
>
> Accordingly, as a specs council member, I hereby file an objection to the
> name Native Application SSO because I believe it is less accurate than it
> could be, and request that the name be changed to “Native Single
> Authorization Agent”, with the mailing list name openid-specs-nssa. If
> those changes are acceptable to the proposers, I’ll withdraw my objection.
> ****
>
> ** **
>
> -- Mike****
>
> ** **
>
> *From:* Chuck Mortimore [mailto:cmortimore at salesforce.com]
> *Sent:* Wednesday, July 17, 2013 1:59 PM
> *To:* Paul Madsen
> *Cc:* Mike Jones; John Bradley; specs at openid.net; John Ehrig; Don Thibeau
>
> *Subject:* Re: [OIDFSC] Native application SSO Working Group****
>
> ** **
>
> Amen!****
>
> ** **
>
> -cmort****
>
> ** **
>
> On Wed, Jul 17, 2013 at 1:56 PM, Paul Madsen <paulmadsen at rogers.com>
> wrote:****
>
> this reminds me of the IETF SCIM-reacronymizing exercise
>
> the group was approved & chartered under the name 'Native SSO' . Those who
> understand what the intent of the work is all agree that the name is an
> accurate description of the work.
>
> Tony didnt like the name as proposed in the charter - but it was approved
> nonetheless.
>
> So why are we still arguing?
>
> paul
>
> ps. I wonder if the proposers of 'Backplane', or ' AB/Connect' ,both
> wonderfully descriptive, faced the same****
>
> On 7/17/13 3:07 PM, Mike Jones wrote:****
>
> So you’d prefer that the work be called something closer to “Native
> Application Authorization”?****
>
> ****
>
> *From:* Anthony Nadalin
> *Sent:* Wednesday, July 17, 2013 11:50 AM
> *To:* Paul Madsen; Don Thibeau
> *Cc:* Mike Jones; John Bradley; specs at openid.net; John Ehrig
> *Subject:* RE: [OIDFSC] Native application SSO Working Group****
>
> ****
>
> I would have been too young back in the 90s****
>
> ****
>
> I don’t like SSO in the name as this is basically this is just a way to
> authorize an app to interact with one or more resource serves on your behalf
> ****
>
> ****
>
> *From:* Paul Madsen [mailto:paulmadsen at rogers.com <paulmadsen at rogers.com>]
>
> *Sent:* Wednesday, July 17, 2013 11:39 AM
> *To:* Don Thibeau
> *Cc:* Anthony Nadalin; Mike Jones; John Bradley; specs at openid.net; John
> Ehrig
> *Subject:* Re: [OIDFSC] Native application SSO Working Group****
>
> ****
>
> I am 99% confident that *our* beloved Tony was not part of the R&B group
> from Oakland, briefly popular in the 90s.....
>
> https://en.wikipedia.org/wiki/Tony!_Toni!_Ton%C3%A9<https://en.wikipedia.org/wiki/Tony%21_Toni%21_Ton%C3%A9>
> !****
>
> On 7/17/13 2:33 PM, Don Thibeau wrote:****
>
> Paul ****
>
> ****
>
> I don't think "Tony Tony Tony" is a good name for a working group :)****
>
> ****
>
> Don Thibeau****
>
> The OpenID Foundation <http://openid.net>****
>
> ****
>
> ****
>
> ****
>
> On Jul 17, 2013, at 2:30 PM, Paul Madsen wrote:****
>
> ****
>
> Tony Tony Tony, how I've missed our time together
>
> The WG's mandate is to profile OIDC to enable an SSO model for native
> mobile applications.
>
> Can you suggest a better (concise & memorable) descriptor for a mail list
> identifier?
>
> paul****
>
> On 7/17/13 2:17 PM, Anthony Nadalin wrote:****
>
> That’s a totally useless name ****
>
> ****
>
> *From:* openid-specs-bounces at lists.openid.net [
> mailto:openid-specs-bounces at lists.openid.net<openid-specs-bounces at lists.openid.net>]
> *On Behalf Of *Paul Madsen
> *Sent:* Wednesday, July 17, 2013 10:59 AM
> *To:* Mike Jones
> *Cc:* John Bradley; specs at openid.net; John Ehrig; Don Thibeau
> *Subject:* Re: [OIDFSC] Native application SSO Working Group****
>
> ****
>
> that list name is fine
>
> thanks****
>
> On 7/17/13 1:51 PM, Mike Jones wrote:****
>
> John, are you able to create the new mailing list at lists.openid.net or
> do we have to ask support at osuosl.org for the list creation?****
>
> ****
>
> Paul and other WG creators, what name do you want the list to have?
> openid-specs-native-sso?****
>
> ****
>
> -- Mike****
>
> ****
>
> *From:* Don Thibeau [mailto:don at oidf.org <don at oidf.org>]
> *Sent:* Wednesday, July 17, 2013 5:03 AM
> *To:* Paul Madsen
> *Cc:* n-sakimura; John Ehrig; openid-specs at lists.openid.net; John
> Bradley; Mike Jones
> *Subject:* Re: [OIDFSC] Native application SSO Working Group****
>
> ****
>
> John Ehrig can set up the web site space and the online Docusign process
> for IPR collection. If done right away it saves all concerned lots of time
> and hassle.****
>
> ****
>
> ****
>
> Don Thibeau****
>
> The OpenID Foundation <http://openid.net/>****
>
> ****
>
> ****
>
> ****
>
> On Jul 17, 2013, at 7:59 AM, Paul Madsen wrote:****
>
>
>
> ****
>
> Thanks Nat,
>
> Don, can you direct me to whomever I should work with on the WG list &
> page logistics?
>
> Paul****
>
> On 7/16/13 6:08 AM, n-sakimura wrote:****
>
> The WG formation is deemed to be approved per section 4.2 of the OpenID
> Process Document v.1.5 of 2009.
>
> A new mailing list should be established promptly per section 4.3 of the
> above document. Also, a WG web pages should be set up at openid.net. You
> should also ask the secretary of the foundation to announce the first
> meeting of the WG, in which scope approval and the chairs selection should
> be done.
>
> Note: the first meeting can only be done after the WG has collected the
> IPR agreement from the participants, so it may not be as quick as you may
> wish, but it has to be done. BTW, NRI's agreement is already in as we have
> a blanket agreement like Google.
>
> Nat
>
> (2013/07/15 14:56), Paul Madsen wrote:
>
> ****
>
> Next steps?
>
> -----------
> Paul Madsen
> Ping Identity
>
> Anthony Nadalin<tonynad at microsoft.com> <tonynad at microsoft.com> wrote:
>
>
> ****
>
> I believe if you dig you will see that there is potential for IPR from
> both Apple and Facebook.
>
> -----Original Message-----
> From: openid-specs-bounces at lists.openid.net [
> mailto:openid-specs-bounces at lists.openid.net<openid-specs-bounces at lists.openid.net>]
> On Behalf Of n-sakimura
> Sent: Wednesday, July 3, 2013 10:20 PM
> To: openid-specs at lists.openid.net
> Subject: Re: [OIDFSC] Native application SSO Working Group
>
> Could you kindly spell it out?
>
> From what I have been hearing, Facebook was just using fast application
> switch, which is nothing more than Self-issued thing that we have, and
> iOS's native login support given to facebook, twitter, and Weibo.
> Perhaps you are thinking of something else.
>
> Of course, I could be complete wrong. I should probably read
> https://developers.facebook.com/docs/howtos/ios-6/
> and
>
>
> http://developer.apple.com/library/ios/#documentation/Social/Reference/Social_Framework/_index.html#//apple_ref/doc/uid/TP40012233
>
> as well.
>
> Having said that, if Apple's interface is not open, perhaps it is a task
> for an industry consortia like OpenID Foundation to go and ask Apple to
> open up the API for other IdPs as well. Do not know if they are going to
> listen, but still, it might be our duty to try.
>
> Nat
>
> (2013/07/04 7:30), Anthony Nadalin wrote:
>
> ****
>
> I also have a concern that we might be infringing on the Facebook SSO
> (iOS) IPR with this effort. ****
>
>
>
>
> --
> Nat Sakimura (n-sakimura at nri.co.jp)
> Nomura Research Institute, Ltd.
> Tel:+81-3-6274-1412 <+81-3-6274-1412> Fax:+81-3-6274-1547
>
> PLEASE READ:
> The information contained in this e-mail is confidential and intended for
> the named recipient(s) only.
> If you are not an intended recipient of this e-mail, you are hereby
> notified that any review, dissemination, distribution or duplication of
> this message is strictly prohibited. If you have received this message in
> error, please notify the sender immediately and delete your copy from your
> system.
> _______________________________________________
> specs mailing list
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs
>
>
>
> _______________________________________________
> specs mailing list
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ** **
>
>
> _______________________________________________
> specs mailing list
> specs at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs****
>
> ** **
>
--
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20130718/ba20d547/attachment.html>
More information about the specs
mailing list