ETSI's validation protocol based on DSS-X

[Andreas Kuehne <kuehne@trustable.de>]

Hallo guys,

today I joined the ESI meeting with it's focus on Validation. Juan Carlos presented the protocol part and presented his extension of the DSS validation protocol. The aspects not supported by DSS are:

- extend and rename   AdditionalKeyInfo to hold

• OCSP responses
• PoEs
• a 'poor man's PoE': a 'known existing time', a plain date/time when the caller is sure the signature existed

- extend the validation protocol to handle multiple signatures with distinct validation settings

- additional requests for signature augmentation

The first topic makes perfect sense to me and I would propose to add it to the current core draft.

The second topic smells a bit of over-engineering to me. I would NOT guess that it's a common use case to validate multiple signatures with different settings at a time. The introduced complexity does not pay off. If you really want to do it you may send several calls simultaneously.

The last topic (signature augmentation, aka upgrade) dtmo. is in the core ever since. In the signatrure creation section it is explicitly mentioned that input documents may be signatures. Maybe we should clarify the specification here.

What's your view on this?

See attached the current working draft of the protocol document. Juan Carlos asked me to distribute it within DSS-X for review purposes.

Greetings,

Andreas

 -- 
Andreas Kühne 
phone: +49 177 293 24 97 
mailto: kuehne@trustable.de

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612

Director Andreas Kühne

Company UK Company No: 5218868 Registered in England and Wales 

Attachment: ESI-0019442v009.docx
Description: Binary data