Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00
Uma Chunduri <uma.chunduri@ericsson.com> Tue, 18 November 2014 20:51 UTC
Return-Path: <uma.chunduri@ericsson.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2F61A8997 for <idr@ietfa.amsl.com>; Tue, 18 Nov 2014 12:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 gspJrbfLEavl for <idr@ietfa.amsl.com>; Tue, 18 Nov 2014 12:51:15 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF5E21A8910 for <idr@ietf.org>; Tue, 18 Nov 2014 12:51:14 -0800 (PST)
X-AuditID: c618062d-f79206d0000014d2-13-546b583571b1
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id DD.3E.05330.5385B645; Tue, 18 Nov 2014 15:31:18 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0174.001; Tue, 18 Nov 2014 15:51:12 -0500
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: Hannes Gredler <hannes@juniper.net>, Ahmed Bashandy <bashandy@cisco.com>
Thread-Topic: [Idr] draft-keyupate-idr-bgp-prefix-sid-00
Thread-Index: AQHP/7iBRq0AzkPp0EOBA2uEewseHJxg+80AgAYI2AD//9tvsA==
Date: Tue, 18 Nov 2014 20:51:11 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F442CE6@eusaamb105.ericsson.se>
References: <D08AB1D4.79199%jeff.tantsura@ericsson.com> <546676FA.8020005@cisco.com> <20141118175026.GA16957@hannes-mba.local>
In-Reply-To: <20141118175026.GA16957@hannes-mba.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFLMWRmVeSWpSXmKPExsUyuXRPlK5ZRHaIwfUjPBbHNl9ksei/94TN 4tXtZ0wOzB5Tfm9k9Viy5CeTx/Wmq+wBzFFcNimpOZllqUX6dglcGSu73rIWfFKq+NO7hbmB 8aFUFyMnh4SAicTzth9sELaYxIV764FsLg4hgSOMEvcvzmUGSQgJLGeUeLpPBcRmE9CT+Dj1 JzuILSLgIzFzQhNYM7OAosTFvx1MILawgLnE+5sQQ0UELCTuz/7FDGE7SfyZ/A8sziKgKvH/ +0Wwel4BX4k/K86wQexqYJT4/EMWxOYUMJNY+HkmK4jNCHTc91NrmCB2iUvcejKfCeJoAYkl e84zQ9iiEi8f/2OFsJUkJi09xwpRryOxYPcnqDu1JZYtfM0MsVdQ4uTMJywTGMVmIRk7C0nL LCQts5C0LGBkWcXIUVqcWpabbmSwiREYOcck2HR3MO55aXmIUYCDUYmHd4NrVogQa2JZcWXu IUZpDhYlcd5ZtfOChQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTBO/OZ7x1+MWY6tPEQ2u/Ds l3nfNJZ7sYrYHVhtVtLutr6w1E/2woyG5q2SIle3FyVWTTqhIHawvv52U88sgSWTD/dOihb6 5pu7KUjt4Q7je+c3H6ydHRPvnVtcOKf549WWhDWXak4as+2Om7evO138TvuJ0Jtvbl7561c/ 0ck4Z9LCzaueqicpsRRnJBpqMRcVJwIAwHmOsH0CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/dOzJOOllzRWcCo8mDNRl_yRMKug
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 20:51:17 -0000
I concur below response. >(*not* assuming identical label-ranges) IMO there are total 2 (actually 3) options 1. Like the node doing "epe" making an eBGP connection to do BGP-LS, every node can do the same and send SRGB to a controller 2. Somehow send SRGB (multiple ranges if needed) to all the nodes - I saw few comments on new SAFI etc - but still not clear how to flood these 3. Use SAME SRGB range on all nodes and send global prefix SID index - this is the one it seems envisioned here (from SPRING presentation) - but I would note that - AFAICT the point of "Globally unique index" came because you can't agree on a common SRGB range in a multi-vendor environment (this is kind of mixed mode, same ranges on all nodes and send global index as opposed to what is proposed in SR base documents - viz a. same ranges and sending globally unique absolute SID value or b. different ranges on each node and using globally unique index) -- Uma C. -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Hannes Gredler Sent: Tuesday, November 18, 2014 9:50 AM To: Ahmed Bashandy Cc: idr@ietf.org Subject: Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 hi ahmed, short-answer: explicit routing using label-stacking. (- isn't this what segment routing is about ;-) ?) The problem is that an ingress router does not know what the label-range of a egress router is. so if you want to fold a stack using node-labels and (*not* assuming identical label-ranges) you need somehow to "learn" about the prefix-SID originators label-range, such that you can construct MPLS label stacks. range range range range range 10000 10000 20000 40000 60000 20000 20000 30000 50000 70000 A-----B-----C------D-----E so assume A wants to create a path with ERO {C (Loose), E (Loose)} we can use the 3107 provided label for getting to C, but unless A "knows" (static config) about the label-range from C there is now way of construting the label to E. /hannes On Fri, Nov 14, 2014 at 01:41:14PM -0800, Ahmed Bashandy wrote: | Hi, | | There is a use case for sending the SRGB of a router in ISIS (e.g. ti-lfa) | What is the use case of having a BGP speaker send its SRGB to its peer in | a BGP-only deployment? | | Ahmed | | On 11/13/2014 7:10 PM, Jeff Tantsura wrote: | | Hi, | In BGP-LS-SR SRGB is encoded in SR Capabilities TLV (1034). | However today it comes from an IGP, e.g. Is ISIS case from SR | Capabilities sub-TLV of Router Capability TLV, so BGP only case should | be added. | Cheers, | Jeff | From: <Henderickx>, Wim Henderickx | <[1]wim.henderickx@alcatel-lucent.com> | Date: Thursday, November 13, 2014 at 4:24 PM | To: "[2]idr@ietf.org" <[3]idr@ietf.org> | Subject: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 | | The new BGP-Prefix-SID Label Index attribute avoids to pack routes in | a single BGP update. I believe the authors did this for backward | compatibility with RFC3107, etc + the environment this is meant for | does not need to scale to Millions of prefixes with this attribute. | The result is that BGP NLRI(s) cannot be grouped in a single BGP | update packet since the index is unique per prefix. We should clarify | this because some environments might not cope with this very well. | Also I believe the solution should accommodate the ability to add | multiple label blocks since we will never know up front how many | prefixes we will allocate and things change, so operationally I | believe this will be required. | | _______________________________________________ | Idr mailing list | [4]Idr@ietf.org | [5]https://www.ietf.org/mailman/listinfo/idr | | References | | Visible links | 1. mailto:wim.henderickx@alcatel-lucent.com | 2. mailto:idr@ietf.org | 3. mailto:idr@ietf.org | 4. mailto:Idr@ietf.org | 5. https://www.ietf.org/mailman/listinfo/idr | _______________________________________________ | Idr mailing list | Idr@ietf.org | https://www.ietf.org/mailman/listinfo/idr _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Henderickx, Wim (Wim)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Jeff Tantsura
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Eric C Rosen
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Jon Mitchell
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Jon Mitchell
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Keyur Patel (keyupate)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Keyur Patel (keyupate)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Saikat Ray (sairay)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Keyur Patel (keyupate)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Saikat Ray (sairay)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Saikat Ray (sairay)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Xuxiaohu
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Ahmed Bashandy
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Hannes Gredler
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Uma Chunduri
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Jakob Heitz (jheitz)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Robert Raszuk
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Eric C Rosen
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Jakob Heitz (jheitz)
- Re: [Idr] draft-keyupate-idr-bgp-prefix-sid-00 Saikat Ray (sairay)