On Thu, Aug 19, 2010 at 11:42:44AM +0200, Andreas.Eversberg wrote:
> hi sebastien,
>
> thanx for you advice. i will have job names like SIM_JOB_READ,
> SIM_JOB_UPDATE, SIM_JOB_GSMALGO,... i am a bit unsure about the path array. i
> always thought that each EF has a unique ID. the DF where it is located, can
> be determined by the first byte of the EF ID. but if it is possible to have a
> sim with multiple DFgsm, then a path is required of course.
I think it isn't good to just think of a normal SIM, but keep it as flexible
with regard to smartcards compliant to 7816-4. Adding a path will not really
make things terribly more complex, so I'd also agree with Sebastien to include
tha path and be more flexible as a result.
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)