Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

1) WG NAME

 
eGovernment Work Group (eGov)
 
(2) PURPOSE: Please provide a clear statement of purpose and justification why the proposed WG is necessary.
 
The eGovernment Work Group (eGov WG) will be responsible for:
 
Facilitating collaboration and discussion among Kantara members with an interest in eGovernment federated identity management applications and services

Acting as a forum to identify core requirements toward the development of policy best practices in the government sector on national, regional and municipal levels.

Identify profiles of these core requirements to address the unique aspects each government must address when binding policy to the technology of Federated Identity Management programs.

Acting as a forum to collect requirements for technical interoperability and assured Trusted Identities for assessment and approval under the Kantara Interoperability and assurance programs.

Presenting "a government view" into other Kantara Work Groups so that these views may be taken into account in the development of Kantara Initiative Policy Recommendations and Specifications for future contribution to an appropriate Standards Setting Organization

Promoting the development, adoption and support for eGovernment deployment profiles of open specifications.


To accomplish this goal the eGov Work Group shall:
 
Provide Kantara with subject matter expertise on government-related requirements, challenges for existing and potential work areas

Provide an information sharing and feedback forum for any Kantara participants, Discussion and Work Groups with an interest in eGovernment, and to communicate core findings and concerns of the Work Group to the relevant Kantara organizational entities.

Where appropriate (e.g. employee able to represent his/her employer), take part in the identification, planning, execution and follow-up of Government-focused industry events and provide Kantara with spokespersons on eGovernment-related topics.

Where appropriate, recommend liaison relationships for Kantara that will further adopt and deploy OASIS SAML 2.0, OAuth based Specification Sets solutions or extensions thereof.

Share solutions and/or technical approaches to avoid 'reinventing the wheel' and to drive adoption of standards-based identity management mechanisms in government on a global basis.
 
(3) SCOPE:
 
Specific Objectives of the eGov Work Group shall:

In respect to the Identity Assurance Framework (IAF 2.0); gather requirements for an eGov profile of the IAF v2.0 Service Assessment Criteria (SACs) or component SACs, and revise as new requirements emerge. Document eGov use cases requiring federation and identify and agree a common set and format of identity attributes used by governments.

In respect to authentication protocols; gather requirements for (and any suggested tests for) the Test Plan to test the presence of and SAML 2.0 conformance with the SAML 2.0 web browser SSO eGov Implementation Profile V2.0, for consumption by the Kantara Federation Interoperability Working Group, and ultimately the Interoperability Review Board.  Continue to develop an operational checklist for the federation and trust aspects of deployments of OASIS SAML 2.0, OAuth 2.0 based Specification Sets solutions or extensions thereof.  Continued input into the Authentication Context Level of Assurance Profile submitted to OASIS SSTC (ongoing as required).

Work in concert with other Kantara groups on further requirements and formalization reflecting deployment experiences, for example (but not limited to); refinement and promotion of privacy, security and legal Frameworks, deployment guidelines for Circles of Trust, IAF and related SAC specifications as required, liability issues between Identity Providers surrounding public/private circles of trust.

 

 
(4) DRAFT TECHNICAL SPECIFICATIONS:
 
No draft technical specifications are planned at this time.

Reports may be developed as appropriate and identified by the eGov WG.
 
(5) OTHER DRAFT RECOMMENDATIONS:
 
No other draft recommendations are planned at this time
 
(6) LEADERSHIP: Proposed WG Chair and Editor(s) (if any) subject to confirmation by a vote of the WG Participants.
 
Rainer Hoerbe, Kismed, Austria (Chair)
Keith Uber, Ubisecure, Finland (Vice Chair)
Colin Wallis, New Zealand Government, Department of Internal Affairs (Vice Chair)
 
(7) AUDIENCE:
 
International Government Electronic Service Delivery administrations and their applicable federated identity service organizations
 
(8) DURATION:

 
The Kantara Leadership Council charters the eGovernment Work Group for two years, expiring in 2014. The fixed end date is to allow for the current work to complete, any subsequent work following the Recommendations to complete, and force a review of whether 'eGov' continues to pose significantly special or different challenges to those faced by other large enterprises. 
 
The charter may be amended from time to time, with changes approved by the Leadership Council. 
 
(9) IPR POLICY:
 
Creative Commons Attribution Share Alike option
 
(10) RELATED WORK AND LIAISONS:
 
Kantara Work Groups (such as the Identity Assurance WG, Privacy & Public Policy WG, Health Identity Assurance Work Group, Info Sharing WG and Federation Interoperability WG and others as they come into existence) as required.

The expected liaisons with SDOs are: OASIS eGov Member Section, OASIS Transformational Government TC, Oasis Trust Elevation TC, OASIS Security Services TC, Open Identity Exchange (OIX), IETF, W3C eGov, UN/ CEFACT TBG19 (eGov), IDABC, APEC, ISO SC27 WG5, ITU-T and other sector based organizations and groups as required.

 

Where the eGov WG contributes to existing liaison relationships which are subject to 3rd party confidentiality (such as ITU-T and ISO) the eGov WG will manage such input through the Kantara Board of Trustee Liaison Sub-Committee.

(11) CONTRIBUTIONS (optional):  

No contributions are expected at this time

(12) MEETING PROCEDURE:

Meetings will be conducted under The Chatham House Rule as the default (see http://www.chathamhouse.org.uk/about/chathamhouserule/ ). However, any individual making a statement retains the right to opt out of the rule and direct the minutes to record that same individual's attribution to the statement.

(13) PROPOSERS:

  • Rainer Hoerbe, KisMed, Austria, rainer (at) hoerbe (dot) at
  • Colin Wallis, New Zealand Government, Department of Internal Affairs, colin (dot) wallis (at) dia (dot) govt (dot) nz
  • Keith Uber, Ubisecure, Finland, keith (dot) uber (at) ubisecure (dot) com
  • Ken Dagg, Government of Canada, Treasury Board Secretariat, kenneth (dot) dagg (at) tbs-sct (dot) gc (dot) ca
  • John Bradley, Ping Identity, jbradley (at) pingidentity (dot) com

 

 

History

Date

Note

November 07, 2012

The Leadership Council accepts this charter for operation.

  • No labels