RE: [Isis-wg] Question about Purge LSP in RFC 1142

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 22 October 2007 20:02 UTC

Return-path: <isis-wg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ik3TU-00058H-1G; Mon, 22 Oct 2007 16:02:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ik3TR-000559-M7 for isis-wg@ietf.org; Mon, 22 Oct 2007 16:02:05 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ik3RX-00052I-Tx for isis-wg@ietf.org; Mon, 22 Oct 2007 16:02:05 -0400
Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-3.cisco.com with ESMTP; 22 Oct 2007 13:00:05 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l9MK0558002530; Mon, 22 Oct 2007 13:00:05 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l9MK04sZ009617; Mon, 22 Oct 2007 20:00:04 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 22 Oct 2007 13:00:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Isis-wg] Question about Purge LSP in RFC 1142
Date: Mon, 22 Oct 2007 13:00:59 -0700
Message-ID: <AE36820147909644AD2A7CA014B1FB520475FA45@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <20071022193154.GA6628@juniper.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Isis-wg] Question about Purge LSP in RFC 1142
Thread-Index: AcgU43WarrvGvjf8SKyF6IsL5wouIwAASIew
References: <9b0da1460710140414s1a3d89byb9cc873fc964eddf@mail.gmail.com> <20071022193154.GA6628@juniper.net>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Hannes Gredler <hannes@juniper.net>, "Theodore.Wang" <theodore.wang@gmail.com>
X-OriginalArrivalTime: 22 Oct 2007 20:00:04.0263 (UTC) FILETIME=[23051B70:01C814E6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1432; t=1193083205; x=1193947205; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ginsberg@cisco.com; z=From:=20=22Les=20Ginsberg=20(ginsberg)=22=20<ginsberg@cisco.com> |Subject:=20RE=3A=20[Isis-wg]=20Question=20about=20Purge=20LSP=20in=20RFC =201142 |Sender:=20; bh=ODE0ujudE593kaVdOM0SIbL7ueDQWtsb8eYMDPwaPAg=; b=Mod/GCjD+gy+yb+/cicRYE/xsEh0S46fZhBvp6fn5agwuhwn2T5dTZlCLam4wWX+j/Ld034w 4Qiq9XORfbml+/SsO24Reqg7QccbDXf7ZFFw/r6IH3Gafsgj24qG8Cof;
Authentication-Results: sj-dkim-7; header.From=ginsberg@cisco.com; dkim=pass ( sig from cisco.com/sjdkim7002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: isis-wg@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
Errors-To: isis-wg-bounces@ietf.org


> -----Original Message-----
> From: Hannes Gredler [mailto:hannes@juniper.net]
> Sent: Monday, October 22, 2007 12:32 PM
> To: Theodore.Wang
> Cc: isis-wg@ietf.org
> Subject: Re: [Isis-wg] Question about Purge LSP in RFC 1142
> 
> On Sun, Oct 14, 2007 at 07:14:16PM +0800, Theodore.Wang wrote:
> |    Therefore, is it possible to attach a new TLV in Purge LSP that
> defines
> |    the originator?
> 
> that would not help you to fix all pathologic cases -
> think of a misconfiguration where you have non-unique
> system-ids somewhere in the network ...

Hmmm...this is a different case entirely.

Now you will be receiving valid LSPs (i.e. no syntax errors, no checksum
errors) but they will look like they are self-generated when they have
actually be generated by your "evil-twin". This will force you to
regenerate or purge depending upon whether that particular LSP number is
part of your current self-generated set or not.

Throttling is important in this case to at least control the rate of
flapping, but ignoring the received LSPs is out of the question. The
network will churn until the misconfiguration is fixed.

   Les

> 
> all you can do is to ignore this LSP and throttle
> your own LSP re-origination.
> 
> /hannes
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg