(1) WG NAME: (and any acronym or abbreviation of the name): The WG name, acronym and abbreviation must not include trademarks not owned by the Organization, or content that is infringing, harmful, or inappropriate.
User-Managed Access (UMA) Work Group
(2) PURPOSE: Please provide a clear statement of purpose and justification why the proposed WG is necessary.
The purpose of this Work Group is to develop a set of draft specifications that enable an individual to control the authorization of data sharing and service access made between online services on the individual's behalf, and to facilitate the development of interoperable implementations of these specifications by others.
The Work Group is necessary to expedite the process of gathering representatives of many different communities - working in areas such as identity management (including user-centric identity), vendor relationship management, and distributed authorization - to collaborate on a draft solution that meets their shared goals in this area.
Specifically, this Work Group is responsible for:
It is anticipated that the work done to date on ProtectServe/Relationship Manager concepts and flows will be leveraged to meet these goals.
(3) SCOPE: Explain the scope and definition of the planned work.
The specifications must meet the following basic functional requirements, in addition to specific use cases and requirements later identified by this Work Group:
The specifications must meet the following basic design principles, in addition to any emergent design principles later identified by this Work Group:
The following are examples of design solutions that are initially out of scope for the first version of the group's output, though the group should avoid precluding such solutions, if possible:
The following is an example of a set of design solutions that we anticipate can be incorporated by reference to external specifications:
(4) DRAFT TECHNICAL SPECIFICATIONS: List Working Titles of draft Technical Specifications to be produced (if any), projected completion dates, and the Standards Setting Organization(s) to which they will be submitted upon approval by the Membership.
It is anticipated that the following technical specifications will be produced, with modular spec boundaries subject to change; both are anticipated to be submitted to the IETF for further work and completion:
(5) OTHER DRAFT RECOMMENDATIONS: Other Draft Recommendations and projected completion dates for submission for All Member Ballot.
It is anticipated that the following auxiliary materials will be produced, at a minimum:
At the group's option, some of this material may be considered non-normative (equivalent to white papers), and some may be split up into multiple pieces (for example, an Overview document and companion slide deck).
(6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants.
(7) AUDIENCE: Anticipated audience or users of the work.
The anticipated audience for the documents produced by this Work Group includes developers, deployers, and designers of online services that act on behalf of individual users. The group also anticipates gathering input from individual users of online services in order to respond to their needs and preferences.
(8) DURATION: Objective criteria for determining when the work of the WG has been completed (or a statement that the WG is intended to be a standing WG to address work that is expected to be ongoing).
This Work Group will target producing use cases and requirements within 6 months of inception in order to guide its design effort, and will target 18-24 months overall to develop a V1.0 set of technical specifications and other auxiliary materials, facilitating the development of multiple independent draft implementations as appropriate during this time. This targeted duration and other aspects of this charter (except the IPR policy stated below) are subject to review, amendment, and extension as approved by the Kantara Leadership Council.
(9) IPR POLICY: The Organization approved Intellectual Property Rights Policy under which the WG will operate.
10) RELATED WORK AND LIAISONS: Related work being done in other WGs or other organizations and any proposed liaison with those other WGs or organizations.
This Work Group has a number of dependencies on, and shared goals with, the output of other efforts. The Kantara groups and external efforts with which this Work Group intends to liaise informally include (but are not limited to):
(11) CONTRIBUTIONS (optional): A list of contributions that the proposers anticipate will be made to the WG.
It is anticipated that the draft ProtectServe protocol flow diagrams will be contributed.
(12) PROPOSERS: Names, email addresses, and any constituent affiliations of at least the minimum set of proposers required to support forming the WG.
Is this site useful to you? Please share it!
| | More
Pages in this Space: