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

Re: [KEYPROV] XML to ASN.1 for attributes

Hannes,
The ASN.1 container has an extensible mechanism to add arbitrary data to a collection of keys or one key. It just happens to be called an attribute. So the term is being a bit overloaded. When we define the attributes we can either define the attributes to be the lowest child element or a collection of child elements. We can also use ASN.1's extensibility mechanism (the "...") to allow more things to be added to an attribute that collects more than one child element. 

spt

Tschofenig, Hannes (NSN - FI/Espoo) wrote:

In XML it is more useful to have child elements rather than attributes.
The main reason is extensibility. When you want to define complex
structures then those cannot be added as attributes. 
I wonder whether a similar restriction replies to ASN.1

Ciao
Hannes



-----Original Message-----
From: keyprov-bounces at ietf.org [mailto:keyprov-bounces at ietf.org] On Behalf Of ext Sean Turner 
Sent: 06 August, 2009 19:27
To: keyprov at ietf.org
Subject: Re: [KEYPROV] XML to ASN.1 for attributes

Sean Turner wrote:
As PSKC is basically done, I'm going to convert the XML elements/attributes to ASN.1. I've got one question: should the elements with child elements be one attribute or separate attributes? 
For example, DeviceInfo is as follows:

<DeviceInfo>
  <Manufacturer>Manufacturer</Manufacturer>
  <SerialNo>987654321</SerialNo>
  <UserId>DC=example-bank,DC=net</UserId>

We could either have one attribute:

DeviceInfo ::= SEQUENCE {
  manufactuer Manufactuer,
  serialNo    SerialNo,
  userId      UserId }

or three separate attributes:

 Manufactuer, SerialNo, and UserId.

Which way do people want it?


I'm leaning towards separate attributes....

spt
_______________________________________________
KEYPROV mailing list
KEYPROV at ietf.org
https://www.ietf.org/mailman/listinfo/keyprov