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

"Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com> Wed, 23 October 2019 00:17 UTC

Return-Path: <bduvivie@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFAAE12021C; Tue, 22 Oct 2019 17:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=L6qZ/+g5; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=gPhNJZzR
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 rMTUeeB-5UAH; Tue, 22 Oct 2019 17:17:04 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C592120152; Tue, 22 Oct 2019 17:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3840; q=dns/txt; s=iport; t=1571789824; x=1572999424; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WbsxOrTnJkzgq5kkT8n/8jMMDPXZrF3bgjP3lXEWXag=; b=L6qZ/+g5MutWU/zyoElwQKUUyUunLeAxcNmn7LqoFdc/DdgFlKvVoPYU DsOu9gTvbekn1KF/XtD8m9RWYcuWZIGdM9gcK8W3rSkoQkSAczD4uFp4H 9tQO7+cZrHhg7BtoerPEKiK/If1vzvbjiPChoe8quK+srYrNldVBezbbJ k=;
IronPort-PHdr: 9a23:r/FLSxGSSDFgvv9UPUcigJ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efTmcjI7AsVPfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AiAADzmq9d/5pdJa1lGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgWoBAQEBAQELAYFKUAVsVyAECyoKhBxigmUDilaCXIlujhSCUgNUCQEBAQwBARgLCgIBAYN7RQIXgxMkNwYOAgMJAQEEAQEBAgEFBG2FNwyFTAEBBAEBEBERDAEBLAkCAQ8CAQgYAgImAgICHwYLFRACBAENBRsHgwABgkYDLgEOpn8CgTiIYXWBMoJ+AQEFhQENC4IXAwaBDigBjA4YgUA/gREnH4JMPoIbRwEBgTonF4J5MoIsjHMfgi83nSlBCoIkkRuBUII7G5lOjjaKN48QAgQCBAUCDgEBBYFoI4FYcBU7KgGCQVAQFIMGDBcVgzuFFIU/dIEpjCSBMQGBIwEB
X-IronPort-AV: E=Sophos;i="5.68,218,1569283200"; d="scan'208";a="348695400"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Oct 2019 00:17:02 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x9N0H2W1008385 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 Oct 2019 00:17:02 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 19:17:01 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 19:17:01 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 22 Oct 2019 20:17:01 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Arhwvp741oeRW81gAlUwfHqfTRxnHnpU5NjLFxXJe5GVui0JWZfukpPg10v8EBTlzeSSpEq+GO90lxjAChZnD0O+RCqTWqaivPfaZLaI+zHA3hulsp4kz+1NJWni+DbB0SK9iJsE83XDMF3P6sJkg1XjgP8NCW4P8jZlwtKtmxtM2sYXTWsNA8jo6TVNbGOdAEmim2RcZBiegemg4WA5HBVY2HVjmaMkvYzbr4WVUNBygSAhm3P1IFL+lwlhf1f+c5Muqjyx6JpgcLHtbNwe/KlBqnQ6Xb1XUdwNcT5rDOcC2ht1zROq8o9MPoyEoR07sQEm/2Prs3jbuo0hsyeN9A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WbsxOrTnJkzgq5kkT8n/8jMMDPXZrF3bgjP3lXEWXag=; b=TF48Kml6s0XxIO/LaRtcGEyqvCBqa8Ddnvg1GaaoFHza+dpU7rAU165WDjOCfc6DNGTeQG2cH6KilsE5jA3LMwMEfb3EQ6J6CGzpA9UwcYJ9JCRYkryNXejPzb8wdm2zTfUoWYPoKTPHKPU19VOnPXf8n2XPpAqaxSf4lIB42OLf2ivmlyKaEisstqL2VsteskRfiEyQm8a8GFJUROz/5PzxCYY5J9CpIBJnwogiulxPfDySnta/LYHFO1lSkyzoEY73zhe1EKgiPxmDXzPXZm1kM6XgFHD/M9BALF7ZQ13f/TGoVFabClCnm3yZr4l+PvKDDyh1Fe5MjMYzyQ+mwA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WbsxOrTnJkzgq5kkT8n/8jMMDPXZrF3bgjP3lXEWXag=; b=gPhNJZzR63d5ggGlJ6kqZeycA4Uc41KaMByQIOTOcczFLDiNT2Pq/HiAXnRP0yDwNX0EEdvmjkyDjFQeKFa/uYZzFUr/kx2vXFmUIOFbD93KPBBg1BcW9SndpWDJEHlqCIJJsGwi6+fH1ieFblL/0rEeXZIHtIkHYYj2cr61yBE=
Received: from MN2PR11MB3902.namprd11.prod.outlook.com (10.255.180.77) by MN2PR11MB3599.namprd11.prod.outlook.com (20.178.251.89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.21; Wed, 23 Oct 2019 00:17:00 +0000
Received: from MN2PR11MB3902.namprd11.prod.outlook.com ([fe80::8829:7db5:3bf1:164e]) by MN2PR11MB3902.namprd11.prod.outlook.com ([fe80::8829:7db5:3bf1:164e%5]) with mapi id 15.20.2347.029; Wed, 23 Oct 2019 00:17:00 +0000
From: "Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.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>
Subject: Re: [spring] New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
Thread-Topic: [spring] New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
Thread-Index: AQHViRsI6HCT61t1VkC5Oeypxz3nGqdnKDOAgABVfIA=
Date: Wed, 23 Oct 2019 00:17:00 +0000
Message-ID: <A5FB92C1-6FFE-432F-923C-19C384D8ED2C@cisco.com>
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> <546dfd39-fbaf-3839-9482-4cb7254b51e0@joelhalpern.com>
In-Reply-To: <546dfd39-fbaf-3839-9482-4cb7254b51e0@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bduvivie@cisco.com;
x-originating-ip: [173.38.220.59]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 238ea18a-cb48-46aa-e158-08d7574e52b5
x-ms-traffictypediagnostic: MN2PR11MB3599:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <MN2PR11MB35996F578B3B2174C3CDC449D66B0@MN2PR11MB3599.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 019919A9E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(346002)(39860400002)(366004)(376002)(136003)(189003)(199004)(110136005)(316002)(71190400001)(6486002)(58126008)(5660300002)(14454004)(478600001)(53546011)(6506007)(966005)(2906002)(66066001)(33656002)(54906003)(102836004)(6246003)(36756003)(26005)(6436002)(99286004)(81166006)(2616005)(476003)(486006)(3846002)(91956017)(76176011)(66446008)(66556008)(11346002)(6306002)(186003)(81156014)(4326008)(256004)(7736002)(305945005)(14444005)(64756008)(71200400001)(66476007)(66946007)(6512007)(6116002)(76116006)(446003)(86362001)(25786009)(229853002)(8676002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3599; H:MN2PR11MB3902.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mRIYt+UiIehlRW8LMAEOPZiqFK4TiC3QVwRvABVTKeCUy6ueqEgGtFj4dx/pWpnw7W9xj58n+x96UY4Xs5iEHzVXzLzajNxFzqQwwCYF6VOA5qsfM8mqMn9PCQ2ldjo5rOgvl4q9T+txQVogFEh+Lt8bE9AgIPYMr3X7XKtC4EkvZaGZBMbz44XdRVjC6Rp/fi0rYjnSlYu2msObx27kVapSPpxpOVbkp6S83v+XrTTt+M4MiOX91uYFehnNpRwrZIsa9uirWL05KAtIcGQkVAkEsT+MWOOoqQ4/1VnuzQ3FRRraWV0xr67Y2gyH94Rn9tXgyFjq0GFqoWo+3fxgN16C0ilh5602HAyEAi7iW1sAaIQWZc3wvBaSjqywFcxJ0LGHfQISa09bMvawp8HcinBtPAAIpWODdznZzXHmbSfUvUERJDvWMyiRNfNHyZD8KyUjO9nY0GIaZ1YnsDbu2A==
Content-Type: text/plain; charset="utf-8"
Content-ID: <F2C3BC883587294181BC5E3C8BA924AE@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 238ea18a-cb48-46aa-e158-08d7574e52b5
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2019 00:17:00.1772 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: UWj2TbL0YzBpft+xzko4dw2Pzf2TibrnlH2tROnGZNKbcT0cIdRDC1mzafBnY8bRBXZ/UA0nJKmxpeWiB6qKrg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3599
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fgG37vychCW9twcg_ph1DNHNIn8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Oct 2019 00:17:07 -0000

Joel,

Fred asked what IPv6 can't resolve.

Not IPv6 + NSH + MPLS.

There is risk and cost with IPv6 + NSH + MPLS as well... 

Best Regards Bertrand


 

On 22/10/2019, 23:11, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

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