[mpls] Avoiding LDP graceful restart with planned node shutdown.

Andy Baker <Andy.Baker@dataconnection.com> Thu, 07 October 2004 09:29 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26944; Thu, 7 Oct 2004 05:29:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFUk5-0006KH-IF; Thu, 07 Oct 2004 05:39:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFUQc-0000gc-Hv; Thu, 07 Oct 2004 05:19:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFUOw-0000EW-9t for mpls@megatron.ietf.org; Thu, 07 Oct 2004 05:17:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26034 for <mpls@ietf.org>; Thu, 7 Oct 2004 05:17:27 -0400 (EDT)
Received: from smtp2.dataconnection.com ([192.91.191.8] helo=smtp2.datcon.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFUYY-0005na-Qx for mpls@ietf.org; Thu, 07 Oct 2004 05:27:30 -0400
Received: by beiderbecke.datcon.co.uk with Internet Mail Service (5.5.2653.19) id <4HNQP2GV>; Thu, 7 Oct 2004 10:16:51 +0100
Message-ID: <16E71652255A3E4796A7AF3A9E5068F90270B5@blakey.datcon.co.uk>
From: Andy Baker <Andy.Baker@dataconnection.com>
To: "'manoj@juniper.net'" <manoj@juniper.net>, "'yakov@juniper.net'" <yakov@juniper.net>, "'rahul@redback.com'" <rahul@redback.com>
Date: Thu, 07 Oct 2004 10:14:17 +0100
Deferred-Delivery: Thu, 7 Oct 2004 10:15:00 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: "'mpls@ietf.org'" <mpls@ietf.org>
Subject: [mpls] Avoiding LDP graceful restart with planned node shutdown.
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Hi,

In the case where a node is to be permanently disabled in a network in an
orderly manner (planned shutdown), but where normally it advertises to its
LDP peers that it supports graceful restart procedures, it is desirable that
peers do not use graceful restart procedures when they detect that the node
has gone.  This is to prevent the peers continuing to forward data to the
stopped node on the assumption that the node's forwarding state is still
intact.  Such forwarded data will be black-holed until the peer neighbour
reconnect timer expires.

To prevent graceful restart usage under these circumstances requires that
nodes can detect the difference between the planned and unplanned shutdown
of a peer.

While RFC3478 makes no specific comment on how to do so, a possible approach
would be that when a node detects the failure of a peer through receipt of a
Notification (shutdown), the receiving node assumes this is a planned
shutdown of the peer, and disables graceful restart.

In all other cases (TCP socket error, keepalive timeout etc.), the node
assumes unplanned shutdown, and starts its graceful restart neighbour
reconnect / liveness timer for the session.

I'd like to get clarification if this is in fact the intent in the standard?

Thanks,

Andy.

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls