- From: Gino Tesei <gino.tesei@ekar.it>
- Date: Tue, 21 Oct 2003 21:52:22 +0200
- To: "Rich Salz" <rsalz@datapower.com>, <w3c-ietf-xmldsig@w3.org>
- Message-ID: <F95FCBD3427A2C48B8704C734F26119E37C4B0@mail.ekar.it>
Thank you for your answer, Rich. >Many vendors have XML DSIG libraries, and there are some open >source packages in (at least) C and Java. These libraries don't >free the application program of all the details Yes ... and we belonging to the community of lazy programmers, appreciate a lot this. Other side, this should be one of (many?) packages inside the application, maybe another one for WS. In addition, legacy systems require their own framework :) ... moreover, developers and designers usually don't maintain the system, that should be virtually maintained by (bank) clerks usually not skilled in such standards/implementations/frameworks. For these reasons, a unique framework/implementation at least for WS, XML Signature and XML Encryption should be suitable. Finally, details concerning other banks platforms are simply not provided; hence joining to a standard makes sense since, if they work over .NET insetead of Bea WebLogic, for instance, they can be compliant without a maior revision of their middleware :) ... >have network devices that add XML security >features as either a true network device, or a set of software running >as a software proxy. This is very good for scalability, reusability and other non functionals concerns (maintenibility?); and I find this an interesting idea ... >Also, in the greater Boston area it will be cloudy with a chance >of rain and temperatures around 68 Fahrenheit. :) I suppose your umbrellas are very Secure :) Gino
Received on Tuesday, 21 October 2003 15:54:25 UTC