Find JSRs
Submit this Search


Ad Banner
 
 
 
 

JSR177 Changelog

JSR 177 Maintenance Release

This document is the Change Log for the JCP Maintenance Release of the Security and Trust Services API for J2METM Specification (JSR 177). The goal of this maintenance release is to allow null implementation.

Summary of Proposed Changes


The table below contains a summary of the proposed changes.



Status
Proposed Change
Motivation




1) Allow null implementation of APDUand JCRMI optional packages
In the SATSA Specification version 1.0, it is written that the APDU and JCRMI optional packages define interfaces for communication of J2ME applications with applications on a smart card. But specification does not clarify situations when smart card reader is not present at all. The main point of proposed change is to process properly the situations when device doesn't have a smart card reader . It allows to develop safe and flexible J2ME applications.




2) Add clarifications for PIN Entry mechanism
PIN Id and PIN type terms are used for PIN Entry mechanism in the SATSA Specification version 1.0.
The values of these terms and their mapping to external specifications (e.g. PKCS#15 ) should be clarified.




3) Add clarifications for SIM, USIM, UICC related to APDU structure used by the APDUConnection interface
These terms are used all together in the SATSA Specification version 1.0. The definitions of these terms are not clear . It should be clarified.




4) The restriction on SAT connection in the SATSA specification needs to be corrected in Appendix B such that it allows access from MIDlets in the handset manufacturer's domain. The security policy defined in Appendix B is a recommendation and is not a "must have"
requirement.
Alignment with MSA specification which requires access to SAT from handset manufacturer's domain.




5) Add clarification to remove any ambiguity regarding affecting of SAT support to APDU connections.
The SATSA specification version 1.0 doesn't specify how SAT support affects APDU connections.




6) Clarify in the specification for APDU and
JCRMI connections that any READ/WRITE/READ_WRITE modes can be used to communicate with SE.
In the SATSA Specification version 1.0 for javax.microedition.io.Connector class, it is written that "The validity of these flag settings is protocol dependent". The protocols, APDU and JCRMI, however, do not specify how these flags might be used when opening a connection to the SE.




7) Fix typos and broken links.
There are some typos in the SATSA Specification
version 1.0 which should be fixed.


Feedback

We are interested in improving our specification and welcome your comments and suggestions. You can e-mail
your comments to: satsa-comments@sun.com