- From: Joseph Reagle <reagle@w3.org>
- Date: Tue, 28 May 2002 13:47:26 -0400
- To: merlin <merlin@baltimore.ie>
- Cc: xml-encryption@w3.org
On Friday 24 May 2002 06:11 pm, merlin wrote:
> >I presume not. (I've argued it shouldn't.) Don, do you mind if I make it
> >required?
>
> FWIW, I agree with you. I dislike the fixed SHA-1 for MGF but
> that has been declared final.
On that note...
The RSAES-OAEP-ENCRYPT, as specified in RFC 2437 [ PKCS1], algorithm takes
two /-optional-/ parameters: a /+MANDATORY+/ message digest function and an
/+OPTIONAL+/ octet string OAEPparams.
> >> (Aside: The Schema Definition quoted in 5.4.2 is no longer current.)
> >
> >In what way?
>
> §5.4.2: Schema Definition:
> ...
> <element name='OAEPparams' minOccurs='0' type='base64Binary'/>
> <element ref='ds:DigestMethod' minOccurs='0'/>
> ...
>
> §3.2 Schema Definition:
> <element name='OAEPparams' minOccurs='0' type='base64Binary'/>
> <any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
The definition in 5.4.2 is for demonstration... I couldn't figure out a
better way to define these schema, but normally, in general, the definition
3.2 applies, but if you use a specific algorithm [1], then the definition
in 5.4.2 is the one you should use. Of course, schema doesn't permit one to
specify this sort of thing... I can get rid of the elipses and use a
comment:
<!-- use these element types as children of EncryptionMethod
when used with RSA-OAEP -->
[1] http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p
--
Joseph Reagle Jr. http://www.w3.org/People/Reagle/
W3C Policy Analyst mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair http://www.w3.org/Signature/
W3C XML Encryption Chair http://www.w3.org/Encryption/2001/
Received on Tuesday, 28 May 2002 13:47:30 UTC