| From | Sent On | Attachments |
|---|---|---|
| Trevor Perrin | Jul 9, 2003 9:59 am | |
| Trevor Perrin | Jul 9, 2003 10:38 am | |
| Trevor Perrin | Jul 9, 2003 7:55 pm | |
| Trevor Perrin | Jul 9, 2003 9:41 pm | |
| Gray Steve | Jul 10, 2003 12:17 am | |
| Nick Pope | Jul 10, 2003 1:49 am | |
| Trevor Perrin | Jul 10, 2003 2:03 am | |
| Trevor Perrin | Jul 10, 2003 2:11 am | |
| Nick Pope | Jul 10, 2003 2:33 am | |
| Trevor Perrin | Jul 10, 2003 9:49 am | |
| Trevor Perrin | Jul 10, 2003 12:07 pm | |
| Trevor Perrin | Jul 10, 2003 2:57 pm | |
| Nick Pope | Jul 11, 2003 1:46 am | |
| Gray Steve | Jul 11, 2003 8:53 am | |
| Trevor Perrin | Jul 11, 2003 11:20 am |
| Subject: | RE: [dss] Fwd: RE: UPU CPC EPM Positioning Proposal vis-a-vis the OASIS DSS | |
|---|---|---|
| From: | Trevor Perrin (tre...@trevp.net) | |
| Date: | Jul 10, 2003 12:07:03 pm | |
| List: | org.oasis-open.lists.dss | |
At 10:52 AM 7/10/2003 +0100, Nick Pope wrote:
Content-Transfer-Encoding: 7bit
Trevor,
Sorry, yes I agree that we should use the same protocol.
Unless it is already there and I have missed it, I suggest that we should add that there is a protocol to obtain a time-stamp token (and verify time-stamp token ???), and that this requirement may be met using the signing request / response.
I agree, though at least Ed disagrees, let's see what anyone else says.
I also missed the words hidden in 3.1.2: "We will also define an XML Timestamp Token format, which will be similar to an RFC 3161 TimeStampToken, and can be used for time-stamping XML-DSIG signatures. We will leave this format extensible to support linking schemes in the future."
I suggest that is made more prominent by putting a new sub-heading "3.1.3 Time-stamp token"
Good idea.
Finally, I would also perhaps suggest that the XML time-stamping can be provided through a profile of DSS, and so that we add to 3.10.2:
- Time-stamping service profile.
I'll change "XML Time-Stamp Binding" to "XML Time-Stamp Binding and Profile", and in general change 3.10 to talk not just about "Signature Profiles" but "Protocol Profiles" as well, since these have played an increasing role in our discussions.
Trevor





