Merge pull request #159 from davidben/bas/charter-private-twaek

charter: elaborate that private PKIs might not need transparency

Author: davidben

charter-ietf-plants.md

@@ -30,7 +30,7 @@ As part of this work, the Working Group may extend PKIX (RFC 5280), e.g. with ne
 
 Though not the initial focus, the PLANTS Working Group may consider other properties of transparent PKIs to improve upon the status quo, such as auditing, monitoring, or revocation. If feasible concrete improvements are identified, the Working Group may recharter to seed secondary deliverables that build on its initial work.
 
-In evaluating decisions and design tradeoffs, the Working Group will consider security, privacy, transparency, performance, and deployment properties, aiming to comparably meet the needs of today's applications that use CT-based PKIs with TLS. In particular the WG will deliver a design that can ensure that a misbehavior by a single party cannot compromise transparency for relying parties. The Working Group may consider and explain how these mechanisms could be adapted for deployment in a private or limited scope PKI as a secondary use case.
+In evaluating decisions and design tradeoffs, the Working Group will consider security, privacy, transparency, performance, and deployment properties, aiming to comparably meet the needs of today's applications that use CT-based PKIs with TLS. In particular the WG will deliver a design that can ensure that a misbehavior by a single party cannot compromise transparency for relying parties. The Working Group may consider and explain how these mechanisms could be adapted for deployment in a private or limited scope PKI (potentially without transparency) as a secondary use case.
 
 The PLANTS Working Group's scope is to explore mechanisms for CAs and transparency ecosystems to certify key/identifier bindings in a publicly monitorable way. Alternate trust models and changes to how TLS uses the end-entity key are not in scope for the Working Group.