This is a formal request to the OpenID Specs Council to review the charter
proposal for creating a Backplane Protocol working group.



Participation and interest in the development of the protocol has grown out
of recent Internet Identity Workshops. The potential formation of an
OpenID work group is an opportunity to provide awareness about the
Backplane Protocol globally so that more application vendors and website
publishers will have the opportunity to guide its development and
collaborate around use cases.



If there is a positive response from the Specifications Council, we would
like to work with the OIDF to schedule time at the 2012 CIS event in
July to have
more discussions on this topic and to seek additional workgroup members.



I look forward to your review of this charter proposal and welcome feedback
you may have on its scope and purpose.



Regards,

Greg



*
*

*Charter submission for the Backplane Protocol Working Group*

There is an interest in creating an OpenID workgroup to broaden
collaboration in the development of the Backplane Protocol specification.

*Charter Proposal*

Following the OpenID Foundation?s IPR policies and procedures this note
proposes the formation of a new working group chartered to broaden input
into the development of a Backplane Protocol specification. The proposed
charter is below and may change during the initial feedback period.

*I. Name*

Backplane Protocol Working Group

*II. Statement of Purpose*

Facilitate the creation of a trust framework between end users, websites
and third-party applications such that all can exchange information with
each other in a standardized way.

While the messages exchanged through the Backplane Protocol are not
required to be identity related or reference OpenID-authenticated users,
these represent the most interesting use case and have constituted one of
the main drivers behind the Backplane efforts to date.

If Backplane continues to build momentum and becomes widely adopted for
inter-widget/inter-application identity message exchange, it would benefit
all parties involved if the development of the protocol continued within
the OpenID Foundation.

This workgroup intends to solidify the current proposed protocol by
ensuring the specifications, reference and production implementations

- adhere to best practices in online security as it pertains to
broadcasting of user identity between multiple applications on a website
- are extensible to support other application scenarios or message types
to broaden the scope of inter-widget communications beyond identity messages


*III. Background*

Echo conceived the protocol and designed it as an open standard. They
later partnered with Janrain and together have evolved the protocol,
incorporating feedback received from interested Relying Parties as well as
the community, including the Internet Identity Workshops in the Spring and
Fall of 2011.

The Backplane Exchange Protocol is currently used today by application
vendors including Echo and Janrain and by website
operators<http://backplanex.com/showcase/>including ABC, Discovery
Channel, NBC Universal, Sports Illustrated, The
Washington Post, Universal Music Group and USA Networks.

*IV. Scope*

The initial scope of effort by the working group is to ensure that the
protocol


- adheres to best practices in online security as it pertains to
broadcasting of user identity between multiple applications on a website
- is extensible to support other application scenarios or message types
to broaden the scope of inter-widget communications beyond identity messages


Scope also involves standardizing the definition and nomenclature of
constructs that describe various aspects of the protocol e.g. message types
or application scenarios, such that it appeals to the technology community
at large.

Scope does not include definition of additional message types (also
currently known as application scenarios) or recruiting additional members
beyond the initially formed working group.

*V. Specifications*

The core Backplane Exchange protocol specifications can be found at the
URLs below:

Version 2.0 (Latest Work)
Backplane Exchange Specification
2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>
(draft
13, June 2012, HTML)

Backplane Exchange Specification
2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf>
(draft 12, May 2012, HTML)
Backplane Exchange Specification
2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf>
(draft 10, March 2012, HTML)
Backplane Exchange Specification
2.0<http://backplanex.com/documentation/backplane-specification-2-0/>
(draft 07, January 2012, HTML)

Version 1.0 (Currently in Production)
Backplane Exchange Specification
1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June
2011, HTML)
Backplane Exchange Specification
1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June
2011, HTML)
Backplane Exchange Specification
1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November
2010, HTML)

*VI. Anticipated Audience*

Interested parties would include:

? Website Operators that need to use third-party applications on
their sites and want to improve usability and interoperability.

? Relying Parties that are looking to distribute personalized
services on other portals versus their own websites.


A number of participating websites and vendors interested in Backplane
Protocol and the advancement of the specifications are listed
here.<http://backplanex.com/showcase/>

*VII. Language of business*

English.

*VIII. Method of work*

Mailing list discussion. Posting of intermediate drafts at
http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
ad-hoc basis.

*IX. Basis for completion of the activity*

When all items set forth in Section IV Scope have been addressed and agreed
upon by members of the working group.

*X. Initial Membership*

Johnny Bufu, Janrain
Greg Keegstra, Janrain
Vidya Shivkumar, Janrain
Tom Raney, Janrain
Vlad Skvortsov, Echo

Yuri Lukyanov, Echo

Alexander Zhuravlev, Echo
Chris Saad, Echo

*XI. Expected contribution*

Draft: Backplane Exchange Specification 2.0 (draft 13)
<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120605/69fc08e2/attachment.html>

Search Discussions

  • Nat Sakimura at Jun 5, 2012 at 11:47 pm
    To: Specs Council

    Please review the attached WG Charter proposal.

    The review period ends on June 19 PDT.

    Best,

    Nat
    On Wed, Jun 6, 2012 at 4:50 AM, Keegstra, Greg wrote:

    This is a formal request to the OpenID Specs Council to review the
    charter proposal for creating a Backplane Protocol working group.



    Participation and interest in the development of the protocol has grown
    out of recent Internet Identity Workshops. The potential formation of an
    OpenID work group is an opportunity to provide awareness about the
    Backplane Protocol globally so that more application vendors and website
    publishers will have the opportunity to guide its development and
    collaborate around use cases.



    If there is a positive response from the Specifications Council, we would
    like to work with the OIDF to schedule time at the 2012 CIS event in July
    to have more discussions on this topic and to seek additional workgroup
    members.



    I look forward to your review of this charter proposal and welcome
    feedback you may have on its scope and purpose.



    Regards,

    Greg



    *
    *

    *Charter submission for the Backplane Protocol Working Group*

    There is an interest in creating an OpenID workgroup to broaden
    collaboration in the development of the Backplane Protocol specification.

    *Charter Proposal*

    Following the OpenID Foundation?s IPR policies and procedures this note
    proposes the formation of a new working group chartered to broaden input
    into the development of a Backplane Protocol specification. The proposed
    charter is below and may change during the initial feedback period.

    *I. Name*

    Backplane Protocol Working Group

    *II. Statement of Purpose*

    Facilitate the creation of a trust framework between end users, websites
    and third-party applications such that all can exchange information with
    each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not
    required to be identity related or reference OpenID-authenticated users,
    these represent the most interesting use case and have constituted one of
    the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for
    inter-widget/inter-application identity message exchange, it would benefit
    all parties involved if the development of the protocol continued within
    the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by
    ensuring the specifications, reference and production implementations

    - adhere to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - are extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    *III. Background*

    Echo conceived the protocol and designed it as an open standard. They
    later partnered with Janrain and together have evolved the protocol,
    incorporating feedback received from interested Relying Parties as well as
    the community, including the Internet Identity Workshops in the Spring and
    Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application
    vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/>including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The
    Washington Post, Universal Music Group and USA Networks.

    *IV. Scope*

    The initial scope of effort by the working group is to ensure that the
    protocol


    - adheres to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - is extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    Scope also involves standardizing the definition and nomenclature of
    constructs that describe various aspects of the protocol e.g. message types
    or application scenarios, such that it appeals to the technology community
    at large.

    Scope does not include definition of additional message types (also
    currently known as application scenarios) or recruiting additional members
    beyond the initially formed working group.

    *V. Specifications*

    The core Backplane Exchange protocol specifications can be found at the
    URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft
    13, June 2012, HTML)

    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November 2010, HTML)

    *VI. Anticipated Audience*

    Interested parties would include:

    ? Website Operators that need to use third-party applications on
    their sites and want to improve usability and interoperability.

    ? Relying Parties that are looking to distribute personalized
    services on other portals versus their own websites.


    A number of participating websites and vendors interested in Backplane
    Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    *VII. Language of business*

    English.

    *VIII. Method of work*

    Mailing list discussion. Posting of intermediate drafts at
    http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
    ad-hoc basis.

    *IX. Basis for completion of the activity*

    When all items set forth in Section IV Scope have been addressed and
    agreed upon by members of the working group.

    *X. Initial Membership*

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo

    Yuri Lukyanov, Echo

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    *XI. Expected contribution*

    Draft: Backplane Exchange Specification 2.0 (draft 13)
    <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>





    _______________________________________________
    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-council/attachments/20120606/c38134e7/attachment-0001.html>
  • Dick Hardt at Jun 6, 2012 at 2:42 am
    I have no opinion.
    On Jun 5, 2012, at 12:50 PM, Keegstra, Greg wrote:

    This is a formal request to the OpenID Specs Council to review the charter proposal for creating a Backplane Protocol working group.


    Participation and interest in the development of the protocol has grown out of recent Internet Identity Workshops. The potential formation of an OpenID work group is an opportunity to provide awareness about the Backplane Protocol globally so that more application vendors and website publishers will have the opportunity to guide its development and collaborate around use cases.


    If there is a positive response from the Specifications Council, we would like to work with the OIDF to schedule time at the 2012 CIS event in July to have more discussions on this topic and to seek additional workgroup members.


    I look forward to your review of this charter proposal and welcome feedback you may have on its scope and purpose.


    Regards,

    Greg




    Charter submission for the Backplane Protocol Working Group

    There is an interest in creating an OpenID workgroup to broaden collaboration in the development of the Backplane Protocol specification.

    Charter Proposal

    Following the OpenID Foundation?s IPR policies and procedures this note proposes the formation of a new working group chartered to broaden input into the development of a Backplane Protocol specification. The proposed charter is below and may change during the initial feedback period.

    I. Name

    Backplane Protocol Working Group

    II. Statement of Purpose

    Facilitate the creation of a trust framework between end users, websites and third-party applications such that all can exchange information with each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not required to be identity related or reference OpenID-authenticated users, these represent the most interesting use case and have constituted one of the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for inter-widget/inter-application identity message exchange, it would benefit all parties involved if the development of the protocol continued within the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by ensuring the specifications, reference and production implementations

    adhere to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website
    are extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages

    III. Background

    Echo conceived the protocol and designed it as an open standard. They later partnered with Janrain and together have evolved the protocol, incorporating feedback received from interested Relying Parties as well as the community, including the Internet Identity Workshops in the Spring and Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application vendors including Echo and Janrain and by website operators including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The Washington Post, Universal Music Group and USA Networks.

    IV. Scope

    The initial scope of effort by the working group is to ensure that the protocol


    adheres to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website
    is extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages

    Scope also involves standardizing the definition and nomenclature of constructs that describe various aspects of the protocol e.g. message types or application scenarios, such that it appeals to the technology community at large.

    Scope does not include definition of additional message types (also currently known as application scenarios) or recruiting additional members beyond the initially formed working group.

    V. Specifications

    The core Backplane Exchange protocol specifications can be found at the URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0 (draft 13, June 2012, HTML)

    Backplane Exchange Specification 2.0 (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0 (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0 (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2 (June 2011, HTML)
    Backplane Exchange Specification 1.1 (June 2011, HTML)
    Backplane Exchange Specification 1.0 (November 2010, HTML)

    VI. Anticipated Audience

    Interested parties would include:


    ? Website Operators that need to use third-party applications on their sites and want to improve usability and interoperability.
    ? Relying Parties that are looking to distribute personalized services on other portals versus their own websites.

    A number of participating websites and vendors interested in Backplane Protocol and the advancement of the specifications are listed here.

    VII. Language of business

    English.

    VIII. Method of work

    Mailing list discussion. Posting of intermediate drafts at http://backplanex.com or the OpenID Wiki. Virtual conferencing on an ad-hoc basis.

    IX. Basis for completion of the activity

    When all items set forth in Section IV Scope have been addressed and agreed upon by members of the working group.

    X. Initial Membership

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo

    Yuri Lukyanov, Echo

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    XI. Expected contribution

    Draft: Backplane Exchange Specification 2.0 (draft 13)




    _______________________________________________
    specs mailing list
    specs at lists.openid.net
    http://lists.openid.net/mailman/listinfo/openid-specs
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120605/d695ace2/attachment.html>
  • David Recordon at Jun 6, 2012 at 3:40 am
    I also have no opinion (and should really remove myself from the Specs
    Council).
    On Tue, Jun 5, 2012 at 7:42 PM, Dick Hardt wrote:

    I have no opinion.

    On Jun 5, 2012, at 12:50 PM, Keegstra, Greg wrote:

    This is a formal request to the OpenID Specs Council to review the
    charter proposal for creating a Backplane Protocol working group.


    Participation and interest in the development of the protocol has grown
    out of recent Internet Identity Workshops. The potential formation of an
    OpenID work group is an opportunity to provide awareness about the
    Backplane Protocol globally so that more application vendors and website
    publishers will have the opportunity to guide its development and
    collaborate around use cases.


    If there is a positive response from the Specifications Council, we would
    like to work with the OIDF to schedule time at the 2012 CIS event in July
    to have more discussions on this topic and to seek additional workgroup
    members.


    I look forward to your review of this charter proposal and welcome
    feedback you may have on its scope and purpose.


    Regards,

    Greg


    *
    *

    *Charter submission for the Backplane Protocol Working Group*

    There is an interest in creating an OpenID workgroup to broaden
    collaboration in the development of the Backplane Protocol specification.

    *Charter Proposal*

    Following the OpenID Foundation?s IPR policies and procedures this note
    proposes the formation of a new working group chartered to broaden input
    into the development of a Backplane Protocol specification. The proposed
    charter is below and may change during the initial feedback period.

    *I. Name*

    Backplane Protocol Working Group

    *II. Statement of Purpose*

    Facilitate the creation of a trust framework between end users, websites
    and third-party applications such that all can exchange information with
    each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not
    required to be identity related or reference OpenID-authenticated users,
    these represent the most interesting use case and have constituted one of
    the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for
    inter-widget/inter-application identity message exchange, it would benefit
    all parties involved if the development of the protocol continued within
    the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by
    ensuring the specifications, reference and production implementations

    - adhere to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - are extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    *III. Background*

    Echo conceived the protocol and designed it as an open standard. They
    later partnered with Janrain and together have evolved the protocol,
    incorporating feedback received from interested Relying Parties as well as
    the community, including the Internet Identity Workshops in the Spring and
    Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application
    vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/>including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The
    Washington Post, Universal Music Group and USA Networks.

    *IV. Scope*

    The initial scope of effort by the working group is to ensure that the
    protocol


    - adheres to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - is extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    Scope also involves standardizing the definition and nomenclature of
    constructs that describe various aspects of the protocol e.g. message types
    or application scenarios, such that it appeals to the technology community
    at large.

    Scope does not include definition of additional message types (also
    currently known as application scenarios) or recruiting additional members
    beyond the initially formed working group.

    *V. Specifications*

    The core Backplane Exchange protocol specifications can be found at the
    URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft
    13, June 2012, HTML)

    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November 2010, HTML)

    *VI. Anticipated Audience*

    Interested parties would include:

    ? Website Operators that need to use third-party applications on
    their sites and want to improve usability and interoperability.
    ? Relying Parties that are looking to distribute personalized
    services on other portals versus their own websites.


    A number of participating websites and vendors interested in Backplane
    Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    *VII. Language of business*

    English.

    *VIII. Method of work*

    Mailing list discussion. Posting of intermediate drafts at
    http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
    ad-hoc basis.

    *IX. Basis for completion of the activity*

    When all items set forth in Section IV Scope have been addressed and
    agreed upon by members of the working group.

    *X. Initial Membership*

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo

    Yuri Lukyanov, Echo

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    *XI. Expected contribution*

    Draft: Backplane Exchange Specification 2.0 (draft 13)
    <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>



    _______________________________________________
    specs mailing list
    specs at lists.openid.net
    http://lists.openid.net/mailman/listinfo/openid-specs

    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120605/1bcd5a4a/attachment-0001.html>
  • Allen Tom at Jun 6, 2012 at 5:30 pm
    Hi Greg,

    Thanks for submitting the Backplane WG proposal. A few questions:


    1. Does the Backplane community already have signed IPR agreements from
    all contributors to the existing Backplane specs?
    2. What is the expected output of the working group? Finalized Backplane
    2.0 spec(s)? A reference Backplane server implementation?
    3. Will the OIDF host any services for Backplane? (similar to
    accountchooser.net)
    4. The WG Proposal says that one of the goals is to create a trust
    framework. Will there be some sort of certification process to determine if
    the apps/users/websites are trustworthy?
    5. Is the scope limited only to websites and JS widgets that embedded by
    websites? Does it also include native apps?


    Thanks,
    Allen

    On Tue, Jun 5, 2012 at 12:50 PM, Keegstra, Greg wrote:

    This is a formal request to the OpenID Specs Council to review the
    charter proposal for creating a Backplane Protocol working group.



    Participation and interest in the development of the protocol has grown
    out of recent Internet Identity Workshops. The potential formation of an
    OpenID work group is an opportunity to provide awareness about the
    Backplane Protocol globally so that more application vendors and website
    publishers will have the opportunity to guide its development and
    collaborate around use cases.



    If there is a positive response from the Specifications Council, we would
    like to work with the OIDF to schedule time at the 2012 CIS event in July
    to have more discussions on this topic and to seek additional workgroup
    members.



    I look forward to your review of this charter proposal and welcome
    feedback you may have on its scope and purpose.



    Regards,

    Greg



    *
    *

    *Charter submission for the Backplane Protocol Working Group*

    There is an interest in creating an OpenID workgroup to broaden
    collaboration in the development of the Backplane Protocol specification.

    *Charter Proposal*

    Following the OpenID Foundation?s IPR policies and procedures this note
    proposes the formation of a new working group chartered to broaden input
    into the development of a Backplane Protocol specification. The proposed
    charter is below and may change during the initial feedback period.

    *I. Name*

    Backplane Protocol Working Group

    *II. Statement of Purpose*

    Facilitate the creation of a trust framework between end users, websites
    and third-party applications such that all can exchange information with
    each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not
    required to be identity related or reference OpenID-authenticated users,
    these represent the most interesting use case and have constituted one of
    the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for
    inter-widget/inter-application identity message exchange, it would benefit
    all parties involved if the development of the protocol continued within
    the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by
    ensuring the specifications, reference and production implementations

    - adhere to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - are extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    *III. Background*

    Echo conceived the protocol and designed it as an open standard. They
    later partnered with Janrain and together have evolved the protocol,
    incorporating feedback received from interested Relying Parties as well as
    the community, including the Internet Identity Workshops in the Spring and
    Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application
    vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/>including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The
    Washington Post, Universal Music Group and USA Networks.

    *IV. Scope*

    The initial scope of effort by the working group is to ensure that the
    protocol


    - adheres to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - is extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    Scope also involves standardizing the definition and nomenclature of
    constructs that describe various aspects of the protocol e.g. message types
    or application scenarios, such that it appeals to the technology community
    at large.

    Scope does not include definition of additional message types (also
    currently known as application scenarios) or recruiting additional members
    beyond the initially formed working group.

    *V. Specifications*

    The core Backplane Exchange protocol specifications can be found at the
    URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft
    13, June 2012, HTML)

    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November 2010, HTML)

    *VI. Anticipated Audience*

    Interested parties would include:

    ? Website Operators that need to use third-party applications on
    their sites and want to improve usability and interoperability.

    ? Relying Parties that are looking to distribute personalized
    services on other portals versus their own websites.


    A number of participating websites and vendors interested in Backplane
    Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    *VII. Language of business*

    English.

    *VIII. Method of work*

    Mailing list discussion. Posting of intermediate drafts at
    http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
    ad-hoc basis.

    *IX. Basis for completion of the activity*

    When all items set forth in Section IV Scope have been addressed and
    agreed upon by members of the working group.

    *X. Initial Membership*

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo

    Yuri Lukyanov, Echo

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    *XI. Expected contribution*

    Draft: Backplane Exchange Specification 2.0 (draft 13)
    <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>





    _______________________________________________
    specs mailing list
    specs at lists.openid.net
    http://lists.openid.net/mailman/listinfo/openid-specs
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120606/eb6a1e0c/attachment.html>
  • Keegstra, Greg at Jun 8, 2012 at 9:08 pm
    Hi Allen,
    Appreciate the feedback on the proposal for the Backplane working group.
    Let me respond to each of your questions below.
    Does the Backplane community already have signed IPR agreements from all
    contributors to the existing Backplane specs?
    In progress.
    What is the expected output of the working group? Finalized Backplane 2.0
    spec(s)? A reference Backplane server implementation?
    The primary output is a finalized Backplane specification. The reference
    implementation is just a side effect but it is not the focus.
    Will the OIDF host any services for Backplane? (similar to
    accountchooser.net)
    None are planned, unless we want the OIDF to take over the Backplanex.com
    site.
    The WG Proposal says that one of the goals is to create a trust
    framework. Will there be some sort of certification process to determine if
    the apps/users/websites are trustworthy?
    None is planned but interested in your feedback here. The proposed trust
    framework will be presented primarily for reference purposes. Since the
    trust framework is between a site and the widgets on the site there is no
    immediate need for certification across a "global" trust framework.
    Is the scope limited only to websites and JS widgets that embedded by
    websites? Does it also include native apps?
    The scope encompasses both external and internal widgets. The origination
    of the widget is irrelevant to its utilization of the Backplane.

    Thanks,
    Greg
    On Wed, Jun 6, 2012 at 10:30 AM, Allen Tom wrote:

    Hi Greg,

    Thanks for submitting the Backplane WG proposal. A few questions:


    1. Does the Backplane community already have signed IPR agreements
    from all contributors to the existing Backplane specs?
    2. What is the expected output of the working group? Finalized
    Backplane 2.0 spec(s)? A reference Backplane server implementation?
    3. Will the OIDF host any services for Backplane? (similar to
    accountchooser.net)
    4. The WG Proposal says that one of the goals is to create a trust
    framework. Will there be some sort of certification process to determine if
    the apps/users/websites are trustworthy?
    5. Is the scope limited only to websites and JS widgets that embedded
    by websites? Does it also include native apps?


    Thanks,
    Allen

    On Tue, Jun 5, 2012 at 12:50 PM, Keegstra, Greg wrote:

    This is a formal request to the OpenID Specs Council to review the
    charter proposal for creating a Backplane Protocol working group.



    Participation and interest in the development of the protocol has grown
    out of recent Internet Identity Workshops. The potential formation of an
    OpenID work group is an opportunity to provide awareness about the
    Backplane Protocol globally so that more application vendors and website
    publishers will have the opportunity to guide its development and
    collaborate around use cases.



    If there is a positive response from the Specifications Council, we
    would like to work with the OIDF to schedule time at the 2012 CIS event
    in July to have more discussions on this topic and to seek additional
    workgroup members.



    I look forward to your review of this charter proposal and welcome
    feedback you may have on its scope and purpose.



    Regards,

    Greg



    *
    *

    *Charter submission for the Backplane Protocol Working Group*

    There is an interest in creating an OpenID workgroup to broaden
    collaboration in the development of the Backplane Protocol specification.

    *Charter Proposal*

    Following the OpenID Foundation?s IPR policies and procedures this note
    proposes the formation of a new working group chartered to broaden input
    into the development of a Backplane Protocol specification. The proposed
    charter is below and may change during the initial feedback period.

    *I. Name*

    Backplane Protocol Working Group

    *II. Statement of Purpose*

    Facilitate the creation of a trust framework between end users, websites
    and third-party applications such that all can exchange information with
    each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not
    required to be identity related or reference OpenID-authenticated users,
    these represent the most interesting use case and have constituted one of
    the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for
    inter-widget/inter-application identity message exchange, it would benefit
    all parties involved if the development of the protocol continued within
    the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by
    ensuring the specifications, reference and production implementations

    - adhere to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - are extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    *III. Background*

    Echo conceived the protocol and designed it as an open standard. They
    later partnered with Janrain and together have evolved the protocol,
    incorporating feedback received from interested Relying Parties as well as
    the community, including the Internet Identity Workshops in the Spring and
    Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application
    vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/>including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The
    Washington Post, Universal Music Group and USA Networks.

    *IV. Scope*

    The initial scope of effort by the working group is to ensure that the
    protocol


    - adheres to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    - is extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages


    Scope also involves standardizing the definition and nomenclature of
    constructs that describe various aspects of the protocol e.g. message types
    or application scenarios, such that it appeals to the technology community
    at large.

    Scope does not include definition of additional message types (also
    currently known as application scenarios) or recruiting additional members
    beyond the initially formed working group.

    *V. Specifications*

    The core Backplane Exchange protocol specifications can be found at the
    URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft
    13, June 2012, HTML)

    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November 2010, HTML)

    *VI. Anticipated Audience*

    Interested parties would include:

    ? Website Operators that need to use third-party applications on
    their sites and want to improve usability and interoperability.

    ? Relying Parties that are looking to distribute personalized
    services on other portals versus their own websites.


    A number of participating websites and vendors interested in Backplane
    Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    *VII. Language of business*

    English.

    *VIII. Method of work*

    Mailing list discussion. Posting of intermediate drafts at
    http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
    ad-hoc basis.

    *IX. Basis for completion of the activity*

    When all items set forth in Section IV Scope have been addressed and
    agreed upon by members of the working group.

    *X. Initial Membership*

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo

    Yuri Lukyanov, Echo

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    *XI. Expected contribution*

    Draft: Backplane Exchange Specification 2.0 (draft 13)
    <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>





    _______________________________________________
    specs mailing list
    specs at lists.openid.net
    http://lists.openid.net/mailman/listinfo/openid-specs

    --
    Greg Keegstra, Strategic Alliances Director, Janrain, Inc.
    e: greg at janrain.com | w: (415) 317-1142 | twitter: @keegstra
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120608/d40cd5de/attachment-0001.html>
  • Mike Jones at Jun 10, 2012 at 6:58 pm
    Hi Greg,

    Could you please send the board and specs-council a list of the individuals who have contributed to the specs and which of them you have OpenID IPR agreements from? That would help me (primarily as a board member) better understand where we are on this.

    Note: Having this isn't a requirement for approving creation of the working group. But having the work be IPR-clean is a requirement for eventually publishing Implementer's Drafts or Final Specifications.

    Best of wishes on moving this forward!

    Thanks,
    -- Mike

    From: openid-specs-council-bounces at lists.openid.net [mailto:openid-specs-council-bounces at lists.openid.net] On Behalf Of Keegstra, Greg
    Sent: Friday, June 08, 2012 2:08 PM
    To: Allen Tom
    Cc: openid-specs-council at lists.openid.net; specs at openid.net; Johnny Bufu
    Subject: Re: [OIDFSC] Backplane Protocol Working Group Charter Submission

    Hi Allen,
    Appreciate the feedback on the proposal for the Backplane working group. Let me respond to each of your questions below.
    Does the Backplane community already have signed IPR agreements from all contributors to the existing Backplane specs?
    In progress.
    What is the expected output of the working group? Finalized Backplane 2.0 spec(s)? A reference Backplane server implementation?
    The primary output is a finalized Backplane specification. The reference implementation is just a side effect but it is not the focus.
    Will the OIDF host any services for Backplane? (similar to accountchooser.net<http://accountchooser.net/>)
    None are planned, unless we want the OIDF to take over the Backplanex.com site.
    The WG Proposal says that one of the goals is to create a trust framework. Will there be some sort of certification process to determine if the apps/users/websites are trustworthy?
    None is planned but interested in your feedback here. The proposed trust framework will be presented primarily for reference purposes. Since the trust framework is between a site and the widgets on the site there is no immediate need for certification across a "global" trust framework.
    Is the scope limited only to websites and JS widgets that embedded by websites? Does it also include native apps?
    The scope encompasses both external and internal widgets. The origination of the widget is irrelevant to its utilization of the Backplane.

    Thanks,
    Greg
    On Wed, Jun 6, 2012 at 10:30 AM, Allen Tom <allentomdude at gmail.comwrote:
    Hi Greg,

    Thanks for submitting the Backplane WG proposal. A few questions:


    1. Does the Backplane community already have signed IPR agreements from all contributors to the existing Backplane specs?
    2. What is the expected output of the working group? Finalized Backplane 2.0 spec(s)? A reference Backplane server implementation?
    3. Will the OIDF host any services for Backplane? (similar to accountchooser.net<http://accountchooser.net>)
    4. The WG Proposal says that one of the goals is to create a trust framework. Will there be some sort of certification process to determine if the apps/users/websites are trustworthy?
    5. Is the scope limited only to websites and JS widgets that embedded by websites? Does it also include native apps?

    Thanks,
    Allen


    On Tue, Jun 5, 2012 at 12:50 PM, Keegstra, Greg <greg at janrain.comwrote:
    This is a formal request to the OpenID Specs Council to review the charter proposal for creating a Backplane Protocol working group.

    Participation and interest in the development of the protocol has grown out of recent Internet Identity Workshops. The potential formation of an OpenID work group is an opportunity to provide awareness about the Backplane Protocol globally so that more application vendors and website publishers will have the opportunity to guide its development and collaborate around use cases.

    If there is a positive response from the Specifications Council, we would like to work with the OIDF to schedule time at the 2012 CIS event in July to have more discussions on this topic and to seek additional workgroup members.

    I look forward to your review of this charter proposal and welcome feedback you may have on its scope and purpose.

    Regards,
    Greg


    Charter submission for the Backplane Protocol Working Group

    There is an interest in creating an OpenID workgroup to broaden collaboration in the development of the Backplane Protocol specification.

    Charter Proposal

    Following the OpenID Foundation's IPR policies and procedures this note proposes the formation of a new working group chartered to broaden input into the development of a Backplane Protocol specification. The proposed charter is below and may change during the initial feedback period.

    I. Name

    Backplane Protocol Working Group

    II. Statement of Purpose

    Facilitate the creation of a trust framework between end users, websites and third-party applications such that all can exchange information with each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not required to be identity related or reference OpenID-authenticated users, these represent the most interesting use case and have constituted one of the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for inter-widget/inter-application identity message exchange, it would benefit all parties involved if the development of the protocol continued within the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by ensuring the specifications, reference and production implementations

    * adhere to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website
    * are extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages

    III. Background

    Echo conceived the protocol and designed it as an open standard. They later partnered with Janrain and together have evolved the protocol, incorporating feedback received from interested Relying Parties as well as the community, including the Internet Identity Workshops in the Spring and Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/> including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The Washington Post, Universal Music Group and USA Networks.

    IV. Scope

    The initial scope of effort by the working group is to ensure that the protocol

    * adheres to best practices in online security as it pertains to broadcasting of user identity between multiple applications on a website
    * is extensible to support other application scenarios or message types to broaden the scope of inter-widget communications beyond identity messages

    Scope also involves standardizing the definition and nomenclature of constructs that describe various aspects of the protocol e.g. message types or application scenarios, such that it appeals to the technology community at large.

    Scope does not include definition of additional message types (also currently known as application scenarios) or recruiting additional members beyond the initially formed working group.

    V. Specifications

    The core Backplane Exchange protocol specifications can be found at the URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft 13, June 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/> (June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/> (June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0> (November 2010, HTML)

    VI. Anticipated Audience

    Interested parties would include:
    * Website Operators that need to use third-party applications on their sites and want to improve usability and interoperability.
    * Relying Parties that are looking to distribute personalized services on other portals versus their own websites.

    A number of participating websites and vendors interested in Backplane Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    VII. Language of business

    English.

    VIII. Method of work

    Mailing list discussion. Posting of intermediate drafts at http://backplanex.com<http://backplanex.com/> or the OpenID Wiki. Virtual conferencing on an ad-hoc basis.

    IX. Basis for completion of the activity

    When all items set forth in Section IV Scope have been addressed and agreed upon by members of the working group.

    X. Initial Membership

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo
    Yuri Lukyanov, Echo
    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    XI. Expected contribution

    Draft: Backplane Exchange Specification 2.0 (draft 13) <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>



    _______________________________________________
    specs mailing list
    specs at lists.openid.net<mailto:specs@lists.openid.net>
    http://lists.openid.net/mailman/listinfo/openid-specs




    --
    Greg Keegstra, Strategic Alliances Director, Janrain, Inc.
    e: greg at janrain.com<mailto:greg@janrain.com> | w: (415) 317-1142 | twitter: @keegstra
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120610/2cadabbd/attachment-0001.html>
  • Keegstra, Greg at Jun 11, 2012 at 2:31 pm
    Mike,
    Yes, agreed. In process and I will send you a list of the contributors as
    well as those who have signed the IPR agreements.

    Thanks
    Greg
    On Sun, Jun 10, 2012 at 11:58 AM, Mike Jones wrote:

    Hi Greg,****

    ** **

    Could you please send the board and specs-council a list of the
    individuals who have contributed to the specs and which of them you have
    OpenID IPR agreements from? That would help me (primarily as a board
    member) better understand where we are on this.****

    ** **

    Note: Having this isn?t a requirement for approving creation of the
    working group. But having the work be IPR-clean is a requirement for
    eventually publishing Implementer?s Drafts or Final Specifications.****

    ** **

    Best of wishes on moving this forward!****

    ** **

    Thanks,****

    -- Mike****

    ** **

    *From:* openid-specs-council-bounces at lists.openid.net [mailto:
    openid-specs-council-bounces at lists.openid.net] *On Behalf Of *Keegstra,
    Greg
    *Sent:* Friday, June 08, 2012 2:08 PM
    *To:* Allen Tom
    *Cc:* openid-specs-council at lists.openid.net; specs at openid.net; Johnny Bufu
    *Subject:* Re: [OIDFSC] Backplane Protocol Working Group Charter
    Submission****

    ** **

    Hi Allen,****

    Appreciate the feedback on the proposal for the Backplane working group.
    Let me respond to each of your questions below.****

    ** **
    Does the Backplane community already have signed IPR agreements from all
    contributors to the existing Backplane specs?****

    In progress. ****

    ** **
    What is the expected output of the working group? Finalized Backplane
    2.0 spec(s)? A reference Backplane server implementation?
    The primary output is a finalized Backplane specification. The reference
    implementation is just a side effect but it is not the focus.****

    Will the OIDF host any services for Backplane? (similar to
    accountchooser.net)
    None are planned, unless we want the OIDF to take over the Backplanex.com
    site.****

    ** **
    The WG Proposal says that one of the goals is to create a trust
    framework. Will there be some sort of certification process to determine if
    the apps/users/websites are trustworthy?
    None is planned but interested in your feedback here. The proposed trust
    framework will be presented primarily for reference purposes. Since the
    trust framework is between a site and the widgets on the site there is no
    immediate need for certification across a "global" trust framework. ****

    ** **
    Is the scope limited only to websites and JS widgets that embedded by
    websites? Does it also include native apps?
    The scope encompasses both external and internal widgets. The origination
    of the widget is irrelevant to its utilization of the Backplane.

    Thanks,
    Greg****

    On Wed, Jun 6, 2012 at 10:30 AM, Allen Tom wrote:
    ****

    Hi Greg,****

    ** **

    Thanks for submitting the Backplane WG proposal. A few questions:****

    ** **

    1. Does the Backplane community already have signed IPR agreements
    from all contributors to the existing Backplane specs?****
    2. What is the expected output of the working group? Finalized
    Backplane 2.0 spec(s)? A reference Backplane server implementation? **
    **
    3. Will the OIDF host any services for Backplane? (similar to
    accountchooser.net)****
    4. The WG Proposal says that one of the goals is to create a trust
    framework. Will there be some sort of certification process to determine if
    the apps/users/websites are trustworthy?****
    5. Is the scope limited only to websites and JS widgets that embedded
    by websites? Does it also include native apps?****

    ** **

    Thanks,****

    Allen****

    ** **

    ** **

    On Tue, Jun 5, 2012 at 12:50 PM, Keegstra, Greg wrote:*
    ***

    This is a formal request to the OpenID Specs Council to review the
    charter proposal for creating a Backplane Protocol working group. ****

    ****

    Participation and interest in the development of the protocol has grown
    out of recent Internet Identity Workshops. The potential formation of an
    OpenID work group is an opportunity to provide awareness about the
    Backplane Protocol globally so that more application vendors and website
    publishers will have the opportunity to guide its development and
    collaborate around use cases.****

    ****

    If there is a positive response from the Specifications Council, we would
    like to work with the OIDF to schedule time at the 2012 CIS event in July
    to have more discussions on this topic and to seek additional workgroup
    members.****

    ****

    I look forward to your review of this charter proposal and welcome
    feedback you may have on its scope and purpose.****

    ****

    Regards,****

    Greg****

    ****

    ** **

    *Charter submission for the Backplane Protocol Working Group*

    There is an interest in creating an OpenID workgroup to broaden
    collaboration in the development of the Backplane Protocol specification.

    *Charter Proposal*

    Following the OpenID Foundation?s IPR policies and procedures this note
    proposes the formation of a new working group chartered to broaden input
    into the development of a Backplane Protocol specification. The proposed
    charter is below and may change during the initial feedback period.

    *I. Name*

    Backplane Protocol Working Group

    *II. Statement of Purpose*

    Facilitate the creation of a trust framework between end users, websites
    and third-party applications such that all can exchange information with
    each other in a standardized way.

    While the messages exchanged through the Backplane Protocol are not
    required to be identity related or reference OpenID-authenticated users,
    these represent the most interesting use case and have constituted one of
    the main drivers behind the Backplane efforts to date.

    If Backplane continues to build momentum and becomes widely adopted for
    inter-widget/inter-application identity message exchange, it would benefit
    all parties involved if the development of the protocol continued within
    the OpenID Foundation.

    This workgroup intends to solidify the current proposed protocol by
    ensuring the specifications, reference and production implementations ****

    - adhere to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    ****
    - are extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages****


    *III. Background*

    Echo conceived the protocol and designed it as an open standard. They
    later partnered with Janrain and together have evolved the protocol,
    incorporating feedback received from interested Relying Parties as well as
    the community, including the Internet Identity Workshops in the Spring and
    Fall of 2011.

    The Backplane Exchange Protocol is currently used today by application
    vendors including Echo and Janrain and by website operators<http://backplanex.com/showcase/>including ABC, Discovery Channel, NBC Universal, Sports Illustrated, The
    Washington Post, Universal Music Group and USA Networks.

    *IV. Scope*

    The initial scope of effort by the working group is to ensure that the
    protocol****

    - adheres to best practices in online security as it pertains to
    broadcasting of user identity between multiple applications on a website
    ****
    - is extensible to support other application scenarios or message
    types to broaden the scope of inter-widget communications beyond identity
    messages****


    Scope also involves standardizing the definition and nomenclature of
    constructs that describe various aspects of the protocol e.g. message types
    or application scenarios, such that it appeals to the technology community
    at large.

    Scope does not include definition of additional message types (also
    currently known as application scenarios) or recruiting additional members
    beyond the initially formed working group.

    *V. Specifications*

    The core Backplane Exchange protocol specifications can be found at the
    URLs below:

    Version 2.0 (Latest Work)
    Backplane Exchange Specification 2.0<https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0> (draft
    13, June 2012, HTML)****

    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 12, May 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplane.wordpress.janrain.com/files/2012/05/backplane-2_0-draft12.pdf> (draft 10, March 2012, HTML)
    Backplane Exchange Specification 2.0<http://backplanex.com/documentation/backplane-specification-2-0/> (draft 07, January 2012, HTML)

    Version 1.0 (Currently in Production)
    Backplane Exchange Specification 1.2<http://backplanex.com/documentation/backplane-specification-1-2/>(June 2011, HTML)
    Backplane Exchange Specification 1.1<http://backplanex.com/documentation/backplane-specification-1-1/>(June 2011, HTML)
    Backplane Exchange Specification 1.0<http://backplanex.com/documentation/backplane-specification-1-0>(November 2010, HTML)

    *VI. Anticipated Audience*

    Interested parties would include:****

    ? Website Operators that need to use third-party applications on
    their sites and want to improve usability and interoperability.****

    ? Relying Parties that are looking to distribute personalized
    services on other portals versus their own websites.****


    A number of participating websites and vendors interested in Backplane
    Protocol and the advancement of the specifications are listed here.<http://backplanex.com/showcase/>

    *VII. Language of business*

    English.

    *VIII. Method of work*

    Mailing list discussion. Posting of intermediate drafts at
    http://backplanex.com or the OpenID Wiki. Virtual conferencing on an
    ad-hoc basis.

    *IX. Basis for completion of the activity*

    When all items set forth in Section IV Scope have been addressed and
    agreed upon by members of the working group.

    *X. Initial Membership*

    Johnny Bufu, Janrain
    Greg Keegstra, Janrain
    Vidya Shivkumar, Janrain
    Tom Raney, Janrain
    Vlad Skvortsov, Echo****

    Yuri Lukyanov, Echo****

    Alexander Zhuravlev, Echo
    Chris Saad, Echo

    *XI. Expected contribution*

    Draft: Backplane Exchange Specification 2.0 (draft 13)
    <https://docs.google.com/viewer?a=v&pid=forums&srcid=MTQ2NzA4MzgwMDk0MDY4NDM0MDABMTM2MTI2MTk1ODQ1OTQ4NDI5MTcBNEZCNDAxNUYuODAyMDUwNUBqYW5yYWluLmNvbQEyAQ&authuser=0>
    ****

    ****

    ****

    ** **

    _______________________________________________
    specs mailing list
    specs at lists.openid.net
    http://lists.openid.net/mailman/listinfo/openid-specs****

    ** **



    ****

    ** **

    --
    Greg Keegstra, Strategic Alliances Director, Janrain, Inc.
    e: greg at janrain.com | w: (415) 317-1142 | twitter: @keegstra ****


    --
    Greg Keegstra, Strategic Alliances Director, Janrain, Inc.
    e: greg at janrain.com | w: (415) 317-1142 | twitter: @keegstra
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.openid.net/pipermail/openid-specs-council/attachments/20120611/3a207b18/attachment-0001.html>

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupopenid-specs-council @
categoriesopenid
postedJun 5, '12 at 7:50p
activeJun 11, '12 at 2:31p
posts8
users6
websiteopenid.net
irc#openid

People

Translate

site design / logo © 2021 Grokbase