|
Does the TC approve the listed cross-reference updates to WSS V1.1.1?
In regards to the TC's approval of Web Services Security Version 1.1.1 Committee Specification 01 as a Candidate OASIS Standard (balloted in https://www.oasis-open.org/apps/org/workgroup/wss-m/ballot.php?id=2154), do the TC members approve requesting TC Administration make the Designated Cross Reference Changes listed below?
List of changes:
In Web Services Security Version 1.1.1 Part: Kerberos Token Profile, Line numbers: 233-235
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
In Web Services Security Version 1.1.1 Part: Rights Expression Language (REL) Token Profile, Line numbers: 614-616
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee
Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
In Web Services Security Version 1.1.1 Part: SAML Token Profile, Line numbers: 1109-1111
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
In Web Services Security Version 1.1.1 Part: SOAP Message with Attachments (SwA) Profile, Line numbers: 120-122
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
In Web Services Security Version 1.1.1 Part: Username Token Profile, Line numbers: 353-355
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee
Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
In Web Services Security Version 1.1.1 Part: X.509 Certificate Token Profile, Line numbers: 423-425
- Current Normative reference: A. Nadalin et al., Web Services Security: SOAP Message Security 1.1.1 http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd01/wss-SOAPMessageSecurity-v1.1.1-csd01.pdf
- Expected Status and date: WSS SOAP Message Security is a Committee Specification 01 as of 30 September 2011. Expected to be an OASIS Standard in March/April 2012
Expected cross-references after approval:
(1)
[WSS-SOAP-Message-Security-V1.1.1] Web Services Security: SOAP
Message Security Version 1.1.1. 30 September 2011. Committee
Specification 01. http://docs.oasis-open.org/wss-m/wss/v1.1.1/cs01/wss-SOAPMessageSecurity-v1.1.1-cs01.html.
(2) Contingent upon membership approval of WSS V1.1.1 as an OASIS Standard
[WSS-SOAP-Message-Security-V1.1.1] Web Services Security: SOAP
Message Security Version 1.1.1. . OASIS Standard.
http://docs.oasis-open.org/wss-m/wss/v1.1.1/os/wss-SOAPMessageSecurity-v1.1.1-os.html.
Designated Cross-Reference Changes requested in accordance with the requirements of Section 2.19 of the TC Process. TC acknowledges that publication may be delayed pending completion of these cross-references.
This ballot requires a Special Majority Vote [1]. The TC roster currently lists 8 voting members. In order to pass, at least 6 members have to vote Yes and no more than 2 members may vote No.
[1] http://www.oasis-open.org/policies-guidelines/tc-process#dSpecialMajority
[2] http://www.oasis-open.org/policies-guidelines/tc-process#cos-Submission-section
|
