Interop: elapsed time estimation, some proposals for leading certaintasks

[Juan Carlos Cruellas <cruellas@ac.upc.edu>]

Dear all,

Below follows some initial estimation of elapsed time for the interop 
tasks as well as a proposal for leaders of certain tasks/sub-tasks

TASK 1. INTEROPERABILITY SCOPE: 2 weeks for initial proposals


For each profile and the core, identify what features (optional inputs 
and optional outputs) will be tested.

So far it seems that most of TC members agreed in having interop on 
certain features of:

. core (leader: Andreas; other volunteers: Stefan, Juan Carlos, other?)

. complete validation report (leader: Detlef; other volunteers: Juan 
Carlos, other?)

. visual signatures (leader: Ezer, other volunteers?)

and maybe others like AdES....


TASK 2. SPECIFICATION OF TEST CASES. 4 to 6 weeks.
(the leaders for core and profiles as before)


For each profile and the core, completely define the test cases. This 
means, at least, to  generate a document (probably better if contains 
tables) that provides all the details of the test cases.

If ETSI's portal used, use the template already developed for previous 
interop tests.

TASK 3. TAILORING OF THE PORTAL FOR THE DSS INTEROP 3 weeks (leader ETSI 
CTI if ETSI portal eventually used)

TASK 4. DEFINITION OF TRUST INFRASTRUCTURE (PKI: CAs chain, CRL issuers, 
OCSP responses issuers) 2 weeks?

TASK 5. COMPLETE PKI'S DEPLOYMENT IF ANY PIECE IS MISSING IN THE PORTAL
(would depend on the trust infrastructure to be used)

TASK 6. COMPLETE DOCUMENTATION IN THE PORTAL (this includes producing 
explanatory material ) 4 weeks

TASK 7. GENERATE THE DSS REQUESTS AND RESPONSES CORRESPONDING TO THE 
TEST CASES (TC MEMBERS INVOLVED). (??)