Re: [bess] SRv6 versus SR-MPLS

Greg Mirsky <gregimirsky@gmail.com> Sat, 05 October 2019 23:44 UTC

Return-Path: <gregimirsky@gmail.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 7F3A0120180 for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 16:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 R3ZS-r9v7NVX for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 16:44:24 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D595120144 for <bess@ietf.org>; Sat, 5 Oct 2019 16:44:24 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id u28so6849947lfc.5 for <bess@ietf.org>; Sat, 05 Oct 2019 16:44:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=i6yCK9KRUsWC+8XLZehQ9RW/ZKUYto8ZGmVua7MWGMQ=; b=lRr31csOOKaADkFW77suaUK7z2Grh2RRNAv8PwpWXTpLdmxopGzFowY5LRl5SraTmk mjpKSxqjW31QWGdtUgZ5q6gm7e4QidN0VwnwTolbTiKClER8hrJ5ExJo5o+2zbcQW1lr lK9r62I3j92SshLjF1dWlIV3MowmPyienRr8nnNHbSm2rvZR4XptNhhlB/WAZEWFWVrZ kGTJbHfURYyj2k5/t32CDEdzusjdZPMG/9goyhlqjGdMfESA5foKvgx10z63fv1bY0gL 1aJdbn8UEyAHyDQdifkfD1bTjM0y3vF0027HS8aMCf8Uu8XiL4OY7Eb53xPun/cYIfc+ EbEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i6yCK9KRUsWC+8XLZehQ9RW/ZKUYto8ZGmVua7MWGMQ=; b=nGYZZ0+XltJIUAiInBcUft57ZJG6I/RcPZPo7BDr1KTvHzg6eCqH6gdMKSFax36Cjw eR4wQ/hNwGQuNtjMoRjx+flQ/yluEllElVhc7FB6zt68ITlNb8maf2Z4NDmMLdUZ+NJX n06s3BwHWuy/GRWLFFX1+IwSLW5SZX54xPF//cW6wd4ibN7n4sQR0yVxPdypcquhMCk6 UoUloMqDIsLby2OydwipUq1/6zSqkL3IwWP2nB1da4pOdqR2DBmy9g8bPL820hfjsyWL qSsATB2GDsEGhlKqcaktfKQX7WMumXnOEEsUltztENqnbz/dE6XqClJ9/SbzJAmOGxox QPVQ==
X-Gm-Message-State: APjAAAUw3XJ/qacEk8n4IJcXvI2INqgicdqlfcXlpnkS3oXIC6v0QhHB 1Yf1BHURLfZIUHqEQiugbYPE3WGgMudgphd7+tI=
X-Google-Smtp-Source: APXvYqxgf1bPcZn3wiaFHpphE1/CKp6VwxWmGW1IOnGr8qFSeaEESsMPSbY+DM/EKqpxSNlDMqQkoz7F/2PqQfL1Zg8=
X-Received: by 2002:ac2:4359:: with SMTP id o25mr12681249lfl.147.1570319062563; Sat, 05 Oct 2019 16:44:22 -0700 (PDT)
MIME-Version: 1.0
References: <8D0ACADB-2F74-4F66-8E67-79E63E1A8FF1@gmail.com> <0C48ECF1-D889-44F9-99F1-AA69B6DD1C28@gmail.com>
In-Reply-To: <0C48ECF1-D889-44F9-99F1-AA69B6DD1C28@gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 05 Oct 2019 16:44:12 -0700
Message-ID: <CA+RyBmWSUi4ooueQ=D+rq=4UVVVepR8zb6KeAzLQ7MU=4=TFNA@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: BESS <bess@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e87f480594326577"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/4wfDtrr8YMOBtmq0uKxOe20NNQc>
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: Sat, 05 Oct 2019 23:44:27 -0000

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> wrote:

>
> In line possible answers
>
> Sent from my iPhone
>
> On Oct 4, 2019, at 8:22 PM, Gyan Mishra <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
>
> Email: gyan.s.mishra@verizon.com
>
> www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT
>
> Sent from my iPhone
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>