XML Security Working Group Teleconference

<trackbot> Date: 02 February 2010

<tlr> Scribe: Hal

<tlr> ScribeNick: hlockhar

Administrative

<tlr> http://www.w3.org/2010/01/26-xmlsec-minutes.html

RESOLUTION: minutes approved

editorial updates / publication status

<Cynthia> no objection

RESOLUTION: The WG agrees to defer publication of the Algorithms Cross Reference until XML Encryption 1.1 is published.

<tlr> http://www.w3.org/TR/2010/NOTE-xmldsig-simplify-20100204/

RESOLUTION: xmldsig-simplify superseded by Reqs 2.0, Sig 2.0, C14N 2.0

XML Encryption 1.1

<tlr> ISSUE-186?

<trackbot> ISSUE-186 -- What is the normative content of section 5.4.2? (PBKDF2) -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/issues/186

tlr: propose we incorporate referenced text in document
... will defer discussion til relevant partys are present

<tlr> http://lists.w3.org/Archives/Public/public-xmlsec/2010Jan/0142.html

pdatta: want to clarify EXI and non-EXI aspects in document

tlr: agree, can help
... some of other pieces are deliberately vague
... not clear whether we need single value for EXI
... processing seems to be the same

pdatta: use content and element a lot in Web Services

tlr: intended model is range of octets to be encrypted/decrypted
... processing is the same

pdatta: think it is needed to distinguish single vs. multiple elements

tlr: is it just an optimization?
... summary indicator makes it easier to determine what do do with decrypted text
... need to ask EXI people is this info is needed

<tlr> ACTION: pratik to propose explanation of use of content vs. element in implementations [recorded in http://www.w3.org/2010/02/02-xmlsec-minutes.html#action01]

<trackbot> Created ACTION-510 - Propose explanation of use of content vs. element in implementations [on Pratik Datta - due 2010-02-09].

<tlr> </a> <a>

esimon2: will look into issue and ask question on list

esimon: can content be an element

<tlr> issue-180?

<trackbot> ISSUE-180 -- Section 8 identifies Joseph Reagle as the contact for the XML Encryption media type. This needs to be updated, perhaps to a generic identity? -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/issues/180

tlr: will follow up to determine what to do

<tlr> ACTION: thomas to propose next steps on media type registration (ISSUE-180) [recorded in http://www.w3.org/2010/02/02-xmlsec-minutes.html#action02]

<trackbot> Created ACTION-511 - Propose next steps on media type registration (ISSUE-180) [on Thomas Roessler - due 2010-02-09].

RetrievalMethod

<tlr> 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

<tlr> issue-182?

<trackbot> ISSUE-182 -- Need Retrieval Method proposal for 2.0, KeyInfo correction or continuation of original material -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/issues/182

scantor: I think I have an action to make a proposal

<tlr> action-502?

<trackbot> ACTION-502 -- Scott Cantor to propose new model for RetrievalMethod in 2.0 -- due 2010-01-26 -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/actions/502

scantor: add new schema element

XML Signature 2.0

<tlr> ISSUE-183?

<trackbot> ISSUE-183 -- Constrain 2.0 SignedInfo canonicalization choice for 2.0 model? -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/issues/183

<esimon2> ACTION: Ed to look at XML Encryption content vs. element options when content equals element [recorded in http://www.w3.org/2010/02/02-xmlsec-minutes.html#action03]

<trackbot> Created ACTION-512 - Look at XML Encryption content vs. element options when content equals element [on Ed Simon - due 2010-02-09].

<tlr> issue-183?

<trackbot> ISSUE-183 -- Constrain 2.0 SignedInfo canonicalization choice for 2.0 model? -- OPEN

<trackbot> http://www.w3.org/2008/xmlsec/track/issues/183

tlr: will skip Juan Carlos issue as he is not present

<esimon2> * gone for 5 minutes

tlr: members should recruit reviewers of the new specs

<tlr> action-351 closed

<trackbot> ACTION-351 Summarize design rationale for xsd:any in note in spec closed

<tlr> action-371 closed

<trackbot> ACTION-371 Add id and position handling in step in draft closed

<tlr> action-409 closed

<trackbot> ACTION-409 Revisit text() with regards to XPath profile closed

<tlr> action-473 closed

<trackbot> ACTION-473 Update xml enc processing proposal with more detail and addressing wg concerns closed

<tlr> action-488 closed

<trackbot> ACTION-488 Rephrase ECC note as appropriate, if needed closed

<tlr> action-496 closed

<trackbot> ACTION-496 Update 2.0 draft based on scott's proposal for 2.0 mode references closed

<tlr> action-498 closed

<trackbot> ACTION-498 Check namespace document and signature algorithms check closed

<tlr> action-500 closed

<trackbot> ACTION-500 Update namespace section in Encryption 1.1 closed

<tlr> action-506 closed

<trackbot> ACTION-506 Update sotd and note in document with change for ISSUE-179 closed

<tlr> action-509 closed

<trackbot> ACTION-509 Help with updating XML Signature 2.0 bibliography closed

<tlr> hal, minutes are here: http://www.w3.org/2010/02/02-xmlsec-minutes.html

<jcruella> Sorry for arriving late....

<jcruella> calling in two minutes