See also: IRC log
<trackbot> Date: 16 August 2011
<scribe> ScribeNick: fjh
Updated Suite B interoperability document - http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0039.html
Approve minutes, 9 August 2011
http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/att-0012/minutes-2011-08-09.html
Proposed RESOLUTION: Minutes from 9 August are approved.
RESOLUTION: Minutes from 9 August are approved.
LC-2543 PRFAlgorithmIdentifierType definition
http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0028.html
shouldn't the AlgorithmIdentifierType have a "type='anyURI' on the Algorithm attribute definition?
<scantor> I concur
RESOLUTION: add 'type="anyURI"' to Algorithm in AlgorithmIdentifierType
<scribe> ACTION: fjh to update xml encryption schema and specification with addition of type for Algorithm in AlgorithmIdentifierType [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action01]
<trackbot> Created ACTION-824 - Update xml encryption schema and specification with addition of type for Algorithm in AlgorithmIdentifierType [on Frederick Hirsch - due 2011-08-23].
LC-2544 xenc-schema-11.xsd does not import xmldsig11-schema.xsd but rather import xmldsigschema.xsd
http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0029.html
<scribe> ACTION: fjh to make formal response, import is for ds:Digest which is from original schema, hence no change needed [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action02]
<trackbot> Created ACTION-825 - Make formal response, import is for ds:Digest which is from original schema, hence no change needed [on Frederick Hirsch - due 2011-08-23].
LC-2542 Note re base64 encoding
http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0027.html
EncryptedType has an optional Encoding attribute. I believe the URI could be used here to specify the encoding used for the CipherData. See the last paragraph of 3.1, http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core-11/Overview.html#sec-EncryptedType
One might expect the encoding to appear as an optional attribute of CipherValue but I suspect this is an attempt to provide it for both CipherValue or CipherReference so that it is applicable to either.
At a minimum we probably should update the last paragraph of 3.1 to make Encoding a new paragraph and maybe also reference the Encoding attribute in the note.
scott: asks if two uses of base64 were there before
fjh: beiieve so
scott: if not shouldn't overload now, otherwise note appropriate
fjh: will double check, then close out issue
LC-2541 self-reference
http://lists.w3.org/Archives/Public/public-xmlsec/2011Aug/0026.html
fjh: maintenance problem to have Media Type registration in document
... proposal to have reference as text within document
http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core-11/Overview.html#sec-MediaType
hal: why not remove registration material from document
fjh: proposal to remove section 8, XML Encryption Media Type registration from this document, or restructure as note with reference
... we could put copy of registration into CVS as separate document and then reference as informational document
alternatively put reference in line
<scribe> ACTION: fjh to check with tlr re removing (and archiving) section 8 from xml encryption 1.1 [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action03]
<trackbot> Created ACTION-826 - Check with tlr re removing (and archiving) section 8 from xml encryption 1.1 [on Frederick Hirsch - due 2011-08-23].
ACTION-814?
<trackbot> ACTION-814 -- Magnus Nystrom to make namespace ("&xenc;") related edits in XML Encryption 1.1 -- due 2011-07-05 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/814
LC-2372 awaiting response from Juan Carlos
<scribe> ACTION: tlr to advise on how to close LC-2372 if no response received from submitter of comment for resolution [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action04]
<trackbot> Created ACTION-827 - Advise on how to close LC-2372 if no response received from submitter of comment for resolution [on Thomas Roessler - due 2011-08-23].
Awaiting actions from Pratik noted in agenda
ACTION-809?
<trackbot> ACTION-809 -- Pratik Datta to fix examples in signature 2.0 -- due 2011-06-21 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/809
ACTION-802?
<trackbot> ACTION-802 -- Pratik Datta to review comments from XML Core WG and formulate response, http://lists.w3.org/Archives/Public/public-xmlsec/2011Jun/0005.html -- due 2011-06-14 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/802
ACTION-717?
<trackbot> ACTION-717 -- Pratik Datta to document the Performance improvements with 2.0 -- due 2010-11-09 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/717
ACTION-238?
<trackbot> ACTION-238 -- Thomas Roessler to update the proposal associated with ACTION-222 and send to list. -- due 2011-09-30 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/actions/238
general discussion of possible additional security considerations for xml encryption
hal: should identify different types of attacks
<scribe> ACTION: hal to propose additional text for security considerations of xml encryption [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action05]
<trackbot> Created ACTION-828 - Propose additional text for security considerations of xml encryption [on Hal Lockhart - due 2011-08-23].
<scribe> ACTION: scantor to provide additional proposal text regarding xml encryption changes for pkcs1.5 [recorded in http://www.w3.org/2011/08/16-xmlsec-minutes.html#action06]
<trackbot> Created ACTION-829 - Provide additional proposal text regarding xml encryption changes for pkcs1.5 [on Scott Cantor - due 2011-08-23].
cynthia: HTML version of Suite B interoperability document looks good.