The MPLS-OPS Archive

["john smith" <johnsmith0302@hotmail.com>]

>
> > >1. Is it possible to bind a label to an MPLS experimental bit across a
> > >network ? The idea is to have only 1 LSP per application (i.e. voice,
exp.
> > >bits = 5), regardless the number of customers for MPLS VPN service? If
> > >this is feasible, will that raise a security issue (because no traffic
> > >separation).
> >
> >
> > It is my understanding that labels are assigned on a per-flow
per-customer
> > basis. This means that if Customer A has two streams of traffic with the
> > same priority and the same next-hop destination, those two streams
become a
> > single flow and will share a single label for that hop. The same type of
> > traffic from Customer B will have a different label over the same
next-hop.
> > In this way the two customers' traffic flows will be kept separate even
> > though they have the same priority.
> >
>
> This is certainly possible, but not the way TE was intended to be
> used, nor how at least one implementation out there behaves.  Think of
> a TE LSP as a unidirectional traffic trunk between two nodes in the
> provider's network.  Customer A and Customer B traffic between the
> same two nodes takes the same trunk.  Seperation is done by DiffServ
> and EXP bits.


is this cisco specific?
does cisco support "TED" and RSVP-TE EROs based on TED parameters?

>
> >
> > >2. What's the behavior of RSVP, when it's configured to constrain &
> > >reserved a 20 MB? Will it maintain 20MB LSP permanently regardless the
> > >traffic usage (no tear down)?
> >
>
> Yes.  But in at least our implementation, the reservation is
> control-plane only.  The idea is to build a reservation for something
> like 95th percentile of your traffic between two points.


Can you please elaborate?



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