|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
OASIS Standard approved 2 February 2009.
|
|
3.
|
Justification for the specific reference:
|
|
|
The OASIS Web Services Reliable Messaging (WS-ReliableMessaging) Version 1.2 is needed for web services security in applications defined in Continua Design Guidelines. WS-ReliableMessaging describes a protocol that allows messages to be transferred reliably between nodes implementing this protocol in the presence of software component, system, or network failures. The protocol is described in WS-ReliableMessaging in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within WS-ReliableMessaging.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
N/A
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standard approved 2 February 2009. This specification replaces or supersedes OASIS WS-ReliableMessaging v1.1.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standard approved 2 February 2009.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
N/A
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
1.2 Normative References/
/
[KEYWORDS] S. Bradner, “Key words for use in RFCs to Indicate Requirement Levels,” RFC 2119, Harvard University, March 1997/
http://www.ietf.org/rfc/rfc2119.txt/
/
[WS-RM Policy] OASIS Standard, "Web Services Reliable Messaging Policy Assertion( WS-RM Policy)," February 2009/
http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-os.doc/
/
[SOAP 1.1] W3C Note, "SOAP: Simple Object Access Protocol 1.1," 08 May 2000./
http://www.w3.org/TR/2000/NOTE-SOAP-20000508//
/
[SOAP 1.2] W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework" June 2003./
http://www.w3.org/TR/2003/REC-soap12-part1-20030624//
/
[URI] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax," RFC 3986, MIT/LCS, U.C. Irvine, Xerox Corporation, January 2005./
http://ietf.org/rfc/rfc3986/
/
[UUID] P. Leach, M. Mealling, R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace," RFC 4122, Microsoft, Refactored Networks - LLC, DataPower Technology Inc, July 2005/
http://www.ietf.org/rfc/rfc4122.txt/
/
[XML] W3C Recommendation, "Extensible Markup Language (XML) 1.0 (Fourth Edition)", September 2006./
http://www.w3.org/TR/REC-xml//
/
[XML-ns] W3C Recommendation, "Namespaces in XML," 14 January 1999./
http://www.w3.org/TR/1999/REC-xml-names-19990114//
/
[XML-Schema Part1] W3C Recommendation, "XML Schema Part 1: Structures," October 2004./
http://www.w3.org/TR/xmlschema-1//
/
[XML-Schema Part2] W3C Recommendation, "XML Schema Part 2: Datatypes," October 2004./
http://www.w3.org/TR/xmlschema-2//
/
[XPATH 1.0] W3C Recommendation, "XML Path Language (XPath) Version 1.0," 16 November 1999./
http://www.w3.org/TR/xpath/
/
[WSDL 1.1] W3C Note, "Web Services Description Language (WSDL 1.1)," 15 March 2001./
http://www.w3.org/TR/2001/NOTE-wsdl-20010315/
/
[WS-Addressing] W3C Recommendation, “Web Services Addressing 1.0 – Core,” May 2006./
http://www.w3.org/TR/2006/REC-ws-addr-core-20060509//
W3C Recommendation, “Web Services Addressing 1.0 – SOAP Binding,” May 2006/
http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509//
1.3 Non-Normative References/
/
[BSP 1.0] WS-I Working Group Draft. "Basic Security Profile Version 1.0," August 2006/
http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html/
/
[RDDL 2.0] Jonathan Borden, Tim Bray, eds. “Resource Directory Description Language (RDDL) 2.0,” January 2004/
http://www.openhealth.org/RDDL/20040118/rddl-20040118.html/
/
[RFC 2617] J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Loutonen, L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication," June 1999./
http://www.ietf.org/rfc/rfc2617.txt/
/
[RFC 4346] T. Dierks, E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.1," April 2006./
http://www.ietf.org/rfc/rfc4346.txt/
/
[WS-Policy] W3C Recommendation, "Web Services Policy 1.5 - Framework," September 2007./
http://www.w3.org/TR/2007/REC-ws-policy-20070904/
/
[WS-PolicyAttachment] W3C Recommendation, "Web Services Policy 1.5 - Attachment," September 2007./
http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904/
/
[WS-Security] Anthony Nadalin, Chris Kaler, Phillip Hallam-Baker, Ronald Monzillo, eds. "OASIS Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)", OASIS Standard 200401, March 2004./
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf/
/
Anthony Nadalin, Chris Kaler, Phillip Hallam-Baker, Ronald Monzillo, eds. "OASIS Web Services Se-curity: SOAP Message Security 1.1 (WS-Security 2004)", OASIS Standard 200602, February 2006./
http://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-SOAPMessageSecurity.pdf/
/
[RTTM] V. Jacobson, R. Braden, D. Borman, "TCP Extensions for High Performance", RFC 1323, May 1992./
http://www.rfc-editor.org/rfc/rfc1323.txt/
/
[SecurityPolicy] OASIS Standard, "WS-SecurityPolicy 1.3", February 2009/
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.doc/
/
[SecureConversation] OASIS Standard, "WS-SecureConversation 1.4", February 2009/
http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc/
/
[Trust] OASIS Standard, "WS-Trust 1.4", February 2009/
http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/os/ws-trust-1.4-spec-os.doc
|
|
9.
|
Qualification of
OASIS:
|
|
|
OASIS is recognized under the provisions of ITU-T Recommendations A.5 and A.4. Qualifying information is on file at TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
N/A
|
|
