proposed charter clarification

["Philpott, Robert" <rphilpott@rsasecurity.com>]

As promised, here is the proposed text change to our charter that incorporates the goals adopted by the TC at the 16-Sep-2003 con-call meeting.  Please provide comments and be prepared to vote on this at the 14-Oct-2003 meeting.

 

The current full charter is available at:

http://www.oasis-open.org/committees/security/charter.php

 

The current OASIS TC process is at:

http://www.oasis-open.org/committees/process.php#formation

 

I propose changing the "List of Deliverables" section to:

--------------------------------------

Scope of Work and List of Deliverables

The TC held its first meeting by telephone on 9 January 2001. On 5 November 2002, the suite of SAML V1.0 specifications was approved as an OASIS Standard. On 2 September 2003, the suite of SAML V1.1 specifications was approved as an OASIS Standard.

The TC is engaged in evolving the suite of SAML specifications with a V2.0 release targeted for the middle of 2004. The goals of the SAML 2.0 effort include:

• Addressing issues and enhancement requests that have arisen from experience with real-world SAML implementations and with standards architectures that use SAML, such as the OASIS WSS and XACML work.

 

• Adding support for features that were deferred from previous versions of SAML for schedule reasons, such as session support, the exchange of metadata to ensure more interoperable interactions, and collection of credentials.

 

• Converging on a unified technology approach for identity federation by integrating the specifications contributed to the TC by the Liberty Alliance.

Auxiliary documents (such as new SAML profile specifications) and additional versions may also be produced at the Committee's discretion. The TC's intent is to pursue OASIS Standard status for all SAML Committee Specifications.

--------------------------------------

 

 

The old deliverables section stated:

List of Deliverables

The TC held its first meeting by telephone on 9 January 2001. On 31 May 2002 it delivered a suite of SAML V1.0 Committee Specifications to the OASIS membership for review. On 5 November 2002 the SAML V1.0 specifications were declared to be approved as an OASIS Standard.

The TC plans to complete the following tasks:

• By summer 2003: SAML V1.1 Committee Specifications. Items considered for SAML V1.1 may include backwards-compatible bug fixes, as well as high-priority new functionality that is backwards-compatible with or orthogonal to the existing design.
• By the end of 2003: SAML V2.0 Committee Specifications. Items considered for SAML V2.0 may include functionality that satisfies major requirements that were deferred from SAML V1.0, as well as new functionality satisfying newly discovered requirements (for example, through implementation and deployment of the existing specifications).

Auxiliary documents (such as SAML profile specifications) and additional versions may also be produced at the Committee's discretion. The TC's intent is to pursue OASIS Standard status for all SAML Committee Specifications.

--------------------------------------

Note that the TC process states the following about the charter:

The charter of the TC, which includes only the following items

1. The name of the TC, such name not to have been previously used for an OASIS TC and not to include any trademarks or service marks not owned by OASIS;
2. A statement of purpose, including a definition of the problem to be solved;
3. The scope of the work of the TC, which must be germane to the mission of OASIS, and which includes a definition of what is and what is not the work of the TC, and how it can be determined when the work of the TC has been completed. The scope may reference a specific contribution of existing work as a starting point, but other contributions may be made by TC members on or after the first meeting of the TC. Such other contributions will be considered by the voting members of the TC on an equal basis to improve the original starting point contribution.
4. A list of deliverables, with completion dates;
5. The anticipated audience or users of the work; and
6. The language in which the TC will conduct business;

 

Rob Philpott
RSA Security Inc.
The Most Trusted Name in e-Security
Tel: 781-515-7115
Mobile: 617-510-0893
Fax: 781-515-7020
mailto:rphilpott@rsasecurity.com