The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Feb> msg00204



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

another ping's fast-reroute draft question

  • From: "Doug Degan" <doug_degan@hotmail.com>
  • Date: Wed, 27 Feb 2002 17:48:43 +0200
  • X-OriginalArrivalTime: 27 Feb 2002 15:48:48.0312 (UTC) FILETIME=[3EDB4B80:01C1BFA6]
  • X-Originating-IP: [212.25.110.131]

 hi. and thanks for the quick answer.
 I look at the proposed methods as such that should enable fully automatic
 FRR protection establishement for a LSP.
 meaning automatic bypass association and de-association (upon the bypass
 shutting) and automatic detour computations.
 I know it is possible to configure almost everything manually but I think
it
 is ugly for example to associate the pre established bypass to the
protected
 LSP manually in the PLR.

 Are the proposed methods enable this automatic establishing?


 and if so - what are the assumptions about the other relevant routers in
the
 network?
 should they push routers addresses/id in the RRO object?
 shoult the bypass tunnels be configured with ERO object?


thanks in forward.








----- Original Message -----
From: "Ping Pan" <pingpan@juniper.net>
To: "Doug Degan" <doug_degan@hotmail.com>
Cc: <mpls@uu.net>
Sent: Sunday, February 24, 2002 6:27 PM
Subject: Re: another ping's fast-reroute draft question


> Doug Degan wrote:
>
> > in section 4.3  it is said that the PLR should try to find the bypass
> > tunnel. NHOP/NNHOP one.
> >
> >
> >
> >  my question is what are the assumptions that are made when saying that
> > the PLR is capable to do so?
> >
> >
> >
> > 1.a) The PLR should choose from the Bypass tunnels available, meaning
> > tunnels which this router is their Ingress.
>
>
> Yes.
>
> > should it know their
> > explicit route, or their recorded route is enough?
> >
>
>
> The bypass LSPs can be established independent from the protected LSPs.
> When protecting a LSP, a PLR just uses a bypass LSP as an alternative
> route for the protected LSP. Knowing ERO or RRO is an implementation
issue.
>
>
> >
> >
> > 1.b) It should parse the current (protected) LSP's recorded route. does
> > it gives enough information?
> >
> > the PLR needs to know which node/link to avoid and what bypass
> > destinations are good.
> >
> > as far as I know - the recorded route doesn't have to include router's
> > ID/addresses.
> >
>
>
> Huh? RRO, Subtype = 1.
>
>
> >
> >
> > 2.a) what happens if TE is not enabled in the PLR or in another node
> > along the protected lsp's path - does it mean that FRR wil not work?
> >
> >
> >
> > 2.b) what if TE is enabled anywhere but CSPF is not used (and no
> > explicit path is found in the candidate for bypass tunnels)
> >
> >
>
>
> The most important task for bypass LSPs is to avoid some links or nodes.
>    If this cannot be doe intelligently, I would recommend to use
> whatever the means available to get the job done.... (type the path by
> hand, for example ...: -))
>
> - Ping
>
>