IETF Logo Mail Archive

Re: [Isis-wg] Conflicting MS entries

"Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com> Fri, 19 June 2015 18:18 UTC

Return-Path: <mustapha.aissaoui@alcatel-lucent.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE091ACE9D; Fri, 19 Jun 2015 11:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 tVWc4hsIBeGz; Fri, 19 Jun 2015 11:18:45 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8EB91ACE9B; Fri, 19 Jun 2015 11:18:45 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (unknown [135.5.2.66]) by Websense Email Security Gateway with ESMTPS id 07FE4E1E3EA0D; Fri, 19 Jun 2015 18:18:38 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id t5JIIffA020371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Jun 2015 18:18:41 GMT
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.190]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Fri, 19 Jun 2015 14:18:41 -0400
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, DECRAENE Bruno IMT/OLN <bruno.decraene@orange.com>
Thread-Topic: Conflicting MS entries
Thread-Index: AQHQqFgIw0yxX2QFqkW6a4BJLQOJuJ2wTXowgAB4/oD///jw4IABHlUQgAABNmCAAbGpwIAAjYgw
Date: Fri, 19 Jun 2015 18:18:40 +0000
Message-ID: <4A79394211F1AF4EB57D998426C9340D94855471@US70UWXCHMBA01.zam.alcatel-lucent.com>
References: <AACFE588-60A1-4652-940A-F127F4845558@cisco.com> <5862_1434530566_55813306_5862_129_1_0719486d-2955-432f-b6fd-44650477256f@OPEXCLILM24.corporate.adroot.infra.ftgroup> <885458B9-75C8-4654-9B12-EF1DC4D30277@cisco.com> <28410_1434552838_55818A06_28410_37_1_46370f62-b81b-4b0c-a50c-2e0aa0acd8c3@OPEXCLILM32.corporate.adroot.infra.ftgroup> <31285_1434612154_558271BA_31285_253_2_7f802e17-6d95-49f0-97e3-edf29a0302dd@OPEXCLILM33.corporate.adroot.infra.ftgroup> <31293_1434612559_5582734F_31293_5808_12_0e15d1df-4591-4e0e-9e6e-a894e1b560c2@OPEXCLILMA1.corporate.adroot.infra.ftgroup> <22234_1434705452_5583DE2C_22234_4536_1_0d3ef822-b1fc-49b5-85d7-ecc8c0ccc710@OPEXCLILM22.corporate.adroot.infra.ftgroup>
In-Reply-To: <22234_1434705452_5583DE2C_22234_4536_1_0d3ef822-b1fc-49b5-85d7-ecc8c0ccc710@OPEXCLILM22.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/rFlU9ELTbnmIDhervr_BZ6YuD_I>
X-Mailman-Approved-At: Mon, 22 Jun 2015 04:22:21 -0700
Cc: "spring@ietf.org" <spring@ietf.org>, "isis-wg@ietf.org list" <isis-wg@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: Re: [Isis-wg] Conflicting MS entries
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 19 Jun 2015 18:18:47 -0000

Hi Stephane and Bruno,
I do not think programming multiple SIDs makes sense. While there are multiple MS prefix sub-TLVs, there is only single active route for the prefix with potentially ECMP next-hops which was resolved from a received IP reachability TLV.

I agree that selecting one of the entries is preferable to dropping traffic. We could come up with selection criteria but the reality is that there no way for the router to check if any of the MS entries is legitimate or not. As a result, I would think that once an entry is selected based on the criteria and programmed, we should not be changing it unless the MS entry is withdrawn.

Mustapha.

> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of
> stephane.litkowski@orange.com
> Sent: Friday, June 19, 2015 5:17 AM
> To: DECRAENE Bruno IMT/OLN; Stefano Previdi (sprevidi)
> Cc: spring@ietf.org; isis-wg@ietf.org list
> Subject: Re: [spring] Conflicting MS entries
> 
> Even if choosing any IP to MPLS entry does not break anything, I'm not sure this is
> a good idea from an operational point of view to let it undeterministic.
> 
> 
> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of
> bruno.decraene@orange.com
> Sent: Thursday, June 18, 2015 09:29
> To: LITKOWSKI Stephane SCE/IBNF; Stefano Previdi (sprevidi)
> Cc: spring@ietf.org; isis-wg@ietf.org list
> Subject: Re: [spring] Conflicting MS entries
> 
> Hi Stéphane,
> 
> > From: stephane.litkowski@orange.com> Sent: Thursday, June 18, 2015
> > 9:23 AM
> >
> > Hi Bruno,
> >
> > "	 1) I don't really the issue. From a forwarding standpoint, looks like
> > we can simply program multiple SIDs in the FIB."
> >
> > [SLI] What about the IP to MPLS entry ?
> 
> [Bruno] If transit LSRs install all SIDs, an ingress may use any SID, no? Local
> decision.
> 
> Bruno
> 
> 
> 
> ____________________________________________________________________

v2.23.0 | Report a Bug | By Email