On Wed, Apr 04, 2001 at 01:06:29PM -0700, Serge Maskalik wrote:
>
> <truncated>
>
> > > Can you explain why it would be useful per interface?
> >
> > We have a specific application where we on a number of dedicated routers
> > originate default route, for use of the routers in the network not
> > carrying full routing (mainly dial and DSL aggregation boxes), these routers
> > will use the LSP formed by LDP/TDP to get to these "default origination
> > boxes", PHP will occur, and the "default .. boxes" will recieve the
> > packets as ordinary IP packets, do NetFlow accounting on them, and do a
> > L3 lookup, and forward them on the LSP to the exit point ...
>
> I can see the ease-of-configuration benefits with your special
> case scenario. In your special case, per-interface control is
> useful. However, with RSVP-TE deployments in large NSP networks,
> one does not has obvious penultimate hop points. Same LSR is
> often a mid-point, head-end and tail-end for many LSPs.
>
> > > I think it makes sense to do on per-LSP basis.
> >
> > Much harder to control on a per-LSP basis, especially when talking about
> > LDP/TDP controlled LSP's.
>
> I'm more interested about the underlying RSVP-TE LSPs.
It all depends on how you build your network, there are multiple ways of
doing it
1) Using LDP LSP's following default IGP paths, and perhaps a few
TE-LSP's
2) Using a full mesh of TE-LSP's
> Imagine a RSVP-TE core w/ overlay consisting of PE->PE
> LDP LSPs. If I can configure exlicit-null behavior for
> just the underlying TE LSPs, I can infer custom queueing
> policies from the EXP field all the way down to the tail.
Both the above senarios can have the need for end to end queuing on the
EXP field, so I don't think one is more important than the other, it's
just different people that is going to use them ...
/Jesper
-- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-)One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:41 EDT