<pre>Internet Engineering Task Force (IETF)                   D. Eastlake 3rd
Request for Comments: 6931                                        Huawei
Obsoletes: <a href="./rfc4051">4051</a>                                               April 2013
Category: Standards Track
ISSN: 2070-1721


      <span class="h1">Additional XML Security Uniform Resource Identifiers (URIs)</span>

Abstract

   This document expands, updates, and establishes an IANA registry for
   the list of URIs intended for use with XML digital signatures,
   encryption, canonicalization, and key management.  These URIs
   identify algorithms and types of information.  This document
   obsoletes <a href="./rfc4051">RFC 4051</a>.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc6931">http://www.rfc-editor.org/info/rfc6931</a>.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






<span class="grey">Eastlake                     Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
      <a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-4">4</a>
      <a href="#section-1.2">1.2</a>. Acronyms ...................................................<a href="#page-4">4</a>
   <a href="#section-2">2</a>. Algorithms ......................................................<a href="#page-5">5</a>
      <a href="#section-2.1">2.1</a>. DigestMethod (Hash) Algorithms .............................<a href="#page-5">5</a>
           <a href="#section-2.1.1">2.1.1</a>. MD5 .................................................<a href="#page-5">5</a>
           <a href="#section-2.1.2">2.1.2</a>. SHA-224 .............................................<a href="#page-6">6</a>
           <a href="#section-2.1.3">2.1.3</a>. SHA-384 .............................................<a href="#page-6">6</a>
           <a href="#section-2.1.4">2.1.4</a>. Whirlpool ...........................................<a href="#page-6">6</a>
           <a href="#section-2.1.5">2.1.5</a>. New SHA Functions ...................................<a href="#page-7">7</a>
      <a href="#section-2.2">2.2</a>. SignatureMethod MAC Algorithms .............................<a href="#page-7">7</a>
           <a href="#section-2.2.1">2.2.1</a>. HMAC-MD5 ............................................<a href="#page-7">7</a>
           <a href="#section-2.2.2">2.2.2</a>. HMAC SHA Variations .................................<a href="#page-8">8</a>
           <a href="#section-2.2.3">2.2.3</a>. HMAC-RIPEMD160 ......................................<a href="#page-8">8</a>
      <a href="#section-2.3">2.3</a>. SignatureMethod Public-Key Signature Algorithms ............<a href="#page-9">9</a>
           <a href="#section-2.3.1">2.3.1</a>. RSA-MD5 .............................................<a href="#page-9">9</a>
           <a href="#section-2.3.2">2.3.2</a>. RSA-SHA256 .........................................<a href="#page-10">10</a>
           <a href="#section-2.3.3">2.3.3</a>. RSA-SHA384 .........................................<a href="#page-10">10</a>
           <a href="#section-2.3.4">2.3.4</a>. RSA-SHA512 .........................................<a href="#page-10">10</a>
           <a href="#section-2.3.5">2.3.5</a>. RSA-RIPEMD160 ......................................<a href="#page-11">11</a>
           <a href="#section-2.3.6">2.3.6</a>. ECDSA-SHA*, ECDSA-RIPEMD160, ECDSA-Whirlpool .......<a href="#page-11">11</a>
           <a href="#section-2.3.7">2.3.7</a>. ESIGN-SHA* .........................................<a href="#page-12">12</a>
           <a href="#section-2.3.8">2.3.8</a>. RSA-Whirlpool ......................................<a href="#page-12">12</a>
           <a href="#section-2.3.9">2.3.9</a>. RSASSA-PSS with Parameters .........................<a href="#page-13">13</a>
           <a href="#section-2.3.10">2.3.10</a>. RSASSA-PSS without Parameters .....................<a href="#page-14">14</a>
           <a href="#section-2.3.11">2.3.11</a>. RSA-SHA224 ........................................<a href="#page-15">15</a>
      <a href="#section-2.4">2.4</a>. Minimal Canonicalization ..................................<a href="#page-15">15</a>
      <a href="#section-2.5">2.5</a>. Transform Algorithms ......................................<a href="#page-16">16</a>
           <a href="#section-2.5.1">2.5.1</a>. XPointer ...........................................<a href="#page-16">16</a>
      <a href="#section-2.6">2.6</a>. EncryptionMethod Algorithms ...............................<a href="#page-17">17</a>
           <a href="#section-2.6.1">2.6.1</a>. ARCFOUR Encryption Algorithm .......................<a href="#page-17">17</a>
           <a href="#section-2.6.2">2.6.2</a>. Camellia Block Encryption ..........................<a href="#page-17">17</a>
           <a href="#section-2.6.3">2.6.3</a>. Camellia Key Wrap ..................................<a href="#page-17">17</a>
           <a href="#section-2.6.4">2.6.4</a>. PSEC-KEM ...........................................<a href="#page-18">18</a>
           <a href="#section-2.6.5">2.6.5</a>. SEED Block Encryption ..............................<a href="#page-19">19</a>
           <a href="#section-2.6.6">2.6.6</a>. SEED Key Wrap ......................................<a href="#page-19">19</a>
   <a href="#section-3">3</a>. KeyInfo ........................................................<a href="#page-19">19</a>
      <a href="#section-3.1">3.1</a>. PKCS #7 Bag of Certificates and CRLs ......................<a href="#page-20">20</a>
      <a href="#section-3.2">3.2</a>. Additional RetrievalMethod Type Values ....................<a href="#page-20">20</a>
   <a href="#section-4">4</a>. Indexes ........................................................<a href="#page-20">20</a>
      <a href="#section-4.1">4.1</a>. Fragment Index ............................................<a href="#page-21">21</a>
      <a href="#section-4.2">4.2</a>. URI Index .................................................<a href="#page-24">24</a>
   <a href="#section-5">5</a>. Allocation Considerations ......................................<a href="#page-27">27</a>
      <a href="#section-5.1">5.1</a>. W3C Allocation Considerations .............................<a href="#page-27">27</a>
      <a href="#section-5.2">5.2</a>. IANA Considerations .......................................<a href="#page-28">28</a>
   <a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-28">28</a>



<span class="grey">Eastlake                     Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   <a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-29">29</a>
   <a href="#appendix-A">Appendix A</a>. Changes from <a href="./rfc4051">RFC 4051</a> .................................<a href="#page-30">30</a>
   Normative References ..............................................<a href="#page-31">31</a>
   Informative References ............................................<a href="#page-33">33</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   XML digital signatures, canonicalization, and encryption have been
   standardized by the W3C and by the joint IETF/W3C XMLDSIG working
   group [<a href="#ref-W3C">W3C</a>].  All of these are now W3C Recommendations and some are
   also RFCs.  They are available as follows:

   RFC
   Status            W3C REC      Topic
   -----------       -------      -----

   [<a id="ref-RFC3275">RFC3275</a>]         [<a href="#ref-XMLDSIG10" title="&quot;XML Signature Syntax and Processing (Second Edition)&quot;">XMLDSIG10</a>]  XML Digital Signatures
   Draft Standard

   [<a id="ref-RFC3076">RFC3076</a>]         [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>]    Canonical XML
   Informational

   - - - - - -       [<a href="#ref-XMLENC10" title="&quot;XML Encryption Syntax and Processing&quot;">XMLENC10</a>]   XML Encryption 1.0

   [<a id="ref-RFC3741">RFC3741</a>]         [<a href="#ref-XCANON" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">XCANON</a>]     Exclusive XML Canonicalization 1.0
   Informational

   All of these documents and recommendations use URIs [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>] to
   identify algorithms and keying information types.  The W3C has
   subsequently produced updated XML Signature 1.1 [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>],
   Canonical XML 1.1 [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>], and XML Encryption 1.1 [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   versions, as well as a new XML Signature Properties specification
   [<a href="#ref-XMLDSIG-PROP">XMLDSIG-PROP</a>].

   All camel-case element names herein, such as DigestValue, are from
   these documents.

   This document is an updated convenient reference list of URIs and
   corresponding algorithms in which there is expressed interest.  Since
   the previous list [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>] was issued in 2005, significant new
   cryptographic algorithms of interest to XML security, for some of
   which the URI is only specified in this document, have been added.
   This document obsoletes [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>].  All of the URIs appear in the
   indexes in <a href="#section-4">Section 4</a>.  Only the URIs that were added by [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>] or
   this document have a subsection in <a href="#section-2">Section 2</a> or 3, with the exception
   of Minimal Canonicalization (<a href="#section-2.4">Section 2.4</a>), for example, use of





<span class="grey">Eastlake                     Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   SHA-256 is defined in [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>] and hence there is no subsection on
   that algorithm here, but its URI is included in the indexes in
   <a href="#section-4">Section 4</a>.

   Specification in this document of the URI representing an algorithm
   does not imply endorsement of the algorithm for any particular
   purpose.  A protocol specification, which this is not, generally
   gives algorithm and implementation requirements for the protocol.
   Security considerations for algorithms are constantly evolving, as
   documented elsewhere.  This specification simply provides some URIs
   and relevant formatting for when those URIs are used.

   Note that progressing XML Digital Signature [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>] along the
   Standards Track required removal of any algorithms from the original
   version [<a href="./rfc3075" title="&quot;XML- Signature Syntax and Processing&quot;">RFC3075</a>] for which there was not demonstrated
   interoperability.  This required removal of the Minimal
   Canonicalization algorithm, in which there appears to be continued
   interest.  The URI for Minimal Canonicalization was included in
   [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>] and is included here.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  Terminology</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

   This document is not intended to change the algorithm implementation
   requirements of any IETF or W3C document.  Use of [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>]
   terminology is intended to be only such as is already stated or
   implied by other authoritative documents.

<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>.  Acronyms</span>

   The following acronyms are used in this document:

   HMAC - Keyed-Hashing MAC [<a href="./rfc2104" title="&quot;HMAC: Keyed-Hashing for Message Authentication&quot;">RFC2104</a>]

   IETF - Internet Engineering Task Force &lt;www.ietf.org&gt;

   MAC - Message Authentication Code

   MD - Message Digest

   NIST - United States National Institute of Standards and Technology
          &lt;www.nist.gov&gt;

   RC - Rivest Cipher



<span class="grey">Eastlake                     Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   RSA - Rivest, Shamir, and Adleman

   SHA - Secure Hash Algorithm

   URI - Uniform Resource Identifier [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]

   W3C - World Wide Web Consortium &lt;www.w3.org&gt;

   XML - eXtensible Markup Language

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Algorithms</span>

   The URI [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>] that was dropped from the XML Digital Signature
   standard due to the transition from Proposed Standard to Draft
   Standard [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>] is included in <a href="#section-2.4">Section 2.4</a> below with its original

      <a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>

   prefix so as to avoid changing the XMLDSIG standard's namespace.

   Additional algorithms in [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>] were given URIs that start with

      <a href="http://www.w3.org/2001/04/xmldsig-more#">http://www.w3.org/2001/04/xmldsig-more#</a>

   while further algorithms added in this document are given URIs that
   start with

      <a href="http://www.w3.org/2007/05/xmldsig-more#">http://www.w3.org/2007/05/xmldsig-more#</a>

   In addition, for ease of reference, this document includes in the
   indexes in <a href="#section-4">Section 4</a> many cryptographic algorithm URIs from several
   XML security documents using the namespaces with which they are
   defined in those documents.  For example, 2000/09/xmldsig# for some
   URIs specified in [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>] and 2001/04/xmlenc# for some URIs
   specified in [<a href="#ref-XMLENC10" title="&quot;XML Encryption Syntax and Processing&quot;">XMLENC10</a>].

   See also [<a href="#ref-XMLSECXREF" title="&quot;XML Security Algorithm Cross-Reference&quot;">XMLSECXREF</a>].

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  DigestMethod (Hash) Algorithms</span>

   These algorithms are usable wherever a DigestMethod element occurs.

<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>.  MD5</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#md5">http://www.w3.org/2001/04/xmldsig-more#md5</a>





<span class="grey">Eastlake                     Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   The MD5 algorithm [<a href="./rfc1321" title="&quot;The MD5 Message-Digest Algorithm&quot;">RFC1321</a>] takes no explicit parameters.  An example
   of an MD5 DigestAlgorithm element is:

   &lt;DigestAlgorithm
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#md5"/&gt;

   An MD5 digest is a 128-bit string.  The content of the DigestValue
   element SHALL be the base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of this bit string
   viewed as a 16-octet stream.  See [<a href="./rfc6151" title="&quot;Updated Security Considerations for the MD5 Message-Digest and the HMAC- MD5 Algorithms&quot;">RFC6151</a>] for MD5 security
   considerations.

<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>.  SHA-224</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#sha224">http://www.w3.org/2001/04/xmldsig-more#sha224</a>

   The SHA-224 algorithm [<a href="#ref-FIPS180-4" title="&quot;Secure Hash Standard (SHS)&quot;">FIPS180-4</a>] [<a href="./rfc6234" title="&quot;US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)&quot;">RFC6234</a>] takes no explicit
   parameters.  An example of a SHA-224 DigestAlgorithm element is:

   &lt;DigestAlgorithm
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#sha224" /&gt;

   A SHA-224 digest is a 224-bit string.  The content of the DigestValue
   element SHALL be the base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of this string viewed
   as a 28-octet stream.

<span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a>.  SHA-384</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#sha384">http://www.w3.org/2001/04/xmldsig-more#sha384</a>

   The SHA-384 algorithm [<a href="#ref-FIPS180-4" title="&quot;Secure Hash Standard (SHS)&quot;">FIPS180-4</a>] takes no explicit parameters.  An
   example of a SHA-384 DigestAlgorithm element is:

   &lt;DigestAlgorithm
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#sha384" /&gt;

   A SHA-384 digest is a 384-bit string.  The content of the DigestValue
   element SHALL be the base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of this string viewed
   as a 48-octet stream.

<span class="h4"><a class="selflink" id="section-2.1.4" href="#section-2.1.4">2.1.4</a>.  Whirlpool</span>

   Identifier:
      <a href="http://www.w3.org/2007/05/xmldsig-more#whirlpool">http://www.w3.org/2007/05/xmldsig-more#whirlpool</a>






<span class="grey">Eastlake                     Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   The Whirlpool algorithm [<a href="#ref-10118-3" title="&quot;Information technology -- Security techniques -- Hash-functions -- Part 3: Dedicated hash-functions&quot;">10118-3</a>] takes no explicit parameters.  A
   Whirlpool digest is a 512-bit string.  The content of the DigestValue
   element SHALL be the base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of this string viewed
   as a 64-octet stream.

<span class="h4"><a class="selflink" id="section-2.1.5" href="#section-2.1.5">2.1.5</a>.  New SHA Functions</span>

   Identifiers:
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-224">http://www.w3.org/2007/05/xmldsig-more#sha3-224</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-256">http://www.w3.org/2007/05/xmldsig-more#sha3-256</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-384">http://www.w3.org/2007/05/xmldsig-more#sha3-384</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-512">http://www.w3.org/2007/05/xmldsig-more#sha3-512</a>

   NIST has recently completed a hash function competition for an
   alternative to the SHA family.  The Keccak-f[1600] algorithm was
   selected [<a href="#ref-Keccak" title="&quot;The KECCAK sponge function family&quot;">Keccak</a>] [<a href="#ref-SHA-3" title="&quot;SHA-3 WINNER&quot;">SHA-3</a>].  This hash function is commonly referred
   to as "SHA-3", and this section is a space holder and reservation of
   URIs for future information on Keccak use in XML security.

   A SHA-3 224, 256, 384, and 512 digest is a 224-, 256-, 384-, and
   512-bit string, respectively.  The content of the DigestValue element
   SHALL be the base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of this string viewed as a
   28-, 32-, 48-, and 64-octet stream, respectively.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  SignatureMethod MAC Algorithms</span>

   This section covers SignatureMethod MAC (Message Authentication Code)
   Algorithms.

   Note: Some text in this section is duplicated from [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>] for the
   convenience of the reader.  <a href="./rfc3275">RFC 3275</a> is normative in case of
   conflict.

<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>.  HMAC-MD5</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-md5">http://www.w3.org/2001/04/xmldsig-more#hmac-md5</a>

   The HMAC algorithm [<a href="./rfc2104" title="&quot;HMAC: Keyed-Hashing for Message Authentication&quot;">RFC2104</a>] takes the truncation length in bits as a
   parameter; if the parameter is not specified, then all the bits of
   the hash are output.  An example of an HMAC-MD5 SignatureMethod
   element is as follows:

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#hmac-md5"&gt;
      &lt;HMACOutputLength&gt;112&lt;/HMACOutputLength&gt;
   &lt;/SignatureMethod&gt;




<span class="grey">Eastlake                     Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   The output of the HMAC algorithm is ultimately the output (possibly
   truncated) of the chosen digest algorithm.  This value SHALL be
   base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoded in the same straightforward fashion as the
   output of the digest algorithms.  Example: the SignatureValue element
   for the HMAC-MD5 digest

      9294727A 3638BB1C 13F48EF8 158BFC9D

   from the test vectors in [<a href="./rfc2104" title="&quot;HMAC: Keyed-Hashing for Message Authentication&quot;">RFC2104</a>] would be

      kpRyejY4uxwT9I74FYv8nQ==

   Schema Definition:

      &lt;simpleType name="HMACOutputLength"&gt;
         &lt;restriction base="integer"/&gt;
      &lt;/simpleType&gt;

   DTD:

      &lt;!ELEMENT HMACOutputLength (#PCDATA) &gt;

   The Schema Definition and DTD immediately above are copied from
   [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>].

   See [<a href="./rfc6151" title="&quot;Updated Security Considerations for the MD5 Message-Digest and the HMAC- MD5 Algorithms&quot;">RFC6151</a>] for HMAC-MD5 security considerations.

<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>.  HMAC SHA Variations</span>

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-sha224">http://www.w3.org/2001/04/xmldsig-more#hmac-sha224</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-sha256">http://www.w3.org/2001/04/xmldsig-more#hmac-sha256</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-sha384">http://www.w3.org/2001/04/xmldsig-more#hmac-sha384</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-sha512">http://www.w3.org/2001/04/xmldsig-more#hmac-sha512</a>

   SHA-224, SHA-256, SHA-384, and SHA-512 [<a href="#ref-FIPS180-4" title="&quot;Secure Hash Standard (SHS)&quot;">FIPS180-4</a>] [<a href="./rfc6234" title="&quot;US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)&quot;">RFC6234</a>] can also
   be used in HMAC as described in <a href="#section-2.2.1">Section 2.2.1</a> above for HMAC-MD5.

<span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>.  HMAC-RIPEMD160</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#hmac-ripemd160">http://www.w3.org/2001/04/xmldsig-more#hmac-ripemd160</a>

   RIPEMD-160 [<a href="#ref-10118-3" title="&quot;Information technology -- Security techniques -- Hash-functions -- Part 3: Dedicated hash-functions&quot;">10118-3</a>] can also be used in HMAC as described in <a href="#section-2.2.1">Section</a>
   <a href="#section-2.2.1">2.2.1</a> above for HMAC-MD5.






<span class="grey">Eastlake                     Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>.  SignatureMethod Public-Key Signature Algorithms</span>

   These algorithms are distinguished from those in <a href="#section-2.2">Section 2.2</a> above in
   that they use public-key methods.  That is to say, the verification
   key is different from and not feasibly derivable from the signing
   key.

<span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>.  RSA-MD5</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#rsa-md5">http://www.w3.org/2001/04/xmldsig-more#rsa-md5</a>

   This implies the PKCS#1 v1.5 padding algorithm described in
   [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>].  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-md5" /&gt;

   The SignatureValue content for an RSA-MD5 signature is the base64
   [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>] encoding of the octet string computed as per <a href="./rfc3447#section-8.2.1">[RFC3447],
   Section&nbsp;8.2.1</a>, signature generation for the RSASSA-PKCS1-v1_5
   signature scheme.  As specified in the EMSA-PKCS1-V1_5-ENCODE
   function in <a href="./rfc3447#section-9.2">[RFC3447], Section&nbsp;9.2</a>, the value input to the signature
   function MUST contain a pre-pended algorithm object identifier for
   the hash function, but the availability of an ASN.1 parser and
   recognition of OIDs is not required of a signature verifier.  The
   PKCS#1 v1.5 representation appears as:

      CRYPT (PAD (ASN.1 (OID, DIGEST (data))))

   Note that the padded ASN.1 will be of the following form:

      01 | FF* | 00 | prefix | hash

   Vertical bar ("|") represents concatenation.  "01", "FF", and "00"
   are fixed octets of the corresponding hexadecimal value, and the
   asterisk ("*") after "FF" indicates repetition.  "hash" is the MD5
   digest of the data.  "prefix" is the ASN.1 BER MD5 algorithm
   designator prefix required in PKCS #1 [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>], that is,

      hex 30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 05 05 00 04 10

   This prefix is included to make it easier to use standard
   cryptographic libraries.  The FF octet MUST be repeated enough times
   that the value of the quantity being CRYPTed is exactly one octet
   shorter than the RSA modulus.

   See [<a href="./rfc6151" title="&quot;Updated Security Considerations for the MD5 Message-Digest and the HMAC- MD5 Algorithms&quot;">RFC6151</a>] for MD5 security considerations.



<span class="grey">Eastlake                     Standards Track                    [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>.  RSA-SHA256</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256">http://www.w3.org/2001/04/xmldsig-more#rsa-sha256</a>

   This implies the PKCS#1 v1.5 padding algorithm [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] as described
   in <a href="#section-2.3.1">Section 2.3.1</a>, but with the ASN.1 BER SHA-256 algorithm designator
   prefix.  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.3.3" href="#section-2.3.3">2.3.3</a>.  RSA-SHA384</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#rsa-sha384">http://www.w3.org/2001/04/xmldsig-more#rsa-sha384</a>

   This implies the PKCS#1 v1.5 padding algorithm [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] as described
   in <a href="#section-2.3.1">Section 2.3.1</a>, but with the ASN.1 BER SHA-384 algorithm designator
   prefix.  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha384" /&gt;

   Because it takes about the same effort to calculate a SHA-384 message
   digest as it does a SHA-512 message digest, it is suggested that
   RSA-SHA512 be used in preference to RSA-SHA384 where possible.

<span class="h4"><a class="selflink" id="section-2.3.4" href="#section-2.3.4">2.3.4</a>.  RSA-SHA512</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#rsa-sha512">http://www.w3.org/2001/04/xmldsig-more#rsa-sha512</a>

   This implies the PKCS#1 v1.5 padding algorithm [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] as described
   in <a href="#section-2.3.1">Section 2.3.1</a>, but with the ASN.1 BER SHA-512 algorithm designator
   prefix.  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha512" /&gt;











<span class="grey">Eastlake                     Standards Track                   [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h4"><a class="selflink" id="section-2.3.5" href="#section-2.3.5">2.3.5</a>.  RSA-RIPEMD160</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#rsa-ripemd160">http://www.w3.org/2001/04/xmldsig-more#rsa-ripemd160</a>

   This implies the PKCS#1 v1.5 padding algorithm [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] as described
   in <a href="#section-2.3.1">Section 2.3.1</a>, but with the ASN.1 BER RIPEMD160 algorithm
   designator prefix.  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-ripemd160"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.3.6" href="#section-2.3.6">2.3.6</a>.  ECDSA-SHA*, ECDSA-RIPEMD160, ECDSA-Whirlpool</span>

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha224">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha224</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha384">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha384</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha512">http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha512</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#ecdsa-ripemd160">http://www.w3.org/2007/05/xmldsig-more#ecdsa-ripemd160</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#ecdsa-whirlpool">http://www.w3.org/2007/05/xmldsig-more#ecdsa-whirlpool</a>

   The Elliptic Curve Digital Signature Algorithm (ECDSA) [<a href="#ref-FIPS180-4" title="&quot;Secure Hash Standard (SHS)&quot;">FIPS180-4</a>] is
   the elliptic curve analogue of the Digital Signature Algorithm (DSA)
   signature method, i.e., the Digital Signature Standard (DSS).  It
   takes no explicit parameters.  For detailed specifications of how to
   use it with SHA hash functions and XML Digital Signature, please see
   [<a href="#ref-X9.62" title="&quot;Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature Algorithm (ECDSA)&quot;">X9.62</a>] and [<a href="./rfc4050" title="&quot;Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures&quot;">RFC4050</a>].  The #ecdsa-ripemd160 and #ecdsa-whirlpool
   fragments in the new namespace identifies a signature method
   processed in the same way as specified by the #ecdsa-sha1 fragment of
   this namespace, with the exception that RIPEMD160 or Whirlpool is
   used instead of SHA-1.

   The output of the ECDSA algorithm consists of a pair of integers
   usually referred by the pair (r, s).  The signature value consists of
   the base64 encoding of the concatenation of two octet streams that
   respectively result from the octet-encoding of the values r and s in
   that order.  Conversion from integer to octet stream must be done
   according to the I2OSP operation defined in the [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>]
   specification with the l parameter equal to the size of the base
   point order of the curve in bytes (e.g., 32 for the P-256 curve and
   66 for the P-521 curve [<a href="#ref-FIPS186-3" title="&quot;Digital Signature Standard (DSS)&quot;">FIPS186-3</a>]).

   For an introduction to elliptic curve cryptographic algorithms, see
   [<a href="./rfc6090" title="&quot;Fundamental Elliptic Curve Cryptography Algorithms&quot;">RFC6090</a>] and note the errata (Errata ID 2773-2777).




<span class="grey">Eastlake                     Standards Track                   [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h4"><a class="selflink" id="section-2.3.7" href="#section-2.3.7">2.3.7</a>.  ESIGN-SHA*</span>

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#esign-sha1">http://www.w3.org/2001/04/xmldsig-more#esign-sha1</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#esign-sha224">http://www.w3.org/2001/04/xmldsig-more#esign-sha224</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#esign-sha256">http://www.w3.org/2001/04/xmldsig-more#esign-sha256</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#esign-sha384">http://www.w3.org/2001/04/xmldsig-more#esign-sha384</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#esign-sha512">http://www.w3.org/2001/04/xmldsig-more#esign-sha512</a>

   The ESIGN algorithm specified in [<a href="#ref-IEEEP1363a" title="&quot;Standard Specifications for Public Key Cryptography- Amendment 1: Additional Techniques&quot;">IEEEP1363a</a>] is a signature scheme
   based on the integer factorization problem.  It is much faster than
   previous digital signature schemes, so ESIGN can be implemented on
   smart cards without special co-processors.

   An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#esign-sha1"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.3.8" href="#section-2.3.8">2.3.8</a>.  RSA-Whirlpool</span>

   Identifier:
      <a href="http://www.w3.org/2007/05/xmldsig-more#rsa-whirlpool">http://www.w3.org/2007/05/xmldsig-more#rsa-whirlpool</a>

   As in the definition of the RSA-SHA1 algorithm in [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>], the
   designator "RSA" means the RSASSA-PKCS1-v1_5 algorithm as defined in
   [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>].  When identified through the #rsa-whirlpool fragment
   identifier, Whirlpool is used as the hash algorithm instead.  Use of
   the ASN.1 BER Whirlpool algorithm designator is implied.  That
   designator is
      hex 30 4e 30 0a 06 06 28 cf 06 03 00 37 05 00 04 40
   as an explicit octet sequence.  This corresponds to OID
   1.0.10118.3.0.55 defined in [<a href="#ref-10118-3" title="&quot;Information technology -- Security techniques -- Hash-functions -- Part 3: Dedicated hash-functions&quot;">10118-3</a>].

   An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-whirlpool"
   /&gt;











<span class="grey">Eastlake                     Standards Track                   [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h4"><a class="selflink" id="section-2.3.9" href="#section-2.3.9">2.3.9</a>.  RSASSA-PSS with Parameters</span>

   Identifiers:
      <a href="http://www.w3.org/2007/05/xmldsig-more#rsa-pss">http://www.w3.org/2007/05/xmldsig-more#rsa-pss</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#MGF1">http://www.w3.org/2007/05/xmldsig-more#MGF1</a>

   These identifiers imply the PKCS#1 EMSA-PSS encoding algorithm
   [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>].  The RSASSA-PSS algorithm takes the digest method (hash
   function), a mask generation function, the salt length in bytes
   (SaltLength), and the trailer field as explicit parameters.

   Algorithm identifiers for hash functions specified in XML encryption
   [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>] [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>] and in <a href="#section-2.1">Section 2.1</a> are considered to be valid
   algorithm identifiers for hash functions.  According to [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>],
   the default value for the digest function is SHA-1, but due to the
   discovered weakness of SHA-1 [<a href="./rfc6194" title="&quot;Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms&quot;">RFC6194</a>], it is recommended that
   SHA-256 or a stronger hash function be used.  Notwithstanding
   [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>], SHA-256 is the default to be used with these
   SignatureMethod identifiers if no hash function has been specified.

   The default salt length for these SignatureMethod identifiers if the
   SaltLength is not specified SHALL be the number of octets in the hash
   value of the digest method, as recommended in [<a href="./rfc4055" title="&quot;Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile&quot;">RFC4055</a>].  In a
   parameterized RSASSA-PSS signature the ds:DigestMethod and the
   SaltLength parameters usually appear.  If they do not, the defaults
   make this equivalent to
   <a href="http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1</a> (see <a href="#section-2.3.10">Section</a>
   <a href="#section-2.3.10">2.3.10</a>).  The TrailerField defaults to 1 (0xBC) when omitted.























<span class="grey">Eastlake                     Standards Track                   [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   Schema Definition (target namespace
   <a href="http://www.w3.org/2007/05/xmldsig-more#">http://www.w3.org/2007/05/xmldsig-more#</a>):

   &lt;xs:element name="RSAPSSParams" type="pss:RSAPSSParamsType"&gt;
       &lt;xs:annotation&gt;
           &lt;xs:documentation&gt;
   Top level element that can be used in xs:any namespace="#other"
   wildcard of ds:SignatureMethod content.
           &lt;/xs:documentation&gt;
       &lt;/xs:annotation&gt;
   &lt;/xs:element&gt;
   &lt;xs:complexType name="RSAPSSParamsType"&gt;
       &lt;xs:sequence&gt;
           &lt;xs:element ref="ds:DigestMethod" minOccurs="0"/&gt;
           &lt;xs:element name="MaskGenerationFunction"
              type="pss:MaskGenerationFunctionType" minOccurs="0"/&gt;
           &lt;xs:element name="SaltLength" type="xs:int"
              minOccurs="0"/&gt;
           &lt;xs:element name="TrailerField" type="xs:int"
              minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
   &lt;/xs:complexType&gt;
   &lt;xs:complexType name="MaskGenerationFunctionType"&gt;
       &lt;xs:sequence&gt;
           &lt;xs:element ref="ds:DigestMethod" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
       &lt;xs:attribute name="Algorithm" type="xs:anyURI"
          default="http://www.w3.org/2007/05/xmldsig-more#MGF1"/&gt;
   &lt;/xs:complexType&gt;

<span class="h4"><a class="selflink" id="section-2.3.10" href="#section-2.3.10">2.3.10</a>.  RSASSA-PSS without Parameters</span>

   [<a id="ref-RFC3447">RFC3447</a>] currently specifies only one mask generation function MGF1
   based on a hash function.  Although [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] allows for
   parameterization, the default is to use the same hash function as the
   digest method function.  Only this default approach is supported by
   this section; therefore, the definition of a mask generation function
   type is not needed yet.  The same applies to the trailer field.
   There is only one value (0xBC) specified in [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>].  Hence, this
   default parameter must be used for signature generation.  The default
   salt length is the length of the hash function.

   Identifiers:
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-224-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha3-224-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-256-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha3-256-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-384-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha3-384-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha3-512-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha3-512-rsa-MGF1</a>




<span class="grey">Eastlake                     Standards Track                   [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


      <a href="http://www.w3.org/2007/05/xmldsig-more#md2-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#md2-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#md5-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#md5-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha1-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha1-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha224-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha224-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha384-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha384-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#sha512-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#sha512-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#ripemd128-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#ripemd128-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#ripemd160-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#ripemd160-rsa-MGF1</a>
      <a href="http://www.w3.org/2007/05/xmldsig-more#whirlpool-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#whirlpool-rsa-MGF1</a>

   An example of use is

   &lt;SignatureMethod
     Algorithm=
     "<a href="http://www.w3.org/2007/05/xmldsig-more#SHA3-256-rsa-MGF1">http://www.w3.org/2007/05/xmldsig-more#SHA3-256-rsa-MGF1</a>"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.3.11" href="#section-2.3.11">2.3.11</a>.  RSA-SHA224</span>

   Identifier:
      <a href="http://www.w3.org/2007/05/xmldsig-more#rsa-sha224">http://www.w3.org/2007/05/xmldsig-more#rsa-sha224</a>

   This implies the PKCS#1 v1.5 padding algorithm [<a href="./rfc3447" title="&quot;Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1&quot;">RFC3447</a>] as described
   in <a href="#section-2.3.1">Section 2.3.1</a>, but with the ASN.1 BER SHA-224 algorithm designator
   prefix.  An example of use is

   &lt;SignatureMethod
      Algorithm="http://www.w3.org/2007/05/xmldsig-more#rsa-sha224" /&gt;

   Because it takes about the same effort to calculate a SHA-224 message
   digest as it does a SHA-256 message digest, it is suggested that
   RSA-SHA256 be used in preference to RSA-SHA224 where possible.

<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>.  Minimal Canonicalization</span>

   Thus far, two independent interoperable implementations of Minimal
   Canonicalization have not been announced.  Therefore, when XML
   Digital Signature was advanced along the Standards Track from
   [<a href="./rfc3075" title="&quot;XML- Signature Syntax and Processing&quot;">RFC3075</a>] to [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>], Minimal Canonicalization was dropped.
   However, there is still interest.  For its definition, see <a href="./rfc3075#section-6.5.1">Section</a>
   <a href="./rfc3075#section-6.5.1">6.5.1 of [RFC3075]</a>.

   For reference, its identifier remains:
      <a href="http://www.w3.org/2000/09/xmldsig#minimal">http://www.w3.org/2000/09/xmldsig#minimal</a>






<span class="grey">Eastlake                     Standards Track                   [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>.  Transform Algorithms</span>

   Note that all CanonicalizationMethod algorithms can also be used as
   transform algorithms.

<span class="h4"><a class="selflink" id="section-2.5.1" href="#section-2.5.1">2.5.1</a>.  XPointer</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#xptr">http://www.w3.org/2001/04/xmldsig-more#xptr</a>

   This transform algorithm takes an [<a href="#ref-XPointer" title="&quot;XPointer Framework&quot;">XPointer</a>] as an explicit
   parameter.  An example of use is:

   &lt;Transform
      Algorithm="http://www.w3.org/2001/04/xmldsig-more/xptr"&gt;
      &lt;XPointer
         xmlns="http://www.w3.org/2001/04/xmldsig-more/xptr"&gt;
            xpointer(id("foo")) xmlns(bar=http://foobar.example)
            xpointer(//bar:Zab[@Id="foo"])
      &lt;/XPointer&gt;
   &lt;/Transform&gt;

   Schema Definition:

      &lt;element name="XPointer" type="string"/&gt;

   DTD:

      &lt;!ELEMENT XPointer (#PCDATA) &gt;

   Input to this transform is an octet stream (which is then parsed into
   XML).

   Output from this transform is a node set; the results of the XPointer
   are processed as defined in the XMLDSIG specification [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>] for a
   same-document XPointer.















<span class="grey">Eastlake                     Standards Track                   [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>.  EncryptionMethod Algorithms</span>

   This subsection gives identifiers and information for several
   EncryptionMethod Algorithms.

<span class="h4"><a class="selflink" id="section-2.6.1" href="#section-2.6.1">2.6.1</a>.  ARCFOUR Encryption Algorithm</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#arcfour">http://www.w3.org/2001/04/xmldsig-more#arcfour</a>

   ARCFOUR is a fast, simple stream encryption algorithm that is
   compatible with RSA Security's RC4 algorithm [<a href="#ref-RC4" title="&quot;Applied Cryptography: Protocols, Algorithms, and Source Code in C&quot;">RC4</a>].  An example
   EncryptionMethod element using ARCFOUR is

   &lt;EncryptionMethod
      Algorithm="http://www.w3.org/2001/04/xmldsig-more#arcfour"&gt;
      &lt;KeySize&gt;40&lt;/KeySize&gt;
   &lt;/EncryptionMethod&gt;

   Note that Arcfour makes use of the generic KeySize parameter
   specified and defined in [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>].

<span class="h4"><a class="selflink" id="section-2.6.2" href="#section-2.6.2">2.6.2</a>.  Camellia Block Encryption</span>

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#camellia128-cbc">http://www.w3.org/2001/04/xmldsig-more#camellia128-cbc</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#camellia192-cbc">http://www.w3.org/2001/04/xmldsig-more#camellia192-cbc</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#camellia256-cbc">http://www.w3.org/2001/04/xmldsig-more#camellia256-cbc</a>

   Camellia is a block cipher with the same interface as the AES
   [<a href="#ref-Camellia" title="&quot;Camellia: A 128-bit Block Cipher Suitable for Multiple Platforms - Design and Analysis&quot;">Camellia</a>] [<a href="./rfc3713" title="&quot;A Description of the Camellia Encryption Algorithm&quot;">RFC3713</a>]; it has a 128-bit block size and 128-, 192-, and
   256-bit key sizes.  In XML encryption, Camellia is used in the same
   way as the AES: it is used in the Cipher Block Chaining (CBC) mode
   with a 128-bit initialization vector (IV).  The resulting cipher text
   is prefixed by the IV.  If included in XML output, it is then base64
   encoded.  An example Camellia EncryptionMethod is as follows:

   &lt;EncryptionMethod
      Algorithm=
      "<a href="http://www.w3.org/2001/04/xmldsig-more#camellia128-cbc">http://www.w3.org/2001/04/xmldsig-more#camellia128-cbc</a>"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.6.3" href="#section-2.6.3">2.6.3</a>.  Camellia Key Wrap</span>

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#kw-camellia128">http://www.w3.org/2001/04/xmldsig-more#kw-camellia128</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#kw-camellia192">http://www.w3.org/2001/04/xmldsig-more#kw-camellia192</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#kw-camellia256">http://www.w3.org/2001/04/xmldsig-more#kw-camellia256</a>



<span class="grey">Eastlake                     Standards Track                   [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   Camellia [<a href="#ref-Camellia" title="&quot;Camellia: A 128-bit Block Cipher Suitable for Multiple Platforms - Design and Analysis&quot;">Camellia</a>] [<a href="./rfc3713" title="&quot;A Description of the Camellia Encryption Algorithm&quot;">RFC3713</a>] key wrap is identical to the AES key
   wrap algorithm [<a href="./rfc3394" title="&quot;Advanced Encryption Standard (AES) Key Wrap Algorithm&quot;">RFC3394</a>] specified in the XML Encryption standard
   with "AES" replaced by "Camellia".  As with AES key wrap, the check
   value is 0xA6A6A6A6A6A6A6A6.

   The algorithm is the same whatever the size of the Camellia key used
   in wrapping, called the "key encrypting key" or "KEK".  If Camellia
   is supported, it is particularly suggested that wrapping 128-bit keys
   with a 128-bit KEK and wrapping 256-bit keys with a 256-bit KEK be
   supported.

   An example of use is:

   &lt;EncryptionMethod
      Algorithm=
      "<a href="http://www.w3.org/2001/04/xmldsig-more#kw-camellia128">http://www.w3.org/2001/04/xmldsig-more#kw-camellia128</a>"
   /&gt;

<span class="h4"><a class="selflink" id="section-2.6.4" href="#section-2.6.4">2.6.4</a>.  PSEC-KEM</span>

   Identifier:
      <a href="http://www.w3.org/2001/04/xmldsig-more#psec-kem">http://www.w3.org/2001/04/xmldsig-more#psec-kem</a>

   The PSEC-KEM algorithm, specified in [<a href="#ref-18033-2" title="&quot;Information technology -- Security techniques -- Encryption algorithms -- Part 3: Asymmetric ciphers&quot;">18033-2</a>], is a key
   encapsulation mechanism using elliptic curve encryption.

   An example of use is:

   &lt;EncryptionMethod
      Algorithm="http://www.w3.org/2001/04/xmlenc#psec-kem"&gt;
      &lt;ECParameters&gt;
         &lt;Version&gt;version&lt;/Version&gt;
         &lt;FieldID&gt;id&lt;/FieldID&gt;
         &lt;Curve&gt;curve&lt;/Curve&gt;
         &lt;Base&gt;base&lt;/Base&gt;
         &lt;Order&gt;order&lt;/Order&gt;
         &lt;Cofactor&gt;cofactor&lt;/Cofactor&gt;
      &lt;/ECParameters&gt;
   &lt;/EncryptionMethod&gt;

   See [<a href="#ref-18033-2" title="&quot;Information technology -- Security techniques -- Encryption algorithms -- Part 3: Asymmetric ciphers&quot;">18033-2</a>] for information on the parameters above.










<span class="grey">Eastlake                     Standards Track                   [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h4"><a class="selflink" id="section-2.6.5" href="#section-2.6.5">2.6.5</a>.  SEED Block Encryption</span>

   Identifier:
      <a href="http://www.w3.org/2007/05/xmldsig-more#seed128-cbc">http://www.w3.org/2007/05/xmldsig-more#seed128-cbc</a>

   SEED [<a href="./rfc4269" title="&quot;The SEED Encryption Algorithm&quot;">RFC4269</a>] is a 128-bit block size with 128-bit key sizes.  In
   XML Encryption, SEED can be used in the Cipher Block Chaining (CBC)
   mode with a 128-bit initialization vector (IV).  The resulting cipher
   text is prefixed by the IV.  If included in XML output, it is then
   base64 encoded.

   An example SEED EncryptionMethod is as follows:

   &lt;EncryptionMethod
      Algorithm="http://www.w3.org/2007/05/xmldsig-more#seed128-cbc" /&gt;

<span class="h4"><a class="selflink" id="section-2.6.6" href="#section-2.6.6">2.6.6</a>.  SEED Key Wrap</span>

   Identifier:
      <a href="http://www.w3.org/2007/05/xmldsig-more#kw-seed128">http://www.w3.org/2007/05/xmldsig-more#kw-seed128</a>

   Key wrapping with SEED is identical to <a href="./rfc3394#section-2.2.1">Section&nbsp;2.2.1 of [RFC3394]</a>
   with "AES" replaced by "SEED".  The algorithm is specified in
   [<a href="./rfc4010" title="&quot;Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)&quot;">RFC4010</a>].  The implementation of SEED is optional.  The default
   initial value is 0xA6A6A6A6A6A6A6A6.

   An example of use is:

   &lt;EncryptionMethod
      Algorithm=
      "<a href="http://www.w3.org/2007/05/xmldsig-more#kw-seed128">http://www.w3.org/2007/05/xmldsig-more#kw-seed128</a>"
   /&gt;

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  KeyInfo</span>

   In <a href="#section-3.1">Section 3.1</a> below a new KeyInfo element child is specified, while
   in <a href="#section-3.2">Section 3.2</a> additional KeyInfo Type values for use in
   RetrievalMethod are specified.













<span class="grey">Eastlake                     Standards Track                   [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  PKCS #7 Bag of Certificates and CRLs</span>

   A PKCS #7 [<a href="./rfc2315" title="&quot;PKCS #7: Cryptographic Message Syntax Version 1.5&quot;">RFC2315</a>] "signedData" can also be used as a bag of
   certificates and/or certificate revocation lists (CRLs).  The
   PKCS7signedData element is defined to accommodate such structures
   within KeyInfo.  The binary PKCS #7 structure is base64 [<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]
   encoded.  Any signer information present is ignored.  The following
   is an example [<a href="./rfc3092" title="&quot;Etymology of &quot;">RFC3092</a>], eliding the base64 data:

   &lt;foo:PKCS7signedData
      xmlns:foo="http://www.w3.org/2001/04/xmldsig-more"&gt;
      ...
   &lt;/foo:PKCS7signedData&gt;

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Additional RetrievalMethod Type Values</span>

   The Type attribute of RetrievalMethod is an optional identifier for
   the type of data to be retrieved.  The result of dereferencing a
   RetrievalMethod reference for all KeyInfo types with an XML structure
   is an XML element or document with that element as the root.  The
   various "raw" key information types return a binary value.  Thus,
   they require a Type attribute because they are not unambiguously
   parsable.

   Identifiers:
      <a href="http://www.w3.org/2001/04/xmldsig-more#KeyName">http://www.w3.org/2001/04/xmldsig-more#KeyName</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#KeyValue">http://www.w3.org/2001/04/xmldsig-more#KeyValue</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#PKCS7signedData">http://www.w3.org/2001/04/xmldsig-more#PKCS7signedData</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#rawPGPKeyPacket">http://www.w3.org/2001/04/xmldsig-more#rawPGPKeyPacket</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#rawPKCS7signedData">http://www.w3.org/2001/04/xmldsig-more#rawPKCS7signedData</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#rawSPKISexp">http://www.w3.org/2001/04/xmldsig-more#rawSPKISexp</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#rawX509CRL">http://www.w3.org/2001/04/xmldsig-more#rawX509CRL</a>
      <a href="http://www.w3.org/2001/04/xmldsig-more#RetrievalMethod">http://www.w3.org/2001/04/xmldsig-more#RetrievalMethod</a>

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Indexes</span>

   The following subsections provide an index by URI and by fragment
   identifier (the portion of the URI after "#") of the algorithm and
   KeyInfo URIs defined in this document and in the standards (plus the
   one KeyInfo child element name defined in this document).  The
   "Sec/Doc" column has the section of this document or, if not
   specified in this document, the document where the item is specified.
   See also [<a href="#ref-XMLSECXREF" title="&quot;XML Security Algorithm Cross-Reference&quot;">XMLSECXREF</a>].








<span class="grey">Eastlake                     Standards Track                   [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Fragment Index</span>

   The initial "<a href="http://www.w3.org/">http://www.w3.org/</a>" part of the URI is not included
   below.  The first six entries have a null fragment identifier or no
   fragment identifier.

   Fragment            URI                                   Sec/Doc
   ---------           ----                                 --------

                       2002/06/xmldsig-filter2                [<a href="#ref-XPATH" title="&quot;XML-Signature XPath Filter 2.0&quot;">XPATH</a>]
                       2006/12/xmlc12n11#                   [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>]
                       TR/1999/REC-xslt-19991116               [<a href="#ref-XSLT" title="&quot;XSL Transformations (XSLT) Version 2.0&quot;">XSLT</a>]
                       TR/1999/REC-xpath-19991116             [<a href="#ref-XPATH" title="&quot;XML-Signature XPath Filter 2.0&quot;">XPATH</a>]
                       TR/2001/06/xml-exc-c14n#              [<a href="#ref-XCANON" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">XCANON</a>]
                       TR/2001/REC-xml-c14n-20010315        [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>]
                       TR/2001/REC-xmlschema-1-20010502      [<a href="#ref-Schema" title="&quot;XML Schema Part 1: Structures Second Edition&quot;">Schema</a>]

   aes128-cbc          2001/04/xmlenc#aes128-cbc           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   aes128-gcm          2009/xmlenc11#aes128-gcm            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   aes192-cbc          2001/04/xmlenc#aes192-cbc           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   aes192-gcm          2009/xmlenc11#aes192-gcm            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   aes256-cbc          2001/04/xmlenc#aes256-cbc           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   aes256-gcm          2009/xmlenc11#aes256-gcm            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   arcfour             2001/04/xmldsig-more#arcfour            2.6.1

   base64              2000/09/xmldsig#base64               [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]

   camellia128-cbc     2001/04/xmldsig-more#camellia128-cbc    2.6.2
   camellia192-cbc     2001/04/xmldsig-more#camellia192-cbc    2.6.2
   camellia256-cbc     2001/04/xmldsig-more#camellia256-cbc    2.6.2
   ConcatKDF           2009/xmlenc11#ConcatKDF             [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]

   decrypt#XML         2002/07/decrypt#XML                  [<a href="#ref-DECRYPT" title="&quot;Decryption Transform for XML Signature&quot;">DECRYPT</a>]
   decrypt#Binary      2002/07/decrypt#Binary               [<a href="#ref-DECRYPT" title="&quot;Decryption Transform for XML Signature&quot;">DECRYPT</a>]
   DEREncodedKeyValue  2009/xmldsig11#DEREncodedKeyValue  [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   dh                  2001/04/xmlenc#dh                   [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   dh-es               2009/xmlenc11#dh-es                 [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   dsa-sha1            2000/09/xmldsig#dsa-sha1             [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   dsa-sha256          2009/xmldsig11#dsa-sha256          [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   DSAKeyValue         2000/09/xmldsig#DSAKeyValue        [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]

   ECDH-ES             2009/xmlenc11#ECDH-ES               [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   ecdsa-ripemd160     2007/05/xmldsig-more#ecdsa-ripemd160    2.3.6
   ecdsa-sha1          2001/04/xmldsig-more#ecdsa-sha1         2.3.6
   ecdsa-sha224        2001/04/xmldsig-more#ecdsa-sha224       2.3.6
   ecdsa-sha256        2001/04/xmldsig-more#ecdsa-sha256       2.3.6
   ecdsa-sha384        2001/04/xmldsig-more#ecdsa-sha384       2.3.6
   ecdsa-sha512        2001/04/xmldsig-more#ecdsa-sha512       2.3.6



<span class="grey">Eastlake                     Standards Track                   [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   ecdsa-whirlpool     2007/05/xmldsig-more#ecdsa-whirlpool    2.3.5
   ecies-kem           2010/xmlsec-ghc#ecies-kem            [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]
   ECKeyValue          2009/xmldsig11#ECKeyValue          [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   enveloped-signature 2000/09/xmldsig#enveloped-signature  [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   esign-sha1          2001/04/xmldsig-more#esign-sha1         2.3.7
   esign-sha224        2001/04/xmldsig-more#esign-sha224       2.3.7
   esign-sha256        2001/04/xmldsig-more#esign-sha256       2.3.7
   esign-sha384        2001/04/xmldsig-more#esign-sha384       2.3.7
   esign-sha512        2001/04/xmldsig-more#esign-sha512       2.3.7

   generic-hybrid      2010/xmlsec-ghc#generic-hybrid       [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]

   hmac-md5            2001/04/xmldsig-more#hmac-md5           2.2.1
   hmac-ripemd160      2001/04/xmldsig-more#hmac-ripemd160     2.2.3
   hmac-sha1           2000/09/xmldsig#hmac-sha1            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   hmac-sha224         2001/04/xmldsig-more#hmac-sha224        2.2.2
   hmac-sha256         2001/04/xmldsig-more#hmac-sha256        2.2.2
   hmac-sha384         2001/04/xmldsig-more#hmac-sha384        2.2.2
   hmac-sha512         2001/04/xmldsig-more#hmac-sha512        2.2.2

   KeyName             2001/04/xmldsig-more#KeyName            3.2
   KeyValue            2001/04/xmldsig-more#KeyValue           3.2
   kw-aes128           2001/04/xmlenc#kw-aes128            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-aes128-pad       2009/xmlenc11#kw-aes-128-pad        [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-aes192           2001/04/xmlenc#kw-aes192            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-aes192-pad       2009/xmlenc11#kw-aes-192-pad        [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-aes256           2001/04/xmlenc#kw-aes256            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-aes256-pad       2009/xmlenc11#kw-aes-256-pad        [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   kw-camellia128      2001/04/xmldsig-more#kw-camellia128     2.6.3
   kw-camellia192      2001/04/xmldsig-more#kw-camellia192     2.6.3
   kw-camellia256      2001/04/xmldsig-more#kw-camellia256     2.6.3
   kw-seed128          2007/05/xmldsig-more#kw-seed128         2.6.6

   md2-rsa-MGF1        2007/05/xmldsig-more#md2-rsa-MGF1       2.3.10
   md5                 2001/04/xmldsig-more#md5                2.1.1
   md5-rsa-MGF1        2007/05/xmldsig-more#md5-rsa-MGF1       2.3.10
   MGF1                2007/05/xmldsig-more#MGF1               2.3.9
   mgf1sha1            2009/xmlenc11#mgf1sha1              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   mgf1sha224          2009/xmlenc11#mgf1sha224            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   mgf1sha256          2009/xmlenc11#mgf1sha256            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   mgf1sha384          2009/xmlenc11#mgf1sha384            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   mgf1sha512          2009/xmlenc11#mgf1sha512            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   MgmtData            2000/09/xmldsig#MgmtData           [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   minimal             2000/09/xmldsig#minimal                 2.4

   pbkdf2              2009/xmlenc11#pbkdf2                [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   PGPData             2000/09/xmldsig#PGPData            [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   PKCS7signedData     2001/04/xmldsig-more#PKCS7signedData    3.1



<span class="grey">Eastlake                     Standards Track                   [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   PKCS7signedData     2001/04/xmldsig-more#PKCS7signedData    3.2
   psec-kem            2001/04/xmldsig-more#psec-kem           2.6.4

   rawPGPKeyPacket     2001/04/xmldsig-more#rawPGPKeyPacket    3.2
   rawPKCS7signedData  2001/04/xmldsig-more#rawPKCS7signedData 3.2
   rawSPKISexp         2001/04/xmldsig-more#rawSPKISexp        3.2
   rawX509Certificate  2000/09/xmldsig#rawX509Certificate   [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   rawX509CRL          2001/04/xmldsig-more#rawX509CRL         3.2
   RetrievalMethod     2001/04/xmldsig-more#RetrievalMethod    3.2
   ripemd128-rsa-MGF1  2007/05/xmldsig-more#ripemd128-rsa-MGF1 2.3.10
   ripemd160           2001/04/xmlenc#ripemd160            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   ripemd160-rsa-MGF1  2007/05/xmldsig-more#ripemd160-rsa-MGF1 2.3.10
   rsa-1_5             2001/04/xmlenc#rsa-1_5              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   rsa-md5             2001/04/xmldsig-more#rsa-md5            2.3.1
   rsa-oaep            2009/xmlenc11#rsa-oaep              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   rsa-oaep-mgf1p      2001/04/xmlenc#rsa-oaep-mgf1p       [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   rsa-pss             2007/05/xmldsig-more#rsa-pss            2.3.9
   rsa-ripemd160       2001/04/xmldsig-more#rsa-ripemd160      2.3.5
   rsa-sha1            2000/09/xmldsig#rsa-sha1             [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   rsa-sha224          2007/05/xmldsig-more#rsa-sha224         2.3.11
   rsa-sha256          2001/04/xmldsig-more#rsa-sha256         2.3.2
   rsa-sha384          2001/04/xmldsig-more#rsa-sha384         2.3.3
   rsa-sha512          2001/04/xmldsig-more#rsa-sha512         2.3.4
   rsa-whirlpool       2007/05/xmldsig-more#rsa-whirlpool      2.3.5
   rsaes-kem           2010/xmlsec-ghc#rsaes-kem            [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]
   RSAKeyValue         2000/09/xmldsig#RSAKeyValue        [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]

   seed128-cbc         2007/05/xmldsig-more#seed128-cbc        2.6.5
   sha1                2000/09/xmldsig#sha1                 [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]
   sha1-rsa-MGF1       2007/05/xmldsig-more#sha1-rsa-MGF1      2.3.10
   sha224              2001/04/xmldsig-more#sha224             2.1.2
   sha224-rsa-MGF1     2007/05/xmldsig-more#sha224-rsa-MGF1    2.3.10
   sha256              2001/04/xmlenc#sha256               [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   sha256-rsa-MGF1     2007/05/xmldsig-more#sha256-rsa-MGF1    2.3.10
   sha3-224            2007/05/xmldsig-more#sha3-224           2.1.5
   sha3-224-rsa-MGF1   2007/05/xmldsig-more#sha3-224-rsa-MGF1  2.3.10
   sha3-256            2007/05/xmldsig-more#sha3-256           2.1.5
   sha3-256-rsa-MGF1   2007/05/xmldsig-more#sha3-256-rsa-MGF1  2.3.10
   sha3-384            2007/05/xmldsig-more#sha3-384           2.1.5
   sha3-384-rsa-MGF1   2007/05/xmldsig-more#sha3-384-rsa-MGF1  2.3.10
   sha3-512            2007/05/xmldsig-more#sha3-512           2.1.5
   sha3-512-rsa-MGF1   2007/05/xmldsig-more#sha3-512-rsa-MGF1  2.3.10
   sha384              2001/04/xmldsig-more#sha384             2.1.3
   sha384-rsa-MGF1     2007/05/xmldsig-more#sha384-rsa-MGF1    2.3.10
   sha512              2001/04/xmlenc#sha512               [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]
   sha512-rsa-MGF1     2007/05/xmldsig-more#sha512-rsa-MGF1    2.3.10
   SPKIData            2000/09/xmldsig#SPKIData           [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]




<span class="grey">Eastlake                     Standards Track                   [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   tripledes-cbc       2001/04/xmlenc#tripledes-cbc        [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]

   whirlpool           2007/05/xmldsig-more#whirlpool          2.1.4
   whirlpool-rsa-MGF1  2007/05/xmldsig-more#whirlpool-rsa-MGF1 2.3.10
   WithComments        2006/12/xmlc14n11#WithComments       [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>]
   WithComments        TR/2001/06/xml-exc-c14n#WithComments  [<a href="#ref-XCANON" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">XCANON</a>]
   WithComments        TR/2001/REC-xml-c14n-20010315#WithComments
                                                            [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>]

   X509Data            2000/09/xmldsig#X509Data           [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]
   xptr                2001/04/xmldsig-more#xptr               2.5.1

   The initial "<a href="http://www.w3.org/">http://www.w3.org/</a>" part of the URI is not included
   above.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  URI Index</span>

   The initial "<a href="http://www.w3.org/">http://www.w3.org/</a>" part of the URI is not included
   below.

   URI                                 Sec/Doc   Type
   ----                                --------  -----

   2000/09/xmldsig#base64              [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Transform
   2000/09/xmldsig#DSAKeyValue         [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#dsa-sha1            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  SignatureMethod
   2000/09/xmldsig#enveloped-signature [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Transform
   2000/09/xmldsig#hmac-sha1           [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  SignatureMethod
   2000/09/xmldsig#MgmtData            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#minimal                2.4     Canonicalization
   2000/09/xmldsig#PGPData             [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#rawX509Certificate  [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#rsa-sha1            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  SignatureMethod
   2000/09/xmldsig#RSAKeyValue         [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#sha1                [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  DigestAlgorithm
   2000/09/xmldsig#SPKIData            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type
   2000/09/xmldsig#X509Data            [<a href="./rfc3275" title="&quot;(Extensible Markup Language) XML-Signature Syntax and Processing&quot;">RFC3275</a>]  Retrieval type

   2001/04/xmldsig-more#arcfour           2.6.1   EncryptionMethod
   2001/04/xmldsig-more#camellia128-cbc   2.6.2   EncryptionMethod
   2001/04/xmldsig-more#camellia192-cbc   2.6.2   EncryptionMethod
   2001/04/xmldsig-more#camellia256-cbc   2.6.2   EncryptionMethod
   2001/04/xmldsig-more#ecdsa-sha1        2.3.6   SignatureMethod
   2001/04/xmldsig-more#ecdsa-sha224      2.3.6   SignatureMethod
   2001/04/xmldsig-more#ecdsa-sha256      2.3.6   SignatureMethod
   2001/04/xmldsig-more#ecdsa-sha384      2.3.6   SignatureMethod
   2001/04/xmldsig-more#ecdsa-sha512      2.3.6   SignatureMethod
   2001/04/xmldsig-more#esign-sha1        2.3.7   SignatureMethod



<span class="grey">Eastlake                     Standards Track                   [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   2001/04/xmldsig-more#esign-sha224      2.3.7   SignatureMethod
   2001/04/xmldsig-more#esign-sha256      2.3.7   SignatureMethod
   2001/04/xmldsig-more#esign-sha384      2.3.7   SignatureMethod
   2001/04/xmldsig-more#esign-sha512      2.3.7   SignatureMethod
   2001/04/xmldsig-more#hmac-md5          2.2.1   SignatureMethod
   2001/04/xmldsig-more#hmac-ripemd160    2.2.3   SignatureMethod
   2001/04/xmldsig-more#hmac-sha224       2.2.2   SignatureMethod
   2001/04/xmldsig-more#hmac-sha256       2.2.2   SignatureMethod
   2001/04/xmldsig-more#hmac-sha384       2.2.2   SignatureMethod
   2001/04/xmldsig-more#hmac-sha512       2.2.2   SignatureMethod
   2001/04/xmldsig-more#KeyName           3.2     Retrieval type
   2001/04/xmldsig-more#KeyValue          3.2     Retrieval type
   2001/04/xmldsig-more#kw-camellia128    2.6.3   EncryptionMethod
   2001/04/xmldsig-more#kw-camellia192    2.6.3   EncryptionMethod
   2001/04/xmldsig-more#kw-camellia256    2.6.3   EncryptionMethod
   2001/04/xmldsig-more#md5               2.1.1   DigestAlgorithm
   2001/04/xmldsig-more#PKCS7signedData   3.2     Retrieval type
   2001/04/xmldsig-more#psec-kem          2.6.4   EncryptionMethod
   2001/04/xmldsig-more#rawPGPKeyPacket   3.2     Retrieval type
   2001/04/xmldsig-more#rawPKCS7signedData 3.2    Retrieval type
   2001/04/xmldsig-more#rawSPKISexp       3.2     Retrieval type
   2001/04/xmldsig-more#rawX509CRL        3.2     Retrieval type
   2001/04/xmldsig-more#RetrievalMethod   3.2     Retrieval type
   2001/04/xmldsig-more#rsa-md5           2.3.1   SignatureMethod
   2001/04/xmldsig-more#rsa-sha256        2.3.2   SignatureMethod
   2001/04/xmldsig-more#rsa-sha384        2.3.3   SignatureMethod
   2001/04/xmldsig-more#rsa-sha512        2.3.4   SignatureMethod
   2001/04/xmldsig-more#rsa-ripemd160     2.3.5   SignatureMethod
   2001/04/xmldsig-more#sha224            2.1.2   DigestAlgorithm
   2001/04/xmldsig-more#sha384            2.1.3   DigestAlgorithm
   2001/04/xmldsig-more#xptr              2.5.1   Transform
   2001/04/xmldsig-more#PKCS7signedData   3.1     KeyInfo child

   2001/04/xmlenc#aes128-cbc          [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#aes192-cbc          [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#aes256-cbc          [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#dh                  [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  AgreementMethod
   2001/04/xmlenc#kw-aes128           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#kw-aes192           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#kw-aes256           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#ripemd160           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  DigestAlgorithm
   2001/04/xmlenc#rsa-1_5             [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#rsa-oaep-mgf1p      [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2001/04/xmlenc#sha256              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  DigestAlgorithm
   2001/04/xmlenc#sha512              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  DigestAlgorithm
   2001/04/xmlenc#tripledes-cbc       [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod

   2002/06/xmldsig-filter2               [<a href="#ref-XPATH" title="&quot;XML-Signature XPath Filter 2.0&quot;">XPATH</a>]  Transform



<span class="grey">Eastlake                     Standards Track                   [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   2002/07/decrypt#XML                 [<a href="#ref-DECRYPT" title="&quot;Decryption Transform for XML Signature&quot;">DECRYPT</a>]  Transform
   2002/07/decrypt#Binary              [<a href="#ref-DECRYPT" title="&quot;Decryption Transform for XML Signature&quot;">DECRYPT</a>]  Transform

   2006/12/xmlc12n11#                  [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>]  Canonicalization
   2006/12/xmlc14n11#WithComments      [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>]  Canonicalization

   2007/05/xmldsig-more#ecdsa-ripemd160   2.3.6   SignatureMethod
   2007/05/xmldsig-more#ecdsa-whirlpool   2.3.5   SignatureMethod
   2007/05/xmldsig-more#kw-seed128        2.6.6   EncryptionMethod
   2007/05/xmldsig-more#md2-rsa-MGF1      2.3.10  SignatureMethod
   2007/05/xmldsig-more#md5-rsa-MGF1      2.3.10  SignatureMethod
   2007/05/xmldsig-more#MGF1              2.3.9   SignatureMethod
   2007/05/xmldsig-more#ripemd128-rsa-MGF1 2.3.10 SignatureMethod
   2007/05/xmldsig-more#ripemd160-rsa-MGF1 2.3.10 SignatureMethod
   2007/05/xmldsig-more#rsa-pss           2.3.9   SignatureMethod
   2007/05/xmldsig-more#rsa-sha224        2.3.11  SignatureMethod
   2007/05/xmldsig-more#rsa-whirlpool     2.3.5   SignatureMethod
   2007/05/xmldsig-more#seed128-cbc       2.6.5   EncryptionMethod
   2007/05/xmldsig-more#sha1-rsa-MGF1     2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha224-rsa-MGF1   2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha256-rsa-MGF1   2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha3-224          2.1.5   DigestAlgorithm
   2007/05/xmldsig-more#sha3-224-rsa-MGF1 2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha3-256          2.1.5   DigestAlgorithm
   2007/05/xmldsig-more#sha3-256-rsa-MGF1 2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha3-384          2.1.5   DigestAlgorithm
   2007/05/xmldsig-more#sha3-384-rsa-MGF1 2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha3-512          2.1.5   DigestAlgorithm
   2007/05/xmldsig-more#sha3-512-rsa-MGF1 2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha384-rsa-MGF1   2.3.10  SignatureMethod
   2007/05/xmldsig-more#sha512-rsa-MGF1   2.3.10  SignatureMethod
   2007/05/xmldsig-more#whirlpool         2.1.4   DigestAlgorithm
   2007/05/xmldsig-more#whirlpool-rsa-MGF1 2.3.10 SignatureMethod
   2009/xmlenc11#kw-aes-128-pad       [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#kw-aes-192-pad       [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#kw-aes-256-pad       [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod

   2009/xmldsig11#dsa-sha256         [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]  SignatureMethod
   2009/xmldsig11#ECKeyValue         [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]  Retrieval type
   2009/xmldsig11#DEREncodedKeyValue [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>]  Retrieval type

   2009/xmlenc11#aes128-gcm           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#aes192-gcm           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#aes256-gcm           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#ConcatKDF            [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#mgf1sha1             [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  SignatureMethod
   2009/xmlenc11#mgf1sha224           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  SignatureMethod
   2009/xmlenc11#mgf1sha256           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  SignatureMethod



<span class="grey">Eastlake                     Standards Track                   [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   2009/xmlenc11#mgf1sha384           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  SignatureMethod
   2009/xmlenc11#mgf1sha512           [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  SignatureMethod
   2009/xmlenc11#pbkdf2               [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#rsa-oaep             [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#ECDH-ES              [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod
   2009/xmlenc11#dh-es                [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>]  EncryptionMethod

   2010/xmlsec-ghc#generic-hybrid      [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]  Generic Hybrid
   2010/xmlsec-ghc#rsaes-kem           [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]  Generic Hybrid
   2010/xmlsec-ghc#ecies-kem           [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>]  Generic Hybrid

   TR/1999/REC-xpath-19991116            [<a href="#ref-XPATH" title="&quot;XML-Signature XPath Filter 2.0&quot;">XPATH</a>]  Transform
   TR/1999/REC-xslt-19991116              [<a href="#ref-XSLT" title="&quot;XSL Transformations (XSLT) Version 2.0&quot;">XSLT</a>]  Transform
   TR/2001/06/xml-exc-c14n#             [<a href="#ref-XCANON" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">XCANON</a>]  Canonicalization
   TR/2001/06/xml-exc-c14n#WithComments [<a href="#ref-XCANON" title="&quot;Exclusive XML Canonicalization Version 1.0&quot;">XCANON</a>]  Canonicalization
   TR/2001/REC-xml-c14n-20010315       [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>]  Canonicalization
   TR/2001/REC-xml-c14n-20010315#WithComments
                                       [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>]  Canonicalization
   TR/2001/REC-xmlschema-1-20010502     [<a href="#ref-Schema" title="&quot;XML Schema Part 1: Structures Second Edition&quot;">Schema</a>]  Transform

   The initial "<a href="http://www.w3.org/">http://www.w3.org/</a>" part of the URI is not included
   above.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Allocation Considerations</span>

   W3C and IANA allocation considerations are given below.

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  W3C Allocation Considerations</span>

   As it is easy for people to construct their own unique URIs [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]
   and, if appropriate, to obtain a URI from the W3C, it is not intended
   that any additional "<a href="http://www.w3.org/2007/05/xmldsig-more#">http://www.w3.org/2007/05/xmldsig-more#</a>" URIs be
   created beyond those enumerated in this RFC.  (W3C Namespace
   stability rules prohibit the creation of new URIs under
   "<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>" and URIs under
   "<a href="http://www.w3.org/2001/04/xmldsig-more#">http://www.w3.org/2001/04/xmldsig-more#</a>" were frozen with the
   publication of [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>].)

   An "xmldsig-more" URI does not imply any official W3C or IETF status
   for these algorithms or identifiers nor does it imply that they are
   only useful in digital signatures.  Currently, dereferencing such
   URIs may or may not produce a temporary placeholder document.
   Permission to use these URI prefixes has been given by the W3C.








<span class="grey">Eastlake                     Standards Track                   [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  IANA Considerations</span>

   IANA has established a registry entitled "XML Security URIs".  The
   initial contents correspond to <a href="#section-4.2">Section 4.2</a> of this document with each
   section number in the "Sec/Doc" column augmented with a reference to
   this RFC (for example, "2.6.4" means "<a href="./rfc6931#section-2.6.4">[RFC6931], Section&nbsp;2.6.4</a>").

   New entries, including new Types, will be added based on Expert
   Review [<a href="./rfc5226" title="">RFC5226</a>].  Criterion for inclusion are (1) documentation
   sufficient for interoperability of the algorithm or data type and the
   XML syntax for its representation and use and (2) sufficient
   importance as normally indicated by inclusion in (2a) an approved W3C
   Note, Proposed Recommendation, or Recommendation or (2b) an approved
   IETF Standards Track document.  Typically, the registry will
   reference a W3C or IETF document specifying such XML syntax; that
   document will either contain a more abstract description of the
   algorithm or data type or reference another document with a more
   abstract description.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

   This RFC is concerned with documenting the URIs that designate
   algorithms and some data types used in connection with XML security.
   The security considerations vary widely with the particular
   algorithms, and the general security considerations for XML security
   are outside of the scope of this document but appear in [<a href="#ref-XMLDSIG11" title="&quot;XML Signature Syntax and Processing Version 1.1&quot;">XMLDSIG11</a>],
   [<a href="#ref-XMLENC11" title="&quot;XML Encryption Syntax and Processing Version 1.1&quot;">XMLENC11</a>], [<a href="#ref-CANON10" title="&quot;Canonical XML Version 1.0&quot;">CANON10</a>], [<a href="#ref-CANON11" title="&quot;Canonical XML Version 1.1&quot;">CANON11</a>], and [<a href="#ref-GENERIC" title="&quot;XML Security Generic Hybrid Ciphers&quot;">GENERIC</a>].

   [<a id="ref-RFC6151">RFC6151</a>] should be consulted before considering the use of MD5 as a
   DigestMethod or RSA-MD5 as a SignatureMethod.

   See [<a href="./rfc6194" title="&quot;Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms&quot;">RFC6194</a>] for SHA-1 security considerations and [<a href="./rfc6151" title="&quot;Updated Security Considerations for the MD5 Message-Digest and the HMAC- MD5 Algorithms&quot;">RFC6151</a>] for MD5
   security considerations.

   Additional security considerations are given in connection with the
   description of some algorithms in the body of this document.

   Implementers should be aware that cryptographic algorithms become
   weaker with time.  As new cryptoanalysis techniques are developed and
   computing performance improves, the work factor to break a particular
   cryptographic algorithm will reduce.  Therefore, cryptographic
   implementations should be modular, allowing new algorithms to be
   readily inserted.  That is, implementers should be prepared for the
   set of mandatory-to-implement algorithms to change over time.







<span class="grey">Eastlake                     Standards Track                   [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgements</span>

   The contributions to this document by the following people, listed in
   alphabetic order, are gratefully acknowledged: Benoit Claise, Adrian
   Farrel, Stephen Farrell, Ernst Giessmann, Frederick Hirsch, Bjoern
   Hoehrmann, Russ Housley, Satoru Kanno, Charlie Kaufman, Konrad Lanz,
   HwanJin Lee, Barry Leiba, Peter Lipp, Subramanian Moonesamy, Thomas
   Roessler, Hanseong Ryu, Peter Saint-Andre, and Sean Turner.

   The following contributors to [<a href="./rfc4051" title="&quot;Additional XML Security Uniform Resource Identifiers (URIs)&quot;">RFC4051</a>], on which this document is
   based, are gratefully acknowledged: Glenn Adams, Merlin Hughs, Gregor
   Karlinger, Brian LaMachia, Shiho Moriai, Joseph Reagle, Russ Housley,
   and Joel Halpern.






































<span class="grey">Eastlake                     Standards Track                   [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Changes from <a href="./rfc4051">RFC 4051</a></span>

   The following changes have been made in <a href="./rfc4051">RFC 4051</a> to produce this
   document.

   1.  Updated and added numerous RFC, W3C, and Internet-Draft
       references.

   2.  Added #ecdsa-ripemd160, #whirlpool, #ecdsa-whirlpool,
       #rsa-whirlpool, #seed128-cbc, and #kw-seed128.

   3.  Incorporated <a href="./rfc4051">RFC 4051</a> errata [<a href="#ref-Errata191" title="RFC 4051">Errata191</a>].

   4.  Added URI and fragment index sections.

   5.  For MD5 and SHA-1, added references to [<a href="./rfc6151" title="&quot;Updated Security Considerations for the MD5 Message-Digest and the HMAC- MD5 Algorithms&quot;">RFC6151</a>] and [<a href="./rfc6194" title="&quot;Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms&quot;">RFC6194</a>].

   5.  Added SHA-3 / Keccak placeholder section including #sha3-224,
       #sha3-256, #sha3-384, and #sha3-512.

   6.  Added RSASSA-PSS sections including #sha3-224-MGF1,
       #sha3-256-MGF1, #sha3-384-MGF1, #sha3-512-MGF1, #md2-rsa-MGF1,
       #md5-rsa-MGF1, #sha1-rsa-MGF1, #sha224-rsa-MGF1,
       #sha256-rsa-MGF1, #sha384-rsa-MGF1, #sha512-rsa-MGF1,
       #ripemd128-rsa-MGF1, #ripemd160-rsa-MGF1, and
       #whirlpool-rsa-MGF1.

   7.  Added new URIs from Canonical XML 1.1 and XML Encryption 1.1
       including: #aes128-gcm, #aes192-gcm, #aes256-gc, #ConcatKDF,
       #pbkdf, #rsa-oaep, #ECDH-ES, and #dh-es.

   8.  Added acronym subsection.

   9.  Added numerous URIs that are specified in W3C XML Security
       documents to the Indexes.  These do not have sections in the body
       of this document -- for example, those for dsa-sha256, mgf1sha*,
       decrypt#XML, and xmldsig-filter2.

   10. Requested establishment of an IANA registry.

   11. Made various editorial changes.










<span class="grey">Eastlake                     Standards Track                   [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


Normative References

   [<a id="ref-10118-3">10118-3</a>]     ISO, "Information technology -- Security techniques --
                 Hash-functions -- Part 3: Dedicated hash-functions",
                 ISO/IEC 10118-3:2004, 2004.

   [<a id="ref-18033-2">18033-2</a>]     ISO, "Information technology -- Security techniques --
                 Encryption algorithms -- Part 3: Asymmetric ciphers",
                 ISO/IEC 18033-2:2010, 2010.

   [<a id="ref-Camellia">Camellia</a>]    Aoki, K., Ichikawa, T., Matsui, M., Moriai, S.,
                 Nakajima, J., and T. Tokita, "Camellia: A 128-bit Block
                 Cipher Suitable for Multiple Platforms - Design and
                 Analysis", in Selected Areas in Cryptography, 7th
                 Annual International Workshop, SAC 2000, August 2000,
                 Proceedings, Lecture Notes in Computer Science 2012,
                 pp. 39-56, Springer-Verlag, 2001.

   [<a id="ref-FIPS180-4">FIPS180-4</a>]   US National Institute of Science and Technology,
                 "Secure Hash Standard (SHS)", FIPS 180-4, March 2012,
                 &lt;<a href="http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf">http://csrc.nist.gov/publications/fips/fips180-4/</a>
                 <a href="http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf">fips-180-4.pdf</a>&gt;.

   [<a id="ref-FIPS186-3">FIPS186-3</a>]   US National Institute of Science and Technology,
                 "Digital Signature Standard (DSS)", FIPS 186-3, June
                 2009, &lt;<a href="http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf">http://csrc.nist.gov/publications/fips/</a>
                 <a href="http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf">fips186-3/fips_186-3.pdf</a>&gt;.

   [<a id="ref-IEEEP1363a">IEEEP1363a</a>]  IEEE, "Standard Specifications for Public Key
                 Cryptography- Amendment 1: Additional Techniques", IEEE
                 1363a-2004, 2004.

   [<a id="ref-RC4">RC4</a>]         Schneier, B., "Applied Cryptography: Protocols,
                 Algorithms, and Source Code in C", Second Edition, John
                 Wiley and Sons, New York, NY, 1996.

   [<a id="ref-RFC1321">RFC1321</a>]     Rivest, R., "The MD5 Message-Digest Algorithm", <a href="./rfc1321">RFC</a>
                 <a href="./rfc1321">1321</a>, April 1992.

   [<a id="ref-RFC2045">RFC2045</a>]     Freed, N. and N. Borenstein, "Multipurpose Internet
                 Mail Extensions (MIME) Part One: Format of Internet
                 Message Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.

   [<a id="ref-RFC2104">RFC2104</a>]     Krawczyk, H., Bellare, M., and R. Canetti, "HMAC:
                 Keyed-Hashing for Message Authentication", <a href="./rfc2104">RFC 2104</a>,
                 February 1997.





<span class="grey">Eastlake                     Standards Track                   [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   [<a id="ref-RFC2119">RFC2119</a>]     Bradner, S., "Key words for use in RFCs to Indicate
                 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC2315">RFC2315</a>]     Kaliski, B., "PKCS #7: Cryptographic Message Syntax
                 Version 1.5", <a href="./rfc2315">RFC 2315</a>, March 1998.

   [<a id="ref-RFC3275">RFC3275</a>]     Eastlake 3rd, D., Reagle, J., and D. Solo, "(Extensible
                 Markup Language) XML-Signature Syntax and Processing",
                 <a href="./rfc3275">RFC 3275</a>, March 2002.

   [<a id="ref-RFC3394">RFC3394</a>]     Schaad, J. and R. Housley, "Advanced Encryption
                 Standard (AES) Key Wrap Algorithm", <a href="./rfc3394">RFC 3394</a>, September
                 2002.

   [<a id="ref-RFC3447">RFC3447</a>]     Jonsson, J. and B. Kaliski, "Public-Key Cryptography
                 Standards (PKCS) #1: RSA Cryptography Specifications
                 Version 2.1", <a href="./rfc3447">RFC 3447</a>, February 2003.

   [<a id="ref-RFC3713">RFC3713</a>]     Matsui, M., Nakajima, J., and S. Moriai, "A Description
                 of the Camellia Encryption Algorithm", <a href="./rfc3713">RFC 3713</a>, April
                 2004.

   [<a id="ref-RFC3986">RFC3986</a>]     Berners-Lee, T., Fielding, R., and L. Masinter,
                 "Uniform Resource Identifier (URI): Generic Syntax",
                 STD 66, <a href="./rfc3986">RFC 3986</a>, January 2005.

   [<a id="ref-RFC4050">RFC4050</a>]     Blake-Wilson, S., Karlinger, G., Kobayashi, T., and Y.
                 Wang, "Using the Elliptic Curve Signature Algorithm
                 (ECDSA) for XML Digital Signatures", <a href="./rfc4050">RFC 4050</a>, April
                 2005.

   [<a id="ref-RFC4055">RFC4055</a>]     Schaad, J., Kaliski, B., and R. Housley, "Additional
                 Algorithms and Identifiers for RSA Cryptography for use
                 in the Internet X.509 Public Key Infrastructure
                 Certificate and Certificate Revocation List (CRL)
                 Profile", <a href="./rfc4055">RFC 4055</a>, June 2005.

   [<a id="ref-RFC4269">RFC4269</a>]     Lee, H., Lee, S., Yoon, J., Cheon, D., and J. Lee, "The
                 SEED Encryption Algorithm", <a href="./rfc4269">RFC 4269</a>, December 2005.

   [<a id="ref-RFC5226">RFC5226</a>]     Narten, T. and H. Alvestrand, "Guidelines for Writing
                 an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC</a>
                 <a href="./rfc5226">5226</a>, May 2008.

   [<a id="ref-RFC6234">RFC6234</a>]     Eastlake 3rd, D. and T. Hansen, "US Secure Hash
                 Algorithms (SHA and SHA-based HMAC and HKDF)", <a href="./rfc6234">RFC</a>
                 <a href="./rfc6234">6234</a>, May 2011.




<span class="grey">Eastlake                     Standards Track                   [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   [<a id="ref-X9.62">X9.62</a>]       American National Standards Institute, Accredited
                 Standards Committee X9, "Public Key Cryptography for
                 the Financial Services Industry: The Elliptic Curve
                 Digital Signature Algorithm (ECDSA)", ANSI X9.62:2005,
                 2005.

   [<a id="ref-XMLENC10">XMLENC10</a>]    Reagle, J. and D. Eastlake, "XML Encryption Syntax and
                 Processing", W3C Recommendation, 10 December 2002,
                 &lt;<a href="http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/</a>&gt;.

   [<a id="ref-XMLENC11">XMLENC11</a>]    Eastlake, D., Reagle, J., Hirsch, F., and T. Roessler,
                 "XML Encryption Syntax and Processing Version 1.1", W3C
                 Proposed Recommendation, 24 January 2013,
                 &lt;<a href="http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/">http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/</a>&gt;.

   [<a id="ref-XPointer">XPointer</a>]    Grosso, P., Maler, E., Marsh, J., and N. Walsh,
                 "XPointer Framework", W3C Recommendation, 25 March
                 2003, &lt;<a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">http://www.w3.org/TR/2003/</a>
                 <a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">REC-xptr-framework-20030325/</a>&gt;.

Informative References

   [<a id="ref-CANON10">CANON10</a>]     Boyer, J., "Canonical XML Version 1.0", W3C
                 Recommendation, 15 March 2001,
                 &lt;<a href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</a>&gt;.

   [<a id="ref-CANON11">CANON11</a>]     Boyer, J., and G. Marcy, "Canonical XML Version 1.1",
                 W3C Recommendation, 2 May 2008,
                 &lt;<a href="http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/">http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/</a>&gt;.

   [<a id="ref-DECRYPT">DECRYPT</a>]     Hughes, M., Imamura, T., and H. Maruyama, "Decryption
                 Transform for XML Signature", W3C Recommendation, 10
                 December 2002, &lt;<a href="http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210">http://www.w3.org/TR/2002/</a>
                 <a href="http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210">REC-xmlenc-decrypt-20021210</a>&gt;.

   [<a id="ref-Errata191">Errata191</a>]   RFC Errata, Errata ID 191, <a href="./rfc4051">RFC 4051</a>,
                 &lt;<a href="http://www.rfc-editor.org">http://www.rfc-editor.org</a>&gt;.

   [<a id="ref-GENERIC">GENERIC</a>]     Nystrom, M. and F. Hirsch, "XML Security Generic Hybrid
                 Ciphers", W3C Working Group Note, 24 January 2013,
                 &lt;<a href="http://www.w3.org/TR/2013/NOTE-xmlsec-generic-hybrid-20130124/">http://www.w3.org/TR/2013/</a>
                 <a href="http://www.w3.org/TR/2013/NOTE-xmlsec-generic-hybrid-20130124/">NOTE-xmlsec-generic-hybrid-20130124/</a>&gt;.

   [<a id="ref-Keccak">Keccak</a>]      Bertoni, G., Daeman, J., Peeters, M., and G. Van
                 Assche, "The KECCAK sponge function family", January
                 2013, &lt;<a href="http://keccak.noekeon.org">http://keccak.noekeon.org</a>&gt;.





<span class="grey">Eastlake                     Standards Track                   [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   [<a id="ref-RFC3075">RFC3075</a>]     Eastlake 3rd, D., Reagle, J., and D. Solo, "XML-
                 Signature Syntax and Processing", <a href="./rfc3075">RFC 3075</a>, March 2001.

   [<a id="ref-RFC3076">RFC3076</a>]     Boyer, J., "Canonical XML Version 1.0", <a href="./rfc3076">RFC 3076</a>, March
                 2001.

   [<a id="ref-RFC3092">RFC3092</a>]     Eastlake 3rd, D., Manros, C., and E. Raymond,
                 "Etymology of "Foo"", <a href="./rfc3092">RFC 3092</a>, 1 April 2001.

   [<a id="ref-RFC3741">RFC3741</a>]     Boyer, J., Eastlake 3rd, D., and J. Reagle, "Exclusive
                 XML Canonicalization, Version 1.0", <a href="./rfc3741">RFC 3741</a>, March
                 2004.

   [<a id="ref-RFC4010">RFC4010</a>]     Park, J., Lee, S., Kim, J., and J. Lee, "Use of the
                 SEED Encryption Algorithm in Cryptographic Message
                 Syntax (CMS)", <a href="./rfc4010">RFC 4010</a>, February 2005.

   [<a id="ref-RFC4051">RFC4051</a>]     Eastlake 3rd, D., "Additional XML Security Uniform
                 Resource Identifiers (URIs)", <a href="./rfc4051">RFC 4051</a>, April 2005.

   [<a id="ref-RFC6090">RFC6090</a>]     McGrew, D., Igoe, K., and M. Salter, "Fundamental
                 Elliptic Curve Cryptography Algorithms", <a href="./rfc6090">RFC 6090</a>,
                 February 2011.

   [<a id="ref-RFC6151">RFC6151</a>]     Turner, S. and L. Chen, "Updated Security
                 Considerations for the MD5 Message-Digest and the HMAC-
                 MD5 Algorithms", <a href="./rfc6151">RFC 6151</a>, March 2011.

   [<a id="ref-RFC6194">RFC6194</a>]     Polk, T., Chen, L., Turner, S., and P. Hoffman,
                 "Security Considerations for the SHA-0 and SHA-1
                 Message-Digest Algorithms", <a href="./rfc6194">RFC 6194</a>, March 2011.

   [<a id="ref-Schema">Schema</a>]      Thompson, H., Beech, D., Maloney, M., and N.
                 Mendelsohn, "XML Schema Part 1: Structures Second
                 Edition", W3C Recommendation, 28 October 2004,
                 &lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>&gt;.

                 Biron, P. and A. Malhotra, "XML Schema Part 2:
                 Datatypes Second Edition", W3C Recommendation, 28
                 October 2004,
                 &lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>&gt;.

   [<a id="ref-SHA-3">SHA-3</a>]       US National Institute of Science and Technology, "SHA-3
                 WINNER", February 2013, &lt;<a href="http://csrc.nist.gov/groups/ST/hash/sha-3/winner_sha-3.html">http://csrc.nist.gov/</a>
                 <a href="http://csrc.nist.gov/groups/ST/hash/sha-3/winner_sha-3.html">groups/ST/hash/sha-3/winner_sha-3.html</a>&gt;.

   [<a id="ref-W3C">W3C</a>]         World Wide Web Consortium, &lt;<a href="http://www.w3.org">http://www.w3.org</a>&gt;.




<span class="grey">Eastlake                     Standards Track                   [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


   [<a id="ref-XCANON">XCANON</a>]      Boyer, J., Eastlake, D., and J. Reagle, "Exclusive XML
                 Canonicalization Version 1.0", W3C Recommendation, 18
                 July 2002,
                 &lt;<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/">http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/</a>&gt;.

   [<a id="ref-XMLDSIG10">XMLDSIG10</a>]   Eastlake, D., Reagle, J., Solo, D., Hirsch, F., and T.
                 Roessler, "XML Signature Syntax and Processing (Second
                 Edition)", W3C Recommendation, 10 June 2008,
                 &lt;<a href="http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/">http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/</a>&gt;.

   [<a id="ref-XMLDSIG11">XMLDSIG11</a>]   Eastlake, D., Reagle, J., Solo, D., Hirsch, F.,
                 Nystrom, M., Roessler, T., and K. Yiu, "XML Signature
                 Syntax and Processing Version 1.1", W3C Proposed
                 Recommendation, 24 January 2013,
                 &lt;<a href="http://www.w3.org/TR/2013/PR-xmldsig-core1-20130124/">http://www.w3.org/TR/2013/PR-xmldsig-core1-20130124/</a>&gt;.

   [<a id="ref-XMLDSIG-PROP">XMLDSIG-PROP</a>]
                 Hirsch, F., "XML Signature Properties", W3C Proposed
                 Recommendation, 24 January 2013, &lt;<a href="http://www.w3.org/TR/2013/PR-xmldsig-properties-20130124/">http://www.w3.org/TR/</a>
                 <a href="http://www.w3.org/TR/2013/PR-xmldsig-properties-20130124/">2013/PR-xmldsig-properties-20130124/</a>&gt;.

   [<a id="ref-XMLSECXREF">XMLSECXREF</a>]  Hirsch, F., Roessler, T., and K. Yiu, "XML Security
                 Algorithm Cross-Reference", W3C Working Group Note, 24
                 January 2013, &lt;<a href="http://www.w3.org/TR/2013/NOTE-xmlsec-algorithms-20130124/">http://www.w3.org/TR/2013/</a>
                 <a href="http://www.w3.org/TR/2013/NOTE-xmlsec-algorithms-20130124/">NOTE-xmlsec-algorithms-20130124/</a>&gt;.

   [<a id="ref-XPATH">XPATH</a>]       Boyer, J., Hughes, M., and J. Reagle, "XML-Signature
                 XPath Filter 2.0", W3C Recommendation, 8 November 2002,
                 &lt;<a href="http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/">http://www.w3.org/TR/2002/</a>
                 <a href="http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/">REC-xmldsig-filter2-20021108/</a>&gt;.

                 Berglund, A., Boag, S., Chamberlin, D., Fernandez, M.,
                 Kay, M., Robie, J., and J. Simeon, "XML Path Language
                 (XPath) 2.0 (Second Edition)", W3C Recommendation, 14
                 December 2010,
                 &lt;<a href="http://www.w3.org/TR/2010/REC-xpath20-20101214/">http://www.w3.org/TR/2010/REC-xpath20-20101214/</a>&gt;.

   [<a id="ref-XSLT">XSLT</a>]        Saxonica, M., "XSL Transformations (XSLT) Version 2.0",
                 W3C Recommendation, 23 January 2007,
                 &lt;<a href="http://www.w3.org/TR/2007/REC-xslt20-20070123/">http://www.w3.org/TR/2007/REC-xslt20-20070123/</a>&gt;.











<span class="grey">Eastlake                     Standards Track                   [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc6931">RFC 6931</a>              Additional XML Security URIs            April 2013</span>


Author's Address

   Donald E. Eastlake, 3rd
   Huawei Technologies
   155 Beaver Street
   Milford, MA  01757
   USA

   Phone: +1-508-333-2270
   EMail: d3e3e3@gmail.com









































Eastlake                     Standards Track                   [Page 36]
</pre>