IETF Logo Mail Archive

Re: [Idr] Reg BGP LS identifier for different ISIS levels

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 15 September 2017 08:49 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEE0132143 for <idr@ietfa.amsl.com>; Fri, 15 Sep 2017 01:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ts3WNw5quLy for <idr@ietfa.amsl.com>; Fri, 15 Sep 2017 01:49:25 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0632F1201F8 for <idr@ietf.org>; Fri, 15 Sep 2017 01:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6782; q=dns/txt; s=iport; t=1505465365; x=1506674965; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=RVP3LUL2aZ+NXElyn+pxh62XlbDRds3WBgKJVjYxQZQ=; b=c6anVoD1kPRoAL9oDvqbZ5XwW/nVeBK49oJ/Wo4wsljBp2n800iy0Vwn Yw0Ockzc0M5PZidJqfhheFlaVdT+DgqcdaK7zuuVLCFtCmXbbRGGMl2Rt cR5NU+EwMZfMmNKPQU9b0j0SzZKS1IOt0dQWa9DTub+oz/l/4LGB5mq/S M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DRAABtk7tZ/5ldJa1dGgEBAQECAQEBAQgBAQEBgm9rZG4nB4NwiiCPcYF0kGiFQIISCoU8AhqEDz8YAQIBAQEBAQEBayiFGAEBAQQjClwCAQgRBAEBKAMCAgIwFAkIAgQBEgiJR2SrVIInizEBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgyuCAoFQhQuFLoJdgmAFoQIClEeSf5UEAhEZAYE4AR84QUx3FYdmdogEgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.42,396,1500940800"; d="scan'208,217";a="295723887"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Sep 2017 08:49:24 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v8F8nOSI024994 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 15 Sep 2017 08:49:24 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 15 Sep 2017 03:49:23 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1263.000; Fri, 15 Sep 2017 03:49:23 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: kotesh <kotesh.chundu@gmail.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Reg BGP LS identifier for different ISIS levels
Thread-Index: AQHTKG8HNDohZECAw0m2I4obkXfL06K1rQEw
Date: Fri, 15 Sep 2017 08:49:23 +0000
Message-ID: <8d8be83d73da4e5892780416b0fe56d2@XCH-ALN-008.cisco.com>
References: <CAFUqOdwi90gqdO8mCJLJTK0kyY4GVnq3A3PPmbzQZrWWudj3PA@mail.gmail.com>
In-Reply-To: <CAFUqOdwi90gqdO8mCJLJTK0kyY4GVnq3A3PPmbzQZrWWudj3PA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.93.151]
Content-Type: multipart/alternative; boundary="_000_8d8be83d73da4e5892780416b0fe56d2XCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0RAqW3fE6QZNbP8FHdQNNq0UWTU>
Subject: Re: [Idr] Reg BGP LS identifier for different ISIS levels
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Sep 2017 08:49:27 -0000

Hi Kotesh,

The BGP-LS Identifier is meant for when dealing with multiple ISIS protocol instances. If you have a ISIS protocol instance with L1 and L2 levels, they will share the same BGP-LS identifier.

Thanks,
Ketan

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of kotesh
Sent: 08 September 2017 12:22
To: idr@ietf.org
Subject: [Idr] Reg BGP LS identifier for different ISIS levels

Hi,
 Is it mandatory to configure different BGP LS identfier for different ISIS levels under a given AS? What are the implications if we configure same BGP LS identifier in different ISIS levels?

Thanks,
Kotesh babu.Chundu

v2.23.0 | Report a Bug | By Email