OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xcbf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xcbf] Groups - XCBF XML Common Biometric Format CS April 3 2003.zip uploaded (fwd)




> -----Original Message-----
> From: Bancroft Scott [mailto:baos@oss.com] 
> Sent: Saturday, April 12, 2003 17:57
> To: xcbf@lists.oasis-open.org
> Subject: Re: [xcbf] Groups - XCBF XML Common Biometric Format 
> CS April 3 2003.zip uploaded (fwd)
> 
> 
> Phil,
> 
> The crux of the problem that we are having lies around the 
> fact that XCBF is using Base64 as an encoding, but Base64 is 
> not available in the current version of X.693.  Given this, 
> plus the fact that that only the EnvelopedData and SignedData 
> types carry certificates and CRLs, 


Also notice that the text mentions BASE-64 only in relation to
EnvelopedData (OriginatorInfo) and NOT in relation to SignedData,
although both EnvelopedData and SignedData may carry certificates.

Therefore the use of BASE-64, as specified by the current normative
text, only applies to the certificates included in EnvelopedData and not
to those included in SignedData, which are probably more common.  The
latter are encoded in hex.

Alessandro



> and that even in these 
> cases, the certificates and CRLs components are optional (and 
> in practice never used), it would solve all our problems if 
> XCBF used straight XER and/or CXER encoding.
> 
> In other words, I propose that we drop the use of (currently 
> non-standard in XER/CXER) Base64 in XCBF and instead stick to 
> HEX encoding as required by XER/CXER.  This would resolve the 
> concerns that everyone, including Ed Day, has voiced.
> 
> Bancroft
> 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]