[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - DSS TC Conference Call modified
DSS TC Conference Call has been modified by Robert Zuccherato (robert.zuccherato@entrust.com). Event description: The dial in numbers are: +1 613 688 3270 Passcode: 123 626# Agenda: Agenda for Digital Signature Services Technical Committee Meeting Date: Monday, May 5, 2003, 12:00-1:00 pm Eastern time. Dial-In Information: +1 613 688 3270 Passcode: 123 626# 1. Welcome by chair. -Approve agenda. 2. Roll call. 3. Approve minutes of previous meeting. -Minutes of DSS TC Meeting April 7, 2003 available at http://www.oasis-open.org/apps/org/workgroup/dss/download.php/1462/meeting%2040703%20minutes.txt 4. Linking-Based Timestamping Protocols (Continued from last meeting) -At the last meeting Dimitri described the linking timestamp protocols. (See minutes.) The suggestion was made that in order to fully specify how to use these protocols in a manner that is truly interoperable we would need to specify the server-to-server protocol to transfer the verification data. This sounds like a lot of work. Do we want to take on that work at this time or do we want to leave it for a future version? 5. XKMS Last Call Draft -The XKMS WG has requested any comments we may have on their Last Call Working Draft. (See http://lists.oasis-open.org/archives/dss/200304/msg00078.html.) After discussion on the list, I posted a suggested response that indicated it might be nice to query a DSS client's key and receive information on the DSS server to which the client has delegated signatures. (See http://lists.oasis-open.org/archives/dss/200305/msg00004.html.) Are we okay with this response? 6. Identifying Requester -There has been quite a bit of discussion on methods for the DSS server to identify the signature requester. In his latest requirements draft Trevor suggested that we leave the question entirely to higher-level standards (See http://lists.oasis-open.org/archives/dss/200304/msg00123.html.) I suggested a compromise position in which we specify an extensible list and leave it up to higher-level standards how to deal with them. (See http://lists.oasis-open.org/archives/dss/200305/msg00005.html.) Can we come to agreement on something here? 7. Next Steps -Assuming we come to agreement on agenda items 4 and 5, I believe we ' will have come to consensus (for the time being) on our Requirements draft. I would then like to see us start work on developing the required protocols. We have had a number of submissions of particular protocols that people are using or have developed. Do any of them make sense as a starting point given our requirements? Should we just start from scratch and take the features of each that seem attractive? Does it make sense to have a face-to-face to start this work? 8. Any other business. 9. Close. Date: Monday, 05 May 2003 Time: 12:00pm - 01:00pm Eastern Time This event is one in a list of recurring events. Other upcoming dates include: Monday, 24 February 2003, 12:00pm to 01:00pm Eastern Time Monday, 10 March 2003, 12:00pm to 01:00pm Eastern Time Monday, 24 March 2003, 12:00pm to 01:00pm Eastern Time Monday, 07 April 2003, 12:00pm to 01:00pm Eastern Time Monday, 21 April 2003, 12:00pm to 01:00pm Eastern Time Monday, 19 May 2003, 12:00pm to 01:00pm Eastern Time View event details: http://www.oasis-open.org/apps/org/workgroup/dss/event.php?event_id=454 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]