Merge pull request #32 from dimmyvi/tfpauly-patch-1

Charter edit proposals

charter.md

@@ -1,4 +1,4 @@
-#Charter for Working Group
+# TIGRESS Charter ("Transfer dIGital cREdentialS Securely")
 
 There are many situations in which it is desirable to transfer a copy of a digital credential to another person. For example, you may want to provide access to your vehicle to a friend or a family member. You may also want to provide access to your home to your cat sitter. Or, you may want to transfer a copy of a hotel key to your spouse. Today, no such standardized method exists in a cross-platform, credential type-agnostic capacity. 
 
@@ -18,22 +18,21 @@ Sufficient security measures should be embedded in the protocol in an effort to:
 
 The solution the WG comes up with must:
 
-- Allow a sender to initiate a share and define a relay server
+- Allow a sender to initiate a share and select a relay server
 - Allow a recipient to view the share request, and provision the credential associated with the share upon receipt
-- Allow opaque message content based on the credential type (the protocol should be able to carry various types of credentials)
-- Allow sender device and receiver device to perform multiple round trip communications within a limited time frame.
+- Allow a sender and a recipient to perform multiple round trip communications within a limited time frame
+- Support opaque message content based on the credential type
 - Support a variety of types of credentials, to include those adhering to public standards (e.g., Car Connectivity Consortium) and proprietary (i.e., non-public or closed community) formats
-- Allow opaque message content based on the credential type 
 
-Planned Deliverables:
-
-2022-12: WG adoption of the secure credential transfer protocol
-2023-12: Submit secure credential transfer protocol to the IESG for publication
-
-Out of scope topics for the WG are:
+The following topics are out of scope for the WG:
 
 - Defining the mechanism the receiver will use in order to provision the credential with the credential authority
-- The User Interface (UI) that is displayed to the sender or receiver during sending or receiving - this will depend on the device OEM’s UI and HI guidelines. 
-- Defining the format or content of each field within the encrypted data (i.e., the provisioned credentials and associated information) stored on the relay server. 
+- The User Interface (UI) that is displayed to the sender or receiver during sending or receiving (this will depend on the device manufacturer's interface guidelines) 
+- Defining the format or content of each field within the encrypted data (i.e., the provisioned credentials and associated information) stored on the relay server
 
 The WG will deliver a protocol to facilitate secure credential transfer. The WG must consider all Privacy and Security considerations in an effort to perform the credential transfer in a secure manner. The protocol will use appropriate cryptographic mechanisms to protect the transferred credentials in accordance with the security and privacy goals described above.
+
+Planned Deliverables:
+
+2022-12: WG adoption of the secure credential transfer protocol
+2023-12: Submit secure credential transfer protocol to the IESG for publication