The MPLS WG Archive[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]
Title: RE: [Fwd: I-D ACTION:draft-pan-rsvp-te-restart-01.txt] Ping: I don't see control and data planes as tightly coupled in your proposal. You're clearly operationally divorcing the two (which is the trend you refer to for BGP, IGP and now RSVP restart mechanisms). Not that this is a bad thing, it just cannot be done in isolation. 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. 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. Every divorce in the fate-sharing world adds a new failure detection requirement and more maintenance messaging. cheers
-----Original Message-----
> David Allan wrote:
Dave, The point was that in the network, there could be cases where the
> 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
Regards, - Ping
|
|