The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-May> msg00532



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

Last call - RSVP problems

  • From: Guangzhi Li <gli@research.att.com>
  • Date: Fri, 25 May 2001 18:11:44 -0400
  • Cc: "'Jonathan Lang'" <jplang@calient.net>, "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org, "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET, ccamp@ops.ietf.org

>
> I agree that if LMP or any link layer fault detection technology
> (such as using SONET/SDH overhead to determine DCC down) can detect
> control channel failure, we don't need to use RSVP Hello.
>
> Note, In a node failure case, a node may lose all of
> its RSVP states. To cover this case, we recommend
> using the Srefresh procedure upon restoration of
> control channel. This will synchronize states on
> both sides.
>

Just thinking. If RSVP-PHOP uses node id instead of control channel
interface address, then control channel failure won't affect control
message forwarding. But node failure is still a problem.

-- Guangzhi