Re: [spring] Regaining Focus on SRv6 and SRv6+
Tom Herbert <tom@herbertland.com> Sat, 07 September 2019 21:19 UTC
Return-Path: <tom@herbertland.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 CF51F120168 for <spring@ietfa.amsl.com>; Sat, 7 Sep 2019 14:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 gEMLYoXNuq09 for <spring@ietfa.amsl.com>; Sat, 7 Sep 2019 14:19:40 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 71CEC1200C3 for <spring@ietf.org>; Sat, 7 Sep 2019 14:19:40 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id c20so698731eds.1 for <spring@ietf.org>; Sat, 07 Sep 2019 14:19:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=hdexjdQWbWWZ5BWEM3As/WJw5ZcdHkjexHpwS0sg2JA=; b=W3iKselq5zWKea+EQT48nrXaKyTtPy16cmiGbuczQ6bYWTRuAJHPE78wYJcArQCwrk XVCDc9WIwN/LfAvnTtndadqDppr/89fviBhWq9mPxAGr+e64k1E6tqun+6FmaKlN1txW BcU4faMBBEa0j+qLLgY7JsjU1jNZ7w05+2Um0yzUq+HK9guLhzpW7pmXua/pRGdm5s2D zht0gFoNUPGiJE6QXbrAbXlhMT+vVYLbxChFHatcgvOfpxxLD2JMcLxLkCEoqqxBc8uB po4+r0mTY1l4+UyScERArWEO8xUY95Dn1lTzSQ6k9zARMO1jKARMmuhQiZlpkQ4y+vyw aKJA==
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:content-transfer-encoding; bh=hdexjdQWbWWZ5BWEM3As/WJw5ZcdHkjexHpwS0sg2JA=; b=rP01F/19IHejzVyLnCqFzoEUR3sm4/5cMCp6fWZF0k8jc8TLWvuoIhKyS3IoV818PO J2cP2DiuXlxCP8b8BrefllX+D5B8H0TVmwRpBiiHrod3THOr4k/KGfzcktE974LmlCCW jD7X3kMSssR7m39YQkiMY6JU25P+uq21fgw0tUsvKv/yTj4BLkkz4z9ZBOFfYZA1rLd0 MW5U7QNSPW/r5jVmila+bAGVTtQ5b0DcA+ctvvyWzEh8aD3uofJdG24BXPy/d7HQz5c3 +9D1Jn05JlM2mBAAsgtxB0IeyWvZi9w3YE0PNDePVf3EEo/c7C9whgODAF5VJLPhyPGn gOHQ==
X-Gm-Message-State: APjAAAVgE8wWvug+y4eYACQCheHOPU1UPqBkAFKAMpy+bxBLp2jb6fdG LtBUVSTsqgrd9xhtZ6qALCQuS1I0KQ607mhkd8a2kCbCL1Y=
X-Google-Smtp-Source: APXvYqx6NDn/dHypG0x//tBIuhJ0DyUvLiWTJRvqgWLCD23jbDZNfNavDWKKActbl4eLNWH9TWGgkSVyLNNA/ET+BP8=
X-Received: by 2002:aa7:d694:: with SMTP id d20mr9217565edr.226.1567891178895; Sat, 07 Sep 2019 14:19:38 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR05MB5463153B47BFE83350C566E7AEBA0@BYAPR05MB5463.namprd05.prod.outlook.com> <CALx6S366MBTKKhYVkzwhtNU1kpXwq5gAB_5LL1s_zs46oXP7AA@mail.gmail.com> <CAOj+MMHf_kikj1D8=Z5Ti8MKKSGOtoLLAmpbbYZdOQBBjSGz-g@mail.gmail.com>
In-Reply-To: <CAOj+MMHf_kikj1D8=Z5Ti8MKKSGOtoLLAmpbbYZdOQBBjSGz-g@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 07 Sep 2019 14:19:26 -0700
Message-ID: <CALx6S36MJi70YdpH8DSwJz=hc=VNr8V1xSr2jjqcL7TFp4qO0g@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/vg1ij8x-3Znt1xW0aWiYvG0vduM>
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: Sat, 07 Sep 2019 21:19:43 -0000
Robert, You've chosen to selectively comment on only parts of what I wrote, not the main thesis which is that SRV6 packet format is more complex than SRV6+. The most obvious difference, besides SID size, is that SRV6 contains TLVs and SRV6+ doesn't. I don't believe that this was ever needed, HBH and destination already exist in RC8200 and could have been used as they will be in SRV6+. Similarly, AH could have been used instead of defining SR specific HMAC. Furthermore, several implementations of SRV6 are listed in draft-ietf-6man-segment-routing-header-22; all except one have the words "no TLV processing". The exception is Linux, which doesn't not implement SR TLVs per the standard and wouldn't interoperate with an implementation that is conformant (I have looked at the Linux code and in fact have suggested a fix). So the claim that SRV6 is mature and deployed is suspect considering there doesn't seem to be proper support for TLVs which is a major part of the protocol. Based on this analysis, I believe my statement that SRV6 format is more complex than SRV6+ is factual. It's my opinion that SRV6, particularly because of TLVs, is overly complex. Tom On Sat, Sep 7, 2019 at 10:54 AM Robert Raszuk <robert@raszuk.net> wrote: > > > > It doesn't depend on extension header insertion > > Nothing depends on extension header insertion ... SRH insertion is an optional optimization. > > > and there's no need to have multiple routing headers in the same packet. > > Really ? > > If I am doing SRv6+ in my network for TE and want to to do TI-LFA how would I not end up with 3 IPv6 fixed headers and two Dest Option EHs and two CRH EHs in the packet under protection ? > > But this is just tip of the ugliness iceberg ... > > All required extensions to protocols developed in to name just a few already proposed by SRv6+ authors: IDR, LSR, BESS and 6MAN WG to support the new mapping (which is other then nomenclature close to SR-MPLS mapping) will require real development resources. > > OAM in spite of few claims from Ron that "just works" is not addressed and does require even more extensions. > > Then last I will not be able to use SRv6+ for my deployment needs in the global IPv6 overlay I am running simply that within my overlay I do not plan to run any control plane. Underlay basic reachability provided by third parties is all I need to construct optimal paths. So any protocol which requires new signalling to distribute mapping is non starter. > > At the end we should learn from others ... (hint SDWANs) and avoid mistakes of the past (hint: LDP). > > Many thx, > R. > > > > > > > > > On Sat, Sep 7, 2019 at 6:41 PM Tom Herbert <tom@herbertland.com> wrote: >> >> On Fri, Sep 6, 2019 at 6:08 AM 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+. >> > >> + 1 >> >> I'd suggest a fourth fact. The packet format of SRv6+ is much simpler >> than SRv6 and the protocol works better with existing mechanisms and >> protocols of IPv6 like Destination and HBH options, as well as AH. It >> doesn't depend on extension header insertion and there's no need to >> have multiple routing headers in the same packet. >> >> Tom >> >> >> > >> > >> > Ron >> > >> > >> > >> > >> > Juniper Business Use Only >> > >> > -------------------------------------------------------------------- >> > IETF IPv6 working group mailing list >> > ipv6@ietf.org >> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >> > -------------------------------------------------------------------- >> >> _______________________________________________ >> spring mailing list >> spring@ietf.org >> https://www.ietf.org/mailman/listinfo/spring
- [spring] Regaining Focus on SRv6 and SRv6+ Ron Bonica
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tarek Saad
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tarek Saad
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Dirk Steinberg
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Chengli (Cheng Li)
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Voyer, Daniel
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Fernando Gont
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Huzhibo
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Mark Smith
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Huzhibo
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Mark Smith
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Huzhibo
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Mark Smith
- [spring] IPv4 EH proposal Robert Raszuk
- Re: [spring] IPv4 EH proposal Alexandre Petrescu
- Re: [spring] IPv4 EH proposal Fernando Gont
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Zafar Ali (zali)
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Xiejingrong
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Gyan Mishra
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Fernando Gont
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tom Herbert
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tom Herbert
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Ron Bonica
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ - … Joel M. Halpern
- Re: [spring] Regaining Focus on SRv6 and SRv6+ - … Ron Bonica
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Xiejingrong
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Chengli (Cheng Li)
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tom Herbert
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Tom Herbert
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Ron Bonica
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Robert Raszuk
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Ron Bonica
- Re: [spring] Regaining Focus on SRv6 and SRv6+ Chengli (Cheng Li)