Sean Mullan		Sun Microsystems, Inc.
	Anthony Nadalin		IBM

 

Apache Software Foundation		Betrusted Inc.		Entrust Technologies Inc.
Fujitsu Limited		Hewlett-Packard		IAIK Graz University of Technology
IBM		Motorola		NEC Corporation
Sun Microsystems, Inc.

Expert Group Private Page

JSR Community Update Page

 

Updates to the Original Java Specification Request (JSR)

The following information has been updated from the original JSR.

2.11 Please describe the anticipated schedule for the development of this specification.

Expert Group JCP Schedule (all dates are tentative)

• May 7: release rev 0.3
• June 3: release rev 0.4
• July 1: release rev 0.5 (if necessary)
• July 29: release community draft
• September: release public draft
• November: release proposed final draft

Original Java Specification Request (JSR)

Identification | Request | Contributions

Original Summary: This JSR is to define a standard set of APIs for XML digital signatures services. The XML Digital Signature specification is defined by the W3C. This proposal is to define and incorporate the high level implementation independent Java APIs.

Section 1. Identification

Submitting Member: IBM

Name of Contact Person: Anthony Nadalin or Maxine Erlund

E-Mail Address: Anthony Nadalin - drsecure@us.ibm.com, Maxine Erlund - maxine.erlund@eng.sun.com

Telephone Number: Anthony Nadalin - +1 512 436 9568, Maxine Erlund - +1 408 517 5486

Fax Number: Anthony Nadalin - +1 512 838 3823, Maxine Erlund - +1 408 863 3155

Specification Lead: Anthony Nadalin and Sean Mullan

E-Mail Address: Anthony Nadalin - drsecure@us.ibm.com, Sean Mullan - sean.mullan@ireland.sun.com

Telephone Number: Anthony Nadalin - +1 512 436 9568, Sean Mullan - +353 1819 9176

Fax Number: Anthony Nadalin - +1 512 436 9568

Initial Expert Group Membership:
(Please provide company or organization names. Note that expert group members must have signed the JSPA.)

IBM - Anthony Nadalin

Sun - Sean Mullan

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to define a standard set of APIs for XML digital signatures services. The XML Digital Signature specification is defined by the W3C. XML Signatures can be applied to any digital content (data object), including XML. An XML Signature may be applied to the content of one or more resources. Enveloped or enveloping signatures are over data within the same XML document as the signature; detached signatures are over data external to the signature element. More specifically, the XML Digital Signature specification defines an XML signature element type and an XML signature application; conformance requirements for each are specified by way of schema definitions and prose respectively. The XML Digital Signature specification also includes other useful types that identify methods for referencing collections of resources, algorithms, and keying and management information.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

JDK 2 SDK, Standard Edition, V 1.3 and above

2.3 What need of the Java community will be addressed by the proposed specification?

Today there is no standard of APIs for XML digital signatures services. This JSR provides a Java API to the XML Digital Signature services.

2.4 Why isn't this need met by existing specifications?

There is no existing specification in JDK 2 SDK for accessing XML Digital Signature via a standard set of APIs.

2.5 Please give a short description of the underlying technology or technologies:

The XML Digital Signature specifies XML syntax and processing rules for creating and representing digital signatures. The XML Signature is a method of associating a key with referenced data; it does not normatively specify how keys are associated with persons or institutions, nor the meaning of the data being referenced and signed. Consequently, while the XML Digital Signature specification is an important component of secure XML applications, it itself is not sufficient to address all application security/trust concerns, particularly with respect to using signed XML (or other data formats) as a basis of human-to-human communication and agreement. Such an application must specify additional key, algorithm, processing and rendering requirements and developers must give consideration to their application threat models.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

javax.security.xml.dsig

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

NO

2.8 Are there any security issues that cannot be addressed by the current security model?

NO

2.9 Are there any internationalization or localization issues?

NO

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

NO

2.11 Please describe the anticipated schedule for the development of this specification.

NOTE that this information has been updated from the original JSR. Please go here to view the updated information.

I'd like to propose a 9-12 week schedule, with 2-3 internal review cycles within that timeframe:

6/1 Release API docs and preliminary spec.
9/25 Comments on first draft due
10/16 2nd draft released
10/30 Comments on 2nd draft due
11/13 3rd draft released (if necessary)
11/27 Comments on 3rd draft due (if necessary)
12/04 Community draft released

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

W3C/IETF XML Signature specification http://www.w3.org/2000/09/xmldsig#

JSR 55 Certification Path

3.2 Explanation of how these items might be used as a starting point for the work.

These documents describe the XML Digital signature standard developed by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF)