IETF Logo Mail Archive

Re: [v6ops] [spring] New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 22 October 2019 21:11 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0EA312008D; Tue, 22 Oct 2019 14:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, URIBL_BLOCKED=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 7bxodke9TdHV; Tue, 22 Oct 2019 14:11:07 -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 F03B712008B; Tue, 22 Oct 2019 14:11:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 46yR4p6JhFzKp6Y; Tue, 22 Oct 2019 14:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1571778666; bh=KOLlvl8SM5TlvHMnDJbrQeZSNHzItHSYr0jpvwlR4UE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=b77nkSyuE54ySMWpSCvUb63hpRRh8EWwSdf1OGNscOvqmBaG05AuoHauSbNa/0TfV TUTyumWw4GxSEFhoNX2BDfqi1BIiNpdbLY+j+h0XKMOntvb9ebWJiKAy5HCvlIJTEc JGVMbZEPB7OaCVS6YOZrhx7w6/HngcvTVzQ+tNj4=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [10.195.197.206] (unknown [135.245.111.233]) (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 46yR4m6Lh7zxQrD; Tue, 22 Oct 2019 14:11:04 -0700 (PDT)
To: "Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com>, Fred Baker <fredbaker.ietf@gmail.com>, Lizhenbin <lizhenbin@huawei.com>
Cc: "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "Clarence Filsfils (cfilsfil)" <cfilsfil@cisco.com>, Satoru Matsushima <satoru.matsushima@g.softbank.co.jp>
References: <157110930835.24708.13140748426444834467.idtracker@ietfa.amsl.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D93503A7B@DGGEMM532-MBX.china.huawei.com> <153D8103-B147-4EE7-B7FE-A845D986938E@gmail.com> <BE2D67F2-B0DA-4551-BBBF-5F737D6A2CE7@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <546dfd39-fbaf-3839-9482-4cb7254b51e0@joelhalpern.com>
Date: Tue, 22 Oct 2019 17:11:01 -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: <BE2D67F2-B0DA-4551-BBBF-5F737D6A2CE7@cisco.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/v6ops/TlUvMP9_uJOj8M_-3mnWGAYv0EE>
Subject: Re: [v6ops] [spring] New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2019 21:11:09 -0000

Hmm.  That seems an overstatement.

IPv6 can carry NSH (RFC 8300) and support Service Chaining.

One can use IP-in-IP encapsulation to support FRR.

While the TE available without NSH or SR is limited capabilities.

And of course if the operators is willing to install MPLS, they can get 
all of the SRv6 capabilities by enabling MPLS (a capability all of their 
devices likely support.)

And there are costs and risks associated with deploying SRv6.

Yours,
Joel


On 10/22/2019 4:55 PM, Bertrand Duvivier (bduvivie) wrote:
> Fred,
> 
> IPv6 without SRH don't support TE, nor FRR (topology independent), nor Service Chaining, nor Network Programming, SRv6 does address all. Which what IPv4 never did, for IPv4, we had to add extra encap (MPLS,NSH,..) introducing constraints like no summarisation to deliver similar use-cases.
> 
> BTW I'm aware of
> - 5+ hardware vendors supporting SRv6
> - 4+ deployed SRv6 networks
> - 20+ network operators interested by SRv6
> - OS's supporting SRv6 like: Linux, FD.io,...
> Thus "before we push SRv6 deployement" sounds not longer an option, it is done already.
> 
> BRGDS Bertrand
> Cisco
> 
> 
> On 18/10/2019, 01:52, "spring on behalf of Fred Baker" <spring-bounces@ietf.org on behalf of fredbaker.ietf@gmail.com> wrote:
> 
>      
>      > On Oct 17, 2019, at 5:30 AM, Lizhenbin <lizhenbin@huawei.com> wrote:
>      >
>      > In the past two years, China pushed the IPv6 deployment and almost all the IP networks of operators achieve the goal "IPv6 Ready". This provide a strong base for SRv6 deployments which can help operators provide new services based on IPv6 infrastructure.
>      
>      With respect, I would suggest that before we push for SRv6 deployment, we develop and SRv6 use case that IPv6 doesn't support. My perception is that SRv6 is a solution looking for a problem.
>      _______________________________________________
>      spring mailing list
>      spring@ietf.org
>      https://www.ietf.org/mailman/listinfo/spring
>      
>      
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email