| 
                                
                                    | 1. | Clear description of the referenced document: |  
                                    |  |  |  
                                    | 2. | Status of approval: |  
                                    |  | Approved OASIS Standard, 1 February 2006 |  
                                    | 3. | Justification for the specific reference: |  
                                    |  | SAML Token Profile 1.1 is needed for web services security in applications defined in Continua Design Guidelines. |  
                                    | 4. | Current information, if any, about IPR issues: |  
                                    |  | N/A |  
                                    | 5. | Other useful information describing the "Quality" of the document: |  
                                    |  | Approved OASIS Standard, 1 February 2006. |  
                                    | 6. | The degree of stability or maturity of the document: |  
                                    |  | Approved OASIS Standard, 1 February 2006. |  
                                    | 7. | Relationship with other existing or emerging documents: |  
                                    |  | N/A. |  
                                    | 8. | Any explicit references within that referenced document should also be listed: |  
                                    |  | [GLOSSARY] Informational RFC 2828, "Internet Security Glossary," May 2000./ [KEYWORDS] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels," RFC 2119, Harvard University, March 1997/
 [SAMLBindV1] Oasis Standard, E. Maler, P.Mishra, and R. Philpott (Editors), Bindings and Profiles for the OASIS Security Assertion Markup Language (SAML) V1.1,September 2003./
 [SAMLBindV2] Oasis Standard, S. Cantor, F. Hirsch, J. Kemp, R. Philpott, E. Maler (Editors),Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0,March 2005./
 [SAMLCoreV1] Oasis Standard, E. Maler, P.Mishra, and R. Philpott (Editors), Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V1.1,September 2003./
 [SAMLCoreV2] Oasis Standard, S. Cantor, J. Kemp, R. Philpott, E. Maler (Editors), Assertions and Protocol for the OASIS Security Assertion Markup Language (SAML) V2.0,March 2005./
 [SOAP] W3C Note, "SOAP: Simple Object Access Protocol 1.1," 08 May 2000. W3C Working Draft, Nilo Mitra (Editor), SOAP Version 1.2 Part 0: Primer, June 2002. W3C Working Draft, Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean- Jacques Moreau, Henrik Frystyk Nielsen (Editors), SOAP Version 1.2 Part 1: Messaging Framework, June 2002. W3C Working Draft, Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean- Jacques Moreau, Henrik Frystyk Nielsen (Editors), SOAP Version 1.2 Part 2: Adjuncts, June 2002./
 [URI] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax," RFC 2396, MIT/LCS, U.C. Irvine, Xerox Corporation, August 1998./
 [WS-SAML] Contribution to the WSS TC, P. Mishra (Editor), WS-Security Profile of the Security Assertion Markup Language (SAML) Working Draft 04, Sept 2002. /
 [WSS: SAML Token Profile] Oasis Standard, P. Hallem-Baker, A. Nadalin, C. Kaler, R. Monzillo (Editors), Web Services Security: SAML Token Profile 1.0, December 2004. /
 [WSS: SOAP Message Security V1.0] Oasis Standard, A. Nadalin, C.Kaler, P. Hallem-Baker, R. Monzillo (Editors), Web Services Security: SOAP Message Security 1.0 (WSSecurity 2004), August 2003./
 [WSS: SOAP Message Security] Oasis Standard, A. Nadalin, C.Kaler, R. Monzillo, P. Hallem-Baker,(Editors), Web Services Security: SOAP Message Security 1.1 (WS-Security 2004), December 2005./
 [XML-ns] W3C Recommendation, "Namespaces in XML," 14 January 1999. [XML Signature] W3C Recommendation, "XML Signature Syntax and Processing," 12 February 2002./
 [XML Token] Contribution to the WSS TC, Chris Kaler (Editor),WS-Security Profile for XML-based Tokens, August 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): |  
                                    |  | N/A |  |