[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wss] PKCS#7 and XML DSIG Implementation
You are correct, it is merely informational. Somehow a "A SMALL GROUP OF SUBJECT MATTER EXPERTS" will soon suggest "REQUIRED STANDARDS TO ACHIEVE INTEROPERABILITY." I suppose that may involve mandating the use of one over the other. r/ John -----Original Message----- From: Blake Dournaee [mailto:blake@sarvega.com] Sent: Thursday, July 29, 2004 12:17 PM To: 'Weiland, John R. NMIMC GS'; klawrenc@us.ibm.com; wss@lists.oasis-open.org Subject: RE: [wss] PKCS#7 and XML DSIG Implementation John, I don't understand the point. It's an obvious fact that PKCS#7 and XML Signature don't interoperate, they are built around completely different technologies. Blake -----Original Message----- From: Weiland, John R. NMIMC GS [mailto:JRWeiland@US.MED.NAVY.MIL] Sent: Thursday, July 22, 2004 8:51 AM To: 'klawrenc@us.ibm.com'; wss@lists.oasis-open.org Subject: [wss] PKCS#7 and XML DSIG Implementation FYI, I just received this message: 3. CURRENTLY, TOOLS USED BY THE ABOVE DOCUMENT PROCESS/VIEWING APPLICATIONS AND WEB BROWSERS TO CREATE DIGITAL SIGNATURES ARE NOT INTEROPERABLE. INTEROPERABILITY ISSUES EXIST WITH INDUSTRY STANDARDS (I.E. PUBLIC KEY CRYPTOGRAPHY STANDARD (PKCS) #7 AND EXTENSIBLE MARKUP LANGUAGE DIGITAL SIGNATURE (XML DSIG)) AND THE COMMERCIAL PRODUCTS THAT IMPLEMENT THEM. THESE STANDARDS ARE USED TO CREATE THE TRANSACTION FORMAT THAT A DIGITAL SIGNATURE IS APPLIED. THE ISSUES CREATE THE FOLLOWING CONDITIONS: A. FORMS OR TRANSACTIONS THAT ARE DIGITALLY SIGNED BY COMMERCIAL PRODUCTS IMPLEMENTING EITHER STANDARD ARE NOT INTEROPERABLE. B. FORMS OR TRANSACTIONS THAT ARE DIGITALLY SIGNED WITH THE PKCS#7 STANDARD CANNOT BE EXCHANGED, VIEWED AND VERIFIED BY COMMERCIAL PRODUCTS THAT IMPLEMENT XML DSIG STANDARD ONLY, AND VICE VERSA. 4. AS A RESULT, DON CIO TASKED A SMALL GROUP OF SUBJECT MATTER EXPERTS FROM HEADQUARTERS COMPONENTS OF THE NAVY AND MARINE CORPS, WITH SUPPORT FROM THE APPROPRIATE ECHELON II COMMANDS, TO EXAMINE THESE ISSUES AND PROVIDE RECOMMENDED PLANS OF ACTION THAT ESTABLISH A DON-ENTERPRISE APPROACH. THESE PLANS WILL POTENTIALLY INCLUDE REQUIRED STANDARDS TO ACHIEVE INTEROPERABILITY AND ACQUISITION STRATEGIES. THIS TEAM IS EXPECTED TO REPORT THEIR RESULTS WITHIN THE NEXT 90 DAYS. AT THAT TIME, THE DON CIO WILL CONTINUE TO WORK WITH DASN (ACQUISITION) TO DEVELOP A WAY AHEAD IN THIS CRITICAL EFFORT. 5. THIS MESSAGE SHOULD NOT BE PERCEIVED AS A MANDATE TO HALT ANY EXISTING OR EMERGING DIGITAL SIGNATURE INITIATIVES. IT IS PROVIDED AS INFORMATION SO THAT EVERYONE IS AWARE OF THE CURRENT ISSUES AND THE EFFORTS UNDERWAY WITHIN THE DEPARTMENT TO ATTEMPT TO BRIDGE THE INTEROPERABILTY GAP. Very Respectfully, John R. Weiland Information Technology Specialist GS 2210 (APPSW) Code 38 Naval Medicine OnLine Naval Medical Information Mngmt Cntr Bldg 27 8901 Wisconsin Ave Bethesda, Md. 20889-5605 301-319-1159 JRWeiland@us.med.navy.mil http://navalmedicine.med.navy.mil/ "GIVE ME A PLACE TO STAND AND I WILL MOVE THE EARTH" A remark of Archimedes quoted by Pappus of Alexandria To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wss/members/leave_workgroup.php . To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wss/members/leave_workgroup.php .
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]