The MPLS-OPS Archive

[Roger Clark Williams <rogerw@nordlink.com>]

Javiar, totally correct. The example I used was only in regards to the 
speed setting itself, but as you point out indirectly, why are we setting 
this speed? For an application. So the speed has to support the app, 
agreed. It still leaves open the question of a "typical" speed, and I would 
hold that the provider will probably be selling something to the customer 
that reflects generally known standards. A silly example, perhaps, but I 
doubt a provider would be selling a 2.15mb service. Just a guess on my 
part, however.

Roger


>X-Real-To: rogerw@nordlink.com
>From: "Javier Perez LLedo" <javi.pll@telefonica.net>
>To: "'Roger Clark Williams'" <rogerw@nordlink.com>,
>         "'MPLS-ops Mailing List'" <mpls-ops@mplsrc.com>
>Subject: Re: [MPLS-OPS]: Question about L2VPN over MPLS
>Date: Tue, 23 Mar 2004 10:47:53 +0100
>X-Mailer: Microsoft Outlook, Build 10.0.4510
>Importance: Normal
>
>Hi,
>
>In general terms, I agree Roger. But, under my understanding, it is not
>obvious the question in the case of VPLS. The risk, I've observed is that a
>low speed for the service could impact in the behaviour and performance of
>the applications over a LAN (local broadcasts, response time, etc) when in
>fact aren´t in local network, ;)
>
>In the case of VPLS or EoMPLS, you should consider the apps the users will
>run and their features, specially in you want to provide a low speed between
>sites.
>
>JAVI
>
>-----Mensaje original-----
>De: Roger Clark Williams [mailto:rogerw@nordlink.com]
>Enviado el: lunes, 22 de marzo de 2004 20:34
>Para: MPLS-ops Mailing List
>Asunto: Fwd: Re: [MPLS-OPS]: Question about L2VPN over MPLS
>
>Luis,  Steinar is quite right, it depends. However, as an example, I am
>working now on a system that is using a GE-WAN interface from a Cisco 7606
>PE pointing towards the CEs. It will be configured as a Multi-VRF
>interface, passing a number of streams of various customers' traffic. How
>fast the traffic may actually travel will be based on the Service Level
>Agreement between the individual customer and the provider, right up to the
>capacity of the entire physical interface. There is nothing typical unless
>the provider is selling services that replace present standard telco
>services, in which case maybe a "typical" speed might be 64k, 128k, T1 or
>the like. It would be controlled by something like the Cisco IOS rate-limit
>command or the policing command which limits the customer to a given
>throughput.
>
>Roger Williams
>
>
> >X-Real-To: rogerw@nordlink.com
> >Resent-Date: Mon, 22 Mar 2004 14:01:22 -0500
> >X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to
> >mpls-ops-request@mplsrc.com using -f
> >To: luis-m-a-santos@telecom.pt
> >Cc: mpls-ops@mplsrc.com
> >Subject: Re: [MPLS-OPS]: Question about L2VPN over MPLS
> >From: sthaug@nethelp.no
> >X-Mailer: Mew version 1.05+ on Emacs 19.34.1
> >Date: Mon, 22 Mar 2004 19:47:18 +0100
> >Resent-From: mpls-ops@mplsrc.com
> >X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/6905
> >X-Loop: mpls-ops@mplsrc.com
> >Resent-Sender: mpls-ops-request@mplsrc.com
> >
> > > Can anyone pls recommend one typical bit rate used between CE and
> > > PE, on implementations of the VPLS service (Layer 2 VPNs) ? And the
> > > technology of that Access?
> >
> >Why do you think there is such a thing as a typical bit rate between
> >CE and PE?
> >
> >The bit rate will normally be whatever the customer wants (and pays
> >for) - anything from 64 kbps to several Mbps. Similarly, there is no
> >one typical access technology for VPLS - DSL, traditional serial lines
> >and Ethernet are all examples of access technologies that can be used.
> >
> >I think you need to reformulate your question.
> >
> >Steinar Haug, Nethelp consulting, sthaug@nethelp.no
> >
> >-------
> >The MPLS-OPS Mailing List
> >Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml