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

Peter Psenak <ppsenak@cisco.com> Wed, 17 December 2014 10:16 UTC

Return-Path: <ppsenak@cisco.com>
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 D05FE1A887E; Wed, 17 Dec 2014 02:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 XlwxAUR9Objv; Wed, 17 Dec 2014 02:16:55 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CA4A1A701C; Wed, 17 Dec 2014 02:16:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1432; q=dns/txt; s=iport; t=1418811415; x=1420021015; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=qKCmb231B1e1RwYdrPDufYC9UNct+jXNfJM8pBpbFi0=; b=LOauVm/3JWPWKku3Ed8XQ5wcvAecKStXR9Pn1Sv73J71xaYsVOjQnL75 Ui4mF3tZkG0Ob7z5aWjaJDpBMVenvVDCWI0GU3bysnhkoEgT2REtOQBGE e5qSPRGgwHSuGiLJohPFfG+8GO6U/Tkg2nLQTzH/hZPmyvs8cNbvC+p5V o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYEAPtWkVStJssW/2dsb2JhbABQCs1Kgk0CgTMBAQEBAX2EDQEBBDg6BgEQCxgJFg8JAwIBAgFFBgEMAQcBAYgo1BsBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjxZcB4QpAQSWeIV8i0Qig209gnQBAQE
X-IronPort-AV: E=Sophos;i="5.07,593,1413244800"; d="scan'208";a="273310890"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 17 Dec 2014 10:16:53 +0000
Received: from [10.148.128.133] ([10.148.128.133]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id sBHAGrX5010092; Wed, 17 Dec 2014 10:16:53 GMT
Message-ID: <54915815.2050102@cisco.com>
Date: Wed, 17 Dec 2014 11:16:53 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Shraddha Hegde <shraddha@juniper.net>, "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>
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>
In-Reply-To: <BY1PR0501MB1381EE162C9D448F4CC978B6D56D0@BY1PR0501MB1381.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/g8mIKQwsP-Uh3v8SD-2I9rCV6ho
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: Wed, 17 Dec 2014 10:16:57 -0000

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