[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DSS-TC 7 February 2005 meeting minutes
DSS TC Conference Minutes Date: Monday, 7 February 2005, 12:00pm to 01:00pm Eastern Time Agenda: 1. Welcome by chair (Nick Pope) 2. Confirm conference call minute taker (Dimitri Andivahis) Dimitri Andivahis took minutes. 3. Roll Call Nick took the roll call. Pieter Kasselman, Betrusted Andreas Kuhne, Individual Trevor Perrin, Individual Nick Pope, Individual John Ross, Individual Glenn Benson, J.P. Morgan Chase & Co. Frederick Hirsch, Nokia Mobile Phones Dimitri Andivahis, Surety 4. Approval of agenda Agenda approved. 5. Approval of minutes of 24th Jan 05 Minutes of 24 January 2004 approved. 6. Outstanding Actions Action 05-10-01: Action on Trevor (TP) to follow up the discussion and input to Roadmap Document. Trevor distributed to the mailing list a Roadmap document based on a first pass over the Profile documents. Done. New ACTION - 05-02-07-01 [Trevor] Add section on Upcoming Profiles to Roadmap Document. New ACTION - 05-02-07-02 [All Profile Editors] Read Roadmap Document and provide comments. Action 05-10-03: Action on JCC and Ed (ES) to discuss in more detained plans on the list and start generating a inter-op and testing document that records what is intended to be done, specify any meta data agreed, recoded decisions; parameters used, test vectors, etc. Ongoing. Action 05-10-04: Following the successful ballot, action NP to update the text of the documents which are to be submitted to OASIS as committee drafts. Ongoing. Action 05-10-05: Action NP to update the web page and generate message for OASIS news, informing them that the documents have been update to committee drafts and to provide information about the proposed inter-op test. Ongoing. For Actions 05-10-04 and 05-10-05, Nick reported that the feedback from OASIS was they are reorganizing the public draft area so that all DSS documents for public access were placed in the same directory. Nick has requested of OASIS that documents be placed under subdirectories based on their day of issue as per existing conventions in OASIS. Action 05-10-07: Action Glen (GB) to kick off a discussion on the list about the binding issue for the Signature gateway profile Glen reported that after discussions with Nick, Burt Kaliski and others, they concluded that the HTTP binding was acceptable for the Signature Gateway Profile, but it shouldn't be constrained as the only one. The proposed course of action is to define the Signature Gateway Profile as an abstract profile, and include in the document a concrete Profile using the HTTP binding. This would allow defining other bindings at a later time. Done. New ACTION - 05-02-07-03 [Glenn] Submit Signature Gateway Profile document with abstract and concrete profiles. 7. Upcoming Profiles - Signature gateway profile (Glenn Benson) No further discussion. - Reports regarding any progress on other profiles Nick reported that the Judicial committee is meeting within the next two weeks to discuss requirements. Glenn reported on a comment he received from John Messing about including XKI in the Signature Gateway Profile and asked for clarification. New ACTION - 05-02-07-04 [All] Look up issue of including XKI as an option in the Signature Gateway Profile. 8. Issued Profiles - Timestamping (see discussion thread "ANSI X9.95 and timestamping profile") Dimitri recapped the discussion on the mailing list about supporting renewed nested timestamps. His proposal was to add support for it in the base timestamping profile. Juan Carlos (Cruellas, not present) had suggested in an email that if this were to be supported, the "inner" timestamp should be preferably placed within the <TstInfo> element of the "outer" timestamp. Nick remarked that changing the definition of <TstInfo> would require updating the Core document. Trevor said that this feature could better be left to a subprofile of the timestamping profile, since the operation of re-timestamping a document together with a previous timestamp can already be done on the client side. Dimitri said that nested timestamps as originally proposed would only affect the timestamping profile and would probably require adding 3 short paragraphs to the appropriate subsections of the document. Trevor said that adding 3 paragraphs to support a minor feature could open the way to a bloated timestamping profile, especially if other parties were to ask that other features from ISO or other documents be supported in the base timestamping profile. Dimitri said this was the only major feature of the other timestamping standards that was not yet directly supported in the base timestamping profile. He added that the vendor he represents was planning support for this feature in the near future, and expected that other vendors would do the same. Nick said that if this feature is easy to define and support, we could consider supporting it in the base documents. He also said that there are other ways (e.g. XAdES) to support the encapsulation of renewed timestamps. Dimitri said that in XAdES the document being timestamped is a digital signature, and the archive timestamps are stored within the digital signature, that is, within the document itself. In contrast, renewed nested timestamps maintain the timestamping history in one object (timestamp), possibly separate from the timestamped document, and they can be handled in the same manner by any application. Trevor asked for input from other people towards building a consensus on this issue. Nick asked what other work remains to be done for the timestamping profile. Trevor replied that some overview text needs to be added, and maybe some editorial cleanup. New ACTION - 05-02-07-05 [Dimitri] Draft text for nested renewal timestamps, specify documents affected, and continue discussion on the mailing list. 9. Interoperability testing Nick passed on report from Juan Carlos that work is progressing on the implementation, and it is hoped that testing will start by the end of next week. 10. Date of Next meeting: Currently planned for 21st February 2005 Nick proposed that the next meeting be moved to February 28, since the currently planned date is a holiday in the US. Nick will send e-mail to the mailing list to confirm. 11. Any other business Nick talked about the public comment submitted by Antonio Ruiz Martinez and the two emails (by Juan Carlos and by Antonio) that he forwarded to the mailing list. The issue is whether the DSS Core should support verifying multiple detached <ds:Signature>s within a single verify request. New ACTION - 05-02-07-06 [Nick, Juan Carlos, Trevor] Draft a response to submitted public comment about multiple signatures, and send to the mailing list. Close New and outstanding Actions ACTION - 05-10-03 [Juan Carlos, Ed] Discuss in more detained plans on the list and start generating a inter-op and testing document that records what is intended to be done, specify any meta data agreed, recoded decisions; parameters used, test vectors, etc. ACTION - 05-10-04 [Chairs] Following the successful ballot, action NP to update the text of the documents which are to be submitted to OASIS as committee drafts. ACTION - 05-10-05 [Chairs] Action NP to update the web page and generate message for OASIS news, informing them that the documents have been update to committee drafts and to provide information about the proposed inter-op test. ACTION - 05-02-07-01 [Trevor] Add section on upcoming Profiles to Roadmap Document. ACTION - 05-02-07-02 [All Profile Editors] Read Roadmap Document and provide comments. ACTION - 05-02-07-03 [Glenn] Submit Signature Gateway Profile document with abstract and concrete profiles. ACTION - 05-02-07-04 [All] Look up issue of including XKI as an option in the Signature Gateway Profile. ACTION - 05-02-07-05 [Dimitri] Draft text for nested renewal timestamps, specify documents affected, and continue discussion on the mailing list. ACTION - 05-02-07-06 [Nick, Juan Carlos, Trevor] Draft a response to submitted public comment about multiple signatures, and send to the mailing list. Submitted by: Dimitri Andivahis, Surety dimitri@surety.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]