<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Issues and News</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/" />
    <link rel="self" type="application/atom+xml" href="http://www.webtorials.com/issues/atom.xml" />
   <id>tag:www.webtorials.com,2007:/issues//8</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8" title="Issues and News" />
    <updated>2006-05-02T21:39:09Z</updated>
    <subtitle>This blog is designed for discussion of current news items and issues being faced in the telecommunications industry.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>Innovation and Legislation</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/05/innovation_and_legislation.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=27" title="Innovation and Legislation" />
    <id>tag:www.webtorials.com,2006:/issues//8.27</id>
    
    <published>2006-05-02T22:29:35Z</published>
    <updated>2006-05-02T21:39:09Z</updated>
    
    <summary>It often seems as if legislation is written to address technical issues that existed years prior. As noted in a soon-to-be-published e-newsletter for Network World, this has been a chronic problem for many years. With issues from intellectual property rights...</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
            <category term="Innovation" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>It often seems as if legislation is written to address technical issues that existed years prior.  As noted in a soon-to-be-published e-newsletter for Network World, this has been a chronic problem for many years.  With issues from  intellectual property rights to the deployment of new telecommunications system capabilities, implementors run the risk of being out of compliance with regulations if they use systems that provide "best practices" for their business. </p>]]>
        <![CDATA[<p>As soon as it is available, we'll provide the URL for the archived version of the above-mentioned newsletter.  In the meantime, we invite your comments and discussion on how you deal with this issue - and how regulatory compliance has (or has not) affected the productivity of your business.</p>]]>
    </content>
</entry>
<entry>
    <title>Do Managed Services Make Sense?</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/04/do_managed_services_make_sense.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=26" title="Do Managed Services Make Sense?" />
    <id>tag:www.webtorials.com,2006:/issues//8.26</id>
    
    <published>2006-04-18T23:42:55Z</published>
    <updated>2006-04-18T22:53:01Z</updated>
    
    <summary>Twenty years ago, the essentially the only &quot;services&quot; that were offered by the telcos were transport services. At least in the US, the ability of the telcos to offer services beyond basic transport were severely limited in the immediate post-divestiture...</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>Twenty years ago, the essentially the only "services" that were offered by the telcos were transport services.  At least in the US, the ability of the telcos to offer services beyond basic transport were severely limited in the immediate post-divestiture era.</p>

<p>However, over the course of the past twenty years, at least two major shifts have occurred.  The service providers are now allowed to offer enhanced "managed services," and the extent to which these services offer reasonable value to customers has increased exponentially.</p>

<p>However, by most metrics, these enhanced services have failed to be adopted to any significant extent.</p>]]>
        <![CDATA[<p>So the question is "why"?  Is it a case of companies not trusting the service providers - maybe with good reason?  Is there too much BYOB (Be Your Own Bell) attitude in the user community?  Is the pricing wrong?  Are the service providers ineffective at selling these services?</p>

<p>What is the key missing ingredient in having these services take off?</p>]]>
    </content>
</entry>
<entry>
    <title>Open Source Based WAN Equipment</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/04/open_source_based_wan_equipment.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=23" title="Open Source Based WAN Equipment" />
    <id>tag:www.webtorials.com,2006:/issues//8.23</id>
    
    <published>2006-04-06T14:29:25Z</published>
    <updated>2006-04-06T16:09:17Z</updated>
    
    <summary>The recent movement to deploy open source based products has now reached out to the WAN equipment market. In particular, there are now open source based PBXs and routers. Is this a cute fad that will soon die or will...</summary>
    <author>
        <name>Jim Metzler</name>
        <uri>http://www.ashtonmetzler.com/</uri>
    </author>
            <category term="Open Source Based WAN Equipment" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>The recent movement to deploy open source based products has now reached out to the WAN equipment market.  In particular, there are now open source based PBXs and routers.  Is this a cute fad that will soon die or will it take off and be as successful as LINUX?  Speaking of LINUX, if there is a problem with LINUX researchers around the globe rush to fix it.  That will not be the case with open source PBXs and routers.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Lucent - Alcatel Merger: Impact on Corporate Networks?</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/04/lucent_alcatel_merger_impact_o.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=22" title="Lucent - Alcatel Merger: Impact on Corporate Networks?" />
    <id>tag:www.webtorials.com,2006:/issues//8.22</id>
    
    <published>2006-04-05T18:23:21Z</published>
    <updated>2006-04-05T17:30:28Z</updated>
    
    <summary>In the laterst MegaMerger-of-the-Month, Lucent and Alcatel have announced an intent to merge. While the question of whether this is a good move for the two companies is not a primary concern for corporate users, the impact of this merger...</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
            <category term="Lucent - Alcatel merger" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>In the laterst MegaMerger-of-the-Month, Lucent and Alcatel have announced an intent to merge. While the question of whether this is a good move for the two companies is not a primary concern for corporate users, the impact of this merger indeed does have a potentially profound impact.</p>]]>
        <![CDATA[<p>So the question whether thsi is a good move or a bad move for the corporate network.  Of particular concern, will this trend of megamergers slow innovation in the industry in general?  Also, what wil be the impact standards and interoperability if each large company starts to produce its own internal architecture?</p>]]>
    </content>
</entry>
<entry>
    <title>NW Wide Area Networking and Convergence e-newsletter</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/03/30906_nw_on_wide_area_networki_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=18" title="NW Wide Area Networking and Convergence e-newsletter" />
    <id>tag:www.webtorials.com,2006:/issues//8.18</id>
    
    <published>2006-03-10T15:10:06Z</published>
    <updated>2006-03-15T15:29:30Z</updated>
    
    <summary>Jim Metzler, Larry Hettick, and I asked for comments on this topic in the electronic newsletters published via Network World. In case you did not receive the newsletters, click here to view the WAN newsletter archives and here to view...</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
            <category term="AT&amp;T and BellSouth" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>Jim Metzler, Larry Hettick, and I asked for comments on this topic in the electronic newsletters published via Network World.</p>

<p>In case you did not receive the newsletters, click <a target="blank" href="http://www.networkworld.com/newsletters/frame/index.html"> here to view the WAN newsletter</a> archives and <a target="blank" href="http://www.networkworld.com/newsletters/converg/index.html"> here to view the Convergence newsletter archives</a>. </p>]]>
        
    </content>
</entry>
<entry>
    <title>AT&amp;T &amp; BellSouth - Impact on the Enterprise/Corporate Network?</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/03/att_bellsouth_impact_on_the_en.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=13" title="AT&amp;T &amp; BellSouth - Impact on the Enterprise/Corporate Network?" />
    <id>tag:www.webtorials.com,2006:/issues//8.13</id>
    
    <published>2006-03-07T15:22:55Z</published>
    <updated>2006-03-07T21:31:36Z</updated>
    
    <summary>My ultimate concern about the proposed merger, essentially rebuilding a substantial portion of the &apos;Bell System,&quot; is the impact on the enterprise/corporate network. Back in the early 1980s, when data nets were first being built, they were - for the...</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
            <category term="AT&amp;T and BellSouth" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>My ultimate concern about the proposed merger, essentially rebuilding a substantial portion of the 'Bell System," is the impact on the enterprise/corporate network.  Back in the early 1980s, when data nets were first being built, they were - for the most part - what we would now call "managed services."  In the intervening twenty-plus years, however, we moved to an era in which companies began to "BYOB," meaning "Be Your Own Bell."  Some of this BYOB attitude was to gain additional features and function, and some of the attitude was necessitated for survival.<br />
</p>]]>
        <![CDATA[<p>Much of the popular press coverage about this merger has focused on "triple play," cellular, and access to residential customers.  And while these are extremely important issues, I'm left wondering what the impact is for the members of the Webtorials community who are primarily responsible for corporate networks.</p>

<p>One view is that this should simplify networking by making "one-stop shopping" simpler than ever.  Additionally, the creation of even stronger service providers might increase your comfort level with moving to "managed services."</p>

<p>At the same time, one could also argue that this will lead to less competition, thereby slowing innovation and leading to increased prices.</p>

<p>At this point, though, I invite you - the corporate and enterprise planners and management - to share your views.  These views will be available in this forum, and we'll also share some of the views with the wider audience of readers of the Network World Fusion WAN and Convergence newsletters.</p>

<p>To add your views, simply click on the "comment" link below. </p>]]>
    </content>
</entry>
<entry>
    <title>AT&amp;T and BellSouth Merger - Analysts Speak Out</title>
    <link rel="alternate" type="text/html" href="http://www.webtorials.com/issues/2006/03/att_and_bellsouth_merger_analy.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.webtorials.com/mt/mt-atom.cgi/weblog/blog_id=8/entry_id=11" title="AT&amp;T and BellSouth Merger - Analysts Speak Out" />
    <id>tag:www.webtorials.com,2006:/issues//8.11</id>
    
    <published>2006-03-06T22:36:14Z</published>
    <updated>2006-03-07T05:59:17Z</updated>
    
    <summary>The proposed merger/acquisition of BellSouth by AT&amp;T essentially rebuilds the old Bell system. My fellow analysts have a lot to say about the proposed merger, and this is the place to find out what everybody thinks....</summary>
    <author>
        <name>Steven Taylor</name>
        <uri>http://www.webtorials.com/blog</uri>
    </author>
            <category term="AT&amp;T and BellSouth" />
    
    <content type="html" xml:lang="en" xml:base="http://www.webtorials.com/issues/">
        <![CDATA[<p>The proposed merger/acquisition of BellSouth by AT&T essentially rebuilds the old Bell system.  My fellow analysts have a lot to say about the proposed merger, and this is the place to find out what everybody thinks.  </p>]]>
        <![CDATA[<p>The purpose of this discussion is both to allow commentary and to raise issues, especially as related to Enterprise networks.  I hope you find these observations to be both interesting and providing food for thought.</p>

<p>If you wish to add a new thread, please email Steven Taylor at <a href="mailto:taylor@webtorials.com">taylor@webtorials.com</a></p>]]>
    </content>
</entry>

</feed> 

