| Subject: | Fwd: Extensibility Sentence | |
|---|---|---|
| From: | Trevor Perrin (tre...@trevp.net) | |
| Date: | Jul 17, 2003 12:38:10 pm | |
| List: | org.oasis-open.lists.dss | |
Refine Search
| From | Sent On | Attachments |
|---|---|---|
| Trevor Perrin | Jul 17, 2003 12:38 pm | |
| Nick Pope | Jul 18, 2003 1:31 am |
| Subject: | Fwd: Extensibility Sentence | |
|---|---|---|
| From: | Trevor Perrin (tre...@trevp.net) | |
| Date: | Jul 17, 2003 12:38:10 pm | |
| List: | org.oasis-open.lists.dss | |
From Ed -
Date: Thu, 17 Jul 2003 15:49:19 -0400 From: Edward Shallow <ed.s...@rogers.com> Subject: Extensibility Sentence To: Trevor Perrin <tre...@trevp.net> Cc: Gray Steve <stev...@upu.int>, po...@secstan.com
Hi Trevor,
On the last conference call I was tasked with sending you a sentence describing a general "extensibility" capability within the protocol. Try this ... Feel free to tweak.
"Support for additional service options characterized by scenarios like Verify and TimeStamp should be provided for more generally as part of an overall "extensibility framework". As such the introduction of various options or directives on core DSS service operations can be extended to support profile-specific requirements. This "extensibility framework" should be designed to support the notion of compound or stacked operations typified by the Verify and TimeStamp scenario as well as the more common notions of "selection of response elements" or "specification of signing attributes".
Ed
P.S. As usual, please post.

