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] | [Elist Home]

Subject: Re: [xcbf] SignedData Attributes - DigitalSignature Attributes

Then it appears that XER is not sufficient here.

It should be possible to send meta data in the
communication, as how would both sides know if
'011000' were a three octet string or a six bit
binary value. This is what attributes are used
for in XML.

I did not seek to disallow a BIT STRING signature
from being carried or displayed as bits when I
proposed that it also be allowed to carry this
information as octets.

And I would not wish to prohibit an application
from carrying a certificate signed as an XML
encoding as XML instead of as a base64 encoding.


John Larmouth wrote:

> The "format=" is not current XER.
> This needs thinking through a bit more, Phil.
> We certainly intend to allow BASE64 encodings, but currently the
> specification that it is BASE64 will be part  of the encoding
> instructions (known to both sides), and not something which is carried
> in an instance of communication.
> So I guess I oppose your "format=" parameter.
> Why do you need to have that transmitted in the XML?
> John L
> Phil Griffin wrote:
>>I proposed on 8/6 that the following XML markup be used
>>in XCBF.
>>    <version> ........................ </version>
>>    <digestAlgorithms> ............... </digestAlgorithms>
>>    <encapContentInfo> ............... </encapContentInfo>
>>    <certificates format='base64'> ... </certificates>
>>    <crls format='base64'> ........... </crls>
>>    <signerInfos> .................... </signerInfos>
>>The signature component of the SIGNATURE parameterized
>>type identifies a value of type BIT STRING. These bits
>>are not used as bit flags, and signatures tend to be in
>>the thousands of bits in length and can more easily and
>>compactly be represented as OCTET STRINGs. I propose that
>>the following XML markup be used for these values:
>>    <signature format='hex'> ... </signature>
>>So far, I have received no comments. Unless I hear comments
>>that use of these attributes is unacceptable, I will include
>>them in the next release of the XCBF document.
>>To subscribe or unsubscribe from this elist use the subscription
>>manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC