<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.fiercemobileit.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>addressed</title>
 <link>http://www.fiercemobileit.com/tags/addressed</link>
 <description></description>
 <language>en</language>
<item>
 <title>Mobile social networks take off</title>
 <link>http://www.fiercemobileit.com/story/mobile-social-networks-take/2007-09-24?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FMI0</link>
 <description>
&lt;P&gt;Companies are rushing to embrace social networking sites and technologies ranging from Facebook to Second Life. For firms that are rapidly deploying wireless applications and platforms, there is a new dilemma regarding whether an existing social networking platform should follow users into the mobile world, or if a new, designed-for-mobile social networking framework should be used. Companies like MocoSpace, Bluepulse, and SayNow are building communities around voice communications and mobile-friendly text nuggets. Organizations moving more of their work to the social networks should check out the newcomers--and should work to ensure that management and &lt;A href=&quot;http://www.it-wireless.com/story/least-surprising-study-it-pros-have-security-worries/2007-08-20&quot;&gt;security issues&lt;/a&gt; are addressed from every angle.&lt;/p&gt;
&lt;P&gt;For more on the new mobile social networks:&lt;BR /&gt;- read the &lt;A href=&quot;http://www.wirelessweek.com/Article-Social-Nets-Mobile-Users.aspx&quot;&gt;whole story&lt;/a&gt; at &lt;EM&gt;WirelessWeek&lt;/em&gt;&lt;/p&gt;

</description>
 <comments>http://www.fiercemobileit.com/story/mobile-social-networks-take/2007-09-24#comments</comments>
 <category domain="http://www.fiercemobileit.com/tags/addressed">addressed</category>
 <category domain="http://www.fiercemobileit.com/tags/implementation">implementation</category>
 <category domain="http://www.fiercemobileit.com/tags/mobile-applications">Mobile Applications</category>
 <category domain="http://www.fiercemobileit.com/tags/platforms">Mobile Operating Systems</category>
 <category domain="http://www.fiercemobileit.com/channel/wireless-security">Wireless Security</category>
 <pubDate>Mon, 24 Sep 2007 06:59:57 -0400</pubDate>
 <dc:creator />
 <guid isPermaLink="false">1694 at http://www.fiercemobileit.com</guid>
</item>
<item>
 <title>Editor&#039;s Corner</title>
 <link>http://www.fiercemobileit.com/story/editor-s-corner/2007-03-05?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FMI0</link>
 <description>&lt;P&gt;&lt;STRONG&gt;&lt;IMG alt=&quot;&quot; hspace=0 src=&quot;http://static.fiercemarkets.com/public/newsletter/businessvoipreport/curtis_headshot.gif&quot; align=right border=0&gt;&lt;IMG src=&quot;http://static.fiercemarkets.com/public/newsletter/assets/editorscorner_big.gif&quot; border=0&gt;&lt;BR&gt;&lt;/STRONG&gt;&lt;BR&gt;&lt;BR&gt;&lt;STRONG&gt;Looking ahead&lt;BR&gt;&lt;/STRONG&gt;It&#039;s always interesting to look to the future. Right now it seems that the U.S. is consumed with which 65 teams will make the NCAA basketball tournament. You can pick your brackets, but the selection committee will work without your input. Technology prediction is like that, too. Take Real ID, one of the initiatives to flow from the response to 9/11. Nearly everyone would have bet that RFID would be part of the requirements, but the final proposal leans on a bar code--and not even the most information-dense version--for encoding information.&lt;/P&gt;
&lt;P&gt;I think leaving RFID out was the right decision for now. There are still too many issues with security remaining to be addressed for RFID to be the right technology for this particular application. In too many cases we believe that our current challenge has never been faced, in any form, by anyone before. Responding to the challenge must, therefore, require the newest technology. New technology may help, but understanding the nature of the challenge, designing the process to respond, then picking a technology that&#039;s best suited for implementing the process will take us farther in more safety than looking at the technology first. -&lt;A href=&quot;mailto:curtis@fiercemarkets.com&quot;&gt;Curtis&lt;/A&gt;&lt;/P&gt;

</description>
 <comments>http://www.fiercemobileit.com/story/editor-s-corner/2007-03-05#comments</comments>
 <category domain="http://www.fiercemobileit.com/tags/addressed">addressed</category>
 <category domain="http://www.fiercemobileit.com/channel/mobile-enterprise">Mobile Enterprise</category>
 <category domain="http://www.fiercemobileit.com/tags/real-id">real id</category>
 <category domain="http://www.fiercemobileit.com/channel/rfid">RFID</category>
 <category domain="http://www.fiercemobileit.com/tags/right-technology">right technology</category>
 <category domain="http://www.fiercemobileit.com/channel/wireless-technology">Wireless Technology</category>
 <pubDate>Sun, 04 Mar 2007 19:01:39 -0500</pubDate>
 <dc:creator />
 <guid isPermaLink="false">1336 at http://www.fiercemobileit.com</guid>
</item>
<item>
 <title>Samsung phones to get device management</title>
 <link>http://www.fiercemobileit.com/story/samsung-phones-to-get-device-management/2007-02-12?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FMI0</link>
 <description>&lt;P&gt;InnoPath Software&#039;s Integrated Mobile Device Management (iMDM) is intended to help eliminate several possibilities that can prevent enterprise IT staffs from recommending a mobile platform for applications. Email problems, equipment lost while holding sensitive data and critical data lost with no backup are three of the significant problems addressed by iMDM. Samsung has signed an agreement with InnoPath to bring iMDM to a number of handsets. The client/server combination will allow an IT staff to maintain critical control of devices and data even without user control of the handset. Device availability and timing will vary by carrier, but the capabilities should be a step in the right direction for many IT departments.&lt;/P&gt;
&lt;P&gt;For more on the InnoPath software:&lt;BR&gt;- read the&amp;nbsp;&lt;A href=&quot;http://www.eweek.com/article2/0,1759,2091615,00.asp&quot;&gt;entire article&lt;/A&gt;&amp;nbsp;at &lt;EM&gt;eWeek&lt;/EM&gt;&lt;/P&gt;

</description>
 <comments>http://www.fiercemobileit.com/story/samsung-phones-to-get-device-management/2007-02-12#comments</comments>
 <category domain="http://www.fiercemobileit.com/tags/addressed">addressed</category>
 <category domain="http://www.fiercemobileit.com/tags/combination">combination</category>
 <category domain="http://www.fiercemobileit.com/tags/critical-data">critical data</category>
 <category domain="http://www.fiercemobileit.com/tags/mobile-devices">Mobile Devices</category>
 <category domain="http://www.fiercemobileit.com/tags/samsung">Samsung</category>
 <pubDate>Sun, 11 Feb 2007 19:01:37 -0500</pubDate>
 <dc:creator />
 <guid isPermaLink="false">1295 at http://www.fiercemobileit.com</guid>
</item>
<item>
 <title>Five things to know about VoIP</title>
 <link>http://www.fiercemobileit.com/story/five-things-to-know-about-voip/2006-07-10?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FMI0</link>
 <description>&lt;P&gt;There are more than a few aspects to deploying a Voice over Internet Protocol network and making it work well. And while you may be aware of a couple of big issues with VoIP, such as security, there are likely a few others you aren&#039;t aware of. One is the cost of pulling the technology in and maintenance and management investment once it&#039;s up and running. That&#039;s why a few enterprises are honing VoIP network skills in-house before launching such an initiative. Another issue is that deployment won&#039;t be as easy as some vendors and pundits might lead you to believe. From configuring IP addresses to hardware integration, deployment comes with a huge suitcase of issues that need to be addressed before you&#039;re in the midst of the project. Find out more about the top five aspects you need to be aware of before jumping onto the VoIP bandwagon. &lt;A href=&quot;http://informationweek.com/shared/printableArticle.jhtml?articleID=189800103&quot;&gt;Article&lt;/A&gt;&lt;/P&gt;

</description>
 <category domain="http://www.fiercemobileit.com/tags/addressed">addressed</category>
 <category domain="http://www.fiercemobileit.com/tags/deployment">Deployment Strategies</category>
 <category domain="http://www.fiercemobileit.com/tags/pundits">pundits</category>
 <category domain="http://www.fiercemobileit.com/tags/voip">VoIP</category>
 <pubDate>Sun, 09 Jul 2006 20:01:36 -0400</pubDate>
 <dc:creator />
 <guid isPermaLink="false">990 at http://www.fiercemobileit.com</guid>
</item>
<item>
 <title>New wireless switch lets 1,000 users connect</title>
 <link>http://www.fiercemobileit.com/story/new-wireless-switch-lets-1-000-users-connect/2005-09-26?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FMI0</link>
 <description>&lt;P&gt;The ability to let 1,000 users wirelessly connect comes with a price. While a new device, the Xirrus XS-3900, supports more than 1,000 concurrent users, many of those must be 802.11a-capable clients/users in order to make it work. Then there&#039;s a slight security hole that needs to be addressed. Described by the vendor as looking like an &quot;overgrown&quot; smoke detector device, the wireless switch features 16 discrete access points sitting within a ceiling-mounted housing and provides 2 Gbps transmission speed. The only big glitch is that the telnet capability for managing the device can&#039;t be turned off, which leaves some security issues. &lt;A href=&quot;http://www.networkworld.com/reviews/2005/082205-xirrus-test.html&quot;&gt;Article&lt;/A&gt;&lt;/P&gt;

</description>
 <category domain="http://www.fiercemobileit.com/tags/addressed">addressed</category>
 <category domain="http://www.fiercemobileit.com/channel/wireless-security">Wireless Security</category>
 <category domain="http://www.fiercemobileit.com/tags/wireless-switch">wireless switch</category>
 <pubDate>Sun, 25 Sep 2005 20:01:34 -0400</pubDate>
 <dc:creator />
 <guid isPermaLink="false">692 at http://www.fiercemobileit.com</guid>
</item>
</channel>
</rss>
