Re: [Idr] Reg BGP LS identifier for different ISIS levels
"Acee Lindem (acee)" <acee@cisco.com> Fri, 15 September 2017 15:54 UTC
Return-Path: <acee@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 B0021132D4B for <idr@ietfa.amsl.com>; Fri, 15 Sep 2017 08:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.02
X-Spam-Level:
X-Spam-Status: No, score=-14.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, 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 KLTWCGYDgyCs for <idr@ietfa.amsl.com>; Fri, 15 Sep 2017 08:54:40 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49030132713 for <idr@ietf.org>; Fri, 15 Sep 2017 08:54:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2690; q=dns/txt; s=iport; t=1505490880; x=1506700480; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=eB4XAaC4inYooIsGygj228tlqlhf2Pysez1R7DyxK2s=; b=CVm7Rz6UkgnumI44im+dsrMLGGkuhycMpa4846TMRFmn4Z5v/z+JA8Fp a9aAGunPcPHBZ7hqWcAaB/pha/J8hqDxTX3eBnqXYe5M2UaWA8hjNIfut kvmJ6u0bgRCZAILamkHgyzZHmnylYlHCEPt2wQLEVsuCmkx6ri5AHCQPt s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+AQDg9rtZ/4ENJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1qBUicHg26aE4F0iDuPfgqFPAIahBBXAQIBAQEBAQJrKIUYAQEBAQMjEVUCAQgRAwEBAQMCIwMCAgIfERQBCAgCBAESihsDFawRgieHNw2DagEBAQEBAQEBAQEBAQEBAQEBAQEfgQ6CHYICgzIBgyiCWIIgJoJtgmAFigqWPjwCj1yEd5J4jFmILAIRGQGBOAFXgQ13FUmHHHaIAoEPAQEB
X-IronPort-AV: E=Sophos;i="5.42,397,1500940800"; d="scan'208";a="4025747"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Sep 2017 15:54:39 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v8FFsda0006195 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 15 Sep 2017 15:54:39 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 15 Sep 2017 11:54:38 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1263.000; Fri, 15 Sep 2017 11:54:38 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, kotesh <kotesh.chundu@gmail.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Reg BGP LS identifier for different ISIS levels
Thread-Index: AQHTKG8I+PllFX3Ry0yl2EKhlbZcU6K18T6AgAAzuYA=
Date: Fri, 15 Sep 2017 15:54:38 +0000
Message-ID: <D5E16EE7.C8135%acee@cisco.com>
References: <CAFUqOdwi90gqdO8mCJLJTK0kyY4GVnq3A3PPmbzQZrWWudj3PA@mail.gmail.com> <8d8be83d73da4e5892780416b0fe56d2@XCH-ALN-008.cisco.com>
In-Reply-To: <8d8be83d73da4e5892780416b0fe56d2@XCH-ALN-008.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.117.47]
Content-Type: text/plain; charset="utf-8"
Content-ID: <29948D0B807E314CB9294C8B6945FB1B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/16ClECU5b8fHwTUL6fwpCyZTDMA>
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 15:54:42 -0000
Hi Kotesh,
Furthermore, note that the Protocol ID in the NLRI can be used to
discriminate between IS-IS level 1 and IS-IS level 2 (which is all that is
needed for single instance of IS-IS). The Protocol-ID field can contain
one of the following values (from RFC 7752):
+-------------+----------------------------------+
| Protocol-ID | NLRI information source protocol |
+-------------+----------------------------------+
| 1 | IS-IS Level 1 |
| 2 | IS-IS Level 2 |
| 3 | OSPFv2 |
| 4 | Direct |
| 5 | Static configuration |
| 6 | OSPFv3 |
+-------------+----------------------------------+
Table 2: Protocol Identifiers
Hope this helps,
Acee
From: Idr <idr-bounces@ietf.org> on behalf of "Ketan Talaulikar (ketant)"
<ketant@cisco.com>
Date: Friday, September 15, 2017 at 4:49 AM
To: kotesh <kotesh.chundu@gmail.com>, IDR List <idr@ietf.org>
Subject: Re: [Idr] Reg BGP LS identifier for different ISIS levels
>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
- [Idr] Reg BGP LS identifier for different ISIS le… kotesh
- Re: [Idr] Reg BGP LS identifier for different ISI… Ketan Talaulikar (ketant)
- Re: [Idr] Reg BGP LS identifier for different ISI… Acee Lindem (acee)