See also: IRC log
<trackbot> Date: 08 January 2013
<scribe> ScribeNick: fjh
Happy New Year to all.
Approve minutes from 4 December 2012
RESOLUTION: Minutes from 4 December 2012 are approved.
Plan publication on 17 January, assuming transition request approved in time.
Call for Consensus completed (CfC) with support for all specs, no objections (see list)
Transition approval step with W3C Team desired to happen soon to enable publication 17 January.
fjh: have started process leading to formal transition approval request including review
... have entered official tracker entries for comments from Juraj so we can officially record and close those
... thomas also noticed an issue with the PAG page and is checking internally to fix that
... once we have these issues fixed I believe we can move forward with the official transition request process
... I have also updated the ReSpec tool to support PR, updating the boilerplate and enabling prEnd etc
... I have also updated the references and requested the git pull, that all should be in the next official ReSpec build (including PR changes)
... this is the message to Juraj listing the tracker entries and requesting confirmation -> http://lists.w3.org/Archives/Public/public-xmlsec/2013Jan/0014.html
PR drafts available, XML Encryption 1.1, XML Signature 1.1, XML Signature Properties
removed the at-risk 'Created', 'Expires' and 'ReplayProtect' items from the schema and external example file associated with the XML Signature Properties draft
removed 'OCSPResponse' from schema file associated with XML Signature 1.1 (bug fix)
CfC completed and received support on list: http://lists.w3.org/Archives/Public/public-xmlsec/2012Dec/0016.html
Publication drafts prepared but will need update for RELAX NG Schemas Note reference.
Please review status, abstract and introduction for Generic Hybrid Ciphers note - http://www.w3.org/2008/xmlsec/Drafts/generic-hybrid-ciphers/2013-01-NOTE/Overview.html
Please review updated Best Practices examples (formatting, bug fixes and moving links out of examples) - http://www.w3.org/2008/xmlsec/Drafts/best-practices/2013-01-Note/Overview.html
Plan publication on 17 January.
Approved with XML Encryption 1.1 PR CfC.
CfC to publish update, removing 'Created', 'Expires' and 'ReplayProtect' and 'OCSPResponse' from schema files and updating references received support
plan to publish update on 17 January
Please review and include xmlsec public list in comments: http://tools.ietf.org/html/draft-eastlake-additional-xmlsec-uris-05
Updated roadmap for 1.1 : http://www.w3.org/2008/xmlsec/wiki/Roadmap#The_following_steps_are_planned_for_XML_Security_1.1
decision discussion : update XML Security 2.0 drafts with recent changes to XML Security 1.1 drafts and publish as Notes, completing work?
fjh: we need to update the 2.0 specifications to align with recent changes in 1.1 and then it is likely that we will publish as W3C WG Notes
fjh: we have responded to this question - I believe they can do what they wish but need to get the References right
<trackbot> ACTION-883 -- Frederick Hirsch to review C14N 20 test cases document -- due 2012-04-10 -- OPEN
fjh: plan to defer unless we progress 2.0
<trackbot> Closed ACTION-883 Review C14N 20 test cases document.
<trackbot> ACTION-928 -- Frederick Hirsch to submit transition request to Proposed Recommendation for XML Encryption 1.1, XML Signature 1.1 and XML Signature Properties once Exclusion Period for XML Encryption 1.1 is completed, after 17 December and CfCs approved -- due 2012-12-11 -- OPEN
<scribe> in progress
<trackbot> ISSUE-236 -- Update all references in all Notes and Recs when publishing final REC? -- open
Plan to have references up to date during each publication as part of normal process so no need for explicit issue for this one
<trackbot> Closed ISSUE-236 Update all references in all Notes and Recs when publishing final REC?.
<trackbot> ISSUE-234 -- Reference SP800-56A later in publication process if the latest version is no longer a draft -- open
<trackbot> ISSUE-122 -- Explain peformance improvements and rationale, relationship to earlier work, document, benchmarks -- open
we should address this issue as part of deciding how to progress 2.0
fjh: we will have calls as needed, looks like we may be near completing 1.1 work
... once we have PR publication I believe not much will be required to transition to Recommendation unless there are AC review concerns
brich: thanks for your work on chairing and excellent leadership
fjh: thanks, and thanks for all your work as well