IETF Logo Mail Archive

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

Peter Psenak <ppsenak@cisco.com> Sun, 14 December 2014 10:38 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 8F8F71A6F32 for <ospf@ietfa.amsl.com>; Sun, 14 Dec 2014 02:38:01 -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 awjthJ_IsDlU for <ospf@ietfa.amsl.com>; Sun, 14 Dec 2014 02:38:00 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B9BA1A6F30 for <ospf@ietf.org>; Sun, 14 Dec 2014 02:37:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=901; q=dns/txt; s=iport; t=1418553479; x=1419763079; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pE00Lc8pVQRLp74RSTWgOE2oEd6LLB2NsVWEERQVG2U=; b=i4T1reWJWfyPIPmlTXeW33hN/W+14fKhYnb+G2eE5TCXxhQ9BKnYgS97 UbRHtU5YVtpf6ZA4W4q9QQUmSVa5WpfjiJqCgufBy+CiC4cv1rg1uZ/a1 mQ8G7CfGrCaAkj8uUklFGrL8POk1J0TjPrTz+PDbO9GOts4sWwE16yzMf M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqYEAGpnjVStJssW/2dsb2JhbABazS6CTQKBJwEBAQEBfYQNAQEEMgEFQAEQCxgJFg8JAwIBAgFFBgEMAQcBAYgo0GEBAQEBAQEBAQEBAQEBAQEBAQEBARiPcgeEKQEElnGFeYs+IoNtPYJzAQEB
X-IronPort-AV: E=Sophos;i="5.07,574,1413244800"; d="scan'208";a="274000073"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 14 Dec 2014 10:37:57 +0000
Received: from [10.55.51.197] (ams-ppsenak-8714.cisco.com [10.55.51.197]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sBEAbv1E029776; Sun, 14 Dec 2014 10:37:57 GMT
Message-ID: <548D6885.1060001@cisco.com>
Date: Sun, 14 Dec 2014 11:37:57 +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>, "draft-ietf-ospf-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-segment-routing-extensions@tools.ietf.org>
References: <BY1PR0501MB1381D2E0190364379D1752B1D5610@BY1PR0501MB1381.namprd05.prod.outlook.com>
In-Reply-To: <BY1PR0501MB1381D2E0190364379D1752B1D5610@BY1PR0501MB1381.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/FHOlyZWORrwHuQLndz93wovvtKw
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: Sun, 14 Dec 2014 10:38:01 -0000

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