ebxml-msg — archive

[System]

I am just catching up on this discussion, and it might have been resolved in some message I have not yet gotten to, but... here is what I thought the major contentions were: 1. Intermediaries may for unknown reasons decide to do some format change that invalidate the signature, using any of the existing w3c defined transforms. 2. Also even when excisable-by-xpath elements are added by intermediaries, there are format changes possible that may fail to provide suitable canonicalization by any existing w3c transform. (suitable canonicalization means to allow signature validity to be preserved under the identified changes.) My question is whether Sanjay and others take this whitespace problem to be resolvable by defining a new canonicalizing transform? If so, should we submit this issue somehow or other to the XMLDsig group/activity in W3C and have them see if they are interested in developed a transform suitable for whitespace under the reformatting changes you have identified? I guess in general I see ebXML messaging as a consumer of security protocols, weaving them into an approach suitable for business requirements. So I do not see this as within our scope/charter to actually fix this, except perhaps by presenting it to w3c for consideration. Maybe SBC can let Sanjay join the w3c committee to represent us! Dale Moberg