Prioritization of secondary features

Hi.
at WebCrypto WG Charter (
http://www.w3.org/2011/11/webcryptography-charter.html)
following secondary features are listed.

   - control of TLS session login/logout
   - derivation of keys from TLS sessions
   - a simplified data protection function
   - multiple key containers
   - key import/export
   - a common method for accessing and defining properties of keys
   - the lifecycle control of credentials such enrollment, selection, and
   revocation of credentials with a focus enabling the selection of
   certificates for signing and encryption

as discussed in previous concall,
we need to set priority for secondary features.

I feel certificate related features has more priority than others.
also TLS related features also have relationship with certificates.
so with my view, I listed following certificate related secondary features

   - certificate enrollment
      - this is different from key generation
      - CMP can be considered.
   - certificate validation
      - certificate chain validation
      - CRL or OCSP validation
   - certificate selection with binded private key
      - has UI related requirement
   - access certificate extension fields
      - including optional fields
   - multi-origin crypto operation with certificate associated.
   - control of TLS session login/logout
   - derivation of keys from TLS sessions.

any comments?

regards
 mountie.

-- 
Mountie Lee

PayGate
CTO, CISSP
Tel : +82 2 2140 2700
E-Mail : mountie@paygate.net

=======================================
PayGate Inc.
THE STANDARD FOR ONLINE PAYMENT
for Korea, Japan, China, and the World