The MPLS-OPS Archive

[Santiago Alvarez <saalvare@cisco.com>]

One example would be to have tunnels for EF traffic between POPs.  All
EF traffic would be routed through those tunnels.  Tunnel between POP A
and POP B would carry aggregate EF traffic between the two locations. 
Underlying QoS mechanisms provide the BW guarantee in the forwarding
plane that was offered in the control plane by MPLS (DiffServ-aware)
TE.  Contrary to Nihal's comment, we've been shipping DiffServ-aware TE
for some time now.

SA
--

HANSEN CHAN wrote:
> 
> Nihal,
> 
> I have a question on the reply. According to my understanding, RSVP-TE can be
> used to establish a LSP with resource reservation between two PE's. However, you
> could have quite a few sites connected to the PE's at each side and they would
> share the same LSP for communication between them.
> 
> Then how can you guarantee bandwidth for any particular site as other sites
> might be sending traffic occupying the bandwidth?
> 
> Cheers,
> Hansen
> 
> Nihal.Samaraweera@vf.vodafone.co.uk wrote:
> 
> > You could use RSVP-TE for resource reservation while using diffserv
> > to differentiate between traffic classes.  Although this issue is
> > addressed by the IETF TEWG (Requirements for support of Diff-Serv-aware
> > MPLS Traffic Engineering, Traffic Engineering Extensions to OSPF),
> > there are no much implementation of relevant drafts.
> >
> > Alternatively you could use an implementation of the draft "MPLS
> > Support of Differentiated Services".  This let you to associate LSP
> > with a diffserv.  RSVP could still be used as the signalling protocol
> > (EXP bits in the shim header to PHB mapping).   However, routers
> > don't maintain any relationship between current bandwidth allocation
> > for each diffserv class, but only maintain the aggregated values.
> > You cold still use an off-line provisioning tool to plan allocation
> > for each class and appropriate diffserv PHB settings.
> >
> > The third possible approach is to use RSVP-TE to make reservation
> > without using diffserv.  In this case, you just specify the traffic
> > descriptor. Again you need an off-line planing tool for provisioning.
> >
> > Regards,
> >
> > Nihal Samaraweera
> > Vodafone Ltd.
> >
> > -----Original Message-----
> > From: Matthew Beggs [mailto:Matthew.Beggs@hutchison3g.com]
> > Sent: 02 October 2001 09:35
> > To: mpls-ops@mplsrc.com
> > Subject: Guaranteed BW for MPLS VPN
> >
> > Hi there
> >
> > I have a requirement to guarantee a certain amount of bandwidth between two
> > sites for a particular application/service, which I want to connect with a
> > MPLS VPN.  Can anyone tell me of a way to do this, or if it is possible ?  I
> > understand that RSVP is used to ensure there is enough BW between the sites
> > to create the VPN, but can this then be used to perform the function I want
> > ?  Can RSVP-TE be used for this ?  I also know we could use the Diffserve
> > Code Point to maybe map all traffic from this app/service and differentiate
> > between traffic that way, but would like to explore other options.
> >
> > Your advice is greatly appreciated.
> >
> > Regards
> >
> > ___________________________________________________________________
> > This communication contains  information which  is confidential and
> > may also be privileged. It is for the exclusive use of the intended
> > recipient. If you are  not the intended recipient, please note that
> > any form of distribution, copying or  use of this  communication or
> > the information in it is strictly prohibited. If  you have received
> > this communication  in  error,  please  return  it  with  the title
> > "received in error"  to  Helpdesk@hutchison3g.com  then  delete the
> > email and destroy any copies of it. Please contact our Helpdesk  on
> > 01628765555 if you need assistance. Thank you for your cooperation.
> > ___________________________________________________________________
> >
> > -------
> > 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

--

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