Eastlake: draft a more complete algorithm section include
algorithm profiles and IV checksum cipher text values.
Maruyama: update the Encryption/Signature Transform. Update
Security Considerations, add a scenario or two (and maybe borrow
"enc:DataRef" instead of using "EncryptedReference").
Maruyama: an email exploring the question of our processing
model and the relationship between DOM, Infoset, and serialization
and the issue related to using current parsers to get a pointer to
a byte where element starting "<" is.
Reagle: "Review the use of a URI versus an ID
and NameKey in an EncryptedKey element?"
Reagle: Inform Don Davis of new requirements document
when complete and that issue 6.2 was dropped.
Now that it's published, please have another look and let me
know if I dropped anything on the floor or didn't get it
Schema reuse: Reagle
investigated, looks like we can not use more sophisticated
ds:KeyInfo reuse, but instead use the ds:KeyInfo ANY and create
"orphaned" elements (KeyRetrievalMethod and EncryptedKey) in the
Reagle: Can we move away from KeyRetrievalMethod, and just use
dsig's RetrievalMethod with a particular type? (This was the intent
Reagle: Any thoughts on this section? I definitely need
Reagle: Next call on May 14. Reagle will be in Asia April
25 - May 8 for WWW10/W3C-AC and Europe from May 22 -May 29th for
XML 2001 Europe. So productivity and ability to convene
teleconferences will be low but discussion can happen on list and I
can still have a bridge made available for discussion.
Reagle: Also, reminder to ourselves to think about FTF in