Correct
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Rimas
Rekasius/Chicago/
IBM@IBMUS To
Sent by: basicB2B@googlegroups.com
basicB2B@googlegr cc
oups.com
Subject
Re: Strength of R5001 (Use of
05/25/2005 05:19 RSA1.5)
PM
Please respond to
basicB2B
OK, so just to be painfully clear, the proposal is to change
R5001 When used for Key Transport, any xenc:EncryptionMethod/@Algorithm
attribute in an ENCRYPTED_KEY MUST have a value of
"http://www.w3.org/2001/04/xmlenc#rsa-1_5".
to
R5001 When used for Key Transport, any xenc:EncryptionMethod/@Algorithm
attribute in an ENCRYPTED_KEY SHOULD have a value of
"http://www.w3.org/2001/04/xmlenc#rsa-1_5".
Unless I hear any objections, I will proceed to make this change in a new
version of the profile that I am working on.
Regards,
Rimas V. Rekasius
e-business Industry Standards Architect
1-312-245-6775 (voice/FAX)
1-773-934-2705 (cell phone)
Anthony Nadalin/Austin/IBM@IBMUS
To
05/13/2005 11:19 AM basicB2B@googlegroups.com
cc
Please respond to Subject
basicB2B Re: Strength of R5001 (Use
of RSA1.5)
There are 2 allowed values, if each site chooses the same algorithm (OEAP
or RSA1.5) no problem (only way to do this today is out of band), so this
should be softened to "SHOULD" and http://www.w3.org/2001/04/xmlenc#rsa-1_5
should be made the default value
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Inactive hide details for Rimas Rekasius/Chicago/IBM@IBMUSRimas
Rekasius/Chicago/IBM@IBMUS
Rimas Rekasius/Chicago/IBM@IBMUS
05/12/2005 03:25 PM
To
Please respond to
basicB2B basicB2B@googlegroups.com
cc
Subject
Strength of R5001 (Use of
RSA1.5)
The current version of the Basic B2B Profile has the following
requirement in it constraining the choice of encryption algorithm:
R5001 When used for Key Transport, any xenc:EncryptionMethod/@Algorithm
attribute in an ENCRYPTED_KEY MUST have a value of
"http://www.w3.org/2001/04/xmlenc#rsa-1_5".
Question: should this be softened to a SHOULD, or is MUST the right
thing to do for the sake of interoperability?
Thanks,
Rimas