OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: WS-SecureConversation 1.4 Submitted for OASIS Standard

OASIS Members:

The OASIS Web Services Secure Exchange (WS-SX) Technical Committee has
submitted the following specification, which is an approved Committee
Specification, to be considered as an OASIS Standard:

WS-SecureConversation 1.4

The text of the TC submission is appended.

You now have until 15 January to familiarize yourself with the submission
and provide input to your organization's voting representative.

On 16 January, a Call For Vote will be issued to all Voting Representatives
of OASIS member organizations. They will have until the last day of January,
inclusive, to cast their ballots on whether this Committee Specification
should be approved as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through

In accordance with the OASIS Technical Committee Process, this Committee
Specification has already completed the necessary 60-day public review
period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS
Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly


Mary P McRae
Director, Technical Committee Administration
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org  
web: www.oasis-open.org
phone: 1.603.232.9090

(a) Links to the approved Committee Specification in the TC's document
repository, and any appropriate supplemental documentation for the
specification, both of which must be written using the OASIS templates. 

SecureConversation v1.4
Editable Source (Word):

(b) The editable version of all files that are part of the Committee
See above.

 (c) Certification by the TC that all schema and XML instances included in
the specification, whether by inclusion or reference, including fragments of
such, are well formed, and that all expressions are valid;

Yes the XML has been verified.
See http://lists.oasis-open.org/archives/ws-sx/200812/msg00011.html

(d) A clear English-language summary of the specification; 

The WS-SecureConversation specification defines extensions to allow security
context establishment and sharing, and session key derivation.  This allows
contexts to be established and potentially more efficient keys or new key
material to be exchanged, thereby increasing the overall performance and
security of the subsequent exchanges.  The security context is defined as a
new WS-Security token type that is obtained using a binding of WS-Trust.

(e) A statement regarding the relationship of this specification to similar
work of other OASIS TCs or other standards developing organizations; 

This  specification utilizes the WS-Security specification and optionally
utilizes the SAML specifications. 
(f) Certification by at least three OASIS member organizations that they are
successfully using the specification; 


 (g) The beginning and ending dates of the public review(s), a pointer to
the announcement of the public review(s), and a pointer to an account of
each of the comments/issues raised during the public review period(s), along
with its resolution; 
Began 24 July 2008 and ended 23 September 2008
Issues and resolutions: http://docs.oasis-open.org/ws-sx/issues/Issues.xml

(h) An account of and results of the voting to approve the specification as
a Committee Specification, including the date of the ballot and a pointer to
the ballot; 

(i) An account of or pointer to votes and comments received in any earlier
attempts to standardize substantially the same specification, together with
the originating TC's response to each comment;

(j) A pointer to the publicly visible comments archive for the originating

(k) A pointer to any minority reports submitted by one or more Members who
did not vote in favor of approving the Committee Specification, which report
may include statements regarding why the member voted against the
specification or that the member believes that Substantive Changes were made
which have not gone through public review; or certification by the Chair
that no minority reports exist. 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]