[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: WS-Trust 1.3 and WS-SecureConversation 1.3 Submitted for OASIS Standard
OASIS Members: The OASIS Web Services Secure Exchange (WS-SX) Technical Committee has submitted the following specification set, which is an approved Committee Specification, to be considered as an OASIS Standard: WS-Trust 1.3 and WS-SecureConversation 1.3 The text of the TC submission is appended. You now have until 15 February to familiarize yourself with the submission and provide input to your organization's voting representative. On 16 February, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have until the last day of February, 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 member-discuss@lists.oasis-open.org. 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 http://www.oasis-open.org/committees/process.php#3.4 Any statements related to the IPR of this specification are posted at: http://www.oasis-open.org/committees/ws-sx/ipr.php Your participation in the review and balloting process is greatly appreciated. Mary Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org phone: 603.232.9090 ----------------------- WS-SX OASIS Submission of WS-Trust 1.3 and WS-SecureConversation 1.3 Simultaneously with the approval of a Committee Specification or at a later date, a TC may resolve by Special Majority Vote to submit the Committee Specification to the membership of OASIS for consideration as an OASIS Standard. Upon resolution of the TC to submit the specification, its Chair shall submit the following items to the TC Administrator: (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. Trust http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-spec-cs-01.doc http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-spec-cs-01.pdf http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-spec-cs-01.htm Schema/WSDL: http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3.xsd http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3.wsdl SecureConversation http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-spec-cs-01.doc http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-spec-cs-01.pdf http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-spec-cs-01.htm Schema: http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3.xsd (b) The editable version of all files that are part of the Committee Specification; Trust: http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-spec-cs-01.doc or SecureConversation: http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-spec-cs-01.doc (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 (d) A clear English-language summary of the specification; The WS-Trust specification uses the base mechanisms of WS-Security and defines additional primitives and extensions for security token exchange to enable the issuance and dissemination of credentials within different trust domains. Specifically, WS-Trust provides methods for issuing, renewing, and validating security tokens and ways to establish assess the presence of, and broker trust relationships. 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; These specifications utilize the WS-Security specifications and optionally utilize the SAML specifications. (f) Certification by at least three OASIS member organizations that they are successfully using the specification; Microsoft: http://www.oasis-open.org/apps/org/workgroup/ws-sx/email/archives/200612/msg00002.html IBM: http://www.oasis-open.org/apps/org/workgroup/ws-sx/email/archives/200612/msg00003.html Sun Microsystems: http://www.oasis-open.org/apps/org/workgroup/ws-sx/email/archives/200612/msg00016.html (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; 15 September 2006 to ends 14 November 2006 (see http://www.oasis-open.org/apps/org/workgroup/ws-sx/email/archives/200609/msg00039.html) Issues and resolutions: http://www.oasis-open.org/apps/org/workgroup/ws-sx/email/archives/200612/msg00000.html (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; http://www.oasis-open.org/apps/org/workgroup/ws-sx/ballot.php?id=1164 (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; N/A (j) A pointer to the publicly visible comments archive for the originating TC; http://lists.oasis-open.org/archives/ws-sx-comment/ (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. N/A
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]