1.
|
Clear description of the referenced document:
|
|
Name:
|
SOAP Version 1.2 Part 1
|
Title:
|
|
|
2.
|
Status of approval:
|
|
The referred standards were approved by OASIS.
|
3.
|
Justification for the specific reference:
|
|
Draft Rec. X.websec-3 refers to and makes use of the WS-SecurityPolicy as a security policy mechanism, OASIS Standard, WS-SecurityPolicy v1.2, 2007.
|
4.
|
Current information, if any, about IPR issues:
|
|
See http://www.oasis-open.org/
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
The status of all the referred documents are "approved documents"
|
6.
|
The degree of stability or maturity of the document:
|
|
The status of all the referred documents are "approved documents"
|
7.
|
Relationship with other existing or emerging documents:
|
|
References within the referenced standards are listed under item (8).
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
[GLOSS] Informational RFC 2828, "Internet Security Glossary," May 2000./
[KERBEROS] J. Kohl and C. Neuman, "The Kerberos Network Authentication Service (V5)," RFC 1510, September 1993, http://www.ietf.org/rfc/rfc1510.txt ./
[KEYWORDS] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels," RFC 2119, Harvard University, March 1997./
[SHA-1] FIPS PUB 180-1. Secure Hash Standard. U.S. Department of Commerce / National Institute of Standards and Technology. http://csrc.nist.gov/publications/fips/fips180-1/fip180-1.txt/
[SOAP11] W3C Note, "SOAP: Simple Object Access Protocol 1.1," 08 May 2000./
[SOAP12] W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework", 23 June 2003./
[SOAPSEC] W3C Note, "SOAP Security Extensions: Digital Signature," 06 February 2001./
[URI] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax," RFC 3986, MIT/LCS, Day Software, Adobe Systems, January 2005./
[XPATH] W3C Recommendation, "XML Path Language", 16 November 1999/
Non-normative references /
[WS-SECURITY] "Web Services Security Language", IBM, Microsoft, VeriSign, April 2002./
"WS-Security Addendum", IBM, Microsoft, VeriSign, August 2002./
"WS-Security XML Tokens", IBM, Microsoft, VeriSign, August 2002./
[XMLC14N] W3C Recommendation, "Canonical XML Version 1.0," 15 March 2001./
[EXCC14N] W3C Recommendation, "Exclusive XML Canonicalization Version 1.0," 8 July 2002./
[XMLENC] W3C Working Draft, "XML Encryption Syntax and Processing," 04 March 2002./
W3C Recommendation, "Decryption Transform for XML Signature", 10 December 2002./
[XML-ns] W3C Recommendation, "Namespaces in XML," 14 January 1999./
[XMLSCHEMA] W3C Recommendation, "XML Schema Part 1: Structures,"2 May 2001. W3C Recommendation, "XML Schema Part 2: Datatypes," 2 May 2001./
[XMLSIG] D. Eastlake, J. R., D. Solo, M. Bartel, J. Boyer , B. Fox , E. Simon. XML2291 Signature Syntax and Processing, W3C Recommendation, 12 February 2002/
|
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):
|
|
None
|
|