The MPLS WG Archive

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



[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 10:12:34 -0700
  • CC: mpls@UU.NET
  • User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1

David Allan wrote:

> You (and others, my 
> point is not specific to this I-D) are eliminating all forms of fate 
> sharing between the control and data planes, despite (in the MPLS case 
> vs. GMPLS) the use of common resources in the control and data plane 
> adjacencies.
> 


David,

What has been proposed in all forms of graceful restart is the message 
format on the wire. How you implement the routers to support these 
messages is totally up to the developers.


> This may suggest that control plane failure is today significantly more 
> frequent than data plane or link failure and there is a real problem to 
> solve, but adding restart mechanisms to everything in the control plane 
> is not the complete answer.


You are right. There are several solutions to help routers/networks in 
case of failure condition. Graceful restart is to solve the problem when 
control plane dies, but data forwarding is up. Fast reroute is to solve 
the problem when data forwarding is in trouble. LSP-ping (please don't 
start all those architectural beatification argument again) is to detect 
data plane black-hole problem....

Regards,

- Ping