IETF Logo Mail Archive

Re: [Isis-wg] LSP Purges

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 25 September 2013 07:07 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C2721F9E7E for <isis-wg@ietfa.amsl.com>; Wed, 25 Sep 2013 00:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgFLiZ8qFru2 for <isis-wg@ietfa.amsl.com>; Wed, 25 Sep 2013 00:07:14 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 074F521F842A for <isis-wg@ietf.org>; Wed, 25 Sep 2013 00:07:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2479; q=dns/txt; s=iport; t=1380092834; x=1381302434; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=hDssHqgH2qHQblK2WGLLhQCjeDV+ffn7Ixm5z9oMbT4=; b=hLY3yL4rsFUZMAvUg0sNSylMQ2YdKjDfqwEBsi+YMCcJSu0mlxU8iL5c SrugLaRrNv0N36fvcZ61h3WjXLqzhhucic8PzmLhTLmVKVlrB3gjKPMKz 823gQTavihvbVQtSZd/MFIPvIS9PcN2y09H3/b/wZaWzauJpO0ZiZXO4q c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAHmKQlKtJXHB/2dsb2JhbABbgwc4UsBFgRwWdIIlAQEBAwEBAQFrEAcEAgEIDgMEAQELHQcnCxQJCAIEARIIh2wDCQYMu2yMZoI6OAaDF4EAA4kAjReDFIsVhTODJIIq
X-IronPort-AV: E=Sophos;i="4.90,976,1371081600"; d="scan'208";a="264185255"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 25 Sep 2013 07:07:13 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r8P77DYx028925 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Sep 2013 07:07:13 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.15]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Wed, 25 Sep 2013 02:07:13 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Qin Wu <bill.wu@huawei.com>, Anshuman <truesylvia@yahoo.co.uk>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] LSP Purges
Thread-Index: AQHOua74SjpYCssKwEW5ZyXE0cknhpnWQ80AgAAHaID//7xi8A==
Date: Wed, 25 Sep 2013 07:07:12 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F16589766@xmb-aln-x02.cisco.com>
References: <1380086268.12889.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1380087600.37113.YahooMailNeo@web28806.mail.ir2.yahoo.com> <B8F9A780D330094D99AF023C5877DABA43C04EF4@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43C04EF4@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.125.124]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Isis-wg] LSP Purges
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2013 07:07:19 -0000

Hmmm...this seems an opportune moment to remind folks NOT to "see RFC1142" - look at ISO 10589 instead.

http://datatracker.ietf.org/doc/draft-ietf-isis-rfc1142-to-historic/

(Apologies Qin - you are not the first and likely not the last...)

   Les


> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf Of
> Qin Wu
> Sent: Tuesday, September 24, 2013 11:07 PM
> To: Anshuman; isis-wg@ietf.org
> Subject: Re: [Isis-wg] LSP Purges
> 
> See RFC1142, when IS resigns as Designated IS, it will initiate a purge, when
> adjacency is taken down, the IS can initiate purge,
> When lifetime field is zero, the IS will initiate a purge.
> 
> In worse case, it will cause purge storm, RFC6232 provides a way to locate
> who flooded the purged LSP.
> 
> Regards!
> -Qin
> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On Behalf Of
> Anshuman
> Sent: Wednesday, September 25, 2013 1:40 PM
> To: isis-wg@ietf.org
> Subject: Re: [Isis-wg] LSP Purges
> 
> Hi,
> 
> ANd i understand that an IS can initiate a purge if it finds a corrupted LSP.
> What are the other scenarios? Why would somebody explicitly want to purge the
> LSP?
> 
> Thanks, Anshuman
> 
> 
> ----- Original Message -----
> > From: Anshuman <truesylvia@yahoo.co.uk>
> > To: "isis-wg@ietf.org" <isis-wg@ietf.org>
> > Cc:
> > Sent: Wednesday, 25 September 2013, 10:47
> > Subject: [Isis-wg] LSP Purges
> >
> > Hi,
> >
> > As per http://tools.ietf.org/html/rfc6232, its usually an implementation
> issue
> > that results in an IS initiating a purge of LSPs that some other IS had
> > generated.
> >
> > I am trying to understand a valid scenario when an IS would want to purge
> LSPs
> > generated by some other IS.
> >
> > In fact, i would like to understand when somebody would issue a command
> like
> > "clear isis database purge" (on Juniper).
> >
> > Thanks, Anshuman
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www.ietf.org/mailman/listinfo/isis-wg
> >
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg

v2.23.0 | Report a Bug | By Email