Re: [bess] SRv6 versus SR-MPLS
"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 06 October 2019 03:18 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B201D120090 for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 20:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 99_9xb4cFR-b for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 20:18:11 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBF1A12006E for <bess@ietf.org>; Sat, 5 Oct 2019 20:18:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 46m82C5tHlzZdJH; Sat, 5 Oct 2019 20:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1570331891; bh=1c/+kXdMJ3lezld3M3snyaypKg/Pw+WkIwb0Rzezgs0=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Wvh8SgymmtXgINFwlpFrPBSF9UTjcbJttk28xnGKDsHYU45du8ghp5wRn4W0rwqSJ b0kZw6SQUsH8+cDqbBIgzNs7yVi4I/g6yNIbz4aea+Rb0LWkW/nnN7+ei1wLQESWrg gCApe79j8rOolOC7/sY+5IU3ysY7g/Zk9/9pOXlo=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 46m82C23vqzKnXm; Sat, 5 Oct 2019 20:18:10 -0700 (PDT)
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: BESS <bess@ietf.org>
References: <8D0ACADB-2F74-4F66-8E67-79E63E1A8FF1@gmail.com> <0C48ECF1-D889-44F9-99F1-AA69B6DD1C28@gmail.com> <CA+RyBmWSUi4ooueQ=D+rq=4UVVVepR8zb6KeAzLQ7MU=4=TFNA@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <caca288a-f85e-0d2b-0607-21dc5ebd4a13@joelhalpern.com>
Date: Sat, 05 Oct 2019 23:18:09 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CA+RyBmWSUi4ooueQ=D+rq=4UVVVepR8zb6KeAzLQ7MU=4=TFNA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/OJXawcvePl_D6lwEKpBKFbOS0OA>
Subject: Re: [bess] SRv6 versus SR-MPLS
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Oct 2019 03:18:14 -0000
No Greg, uSID does not bring all the benefits of SRv6 while using shorter SIDs. It also violates the basic IP archtiecture really abdly. Yours, Joel On 10/5/2019 7:44 PM, Greg Mirsky wrote: > Hi Gyan, > you're asking very good questions and your arguments are all correct. > But I think that now there are several proposals that address what is > considered the scalability issue of SRv6. Among these is the Unified SID > for SRv6 > <https://datatracker.ietf.org/doc/draft-mirsky-6man-unified-id-sr/>. > U-SID benefits from all the advantages SRH provides while adding a > higher density of SIDs thus allowing stricter path control. > > Regards, > Greg > > On Fri, Oct 4, 2019 at 10:02 PM Gyan Mishra <hayabusagsm@gmail.com > <mailto:hayabusagsm@gmail.com>> wrote: > > > In line possible answers > > Sent from my iPhone > > On Oct 4, 2019, at 8:22 PM, Gyan Mishra <hayabusagsm@gmail.com > <mailto:hayabusagsm@gmail.com>> wrote: > >> >> Bess, >> >> What is the benefit of SRv6 over SR-MPLS for greenfield >> deployments or existing mpls deployments. >> > I think I answered my own question but please chime in with your > thoughts.. > > This NANOG document talks about the state of TE with providers and > currently the big show stopper with SRv6 which removes it off the > table as a possibility is the SID depth and larger packet size given > that customers are set to 9100 and the core is 9216 so when adding > in mpls overhead vpn labels and Ti-LFA EH insertion at PLR node to > PQ node that adding in the entire SID list for long TE paths that > have huge SID depth makes SRv6 not viable at this point. > > https://pc.nanog.org/static/published/meetings/NANOG73/1646/20180627_Gray_The_State_Of_v1.pdf > > For existing implementations it appears from my research a no > brainer to go with SR-MPLS as that is a painless seamless migration > but SRv6 due to SID depth issues and given limited head room from > customer MTU to the backbone MTU today we are over the limit with > larger SID depth for Ti-LFA paths or non protected paths. Until > that is addressed SRv6 unfortunately may not get much traction with > service providers which I think due to the SRv6 issues ....uSID and > SRv6+ may tend to be more viable and more attractive. > > > > >> Regards, >> >> Gyan Mishra ____ >> >> IT Network Engineering & Technology ____ >> >> Verizon Communications Inc. (VZ)____ >> >> 13101 Columbia Pike >> <https://www.google..com/maps/search/13101+Columbia+Pike?entry=gmail&source=g> FDC1 >> 3rd Floor____ >> >> Silver Spring, MD 20904____ >> >> United States____ >> >> Phone: 301 502-1347 <tel:301%20502-1347>____ >> >> Email: gyan.s.mishra@verizon.com >> <mailto:gyan.s.mishra@verizon.com>____ >> >> www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT >> <http://www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT> >> >> >> Sent from my iPhone > _______________________________________________ > BESS mailing list > BESS@ietf.org <mailto:BESS@ietf.org> > https://www.ietf.org/mailman/listinfo/bess > > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess >
- [bess] SRv6 versus SR-MPLS Gyan Mishra
- Re: [bess] SRv6 versus SR-MPLS Gyan Mishra
- [bess] 答复: SRv6 versus SR-MPLS Lizhenbin
- Re: [bess] 答复: SRv6 versus SR-MPLS Robert Raszuk
- Re: [bess] 答复: SRv6 versus SR-MPLS Krzysztof Szarkowicz
- Re: [bess] SRv6 versus SR-MPLS Greg Mirsky
- Re: [bess] 答复: SRv6 versus SR-MPLS Jeff Tantsura
- Re: [bess] SRv6 versus SR-MPLS Joel M. Halpern
- Re: [bess] SRv6 versus SR-MPLS Krzysztof Szarkowicz
- Re: [bess] SRv6 versus SR-MPLS Greg Mirsky
- Re: [bess] SRv6 versus SR-MPLS Joel M. Halpern
- Re: [bess] SRv6 versus SR-MPLS Gyan Mishra
- Re: [bess] SRv6 versus SR-MPLS Stewart Bryant
- Re: [bess] SRv6 versus SR-MPLS Gyan Mishra