OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: OASIS Call for Participation: OASIS Digital Signature Services eXtended (DSS-X) TC

To:  OASIS members & interested parties

   A new OASIS technical committee is being formed. The OASIS Digital Signature
Services eXtended (DSS-X) Technical Committee has been proposed by the members
of OASIS listed below. The proposal, below, meets the requirements of the OASIS
TC Process [a]. The TC name, statement of purpose, scope, list of deliverables,
audience, and language specified in the proposal will constitute the TC's
official charter. Submissions of technology for consideration by the TC, and the
beginning of technical discussions, may occur no sooner than the TC's first

   This TC will operate under our 2005 IPR Policy [b]. The eligibility
requirements for becoming a participant in the TC at the first meeting (see
details below) are that:

   (a) you must be an employee of an OASIS member organization or an individual
member of OASIS;
   (b) the OASIS member must sign the OASIS membership agreement [c];
   (c) you must notify the TC chair of your intent to participate at least 7
days prior to the first meeting, which members may do by using the "Join this
TC" button on the TC's public page at [d]; and
   (d) you must attend the first meeting of the TC, at the time and date fixed

Of course, participants also may join the TC at a later time. OASIS and the TC
welcomes all interested parties.

   Non-OASIS members who wish to participate may contact us about joining OASIS
[c]. In addition, the public may access the information resources maintained for
each TC: a mail list archive, document repository and public comments facility,
which will be linked from the TC's public home page at [d].

   Please feel free to forward this announcement to any other appropriate lists.
OASIS is an open standards organization; we encourage your feedback.



Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org 

[a] http://www.oasis-open.org/committees/process.php
[b] http://www.oasis-open.org/who/intellectualproperty.php
[c] See http://www.oasis-open.org/join/ [d]

OASIS Digital Signature Services eXtended (DSS-X) TC

(1)(a) TC NAME:
OASIS Digital Signature Services eXtended (DSS-X) Technical Committee

This Technical Committee has as its mandate production of new profiles of the
existing OASIS Digital Signature Services core protocol "Digital Signature
Service Core Protocols, Elements, and Bindings Version 1.0" and maintenance of
this specification and its existing profiles. If at a later date it becomes
clear that a new version of DSS is necessary then this may be produced by the

This further includes promotion of the standard and the creation of material
helping dissemination. In general terms, the TC has the goal to facilitate the
processing of digital signatures and time stamps in a client server environment.

The scope of activity for this TC will be within the following topics:

   a. Support of the server-based creation and verification of different types
of signatures, among which the most relevant ones are XML Sig and CMS, and
timestamps, both RFC 3161 and the XML time-stamps defined by the OASIS Digital
Signature Services (DSS) TC.
   b. Production of new profiles suitable for a number of environments and
purposes, which spread the usage of the specifications.
   c. Production of an analysis of inter-relationship among existing profiles in
a matrix where new profiles shall state their relationship to existing ones.
   d. Production of dissemination material for promoting usage and facilitating
tools development.
   e. Maintenance of the existing OASIS DSS standard and core protocol "Digital
Signature Service Core Protocols, Elements, and Bindings Version 1.0" and
related profiles produced by the former OASIS Digital Signature Services
Technical Committee, subject to appropriate access to underlying intellectual

Below follows the list of generic deliverables (estimated completion Q4 2008):
   a. New DSS Profiles

   b. Further Interoperability tests

   c. Cross Matrix for existing profiles showing their inter-relationship 

   d. WSDL definition for the DSS soap bindings 

   e. Maintenance of "Digital Signature Service Core Protocols, Elements,and
Bindings Version 1.0"

   f. Maintenance of existing Profiles

Below follows the list of candidate new profiles:
   a. Visible signatures

   b. Profile for ebXML

   c. Profile for individual reports on every signature verified
inmulti-signature documents 

   d. Profile for requesting signed verification responses 

   e. "baseline" profiles. Profiles for basic functions in support of generation
and verification of XML signatures, CMS signatures, XML time-stamps and RFC 3161

   f. Handling of signature & service policy 

   g. Profile for supporting centralized encryption and decryption services

This list must not be taken as a closed one: the TC may decide to specify any
other additional suitable profile during its lifetime. Additionally the TC may
decide to drop one of these candidates if there is not sufficient support.

(1)(e) Specification of the IPR Mode under which the TC will operate.
RF on Limited Terms.

(1)(f) The anticipated audience or users of the work.
Anticipated audience or users of the work include:
- Applications requiring digital signatures

- Companies requiring centralized electronic signature generation solutions in
place (e-Invoice in Europe for instance).

- Companies offering signing, time stamping and verification as a service (ASP

- Trusted Service Providers of more or less closed communities offering
centralized electronic signatures verification services.

- Public Administrations launching e-Identity initiatives.

- Public Administrations and private companies doing Government-Business
Electronic Commerce.

- Public Administrations agencies exchanging signed documents. Participants in
Exchange Processes, where signed documents are to be exchanged, archived and/or

(1)(g) The language in which the TC shall conduct business.

(2) Non-normative information regarding the startup of the TC:

(2)(a) Identification of similar or applicable work that is being done in other
OASIS TCs or by other organizations, why there is a need for another effort in
this area and how this proposed TC will be different, and what level of liaison
will be pursued with these other organizations.

The work of the DSS TC requires ongoing maintenance and enhancement to fully
exploit Digital Signatures within OASIS and the world at large. 

This central role of packaging and  profiling use of base standards:

W3C XML Signature
W3C XML Encryption
XAdES developed by ETSI Electronic Signatures and Infrastructures Technical
Committee - -ANSI X9F4 X9.95 (Trusted Time Stamps) Standard ISO/IEC 18014
developed by ISO/IEC JTC1/SC27
for convenient and consistent use by:

OASIS Access Control TC (XACML)

OASIS Rights Language TC (XrML) [closed] 

OASIS Security Services TC (SAML) 

OASIS Web Services Security TC (WSS) [completed] 

OASIS Election and Voter Services TC 

OASIS LegalXML eNotarization TC 

OASIS LegalXML Electronic Court filing 

OASIS ebXML Registry TC 

OASIS XML Common Biometric Format TC (XCBF) [completed] 

OASIS Biometric Identity Assurance Services Integration TC (BIAS) 

OASIS Enterprise Key Management Infrastructure TC (EKMI) 

OASIS Public Key Infrastructure Adoption TC (PKIA) 

W3C XML Key Management 

Universal Postal Union S43-2 (Electronic PostMark -EPM- interface standard)

A significant number of former DSS TC members have expressed their support,
ensuring critical mass to accomplish the goals set forth above.

Each of the entities listed above deal with standardization in areas closely
related to the proposed TC. It is the intention of this TC to keep informal
contacts with those whose work have an impact on its specifications. Formal
liaisons may also be established.

(2)(b) The date, time, and location of the first meeting, whether it will be
held in person or by phone, and who will sponsor this first meeting. The first
meeting of a TC shall occur no less than 30 days after the announcement of its
formation in the case of a telephone or other electronic meeting, and no less
than 45 days after the announcement of its formation in the case of a
face-to-face meeting.

The first meeting will be a conference call taking place on 23 July 2007 at noon
EDT, 6pm CET.
ARX will be the host.

(2)(c) The projected on-going meeting schedule for the year following the
formation of the TC, or until the projected date of the final deliverable,
whichever comes first, and who will be expected to sponsor these meetings.
Initially one conference call every two weeks. 

The group knows a number of companies that offer free conference calling
services.  It is the intention of the group to make use of these services for
the TC conference calls. This issue will be co-ordinated by the chairs of the
new TC. As a back-up alternative BEA is also willing to provide a call bridge.

(2)(d) The names, electronic mail addresses, and membership affiliations of at
least Minimum Membership who support this proposal and are committed to the
Charter and projected meeting schedule.

Ignacio Alamillo, CATCERT, ialamillo@catcert.net 

Juan Carlos Cruellas, CANET, cruellas@ac.upc.edu 

Stefan Drees, Individual, stefan@drees.name 

Julian Inza, Eurobits Technologies, julian.inza@eurobits.es 

Andreas Khuene, Individual, kuehne@klup.de 

Helbert Leithold, A-SIT, herbert.leitold@a-sit.at 

Tommy Lindbert, Dajeil, tommy.lindberg@gmail.com 

Hal Lockhart, BEA, hlockhar@bea.com 

Nick Pope, Thales, Nick.Pope@thales-esecurity.com 

Uri Resnitzky, Associate, uri@arx.com

(2)(e) The name of the Convener who must be an Eligible Person.
Juan Carlos Cruellas - CANET.

(2)(f) The name of the Member Section with which the TC intends to affiliate, if
 IDTrust proposed subject to confirmation.

(2)(g) Optionally, a list of contributions of existing technical work that the
proposers anticipate will be made to this TC.

(2)(h) Optionally, a draft Frequently Asked Questions (FAQ) document regarding
the planned scope of the TC, for posting on the TC's website.

(2)(i) Optionally, a proposed working title and acronym for the
specification(s) to be developed by the TC.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]