W3C home > Mailing lists > Public > xml-encryption@w3.org > July 2001

AgreementMethod

From: merlin <merlin@baltimore.ie>
Date: Sat, 28 Jul 2001 14:18:10 +0100
To: xml-encryption@w3.org
Message-Id: <20010728131810.DF55043BCB@yog-sothoth.ie.baltimore.com>

Hi,

It appears that our definition of AgreementMethod is somewhat
over-restrictive. It could (?) be readily used in a MAC-based signature,
but this is not provided for in the text or definition.

I'd suggest generalizing some of the text from EncryptionAlg to TargetAlg
(with text stating that this may be an EncryptionAlg, a MacAlg, etc.)

We'd also need text to state the size of key to produce for a HMAC
algorithm; maybe, unless otherwise stated, equal to the (possibly
truncated) size of the HMAC output; e.g., 160 bits for HMAC-SHA1, or 80
bits for 80-bit truncated HMAC-SHA1.

The text also states that this will be the child of an EncryptedData
or EncryptedKey; this may not be true, as it could be the target of
a RetrievalMethod or (in the case above) the child of a Signature.
I'd suggest changing "a child of" to "the keying information for" or
something similarly vague.

Merlin


-----------------------------------------------------------------------------
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 Saturday, 28 July 2001 09:18:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:00 UTC