- From: merlin <merlin@baltimore.ie>
- Date: Wed, 09 May 2001 17:08:38 +0100
- To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
- Cc: w3c-ietf-xmldsig@w3.org
Hi Donald, The RetrievalMethod example from the last interop points at an X509Data containing X509SubjectName, X509IssuerSerial and X509Certificate. Clearly the certificate worked, as that is where the verification key was retrieved. As for the other bits, what are the criteria for interop? Successful parsing? Is it important (from the perspective of having XMLDSIG successfully advanced along standards tracks) to have hard interop on these other features? Merlin r/dee3@torque.pothole.com/2001.05.08/15:37:02 >Hi, > >I'd like to know what interoperability there has benn between >independent implementations of KeyInfo types other than KeyValue and >RetrievalMethod. > >In particular, has there been such interoperation for > X509Data, PGPData, or SPKIData >and if so with what subelement or elements? >Also for KeyName, are there two implementations which have agreed on >some particular interpretation for some KeyName values and >interoperated? > >Thanks, >Donald > >===================================================================== > Donald E. Eastlake 3rd dee3@torque.pothole.com > 155 Beaver Street +1 508-634-2066(h) > Milford, MA 01757 USA +1 508-261-5434(w) ----------------------------------------------------------------------------- Baltimore Technologies plc will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. In addition, certain Marketing collateral may be added from time to time to promote Baltimore Technologies products, services, Global e-Security or appearance at trade shows and conferences. This footnote confirms that this email message has been swept by Baltimore MIMEsweeper for Content Security threats, including computer viruses. http://www.baltimore.com
Received on Wednesday, 9 May 2001 12:09:00 UTC