--- DANE-charter-2014-02.txt	2014-05-12 14:24:46.000000000 -0400
+++ DANE-charter-2014-03.txt	2014-05-13 15:39:11.000000000 -0400
@@ -1,4 +1,5 @@
 Current Status: Active
+DRAFT-03 
 
 Chairs:
      Warren Kumari
@@ -17,7 +18,6 @@
     working group will also assist other working groups with adding
     DANE functionality to their work. In addition the working group
     will monitor and provide guidance to operators and tool developers.
-    will monitor and provide guidance to operators and tool developers.
     When work on currently chartered documents is complete the WG
     may re-charter if sufficiently pressing new work is identified.
     DANE is not intended to be a long-lived catch-all WG
@@ -28,42 +28,44 @@
 
     The DANE working group has developed a framework for securely
     retrieving keying information from the DNS [RFC6698]. This
-    framework allows secure storing and looking up public key
+    framework allows secure storing and looking up server public key
     information in the DNS. This provides a binding between a domain
     name providing a particular service and the key that can be used
     to establish encrypted connection to that service.  
 
-    By requiring DNSSEC protection for the lookup of the public key
+    By requiring DNSSEC protection for the look-up of the public key
     information, DANE leverages the integrity protection provided by
     DNSSEC to enable secure discovery of keying information. Operators
     wanting to take advantage of DANE for their services must turn on
     DNSSEC signing on the zones used in finding the services. Using
-    DNS this way, bindings of keys to domains are asserted not by
-    external entities, but by the entities that operate the DNS. 
+    DNS this way, bindings of keys to domains are asserted by the entities that 
+    operate the DNS for that domain, not by external entities. 
 
     The DANE mechanisms provide flexibility in how the keying
     information is presented. DANE supports both Certificates and raw
     keys, further more Certificates and raw keys can be either the full
     key or a hash of the key. 
     The group will work on documenting the different approaches to use
-    DANE keying, and the security implication of each. 
+    DANE keying, and the security implication of each. In addition
+    the WG may develop a framework(s) to facilitate the lookup "client" DANE 
+    records for authorization/authentication purposes. 
 
     The group may also create documents that describe how protocol
     entities can discover and validate these bindings in the execution
     of specific applications. This work would be done in coordination
     with the IETF Working Groups responsible for the protocols. 
 
-    The group may in addition encourage interop testing and document
-    results of such testing. 
+    The group may in addition encourage interoperability testing and document
+    the results of such testing. 
 
 Goals and Milestones:
   DONE - First WG draft of standards-track protocol for using DNS to associate hosts with keys for TLS and DTLS
   DONE - Protocol for using DNS to associate domain names with keys for TLS and DTLS to IESG
   Jun 2014 - Advance DANE SRV document to IESG
-  Jun 2014 - Advance DANE SMPT document to IESG
+  Jun 2014 - Advance DANE SMTP document to IESG
   Aug 2014 - Advance DANE SMIME document to IESG
   Aug 2014 - Advance DANE OPENPGP document to IESG
-  Sep 2014 - Advance DANE operational guidance document to IESG
+  Sep 2014 - Advance DANE operational guidance/errata document to IESG
   Jan 2015 - Advance DANE security model document to IESG. 
   May 2015 - Advance DANE IPSEC document to IESG
   Sep 2015 - Advance DANE RFC6698 and DANE SRV RFC to Internet Standard