IETF Logo Mail Archive

Re: [OSPF] draft-ietf-ospf-segment-routing-extensions-03

Shraddha Hegde <shraddha@juniper.net> Thu, 18 December 2014 05:08 UTC

Return-Path: <shraddha@juniper.net>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BA21A01AA; Wed, 17 Dec 2014 21:08:33 -0800 (PST)
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 llpNGCM0wBEM; Wed, 17 Dec 2014 21:08:30 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0732.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765FC1A01A9; Wed, 17 Dec 2014 21:08:30 -0800 (PST)
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) by BY1PR0501MB1382.namprd05.prod.outlook.com (25.160.107.140) with Microsoft SMTP Server (TLS) id 15.1.36.22; Thu, 18 Dec 2014 05:08:07 +0000
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) by BY1PR0501MB1381.namprd05.prod.outlook.com ([25.160.107.139]) with mapi id 15.01.0049.002; Thu, 18 Dec 2014 05:08:06 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: Peter Psenak <ppsenak@cisco.com>, "rob.shakir@bt.com" <rob.shakir@bt.com>, "draft-ietf-ospf-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-segment-routing-extensions@tools.ietf.org>
Thread-Topic: draft-ietf-ospf-segment-routing-extensions-03
Thread-Index: AdAW/kuWGscufT8EQDeA0Yv5U29aiwAi7qSAAGZ5RmAACscGgAABGydwAAHhR4AAF+92MAAE7zeAAAFQ+jAAA7cVgAAne0cA
Date: Thu, 18 Dec 2014 05:08:06 +0000
Message-ID: <BY1PR0501MB13812DF01ADCC4B2F1C358D3D56A0@BY1PR0501MB1381.namprd05.prod.outlook.com>
References: <BY1PR0501MB13814F720E08CE2F7F36BE44D56C0@BY1PR0501MB1381.namprd05.prod.outlook.com> <D0B60FCD.70368%rob.shakir@bt.com> <BY1PR0501MB13811178FB2F413C670A0B45D56C0@BY1PR0501MB1381.namprd05.prod.outlook.com> <54907493.8030800@cisco.com> <BY1PR0501MB13810327100BBA41ECEFA68DD56D0@BY1PR0501MB1381.namprd05.prod.outlook.com> <54913651.2050600@cisco.com> <BY1PR0501MB1381EE162C9D448F4CC978B6D56D0@BY1PR0501MB1381.namprd05.prod.outlook.com> <54915815.2050102@cisco.com>
In-Reply-To: <54915815.2050102@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.17]
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1382;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1382;
x-forefront-prvs: 042957ACD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(479174004)(24454002)(189002)(51704005)(377454003)(199003)(13464003)(230783001)(76576001)(99286002)(101416001)(120916001)(2950100001)(107046002)(105586002)(106356001)(2501002)(97736003)(46102003)(31966008)(102836002)(2900100001)(68736005)(33656002)(99396003)(50986999)(122556002)(92566001)(77156002)(86362001)(54356999)(76176999)(2201001)(19580395003)(62966003)(54606007)(21056001)(40100003)(93886004)(64706001)(20776003)(66066001)(87936001)(54206007)(4396001)(19580405001)(2656002)(74316001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1382; H:BY1PR0501MB1381.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2014 05:08:06.7340 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1382
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/QXBCF16FIJxT2nixB4IKdfDG078
Cc: "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [OSPF] draft-ietf-ospf-segment-routing-extensions-03
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 05:08:33 -0000

OK. Sounds good.

Rgds
Shraddha

-----Original Message-----
From: Peter Psenak [mailto:ppsenak@cisco.com] 
Sent: Wednesday, December 17, 2014 3:47 PM
To: Shraddha Hegde; rob.shakir@bt.com; draft-ietf-ospf-segment-routing-extensions@tools.ietf.org
Cc: ospf@ietf.org; isis-wg@ietf.org
Subject: Re: draft-ietf-ospf-segment-routing-extensions-03

Shraddha,

On 12/17/14 09:51 , Shraddha Hegde wrote:
> <Shraddha> Lets say set  S1 has some characteristic  "X" and set S2 has characteristic "Y".
>  Lets say we want to build explicit routed label stack which says " give me load balancing path using links with characteristic X".
>
> Lets say there is another set of nodes R3 and R4 and similar S1 and S2 
> bundles on them and R3 advertising label 30 and 40 for S1 and S2 Respectively. Labels are local to the nodes and we cannot use labels to identify what characteristic or set they stand for.
>
> To satisfy the constraint whether to use label 10
> Or 20 on R1 and whether to use 30 or 40 is a problem. The application which is trying to build the label stack cannot identify which label to use from R1 and R3 because there are              sets and labels but which label  Represents which set is missing.
> If there is an identifier for the set and this identifier comes with label it can be done easily.

If I understand you correctly, what you want to color links based on the link characteristics - e.g. you want to associate link with a group
(color) and group (color) to have global significance.

Sure, you can do that, but I do not see a direct relationship to SR, e.g. I would not add the group-id to the Adj-SID sub-TLV. You can define a new sub-TLV for the group-id distribution and advertise it in the Extended link TLV.

thanks,
Peter

v2.23.0 | Report a Bug | By Email