Re: [spring] Regaining Focus on SRv6 and SRv6+

Robert Raszuk <rraszuk@gmail.com> Fri, 06 September 2019 14:18 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4EBB120C7B; Fri, 6 Sep 2019 07:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, URIBL_BLOCKED=0.001] autolearn=unavailable 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 3udU_TvAuUD2; Fri, 6 Sep 2019 07:18:18 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 5C036120088; Fri, 6 Sep 2019 07:09:17 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id w22so4557022pfi.9; Fri, 06 Sep 2019 07:09:17 -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=GZRMIDzm+/FchEbS4TTpMkOVQ3CgOSB79wuXnq1YYIM=; b=H7opXffze9z3YbPh3v/1RpLJiC0PDn9frEtnUToKVZl72RKWdk9CMhtvYedVbBrSdx xy5lZ2aqlbidfFXInJExCi6JeG5QupoZmtVVj7GaVd4lpZ/0DYb+OVNWB65QDdvuNZIW ScvZnjE6+AEVmUmkKXxQg2j71ekYPAqe0z1n2uEIlRd7OP+BTSg+rDHxv+hxcv8qcHxZ LxVyYxdCmu3Un2LNjyxkU22F5FH9NSI65Iwe/8RInhI8C1YNwG93bH9o1u3NL/FwbpN6 Z5IgQ/n+nVNxp3x7D27d5Qdapg8fk5BBTsuZj1yAwLFel4pc5tXs3Nxv/ATxXhMB2BBc IDeg==
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=GZRMIDzm+/FchEbS4TTpMkOVQ3CgOSB79wuXnq1YYIM=; b=meDHVrEtJIg/duwxNsRddkeH7r8lvvdk+zbc2SgAZlWu95mdk7Uo4NMCpIIs/Aizln LON1pPRw7D54g8s9vxlDXBs7j4P5nA4yr3w+RHnxf52uc5OGzm1Z+p/G6rjl0FznF9o5 IKmFMY0TK3G2qOCRJSt+IOhvRMKw87MKAxvjqAtX5ATxA6iBnQuvhL5TzRZ0dUOLULpD UDiCM8fGo+y7J11ckvT4ni8qlkGGCztHuaIhOex5uTqqjEORWVlxeJktWzPgAjd7jkDS QcATlbM4qXlN29hIr8Dgz60SgQ6MNhEBPP7DSch0kV/lWpADnuFSwQnaSXEs4i1i7M2z Fr6A==
X-Gm-Message-State: APjAAAW9z97bFjLNeTTptefU1xlsxQfApP2OytI64uQlGBOlhErPnZzf QCMQGnM2tnismAB9u1Zorke5NF9d2UvrN3YNBKc=
X-Google-Smtp-Source: APXvYqzheaGQBu4p66EH9D+tP8G0bL5Y9S9vopSfjzHiBtUjK88LC9zZSjrha6j01qHng+NJuwZE8mSrBFYE44OwPRs=
X-Received: by 2002:aa7:9386:: with SMTP id t6mr11053791pfe.214.1567778956173; Fri, 06 Sep 2019 07:09:16 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR05MB5463153B47BFE83350C566E7AEBA0@BYAPR05MB5463.namprd05.prod.outlook.com> <CA+b+ERm4x072JQZQovX0MVcea3=0DOCSESopAXj_SE1vMi8qkQ@mail.gmail.com> <BYAPR19MB3415BA05D2BD5525FEAE2771FCBA0@BYAPR19MB3415.namprd19.prod.outlook.com>
In-Reply-To: <BYAPR19MB3415BA05D2BD5525FEAE2771FCBA0@BYAPR19MB3415.namprd19.prod.outlook.com>
From: Robert Raszuk <rraszuk@gmail.com>
Date: Fri, 06 Sep 2019 16:09:00 +0200
Message-ID: <CA+b+ERk6WzSu9OyrHN79MFv6tSgR=X49s0bYaaoQLh61d6rNdg@mail.gmail.com>
To: Tarek Saad <tsaad.net@gmail.com>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c4e4f90591e2fb6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/TlmLAPy4YNY4PWqoRdmS1wOk1oY>
Subject: Re: [spring] Regaining Focus on SRv6 and SRv6+
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 14:18:28 -0000

Please see my elaborated note on that ...

https://mailarchive.ietf.org/arch/msg/spring/qvRUp8SC2cWeIE5UhhU9aKGtpHM

Cheers,
R.

On Fri, Sep 6, 2019 at 4:03 PM Tarek Saad <tsaad.net@gmail.com> wrote:

> Hi Robert,
>
>
>
> >> * If operators choose not to use MPLS transport SR-MPLS can be easily
> transported over IPv4 or IPv6 vanilla data plane
>
> I’m little confused about the above argument – given it starts with don’t
> want to use MPLS, can you clarify?
>
>
>
> Regards,
>
> Tarek
>
>
>
> *From: *spring <spring-bounces@ietf.org> on behalf of Robert Raszuk <
> rraszuk@gmail.com>
> *Date: *Friday, September 6, 2019 at 9:33 AM
> *To: *Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
> *Cc: *"spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>
> *Subject: *Re: [spring] Regaining Focus on SRv6 and SRv6+
>
>
>
> Dear Ron,
>
>
>
> I think you forgot few main points in the summary:
>
>
>
> * Many operators use SR-MPLS successfully and it has been both
> standardized and successfully deployed in the network with interoperable
> implementations
>
>
>
> * The overhead on the data plane of SRv6+ is very comparable to overhead
> of SR-MPLS
>
>
>
> * The control plane extensions BGP, IGP are available for SR-MPLS and non
> are available for SRv6+
>
>
>
> * SRv6+ requires a new mapping of SIDs to prefixes to be distributed by
> control plane
>
>
>
> * If operators choose not to use MPLS transport SR-MPLS can be easily
> transported over IPv4 or IPv6 vanilla data plane
>
>
>
> * Extensions for additional applications like L3VPNs or L2VPNs will
> require another set of protocol and implementation changes.
>
>
>
> * If there are vendors who do not want to provide SR-MPLS SID mapping to
> IPv6 addresses in their control planes let's focus standardization and
> industry work in this direction.
>
>
>
> With all of the above I think it would be a serious mistake - at this
> point of time - to continue work on SRv6+ in the IETF.
>
>
>
> Thank you,
>
> Robert.
>
>
>
>
>
> On Fri, Sep 6, 2019 at 3:08 PM Ron Bonica <rbonica=
> 40juniper.net@dmarc.ietf.org> wrote:
>
> Folks,
>
>
>
> We have explored many facets of SRv6 and SRv6, sometime passionately. I
> think that this exploration is a good thing. In the words of Tolkien, “All
> who wander are not lost.”
>
>
>
> But it may be time to refocus on the following:
>
>
>
> · For many operators, SRv6 is not deployable unless the problem of header
> length is addressed
>
> · Many objections the uSID proposal remain unanswered
>
> · SRv6+ offers an alternative solution
>
>
>
> Given these three facts, I think that it would be a mistake to discontinue
> work on SRv6+.
>
>
>
>
> Ron
>
>
>
>
>
> Juniper Business Use Only
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>