[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RSVP Graceful Restart
Nic,
Could you set out the problem in a couple of paragraphs (perhaps with an example) and let
everyone see what it is you're working on so that they can join in the discussions.
Thanks,
Adrian
----- Original Message -----
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: "Juniper - Kireeti Kompella" <kireeti@juniper.net>
Cc: "'mpls@uu.net'" <mpls@UU.NET>; <ccamp@ops.ietf.org>
Sent: Monday, October 27, 2003 1:23 PM
Subject: RE: RSVP Graceful Restart
> Hi Kireeti,
>
> As you say, FRR and GR solve very different problems, and that is why it's
> desirable to have both in the same network.
>
> The issue with that is not with overlap in the problems they are solving,
> but in recovering FRR backup and protected LSPs (which may not be being
> refreshed from upstream) after a restart. Is this a problem that interests
> you?
>
> Nic
>
> -----Original Message-----
> From: Juniper - Kireeti Kompella
> Sent: Friday, October 24, 2003 7:40 PM
> To: Nic Neate
> Cc: 'mpls@uu.net'; 'ccamp@ops.ietf.org'
> Subject: RE: RSVP Graceful Restart
>
>
> Hi Nic,
>
> On Wed, 22 Oct 2003, Nic Neate wrote:
>
> > Together with some colleagues at Data Connection, I have done some work
> > looking at how GMPLS Restart could work with RSVP Fast Reroute LSPs.
>
> FRR and GR solve *very* different problems: the first is for link or
> node failures where the data plane is affected, the second for control
> plane failures (a special subset of node failures).
>
> Could you explain the problem you see here?
>
> Kireeti.
>
>