<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: AT&#x26;T &#x26; Verizon probably do the same thing or will in </title>
<link>http://www.dslreports.com/forum/r20220843</link>
<description></description>
<language>en</language>
<pubDate>Fri, 04 Dec 2009 12:18:30 EDT</pubDate>
<lastBuildDate>Fri, 04 Dec 2009 12:18:30 EDT</lastBuildDate>

<item>
<title>Re: AT&#x26;T &#x26; Verizon probably do the same thing or will</title>
<link>http://www.dslreports.com/forum/remark,20222068</link>
<description><![CDATA[<A HREF="/useremail/u/737475"><b>BosstonesOwn</b></A> : Ahh I didn't get what they meant. <br><br>Have to stamp the burnt out logo on my head for it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20222068</guid>
<pubDate>Tue, 25 Mar 2008 11:19:44 EDT</pubDate>
</item>

<item>
<title>Re: AT&#x26;T &#x26; Verizon probably do the same thing or will</title>
<link>http://www.dslreports.com/forum/remark,20220843</link>
<description><![CDATA[<A HREF="/useremail/u/1171315"><b>tc1uscg</b></A> : <div class="bquote"><small>said by  BosstonesOwn <A HREF="/useremail/u/737475"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Verizon Wireless has been doing this for years. They mux the Verizon wireless traffic onto the Verizon backbone.<br><br>Funny thing is that this is how Verizon makes a lot of their profit, they double dip. VW is a holding of V so they bill for the network capacity then they take a chunk of the profit as well. Pretty good gig.<br> </div>That's not what they are talking about. ALL telco's "mux" their different levels of communications. Sprint has iDen MSO's jumping on MAN fiber to a LD site, which lets the T1's trickle down to whatever backbone that's needed. What VZ/VZW isn't doing (or saying) is offloading traffic from legacy switches, like a Nortel DMS and/or Lucent platform and putting it all on a single platform (ip based) so it all forms one cloud.. not many. It's nice to have 1 cabinet (mux's, echo cans, WBDac's and BBDacs) that has everything one needs instead of a plant scattered all over the building.  ;) ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20220843</guid>
<pubDate>Tue, 25 Mar 2008 02:01:54 EDT</pubDate>
</item>

<item>
<title>Re: AT&#x26;T &#x26; Verizon probably do the same thing or will</title>
<link>http://www.dslreports.com/forum/remark,20219426</link>
<description><![CDATA[<A HREF="/useremail/u/737475"><b>BosstonesOwn</b></A> : Verizon Wireless has been doing this for years. They mux the Verizon wireless traffic onto the Verizon backbone.<br><br>Funny thing is that this is how Verizon makes a lot of their profit, they double dip. VW is a holding of V so they bill for the network capacity then they take a chunk of the profit as well. Pretty good gig.<br><small>--<br> "It's always funny until someone gets hurt......and then it's absolutely friggin' hysterical!"</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20219426</guid>
<pubDate>Mon, 24 Mar 2008 20:52:55 EDT</pubDate>
</item>

<item>
<title>AT&#x26;T &#x26; Verizon probably do the same thing or will</title>
<link>http://www.dslreports.com/forum/remark,20215946</link>
<description><![CDATA[<A HREF="/useremail/u/594412"><b>TKJunkMail</b></A> : It only makes sense to have a single backbone network to handle all the traffic, both voice and data. By combining all the separate backbones in to one you get the advantage of a more robust network with more diversity and redundancy. And the combined capacity allows the backbone to handle peaks more readily.<br><small>--<br><A HREF="http://tinyurl.com/bqv2h"><b>My BLOG ..</b></a><A HREF="http://tinyurl.com/2a9xcb"><i> .. Internet News ..</i></a><A HREF="http://tinyurl.com/yz8xto"><b> .. My Web Page</b></a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20215946</guid>
<pubDate>Mon, 24 Mar 2008 09:20:38 EDT</pubDate>
</item>

</channel>
</rss>
