[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New proposed charter and disposition of comments.
Dear all, As agreed in our conf call with OASIS staff and DSSX TC supporters, I have generated: 1. A new version of the charter that takes into consideration the comments by Clemens Orthacker , William Cox and the one that Jamie Clark did on the call. 2. A text file including disposition of comments for all of them. I attach them to this email. Could I kindly ask you to take a look to them so that we may agree in their definitive version on next Monday call? I will circulate the agenda and dialing details in few minutes. Regards Juan Carlos.
(1)CHARTER (1)(a) TC NAME: OASIS Digital Signature Services eXtended (DSS-X) Technical Committee (1)(b) STATEMENT OF PURPOSE 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 TC. 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. (1)(c) SCOPE OF THE WORK 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 property. (1)(d) LIST OF DELIVERABLES AND COMPLETION DATES. 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 [eb]XML c. Profile for individual reports on every signature verified in multi-signature documents d. Profile for requesting signed verification responses e. "baseline" profiles 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: TC members may decide to specify any other additional suitable profile during TC's lifetime (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 provider). - 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 retrieved. (1)(g) The language in which the TC shall conduct business. English (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 (WSSTC) [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 July 9th noon Eastern, 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 any. 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.
The DSSX TC supporters have agreed in the following dispositions of comments for the DSSX charter proposal circulated May 29th 2007. 1. Comment by Clemens Orthacker. Reference: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/email/archives/200706/msg00000.html Disposition: The supporters have decided to accept the request. The following text has been added to the charter in (1)(d) LIST OF DELIVERABLE AND COMPLETION DATES. "g. Profile for supporting centralized encryption and decryption services" 2. Comment (1) by William Cox. Reference: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/email/archives/200706/msg00005.html Disposition: The supporters have acknowledged the need for further explanations of the term '"baseline" profiles '. The following modification has been produced in (1)(d): Item: ' e. "baseline" profiles ' has been substituted by: 'e. "baseline" profiles. They will be profiles for easy generation and validation of only a specific type of signature (i.e. XML, CMS) or timestamp (i.e. XML based, CMS based).' 3. Comment (2) by William Cox. Reference: as above. Disposition: The supportes have agreed to include in (2)(b) the indication that the first meeting will be a conference call. 4. Comment (3) by William Cox. Reference: as above. Disposition: The supporters have agreed to include the text proposal by Willliam Cox in (2)(a). Below follows the final version of (2)(a): "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 (WSSTC) [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." 5. Comment by Jamie Clark on the conference call with convenor and supporters. Comment: Indicate that the list of envisaged profiles in (1)(d) is not closed. Disposition: The supporters have agreed to include text that makes it clear that the list is an open one. The following text has been inserted within (1)(d): "This list must not be taken as a closed one: TC members may decide to specify any other additional suitable profile during TC's lifetime"
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]