RE: [dss] timestamping profile wd-05

["Dimitri Andivahis" <dimitri@surety.com>]

Trevor,
How about this alternative to your second paragraph below:

"The client SHOULD only send a single input document
if the server receiving the request returns time-stamps 
that can only cover one document per time-stamp (e.g. RFC 3161)."

Dimitri

-----Original Message-----
From: Trevor Perrin [mailto:trevp@trevp.net]
Sent: Tuesday, March 09, 2004 6:55 PM
To: Dimitri Andivahis; dss@lists.oasis-open.org
Subject: RE: [dss] timestamping profile wd-05


At 06:07 PM 3/9/2004 -0500, Dimitri Andivahis wrote:

> > -----Original Message-----
> > From: Trevor Perrin [mailto:trevp@trevp.net]
> > ...
> > Also, I added a restriction in Input Documents, so the client can
> > only send
> > a *single* input document, since RFC 3161 Timestamps (and possibly other
> > types of time-stamps) can only time-stamp a single hash at a time.
> > ...
>
>I disagree with this restriction.  Other types of time-stamps
>may be able to deal with multiple hashes at once.
>You could instead add a note stating that RFC 3161 timestamps
>are restricted to a single hash in the client request.

What if we relax this from a MUST to a SHOULD?

"The client MUST only send <DocumentHash> input documents.  The client MUST 
NOT sent <Document> input documents.

The client SHOULD only send a single input document, since some types of 
time-stamps (e.g. RFC 3161) can only cover one document per time-stamp."


Trevor 


To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_workgroup.php.