In the EPS-LockBox structure, there is a place to put a policy tree. This is currently coded as an ASN.1 structure with various leaf types. There is an equivalent structure, but encoded in XML in the server protocol document. There are some potential issues with having two different encodings and I am looking for input into the question of moving to a single encoding method.
The ASN.1 encoding is going to be smaller, when placed in an ASN.1 context, such as the EPS-LockBox structure. It would probably not be smaller if we used the ASN.1 structure in an XML context because of the base64 expansion of all of the text strings associated with policy names and policy parameters. Having a single method of encoding would mean that there is a single method of encoding and the same parsing could be used in many places, however there is a question of what happens for schema tagging in the case of placing the XML into the ASN.1 context. If we use XML in the ASN.1 context, should we require that a full schema tag be added or would the XML parser be required to deal with any nodes found. There is a high probably that one would need to deal with schema strings for expanded sets of parameters which are currently incorrectly done in the ASN.1 document. I am currently in the process of updating the document and want to have it published before next Monday. I am currently on the fence about making the change to using the XML format of policies in the ASN.1 document. If you want to give me input please do so this week. We can always revisit later if we decide it is wrong, but the fewer times we change this, the better for implementers. Jim _______________________________________________ plasma mailing list [email protected] https://www.ietf.org/mailman/listinfo/plasma
