At 09:45 5/17/2001 -0700, Blair Dillaway wrote: >[blaird] yes, this is how we agreed it would work in past discussions. >but, to reiterate a point in my post, if we allow the application to >handle the serialization to an octet sequence then I don't see how >we can enforce this behavior. This is true I'm realizing. >I do believe we need to allow the app >to do the serialization so they can choose to do operations such as >C14N or serialize & compress. A big issue is whether we define a >required serialization method in XML Encryption or always defer this >operation to the using application. If we are doing octet encrpytion, then I think my bias shifts back to Infoset to use to describe these things. And how an application serializes the infoset into octets (that our spec then defines how to encrypt) could be up to it even. __ Joseph Reagle Jr. http://www.w3.org/People/Reagle/ W3C Policy Analyst mailto:reagle@w3.org IETF/W3C XML-Signature Co-Chair http://www.w3.org/Signature W3C XML Encryption Chair http://www.w3.org/Encryption/2001/Received on Thursday, 17 May 2001 15:27:15 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 27 May 2007 00:08:56 GMT