Re: [Isis-wg] some questions for SR-ISIS

Pushpasis Sarkar <psarkar@juniper.net> Wed, 22 April 2015 12:02 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 184DB1B34FB; Wed, 22 Apr 2015 05:02:38 -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 LlAoskzyjLGf; Wed, 22 Apr 2015 05:02:35 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0742.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:742]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4907B1B34FD; Wed, 22 Apr 2015 05:02:00 -0700 (PDT)
Received: from DM2PR0501MB1248.namprd05.prod.outlook.com (25.160.130.139) by DM2PR0501MB889.namprd05.prod.outlook.com (10.242.173.152) with Microsoft SMTP Server (TLS) id 15.1.136.25; Wed, 22 Apr 2015 12:01:41 +0000
Received: from DM2PR0501MB1245.namprd05.prod.outlook.com (25.160.130.11) by DM2PR0501MB1248.namprd05.prod.outlook.com (25.160.130.139) with Microsoft SMTP Server (TLS) id 15.1.148.16; Wed, 22 Apr 2015 12:01:41 +0000
Received: from DM2PR0501MB1245.namprd05.prod.outlook.com ([25.160.130.11]) by DM2PR0501MB1245.namprd05.prod.outlook.com ([25.160.130.11]) with mapi id 15.01.0148.008; Wed, 22 Apr 2015 12:01:41 +0000
From: Pushpasis Sarkar <psarkar@juniper.net>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "peng.shaofu@zte.com.cn" <peng.shaofu@zte.com.cn>
Thread-Topic: [Isis-wg] some questions for SR-ISIS
Thread-Index: AQHQfPQXjLsy8vMF6EGmvt864Gul2A==
Date: Wed, 22 Apr 2015 12:01:40 +0000
Message-ID: <D15D8839.25B53%psarkar@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.9.150325
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [116.197.184.12]
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1248; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB889;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(24454002)(377454003)(479174004)(92566002)(2656002)(5890100001)(2501003)(122556002)(87936001)(46102003)(40100003)(36756003)(4001350100001)(86362001)(66066001)(2900100001)(19580405001)(19580395003)(83506001)(102836002)(15975445007)(54356999)(50986999)(106116001)(5001770100001)(77156002)(99286002)(62966003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1248; H:DM2PR0501MB1245.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-microsoft-antispam-prvs: <DM2PR0501MB1248999EF0A601BE06C8C8E7BCEE0@DM2PR0501MB1248.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:DM2PR0501MB1248; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1248;
x-forefront-prvs: 0554B1F54F
Content-Type: text/plain; charset="iso-2022-jp"
Content-ID: <9160819B51F9CE4FB39ECDB0B1CC34CC@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2015 12:01:40.9689 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1248
X-OriginatorOrg: juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/BbGt6rZt8iudnUrygEZ-iFDDtjU>
Cc: "spring@ietf.org" <spring@ietf.org>, "isis-wg@ietf.org list" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] some questions for SR-ISIS
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: <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, 22 Apr 2015 12:02:38 -0000

Hi Deccan,

On 4/22/15, 4:23 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

><adding isis list>
>
>Hi Deccan,
>
>On Apr 20, 2015, at 6:03 AM, peng.shaofu@zte.com.cn wrote:
>> 
>> hi Stefano and other SR-ISIS authors,
>> 
>> I have some questions when study
>>draft-ietf-isis-segment-routing-extensions-03
>> 
>> 1) for Prefix-SID Sub-TLV
>> It seems that we cannot support Prefix-SID Propagation with local label
>>inside the level, because each node cannot change the received flooding
>>information such as the label value before it propagate again, otherwise
>>packet inconsistency will occur in some remote nodes.
>> So, the only way to create the SR LSP inside the level is to advertise
>>prefix-sid with INDEX type.
>
>
>indeed. note that since most of the implementors agreed to use the same
>SRGB space for SR, we're pretty close to the concept of global labels...
>oops, no, sorry, I went too far...
>
>
>> Another way may directly advertise global label,
>
>
>you said that, not me... ;-)
>
>
>> but it's not appropriate for distribution network.
>
>
>"not appropriate", yes, let's put it this way...
>
>
>> In the case of propagation between levels, although in the document it
>>says the level-1-2 router can change the flooding information, but the
>>same problem is there, the total SR LSP can not be building with local
>>label advertisement.
>> Is it right? 
>
>
>ok, jokes apart, the reason why indexes have been defined is to cope with
>the local scope of mpls labels. I think it's good not to brake an
>architecture but I also think it's good to focus on practical problems to
>solve and the index gives you the best of both worlds: they don't brake
>mpls architecture and allows you to play with global (index) values.
>
>
>> 2) for Adj-SID Sub-TLV
>> In the document is says that an adjacency-sid can set the S-flagļ¼Œbut it
>>is possible that an adjacency can join many adjacency group. It is
>>difficult for the ingress node to process the received Adj-SID Sub-TLV
>>for the same specific remote adjacency with different  adjacency-sid
>>value with S-flag set, whether adj-sid 200 can overwrite adj-sid 100 or
>>they indicate different groups?
>> It seems that we need add ADJACENCY-GROUP-NAME information in the
>>Adj-SID Sub-TLV. 
>> Is it right? 
>
>
>sorry, I'm not sure I understand your point. The S bit tells you that the
>value may be shared among other adjacencies. This will tell you what you
>call "group".
>
>s.
[Pushpasis] I think you are trying to refer to a case where the same
adjacency is part of two adjacency-sets. I guess the same adjacency will
advertise 3 adjacency-sids, one for the indvidual link itself (S-Flag set
to 0) and one for each adjacency sets it belongs to (S-Flag set to 1). The
adjacency-sids in this cases will be additive and not overwrite each
other. The Adjacency-SID associated with adjacency set itself will act as
the group-identifier. There should not be a separate name needed. The same
Adjacency-SID will be advertised by all adjacencies that are part of it.

So if are 3 adjacencies A1, A2, A3 with individual sids 100, 200, 300
respectively. And there are following two Adjacency sets

Set 1: adjacencies A1 and A2, SID: 1000
Set 2: adjacencies A2 and A3, SID: 2000

Then following are the adjacency-Sids advertised by each adjacencies

A1: 100(S=0), 1000(S=1),
A2: 200(S=0), 1000(S=1), 2000(S=1)
A3: 300(S=0), 2000(S=1)

Hope my understanding was correct :)

>
>
>> 
>> Regards, 
>> 
>> deccan 
>> 
>> 
>> 
>> 
>> 
>> 
>> --------------------------------------------------------
>> ZTE Information Security Notice: The information contained in this mail
>>(and any attachment transmitted herewith) is privileged and confidential
>>and is intended for the exclusive use of the addressee(s).  If you are
>>not an intended recipient, any disclosure, reproduction, distribution or
>>other dissemination or use of the information contained is strictly
>>prohibited.  If you have received this mail in error, please delete it
>>and notify us immediately.
>> 
>> 
>> 
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www.ietf.org/mailman/listinfo/isis-wg