RE: Revised draft charter

["Turner, Sean P." <turners@xxxxxxxx>]

I did a really bad cut and paste job on version 2 when I was incorporating
comments from the list.  I posted version 3 (on 8/21) that addressed some
off-line comments (including your scope comment).  I also added out-of-scope
ideas suggested on the list.  I missed deleting the redundant sentence, but
it will be gone in version 4. I'll also make the other changes you suggested
to the trust anchor definition. As for the TAA definition, how about:

A Trust Anchor Administrator (TAA) is the entity represented by the trust
anchor.  The TAA controls the private key of the trust anchor.

The following is the new suggested scope paragraphs:

The scope of the work is to include:

- Supporting a single trust anchor administrator, such as in a typical
enterprise, who may be administering multiple trust anchors in her domain
- Supporting multiple trust anchor administrators, each of whom is
independant
- Supporting systems with limited or no user interface
- Supporting devices that may or many not be connected to the Internet at
the time of management (e.g., relying on physical delivery of delivery trust
anchor management messages)

The scope of work will not include:

- Management of non-anchor signature validation objects such as intermediate
certificates in a validation path.
- Mandating whether the recipient of trust anchors from a trust anchor
manager will use those anchors

spt