[jsr351-experts] Re: [identity-api-spec users] Re: No longer on Daylight Savings Time
- From: Werner Keil <werner.keil@...>
- To: jsr351-experts@...
- Subject: [jsr351-experts] Re: [identity-api-spec users] Re: No longer on Daylight Savings Time
- Date: Tue, 5 Nov 2013 21:26:01 +0100
Sorry for the bad connection, I might give it a try next time with the
bluetooth headset again. Speaker (on Google "voice" option of the Hangout)
was OK and I could hear the second half much better than Skype, but the
built-in micro was either not liked by Google or I have to tweak or replace
it with an external one)
As mentioned, certain vendors like Xing have a much more fine grained
security model, while others like Facebook may be a little less concerned
I don't know to what extent we'd like the spec to "duplicate" what the more
privacy cautious providers do?
Maybe some sort of "profile" (the closest analogy could be what browsers
including Internet Explorer used to do, having a "More secure zone" as
opposed to a less secure one)
I currently write about Agorava for that book, and given the recent
security and privacy issues all the way to social networks beeing hacked
(we certainly can't do anything about that[?])
The thing Todd I believe said about inventory of equipment sounds very
useful towards the "Internet of Things". We should keep that in mind. While
not Identity-related, support for DTLS was discussed by the JSR 360 EG and
recommended by some EG members, but for the first version of 360 it won't
be mandatory or part of the spec.
DTLS is designed to prevent eavesdropping, tampering, or message forgery.
The latter actually sounds like some sort of "identity" between sender and
receiver must be established.
This GitHub document explains a few interesting aspects of DTLS especially
with options of either Anonymity or full Identity:
As there is a JCP EC call next week, I'm good with the next call in 2
weeks. Hopefully the microphone (or if all else fails I'd check for a 3G
SIM for my Android Tablet if the Wifi is too bad) issue could be solved.
P.s.; at the end of that week on Nov 22, I plan to participate in an
Eclipse Hackathon in Hamburg (http://wiki.eclipse.org/Hackathon_Hamburg_2013
hosted by the local *Chaos Computer Club* chapter. They may not be focussed
on Java as much, but trends and legal aspects especially in Germany and
Europe are high on their agenda, so maybe I could gather some contacts for
input or what they might like to see in this JSR.
On Tue, Nov 5, 2013 at 8:19 PM, Werner Keil <werner.keil@...> wrote:
> Sorry the Wifi connection or at least Skype performance is such a
> catastrophy, it won't even recognize the correct codes or pin in 99% of
> Will try over time but it may not be on long. 8pm CET is when the "rush
> hour" in the hotel starts, and it stays that bad till around 11 pm or
> On Tue, Nov 5, 2013 at 5:56 PM, Ron Monzillo <ron.monzillo@...>wrote:
>> On 11/5/13 11:48 AM, Aven, Todd S. wrote:
>>> One simple solution: UTC/GMT
>>> thanks Todd, and (assuming I have done the conversion to GMT correctly),
>> this meeting will be at 7:00 PM GMT
>> -----Original Message-----
>>> From: Ron Monzillo [mailto:ron.monzillo@...]
>>> Sent: Tuesday, November 05, 2013 11:45 AM
>>> To: jsr351-experts@...
>>> Subject: [jsr351-experts] No longer on Daylight Savings Time
>>> Here in the US, we gained an hour due to the change from Daylight
>>> Savings time.
>>> Thus the times in the meeting announcement (i.e., 11am pacific/2pm
>>> eastern/8pm CET)
>>> are actually 1 hour earlier (wrt to timezones that have not pushed back
>>> their clocks)
>>> than they were the week before. Sorry if I am making this more confusing.
Description: GIF image
Description: GIF image