--- 1/draft-ietf-jose-json-web-key-00.txt	2012-03-13 00:14:03.038670658 +0100
+++ 2/draft-ietf-jose-json-web-key-01.txt	2012-03-13 00:14:03.058671194 +0100
@@ -1,18 +1,18 @@
 
 JOSE Working Group                                              M. Jones
 Internet-Draft                                                 Microsoft
-Intended status: Standards Track                        January 16, 2012
-Expires: July 19, 2012
+Intended status: Standards Track                          March 12, 2012
+Expires: September 13, 2012
 
                            JSON Web Key (JWK)
-                    draft-ietf-jose-json-web-key-00
+                    draft-ietf-jose-json-web-key-01
 
 Abstract
 
    A JSON Web Key (JWK) is a JSON data structure that represents a set
    of public keys.
 
 Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
@@ -26,21 +26,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at http://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on July 19, 2012.
+   This Internet-Draft will expire on September 13, 2012.
 
 Copyright Notice
 
    Copyright (c) 2012 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -266,20 +266,22 @@
    No IANA actions are required by this specification.
 
 7.  Security Considerations
 
    TBD
 
 8.  Open Issues and Things To Be Done (TBD)
 
    The following items remain to be done in this draft:
 
+   o  Consider how additional key families would be added.
+
    o  Write the Security Considerations section.
 
 9.  References
 
 9.1.  Normative References
 
    [FIPS.186-3]
               National Institute of Standards and Technology, "Digital
               Signature Standard (DSS)", FIPS PUB 186-3, June 2009.
 
@@ -292,36 +294,40 @@
 
    [RFC4627]  Crockford, D., "The application/json Media Type for
               JavaScript Object Notation (JSON)", RFC 4627, July 2006.
 
    [RFC4648]  Josefsson, S., "The Base16, Base32, and Base64 Data
               Encodings", RFC 4648, October 2006.
 
 9.2.  Informative References
 
    [JWE]      Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web
-              Encryption (JWE)", January 2012.
+              Encryption (JWE)", March 2012.
 
    [JWS]      Jones, M., Bradley, J., and N. Sakimura, "JSON Web
-              Signature (JWS)", January 2012.
+              Signature (JWS)", March 2012.
 
    [MagicSignatures]
               Panzer (editor), J., Laurie, B., and D. Balfanz, "Magic
-              Signatures", August 2010.
+              Signatures", January 2011.
 
 Appendix A.  Acknowledgements
 
    A JSON representation for RSA public keys was previously introduced
    in Magic Signatures [MagicSignatures].
 
 Appendix B.  Document History
 
+   -01
+
+   o  Corrected the Magic Signatures reference.
+
    -00
 
    o  Created the initial IETF draft based upon
       draft-jones-json-web-key-03 with no normative changes.
 
 Author's Address
 
    Michael B. Jones
    Microsoft