Minutes

["Nick Pope" <pope@secstan.com>]

I attach draft minutes from Mondays meeting.  Thanks Merlin for putting
these together.

(Merlin I removed the actions regarding profiles as these are two of several
profiles which we will be progressing later.)

Minutes
OASIS Digital Signature Services
Teleconference, 11 August 2003

Voting Members:
----

Dimitri Andivahis, Surety
Frederick Hirsch, Nokia Mobile Phones
Burt Kaliski, RSA Security
Pieter Kasselman, Baltimore
Andreas Kuehne, self
Hal Lockhart, BEA Systems
Tim Moses, Entrust
Anthony Nadalin, IBM
Nick Pope, self
John Ross, self
Krishna Yellepeddy, IBM

Observers:
----

Merlin Hughes, Baltimore
Ed Shallow, Universal Postal Union

Existing Actions:
----

Action 1. Update requirements document by August 1st (Trevor).
  Done + see New Action 12

Action 2. Produce initial schema for the sign/verify and timestamp
operations by 5th Aug.
  Done

Action 3. Post a discussion on compound operations to the list (Ed).
  Ongoing

Action 4. Produce analysis of the submitted materials on timestamp
token syntax. If possible, provide draft text to Trevor by 1st Aug
(Tim).
  Done

Action 5. Send references to timestamp token syntax to Tim.  (Juan-
Carlos)
  Done

Action 6. Send Overview text to Trevor by 1st Aug.  Mention bindings
issues (Frederick).
  Done

Action 7. Produce initial text on the WS-Security profile
(Frederick).
  Ongoing

Action 8. Update intellectual property page (Nick/Juan-Carlos).
Currently, the DSS page has two declarations on IPR.
  Ongoing

Action 10. Check with John Messing regarding an author for the notary
service profile (Nick).
  Done - John Messing will author it

Action 11. Check whether there is a need for a profile for the German
signature law (Andreas).
  Done - See Andreas response

New Actions:
----

Action 12. Ed & Trevor agreed on 2 sentences wrt compound
operations for reqs document, not there, has been removed. To be added 
again.

Action 13: Ed to send text to Trevor wrt Option element missing
from sign req/resp schema.

Action 14: Tim will propose text for core document capturing
timestamp syntax, semantically equiv to ietf 3161.

Action 15: Ed post links to Swedish ?Signform patent.

Action 16: Fred check on Volera patent statement.

Action 17: Nick to send text to list acknowledging that the XKMS
response meets our needs; then will forward to XKMS group.

Action 18: Nick to send proposed FAQ for OASIS to list, then
will forward to OASIS.

Action 19: Ed to submit text to list wrt combined operations,
ref 5.4 from agenda.

Minutes:
----

Quorum was achieved.

The minutes from the F2F were approved by consensus, subject to
a change wrt the terminology in section 4.6: It was agreed at
the F2F that the word 'policy' would not be overloaded to also
refer to profile. 'Policy' will only be used to refer to a
signature policy; 'profile' will be used for the different
documents.

The agenda was approved, with a discussion on a FAQ for the
Website added to AoB.

Nick Pope's thanks to Tim Moses & John Messing for note taking
thus far and proposal for a rota (mailing list 06 August 2003
11:28) were agreed upon.

4. Requirements document:
----

Two outstanding issues:

1. Compound operations text from Ed + Trevor.
   New Action 12.

2. Outstanding question on use of 'policy' vs 'profile'.
   Not a problem in the reqs, just the minutes. Closed.

Document not closed without editor. Intend to close requirements
document @ next meeting.

5. Core document
----

Consensus that we develop the core schema first, then write text
around the schema.

No issues with proposed outline document.

Agreement that Trevor + Juan Carlos take on sign
request/response schema work as input to ultimate spec.

Agreement that Juan Carlos' document be used as input for
validation schema.

Tim's analysis of Apvrille And Girier timestamp paper submitted
to list; their conclusion is that a wholly XML solution is
needed, which is good for us. DSS had come to most of the the
same conclusions. Their document raises no concerns, but people
should read Tim's notes.

Request/response schema for timestamp can be handled by Juan
Carlos & Trevor, building on existing schema.

Some profiles may have unique timestamp formats, but the core
will specify a generic timestamp syntax, based probably on IETF
3161. Need to collate info from IETF, ISO, XADeS, other related
documents. New Action 14.

6. Profiles
----

Plan of action: Do core spec first, aim to get it stable by the
end of the year. Start on the profiles soon, aim to get them
stable by the end of Q1 next year. Publish all documents
together by June next year.

Andreas proposed profile for German signature legislation; we
will work with the folks already working on capturing this
legislation in XML, to derive a DSS profile. Andreas will lead
this. 

Nick will work on a corporate seal profile. This should not add
new syntax that the core does not support, but instead will
refine the broad core to specific corporate seal usage:
Selecting options and adding descriptive text. 

7. Patents
----

Three patents at various stages may overlap wuith DSS; still
waiting for firm statements from some of the relevant companies.
New Action 16.

Ed believs there's another submitted patent from ?Signform in
Sweden; patent relates to signature timestamping area. New 
Action 15.

8. AOB
----

Couple of months ago, sent liaison to XKMS on how to identify
DSS key information. They responded that we should use a
UseKeyWith URI. This was an acceptable solution to the DSS
group. New Action 17.

Request from OASIS asking for FAQ for the website - what is the
need for the spec, who should be involved, what are its
benefits, how does it compare with other work, when will it be
complete. has to be in < 25th, nick ACTION: will send out a faq
to list, then to oasis. New Action 18.

Date of next meeting: 25th August. This is a holiday in the UK;
enough interest to proceed with it anyway. Nick will sort out
who hosts the call.

End.