W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2009

html5/spec Overview.html,1.2776,1.2777

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Aug 2009 06:50:01 +0000
To: public-html-commits@w3.org
Message-Id: <E1MalBJ-0001yK-K5@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv7566

Modified Files:
	Overview.html 
Log Message:
Update <keygen> references. (whatwg r3584)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2776
retrieving revision 1.2777
diff -u -d -r1.2776 -r1.2777
--- Overview.html	11 Aug 2009 06:14:28 -0000	1.2776
+++ Overview.html	11 Aug 2009 06:49:58 -0000	1.2777
@@ -37666,7 +37666,7 @@
       user, if appropriate.</p>
 
       <p>Select an RSA signature algorithm from those listed in
-      section 7.2.1 ("RSA Signature Algorithm") of RFC2459. <a href="#refsRFC2459">[RFC2459]</a></p>
+      section 2.2.1 ("RSA Signature Algorithm") of RFC 3279. <a href="#refsRFC3279">[RFC3279]</a></p>
 
      </dd>
 
@@ -37702,22 +37702,22 @@
    <li>
 
     <p>Let <var title="">algorithm</var> be an ASN.1 <code title="">AlgorithmIdentifier</code> structure as defined by
-    RFC2459, with the <code title="">algorithm</code> field giving the
+    RFC 5280, with the <code title="">algorithm</code> field giving the
     ASN.1 OID used to identify <var title="">signature
-    algorithm</var>, using the OIDs defined in section 7.2 ("Signature
-    Algorithms") of RFC2459, and the <code title="">parameters</code>
-    field set up as required by RFC2459 for <code title="">AlgorithmIdentifier</code> structures for that
-    algorithm. <a href="#refsX690">[X690]</a> <a href="#refsRFC2459">[RFC2459]</a></p>
+    algorithm</var>, using the OIDs defined in section 2.2 ("Signature
+    Algorithms") of RFC 3279, and the <code title="">parameters</code>
+    field set up as required by RFC 3279 for <code title="">AlgorithmIdentifier</code> structures for that
+    algorithm. <a href="#refsX690">[X690]</a> <a href="#refsRFC5280">[RFC5280]</a> <a href="#refsRFC3279">[RFC3279]</a></p>
 
    </li>
 
    <li>
 
     <p>Let <var title="">spki</var> be an ASN.1 <code title="">SubjectPublicKeyInfo</code> structure as defined by
-    RFC2459, with the <code title="">algorithm</code> field set to the
+    RFC 5280, with the <code title="">algorithm</code> field set to the
     <var title="">algorithm</var> structure from the previous step,
     and the <code title="">subjectPublicKey</code> field set to the
-    BIT STRING value resulting from ASN.1 DER encoding the <var title="">public key</var>. <a href="#refsX690">[X690]</a> <a href="#refsRFC2459">[RFC2459]</a></p>
+    BIT STRING value resulting from ASN.1 DER encoding the <var title="">public key</var>. <a href="#refsX690">[X690]</a> <a href="#refsRFC5280">[RFC5280]</a></p>
 
    </li>
 
@@ -37761,7 +37761,7 @@
 
   <p>The data objects used by the above algorithm are defined as
   follows. These definitions use the same "ASN.1-like" syntax defined
-  by RFC2459. <a href="#refsRFC2459">[RFC2459]</a></p>
+  by RFC 5280. <a href="#refsRFC5280">[RFC5280]</a></p>
 
   <pre class="asn"><dfn id="publickeyandchallenge">PublicKeyAndChallenge</dfn> ::= SEQUENCE {
     spki <span>SubjectPublicKeyInfo</span>,
@@ -78422,11 +78422,6 @@
    and Scheduling Core Object Specification (iCalendar)</a></cite>, F. Dawson, D.
    Stenerson. IETF, November 1998.</dd>
 
-   <dt id="refsRFC2459">[RFC2459]</dt>
-   <dd><cite><a href="http://www.ietf.org/rfc/rfc2459.txt">Internet X.509 Public
-   Key Infrastructure Certificate and CRL Profile</a></cite>, R. Housley, W.
-   Ford, W. Polk, D. Solo. IETF, January 1999.</dd>
-
    <dt id="refsRFC2483">[RFC2483]</dt>
    <dd><cite><a href="http://www.ietf.org/rfc/rfc2483.txt">URI Resolution
    Services Necessary for URN Resolution</a></cite>, M. Mealling, R. Daniel.
@@ -78444,6 +78439,13 @@
    <dd><cite><a href="http://www.ietf.org/rfc/rfc3023.txt">XML Media
    Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF, January 2001.</dd>
 
+   <dt id="refsRFC3279">[RFC3279]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc3279.txt">Algorithms
+   and Identifiers for the Internet X.509 Public Key Infrastructure
+   Certificate and Certificate Revocation List (CRL)
+   Profile</a></cite>, W. Polk, R. Housley, L. Bassham. IETF, April
+   2002.</dd>
+
    <dt id="refsRFC3490">[RFC3490]</dt>
    <dd><cite><a href="http://www.ietf.org/rfc/rfc3490.txt">Internationalizing
    Domain Names in Applications (IDNA)</a></cite>, P. Faltstrom, P. Hoffman, A.
@@ -78478,6 +78480,12 @@
    Instant Messaging (IM)</a></cite>, C. Jennings, J. Reschke. IETF,
    January 2007.</dd>
 
+   <dt id="refsRFC5280">[RFC5280]</dt>
+   <dd><cite><a href="http://www.ietf.org/rfc/rfc5280.txt">Internet
+   X.509 Public Key Infrastructure Certificate and Certificate
+   Revocation List (CRL) Profile</a></cite>, D. Cooper, S. Santesson,
+   S. Farrell, S. Boeyen, R. Housley, W. Polk. IETF, May 2008.</dd>
+
    <dt id="refsRFC5322">[RFC5322]</dt>
    <dd><cite><a href="http://www.ietf.org/rfc/rfc5322.txt">Internet Message
    Format</a></cite>, P. Resnick. IETF, October 2008.</dd>
Received on Tuesday, 11 August 2009 06:50:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 06:50:15 GMT