[pim] PIM graceful restart (non-stop forwarding) capability
"Srikanth Rao" <srikanth@force10networks.com> Tue, 21 August 2007 21:00 UTC
Return-path: <pim-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1INapk-0004uY-2E; Tue, 21 Aug 2007 17:00:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1INapi-0004uR-Sp for pim@ietf.org; Tue, 21 Aug 2007 17:00:14 -0400
Received: from corp.force10networks.com ([64.186.164.204] helo=mx.force10networks.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INapi-0004BA-Fb for pim@ietf.org; Tue, 21 Aug 2007 17:00:14 -0400
Received: from mx.force10networks.com ([10.11.0.222]) by mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Aug 2007 14:00:57 -0700
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 21 Aug 2007 14:00:56 -0700
Message-ID: <270D64FB3224334F8D5679719AEEA27AB1DB24@EXCH-CLUSTER-07.force10networks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PIM graceful restart (non-stop forwarding) capability
Thread-Index: AcfkNl3reh1jJ1/oSPGGNSYkN38f4g==
From: Srikanth Rao <srikanth@force10networks.com>
To: pim@ietf.org
X-OriginalArrivalTime: 21 Aug 2007 21:00:57.0669 (UTC) FILETIME=[5F021F50:01C7E436]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Subject: [pim] PIM graceful restart (non-stop forwarding) capability
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1679149305=="
Errors-To: pim-bounces@ietf.org
Hi, How do PIM routers know about the graceful-restart capability of their peers? In BGP, OSPF and other protocols, this capability is advertised upfront when the adjacencies are formed. So that when their neighbor liveliness is lost, they hold on to the routes to support the non stop forwarding of traffic. In PIM, a new GenID in the Hello message indicates that the router restarted. But that doesn't necessarily mean that router is capable of doing non stop forwarding. So, in other words, when a PIM speaker detects that its neighbor has gone down (or restarting), what is the criterion on which it holds on to the updates from its neighbor in non-stop forwarding mode? Is there any standardized option or mechanism for this? If this has been already discussed, can someone point me to the discussion? Thanks Srikanth
_______________________________________________ pim mailing list pim@ietf.org https://www1.ietf.org/mailman/listinfo/pim
- [pim] PIM graceful restart (non-stop forwarding) … Srikanth Rao
- Re: [pim] PIM graceful restart (non-stop forwardi… janardhan kulkarni