These are not mutually exclusive things... I consider VPLS over a
routed infrastructure to be equivalent to "carrier ethernet."
On 12/17/2014 08:30 AM, Gino Villarini via Af wrote:
It all depends on your vision and long term strategy�. If you are only
ogint to do Internet to residential� well L3 routed is the way to do
it� but if you want to to be a player on business/wholesale/carrier
market, you need to go Carrier Ethernet�
Gino A. Villarini
President
Aeronet Wireless Broadband Corp.
www.aeronetpr.com
@aeronetpr
From: "af@afmug.com <mailto:af@afmug.com>" <af@afmug.com
<mailto:af@afmug.com>>
Reply-To: "af@afmug.com <mailto:af@afmug.com>" <af@afmug.com
<mailto:af@afmug.com>>
Date: Wednesday, December 17, 2014 at 12:18 PM
To: "af@afmug.com <mailto:af@afmug.com>" <af@afmug.com
<mailto:af@afmug.com>>
Subject: Re: [AFMUG] ISP Radio Wednesday -- Bridged vs Routed
In my experience MEF related products are very popular with oldschool
PSTN operators and big cellular carrier, less so with ISPs that do
100% IP. You can sell an Ethernet tunnel over MPLS just as well.
On Wed, Dec 17, 2014 at 4:16 PM, Mark Radabaugh via Af <af@afmug.com
<mailto:af@afmug.com>> wrote:
This is where the majority of large carriers are going:
http://metroethernetforum.org/carrier-ethernet/carrier-ethernet-services
If you are buying (or selling) services to any of the larger
carriers you are likely seeing MEF standards in use - Ethernet
Virtual Connections, NNI and UNI interfaces.
There are a lot of really nice features in MEF that allow you to
sell protocol independent Ethernet across your network or across
multiple networks. Something like a point to point where Time
Warner is one end and your customer is on the other end. Or a
PMP type of arrangement where 2 customers are on Comcast, 3 are on
AT&T, and 4 are your wireless customers. To the customer it just
appears as if the 9 sites are connected via an Ethernet switch and
you don't care in the least what addressing or protocols they run.
If you are selling to any of the cell carriers they expect MEF
services and specifically Y.1731 performance monitoring. This
allows you and your customers to prove that you are actually
providing the bandwidth, latency, jitter, and uptime.
MEF adds a great deal of monitoring and troubleshooting capability
to the network. It allows you to monitor end to end and within
your own network in order to identify both to you and your
partners where a problem exists and who is responsible for it.
--
Mark Radabaugh
Amplex
m...@amplex.net <mailto:m...@amplex.net> 419.837.5015 x 1021
!DSPAM:2,5491b0d5316499947210542!
