[jsr360-experts] Re: [jsr360-observers] Re: Updated JSR 360 Draft Specification
- From: Lampart Thomas <
- To: "
- Subject: [jsr360-experts] Re: [jsr360-observers] Re: Updated JSR 360 Draft Specification
- Date: Tue, 2 Jul 2013 16:18:58 +0200
- Accept-language: de-DE, en-US
- Acceptlanguage: de-DE, en-US
From: roger riggs
Sent: Dienstag, 2. Juli 2013 15:51
Subject: [jsr360-observers] [jsr360-experts] Re: Updated JSR 360 Draft
Sorry for the delay.
On 6/27/2013 11:56 AM, Lampart Thomas wrote:
Hi Roger, Michael, experts,
Thanks for giving us this update with a bunch of new features.
I do have some comments:
-I do like the extended TLS support
-SecureServerConnection, what is the ClientAuth “want” parameter good for ?
In my understanding a server either does client authentication or not.
There is a provision in the Java SE api for the client to request client
Oh. Interesting. However this works.
The SSL/TLS protocol does leave it to the server to require client
and that may be sufficient.
So you agree to my point about the “want” parameter ? What would be the
difference in processing between setting “ClientAuth” to “need” or to “want”
? I don’t think that a client can refuse client authentication when the
server requests it, can it ?
Is there any use case where the client would refuse to
talk to a server that did not authenticate the client?
I can’t imagine such a case.
-Why squeezing the TLS into the DatagramConnection and not have
Good point, it seemed initially like an easy extension but several questions
have been raised about it and we'll reexamine creating a separate interface.
-AccessPoint: as far as I know in CDMA there is only a Mobile IP (or Simply
IP) configuration profile id to select, when opening a packet service. No
ok, can you refer me to a CDMA spec on that?
I will try to dig up some specs.
-AccessPoint: I think for WLAN there is only a password, no DNS.
Any TCP/IP stack needs a DNS server; where does it come from for a WAN?
You are right. We should not assume that we have DHCP. This might not be
available in all setups. But then we probably need even more parameters for
the WAN, like IP address, netmask and default gateway.
We have had questions about why an explicit DNS server is required in any of
For CSD it was a carry over from IMP-NG.
What is the use case for needing application control over the dns-server.
Can we simplify and leave it to the platform in all cases (DHCP or host
We could. It depends on how far you want to go in specifying possible
parameters for different interfaces. For 2G/3G we definitely have the use
case where a user wants to override the DNS server given by the network.
That’s the reason why we have DNS here.
From: roger riggs
Sent: Dienstag, 25. Juni 2013 15:45
Subject: [jsr360-observers] [jsr360-experts] Updated JSR 360 Draft
The updated SpecLead Draft of JSR 360
available from the
JSR 360 downloads<https://java.net/projects/jsr360/downloads
> on java.net.
The update is based on the EDR draft, Expert Group comments and input from
the RI developers.
This draft includes extensions and resolutions for the following:
* CLDC Full vs Compact APIs to support smaller devices with fewer new APIs
* SecureServerConnection (new)
* ModemConnection (new)
* NetworkUtilities (new)
* Access Point improvements
* Support for TLS1.2 / DTLS (revised)
Please review and comment, Roger and Michael