The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Aug> msg00105



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

[Fwd: I-D ACTION:draft-pan-rsvp-te-restart-01.txt]

  • From: Ping Pan <pingpan@juniper.net>
  • Date: Wed, 15 Aug 2001 07:33:02 -0700
  • CC: neil.2.harrison@bt.com, mpls@UU.NET

> David Allan wrote:
> 
> Ping:
> 
> I'm having trouble correlating route flap instability data with your
> problem statement. Similarly I have trouble with the analogy between
> graceful restart for routing (which has a fair chasm between it and
> forwarding) and a soft state signalling protocol which would appear to
> require a much tighter coupling.
> 

Dave,

The point was that in the network, there could be cases where the
control engine is crashed while the data forwarding engine is fine. To
reduce the side-effects, control protocols (routing and signaling)
should use various graceful restart mechanisms. In our draft, I think
the control and forwarding are tightly coupled. Please let me know why
you think otherwise.

> Is this really more applicable to GMPLS and should be tagged as such?
> 

Both GMPLS and MPLS can benefit from this. In case of GMPLS, graceful
restart can be used to recover from control channel failure.

Regards,

- Ping