<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: e-Smart again</title>
	<atom:link href="http://javacard.vetilles.com/2007/09/20/e-smart-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://javacard.vetilles.com/2007/09/20/e-smart-again/</link>
	<description>A weblog on Java Card, security, and other things personal</description>
	<lastBuildDate>Thu, 18 May 2017 07:26:32 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.32</generator>
	<item>
		<title>By: Guerin Vincent</title>
		<link>http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3106</link>
		<dc:creator><![CDATA[Guerin Vincent]]></dc:creator>
		<pubDate>Mon, 19 Nov 2007 09:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3106</guid>
		<description><![CDATA[I agree with you Eric, my figures are not very accurate. 16K of RAM are enought whereas 256K of NVM seems more reasonnable. We can notice that this ratio of sizes better fits to the chips from the market.]]></description>
		<content:encoded><![CDATA[<p>I agree with you Eric, my figures are not very accurate. 16K of RAM are enought whereas 256K of NVM seems more reasonnable. We can notice that this ratio of sizes better fits to the chips from the market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric VÃ©tillard</title>
		<link>http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3089</link>
		<dc:creator><![CDATA[Eric VÃ©tillard]]></dc:creator>
		<pubDate>Fri, 21 Sep 2007 08:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3089</guid>
		<description><![CDATA[Vincent mentioned 32K, and I believe that he is about right. We could do it with less memory, but then, applications need memory as well. So, 1.5k is way too small.

Actually, the problem is the same for EEPROM, which is why I found Vincent&#039;s 64k too small. It is enough for the system, but not for the applications.]]></description>
		<content:encoded><![CDATA[<p>Vincent mentioned 32K, and I believe that he is about right. We could do it with less memory, but then, applications need memory as well. So, 1.5k is way too small.</p>
<p>Actually, the problem is the same for EEPROM, which is why I found Vincent&#8217;s 64k too small. It is enough for the system, but not for the applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lexdabear</title>
		<link>http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3084</link>
		<dc:creator><![CDATA[lexdabear]]></dc:creator>
		<pubDate>Thu, 20 Sep 2007 16:55:08 +0000</pubDate>
		<guid isPermaLink="false">http://javacard.vetilles.com/2007/09/20/e-smart-again/#comment-3084</guid>
		<description><![CDATA[I attended the presentation from Gemalto about smart card web server. It was quite interesting to see a presentation of web content on the SIM. The demonstration included a OTP generation with the corresponding bar code which can be read via a web camera from mobile phone&#039;s display. Gemalto also presented a commercial development tool (Eclipse plugin, similar to JCOP Tools) which can be used for &quot;normal&quot; Java Card programming as well.

I was surprised to hear that Gemalto cannot wait for the new Java Card 3 Connected Edition, but pushed their concept through the Open Mobile Alliance. Not sure if it is the right to bypass the owner of the technology.

Regarding the hardware requirements for such a SCWS we heard RAM numbers starting from 1.5kB to 20kB, I guess aiming for the lower cost SIM cards.

Overall the demonstration was good.

Eric, could you please elaborate more on the HW requirements (especially the most expensive part: RAM) for a JC 3.0 connected edition? I hear so many different numbers and would like to know  a minimum.

Also I would like to understand the TCP/IP optimization you mentioned. Is it planned to make again a smart card specific protocol? (I hope not.)]]></description>
		<content:encoded><![CDATA[<p>I attended the presentation from Gemalto about smart card web server. It was quite interesting to see a presentation of web content on the SIM. The demonstration included a OTP generation with the corresponding bar code which can be read via a web camera from mobile phone&#8217;s display. Gemalto also presented a commercial development tool (Eclipse plugin, similar to JCOP Tools) which can be used for &#8220;normal&#8221; Java Card programming as well.</p>
<p>I was surprised to hear that Gemalto cannot wait for the new Java Card 3 Connected Edition, but pushed their concept through the Open Mobile Alliance. Not sure if it is the right to bypass the owner of the technology.</p>
<p>Regarding the hardware requirements for such a SCWS we heard RAM numbers starting from 1.5kB to 20kB, I guess aiming for the lower cost SIM cards.</p>
<p>Overall the demonstration was good.</p>
<p>Eric, could you please elaborate more on the HW requirements (especially the most expensive part: RAM) for a JC 3.0 connected edition? I hear so many different numbers and would like to know  a minimum.</p>
<p>Also I would like to understand the TCP/IP optimization you mentioned. Is it planned to make again a smart card specific protocol? (I hope not.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
