Re: [Isis-wg] How to handle multiple overlapping SRGB ranges

Pushpasis Sarkar <psarkar@juniper.net> Thu, 25 June 2015 13:47 UTC

Return-Path: <psarkar@juniper.net>
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 C5C291A88D9 for <isis-wg@ietfa.amsl.com>; Thu, 25 Jun 2015 06:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Glp2GsLFxe3u for <isis-wg@ietfa.amsl.com>; Thu, 25 Jun 2015 06:47:40 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0724.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:724]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D03BB1A88D1 for <isis-wg@ietf.org>; Thu, 25 Jun 2015 06:47:39 -0700 (PDT)
Received: from BLUPR05MB1969.namprd05.prod.outlook.com (10.162.224.23) by BLUPR05MB1969.namprd05.prod.outlook.com (10.162.224.23) with Microsoft SMTP Server (TLS) id 15.1.195.15; Thu, 25 Jun 2015 13:47:24 +0000
Received: from BLUPR05MB1969.namprd05.prod.outlook.com ([10.162.224.23]) by BLUPR05MB1969.namprd05.prod.outlook.com ([10.162.224.23]) with mapi id 15.01.0195.005; Thu, 25 Jun 2015 13:47:24 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "isis-wg@ietf.org list" <isis-wg@ietf.org>
Thread-Topic: [Isis-wg] How to handle multiple overlapping SRGB ranges
Thread-Index: AQHQr013t1K7+i0/iUyxxlSOTpbr8A==
Date: Thu, 25 Jun 2015 13:47:23 +0000
Message-ID: <D1B202A7.29CA9%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.2.150604
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [116.197.184.10]
x-microsoft-exchange-diagnostics: 1; BLUPR05MB1969; 5:WXXYUhCBCb4vVIDTyQmbP/nHH+YDoYD11UMcaMoS+qxvKTPrsLxcLYDOMuvuierbFA6j4tmozofEjIM2jBaFZuTr38RGhTXNvm74DtEce95C91L0svdqqMHZBC6esVyaoS0nBuQZvRawBWUUHeFPCg==; 24:GUbdTbBnJy9KxJyu6/0rqVyhCelCrb9nGqW6WR3yH/oVq1BqecMCKEedNimKTwamBOi12u6viD/6PGw3XDGjqptitI6/JtnMLF1KOXKzm54=; 20:PFUswrkZObIgqmmaev2Xph7Erjrozj7AaGm3YZwpElNGuHVkqSkwCLCFEyYOOyx+ozMcRBz9qiesGsom/gZsew==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB1969;
x-microsoft-antispam-prvs: <BLUPR05MB196918E5CC46805AD44A1550BCAE0@BLUPR05MB1969.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BLUPR05MB1969; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB1969;
x-forefront-prvs: 0618E4E7E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(52044002)(377454003)(51704005)(479174004)(83506001)(102836002)(15975445007)(77156002)(77096005)(122556002)(66066001)(40100003)(2900100001)(62966003)(189998001)(107886002)(5001960100002)(92566002)(5002640100001)(87936001)(2656002)(46102003)(86362001)(19580405001)(19580395003)(54356999)(50986999)(106116001)(99286002)(4001350100001)(36756003)(5001770100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB1969; H:BLUPR05MB1969.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8FD3A319D087014F841E0AEFDB48C570@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jun 2015 13:47:23.8896 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB1969
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/fLbKJH4aLsiXFHabaAkSsYHe2IA>
Subject: Re: [Isis-wg] How to handle multiple overlapping SRGB ranges
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: Thu, 25 Jun 2015 13:47:41 -0000

Hi Stefano,

On 6/25/15, 7:07 PM, "Isis-wg on behalf of Stefano Previdi (sprevidi)"
<isis-wg-bounces@ietf.org on behalf of sprevidi@cisco.com> wrote:

>All,
>
>there's an open question that requires the wg to agree
>
>The issue here is related to SRGB ranges advertised within the
>SR-Cap SubTLV.
>
>The question is: what a receiving router should do when
>receiving SRGB ranges that overlaps ?
>
>Knowing that the spec mandates a single SR-Cap SubTLV, the
>overlap may happen only within the same SR-Cap subTLV and
>therefore it is clearly a local misconfiguration or an
>implementation bug in the router originating the SR-Cap.
>
>Personally, I would recommend to ignore the whole SRGB (not
>only the overlapping ranges) from the faulty router. Ignoring
>only the overlapping ranges would not work since the whole
>index space is affected anyway.
[Pushpasis] I would agree with you on this. A receiving router receiving
such SR-Cap SubTLV should ignore the total SR-Cap SubTLV and consider the
originating as SR-incapable. Mandating this behavior should remove all
forms of ambiguity and keep implementation simple. I would also like the
receiving router to generate some kind of error message notifying the
receipt of such SR-Cap Sub-TLV. But I would leave it as a implementation
choice.

Thanks
-Pushpasis

>
>There are different opinions on how the receiving router should
>behave. Ideally, we should converge towards a single solution so
>feel free to comment.
>
>Thanks.
>s.
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www.ietf.org/mailman/listinfo/isis-wg