See also: IRC log
<trackbot> Date: 30 March 2010
<Cynthia> +Present Cynthia_Martin
<fjh> http://www.w3.org/2008/xmlsec/wiki/Interop
<fjh> Proposed RESOLUTION: Cancel the 6 April 2010 teleconference. Next teleconference 13 April 2010
<Cynthia> I agree with resolution
<fjh> ScribeNick: brich
RESOLUTION: Cancel the 6 April 2010 teleconference. Next teleconference 13 April 2010
<fjh> XML Security F2F at TPAC might get shifted to Thursday/Friday, 4-5 November 2010.
<Cynthia> The shift does not impact me
<fjh> http://www.w3.org/2010/03/09-xmlsec-minutes.html
<fjh> Proposed RESOLUTION: Minutes from 9 March 2010 approved.
RESOLUTION: Minutes from 9 March 2010 approved.
<fjh> Publication, 16 March 2010
<fjh> XML Encryption Syntax and Processing Version 1.1
<fjh> XML Security RELAX NG Schemas
<fjh> XML Security Generic Hybrid Ciphers.
<fjh> XML Security Algorithm Cross-Reference,
<fjh> See W3 news, http://www.w3.org/News/2010#entry-8749
<fjh> http://www.w3.org/2008/xmlsec/wiki/Interop
fjh: plan for RELAX-NG testing? suggestions?
<fjh> Editorial updates
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0084.html
fjh: Progress made, new proposal by RIM/Certicom, additional discussion continues
scantor: IETF presentation/discussion on ECC
<scantor> http://www.ietf.org/id/draft-mcgrew-fundamental-ecc-02.txt
<scantor> I figured somebody had
<fjh> ISSUE-195?
<trackbot> ISSUE-195 -- Camelli a cipher -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/195
<fjh> ISSUE-134?
<trackbot> ISSUE-134 -- Camellia algorithm for section of 5.2 Block Encryption Algorithm and 5.6 Symmetric Key Wrap -- CLOSED
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/134
fjh: discussion at the time was to NOT add a lot of algs in Encryption, but just have it in cross-reference
RESOLUTION: Camellia will NOT be added to XML Encryption 1.1
<fjh> reasons include need to limit what is in core spec and limit WG resources for interop
<fjh> extensibility enables algorithm to be used, listed in security algorithms cross-reference
<fjh> ACTION: fjh to respond regarding ISSUE-134 [recorded in http://www.w3.org/2010/03/30-xmlsec-minutes.html#action01]
<trackbot> Created ACTION-546 - Respond regarding ISSUE-134 [on Frederick Hirsch - due 2010-04-06].
<fjh> XML Encryption request
<fjh> http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0088.html
<fjh> send pointer to web site?
<fjh> wg agrees to ignore
<mjensen> Still working on reviews (was out of order for some weeks until now, still not at 100%...)
<fjh> please complete open actions
<fjh> http://www.w3.org/2008/xmlsec/track/actions/open
<mjensen> will send comments on mailing list within 2 weeks
fjh: Please review actions that you own
<fjh> Benchmarking, performance issues - Pratik working on these, ISSUE-86, ISSUE-122
<fjh> ISSUE-150?
<trackbot> ISSUE-150 -- Use of XML encryption type encoding in EXI -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/150
<tlr> yes
<fjh> ISSUE-150 addressed in 1.1 draft
<fjh> ISSUE-150: addressed in 1.1 draft
<trackbot> ISSUE-150 Use of XML encryption type encoding in EXI notes added
<tlr> ISSUE-150: addressed in latest 1.1 Working Draft
<trackbot> ISSUE-150 Use of XML encryption type encoding in EXI notes added
<fjh> ISSUE-150 closed
<trackbot> ISSUE-150 Use of XML encryption type encoding in EXI closed
<fjh> ISSUE-160?
<trackbot> ISSUE-160 -- Define URI for Canonical XML 2.0, add section to Signature 2.0 defining Canonical XML 2.0 -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/160
<fjh> do we have pointer to email for ISSUE-160?
<fjh> ISSUE-161?
<trackbot> ISSUE-161 -- Should the RetrievalMethod schema error be fixed in 2.0, see note at end of http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-RetrievalMethod -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/161
scantor: Nothing has changed, this error is still there, may be sufficient to give implementation guidance
<fjh> Proposed resolution is to (a) not change the schema but (b) give guidelines for correction and allow local use of corrected schema
<fjh> scantor notes no additional action required
scantor: since few implementations validates at runtime, it makes little difference what one does
<fjh> proposed RESOLUTION: Close ISSUE-161 with no action, and no schema change, allowing implementers to make use of the current warning note in the document as already provided
RESOLUTION: Close ISSUE-161 with no action, and no schema change, allowing implementers to make use of the current warning note in the document as already provided
<fjh> ACTION: pdatta to confirm that RetrievalMethod warning remains in 2.0 draft of signature [recorded in http://www.w3.org/2010/03/30-xmlsec-minutes.html#action02]
<trackbot> Created ACTION-547 - Confirm that RetrievalMethod warning remains in 2.0 draft of signature [on Pratik Datta - due 2010-04-06].
<fjh> ISSUE-161: RESOLUTION on 30 March: Close ISSUE-161 with no action, and no schema change, allowing implementers to make use of the current warning note in the document as already provided
<trackbot> ISSUE-161 Should the RetrievalMethod schema error be fixed in 2.0, see note at end of http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-RetrievalMethod notes added
<fjh> ISSUE-161 closed
<trackbot> ISSUE-161 Should the RetrievalMethod schema error be fixed in 2.0, see note at end of http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-RetrievalMethod closed
<fjh> ISSUE-164?
<trackbot> ISSUE-164 -- RNG schema needed for Generic Hybrid Ciphers -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/164
<fjh> ISSUE-164: RNG schema draft includes Generic Hybrid Ciphers
<trackbot> ISSUE-164 RNG schema needed for Generic Hybrid Ciphers notes added
<fjh> ISSUE-164 closed
<trackbot> ISSUE-164 RNG schema needed for Generic Hybrid Ciphers closed
<fjh> ISSUE-184?
<trackbot> ISSUE-184 -- Add reference to RNG Schema document -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/184
<fjh> ISSUE-184: done, http://www.w3.org/2008/xmlsec/Drafts/generic-hybrid-ciphers/Overview.html#sec-rngSchema
<trackbot> ISSUE-184 Add reference to RNG Schema document notes added
<fjh> ISSUE-184 closed
<trackbot> ISSUE-184 Add reference to RNG Schema document closed
<fjh> ISSUE-190?
<trackbot> ISSUE-190 -- Two different sha384 URIs -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/190
<fjh> ISSUE-191?
<trackbot> ISSUE-191 -- XML Signature 1.1 and XML Encryption 1.1 use different URIs for sha384. -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/191
<fjh> ISSUE-191: duplicate of ISSUE-190
<trackbot> ISSUE-191 XML Signature 1.1 and XML Encryption 1.1 use different URIs for sha384. notes added
<fjh> ISSUE-191 closed
<trackbot> ISSUE-191 XML Signature 1.1 and XML Encryption 1.1 use different URIs for sha384. closed
<fjh> ISSUE-192?
<trackbot> ISSUE-192 -- Namespaces for DerivedKey and pbkdf2 outside of xenc11 namespace -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/192
<tlr> fixed
<fjh> ISSUE-195?
<trackbot> ISSUE-195 -- Camelli a cipher -- OPEN
<trackbot> http://www.w3.org/2008/xmlsec/track/issues/195
<Cynthia> I will get back to you on the RNG schema also
<fjh> Scribe: Bruce_Rich