[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[TSP] signedData version calculation

To: ietf-pkix <ietf-pkix@xxxxxxx>
Subject: [TSP] signedData version calculation
From: tho <thomas.fossati@xxxxxx>
Date: Wed, 18 Dec 2002 13:56:00 +0100
List-archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-id: <ietf-pkix.imc.org>
List-unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
Sender: owner-ietf-pkix@xxxxxxxxxxxx
User-agent: Mutt/1.2.5.1i


There seems to be an inconsistency in the calculation of signedData's 
version between different versions of the CMS document: rfc2630 implies 
version = 3, while rfc3369 implies version = 1 or 3 depending on certReq 
field value in the TimeStampReq.

Both rfc3161 and draft-rfc3161bis refer to rfc2630, hence from a TSP 
specs perspective we are at least consistent, yet that doesn't save 
us from an actual implementation problem...

Thomas

Follow-Ups:
- Re: [TSP] signedData version calculation
  - From: tho

Prev by Date: [TSP] misc comments
Next by Date: [TSP] PKIStatus constants clarification
Previous by thread: [TSP] misc comments
Next by thread: Re: [TSP] signedData version calculation
Index(es):
- Date
- Thread