IETF Logo Mail Archive

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

Shraddha Hegde <shraddha@juniper.net> Tue, 16 December 2014 16:34 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 78D3E1A1BE1 for <ospf@ietfa.amsl.com>; Tue, 16 Dec 2014 08:34:35 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 qbjDL1IIblAX for <ospf@ietfa.amsl.com>; Tue, 16 Dec 2014 08:34:33 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0126.outbound.protection.outlook.com [207.46.100.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4C8D1A1BD9 for <ospf@ietf.org>; Tue, 16 Dec 2014 08:34:33 -0800 (PST)
Received: from BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) by BY1PR0501MB1381.namprd05.prod.outlook.com (25.160.107.139) with Microsoft SMTP Server (TLS) id 15.1.31.17; Tue, 16 Dec 2014 16:34:32 +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.0031.000; Tue, 16 Dec 2014 16:34:32 +0000
From: Shraddha Hegde <shraddha@juniper.net>
To: Peter Psenak <ppsenak@cisco.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/kuWGscufT8EQDeA0Yv5U29aiwAi7qSAAGZ5RmA=
Date: Tue, 16 Dec 2014 16:34:32 +0000
Message-ID: <BY1PR0501MB13814F720E08CE2F7F36BE44D56C0@BY1PR0501MB1381.namprd05.prod.outlook.com>
References: <BY1PR0501MB1381D2E0190364379D1752B1D5610@BY1PR0501MB1381.namprd05.prod.outlook.com> <548D6885.1060001@cisco.com>
In-Reply-To: <548D6885.1060001@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.19]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1381;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1381;
x-forefront-prvs: 04270EF89C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51704005)(377454003)(189002)(199003)(24454002)(13464003)(479174004)(87936001)(74316001)(40100003)(21056001)(86362001)(54356999)(50986999)(120916001)(105586002)(33656002)(101416001)(99396003)(122556002)(92566001)(62966003)(31966008)(2950100001)(54606007)(2900100001)(77156002)(2656002)(19580395003)(19580405001)(106356001)(76176999)(20776003)(64706001)(54206007)(107046002)(230783001)(4396001)(97736003)(66066001)(99286002)(76576001)(46102003)(102836002)(68736005); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1381; 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
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/MYAttCqFwy5HwPAaNpUQiYwKmdA
Cc: OSPF WG List <ospf@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: Tue, 16 Dec 2014 16:34:35 -0000

Peter,

An extended link LSA can contain multiple adj-sid labels with "s bit" set.
During graceful restart , when self generated LSAs are learnt from neighbors,
A handle is required to associate the set label with the bundle.

I think a group-id field along with set label would serve the purpose.

Rgds
Shraddha
-----Original Message-----
From: Peter Psenak [mailto:ppsenak@cisco.com] 
Sent: Sunday, December 14, 2014 4:08 PM
To: Shraddha Hegde; draft-ietf-ospf-segment-routing-extensions@tools.ietf.org
Cc: OSPF WG List
Subject: Re: draft-ietf-ospf-segment-routing-extensions-03

Shraddha,

the idea is that you can assign the same Adj-SID to multiple links. That way you can create multiple sets as you need.

thanks,
Peter


On 12/13/14 19:19 , Shraddha Hegde wrote:
> Authors,
>
>          When there are multiple parallel links between two nodes, it 
> is useful to
>
> Group them into different bundles and use each bundle for load-balancing
>   for different traffic flows.
>
> What we have in adjacency sid is just a flag to indicate that the 
> label is a "set label" by setting a flag
>
> In adj-sid TLV. It serves the purpose when all the parallel links  are 
> in one bundle but not sufficient when
>
> There can be different bundles and different labels for each of them.
>
> An identifier for the group, probably "group-id" is needed to 
> associate the label with the interface group.
>
> Any thoughts on this?
>
> Rgds
>
> Shraddha
>

v2.23.0 | Report a Bug | By Email