IETF Logo Mail Archive

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

Fred Baker <fredbaker.ietf@gmail.com> Thu, 17 October 2019 23:52 UTC

Return-Path: <fredbaker.ietf@gmail.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 AFF241208A1; Thu, 17 Oct 2019 16:52:57 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 9NcRlCxTU8Eo; Thu, 17 Oct 2019 16:52:55 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 5D362120168; Thu, 17 Oct 2019 16:52:55 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id a2so2640535pfo.10; Thu, 17 Oct 2019 16:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MKYQenrD7ifF5pT0pKEk5HOi26gpKikhz3InfV7swUY=; b=t+kFUJpdyaQA5B0tAjvD32IEPYmxIjqFaTuAJNC4lIjIFKANe/R2wVfgVqL7N0fxVZ nm8XERCf9F2NmnlSeWzFmc9uE3mUIETR3Z+Q184jxMPg6ub2zth5EGHPz4vuPCNblM30 RkLS+b95xfmSMfOagKR0IMxzL8IB6pCxRt2b0ygYF4GiMcyHbvu32SfvP34jGVu9GfR3 s0MLK20DALW4me7Ei7Y1y2ipayBKvt3QXSLGF6VFJ34wOnN4BWwnlRHLgxnCkS9zZ1Ks MIdBPzqxOsxy11zjU6NBHrSnK1ly0+WtWJR8bzNTFm+O4lWsRM3Vy68S9fDS3hX9LI/0 dzQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MKYQenrD7ifF5pT0pKEk5HOi26gpKikhz3InfV7swUY=; b=lcDRrZhGux2J+b8soNktNWTftz9ZRYrjS8/B9gbYLavxbmIItdhx6EWt/msZr39+wR agMlzDbQKF0QNQ3Z51jSdAYvR3PANoCAHcBg0a1zVN4d30P1FVpTxZkknEjwYeN6JEEr wiKEGQ0UpXjpj5fXx24J3DQAbcsbIRDuQYAtecj0vIP7uzI0r2pLVZ4rQDI6alNqAIYa HBl67rtnQ9aVNcOJuQG2mRwtpM1Bt2dFfYhrTRjzSB/fT2d7CbHA3aBblHXvUpeqW3l+ iGjiFRaX1AjMn/zR7xLPEfuKGuKtEFj/Y3nfPhB3oynP3w9kY4fSE24mbfCPSKYu1rVH dl9w==
X-Gm-Message-State: APjAAAX9mPl3rFGs3vkmPnHbTJDT/bR52nmrvknfVkc9bEy7+Y7RX/gQ iCM5+s+Pj9JiO5YFxEcC1Bc=
X-Google-Smtp-Source: APXvYqzgg3rTClcQE+A1TJS5W2yoew4Dum9vlYzT8nPqXazzqvwuVEoNBKpm0Y6EUfydm6ty+0zDBA==
X-Received: by 2002:a62:3387:: with SMTP id z129mr3135237pfz.185.1571356375018; Thu, 17 Oct 2019 16:52:55 -0700 (PDT)
Received: from 205.66.20.149.in-addr.arpa (205.66.20.149.in-addr.arpa. [149.20.66.205]) by smtp.gmail.com with ESMTPSA id x65sm4712300pgb.75.2019.10.17.16.52.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Oct 2019 16:52:54 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D93503A7B@DGGEMM532-MBX.china.huawei.com>
Date: Thu, 17 Oct 2019 16:52:53 -0700
Cc: "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, Satoru Matsushima <satoru.matsushima@g.softbank.co.jp>
Content-Transfer-Encoding: quoted-printable
Message-Id: <153D8103-B147-4EE7-B7FE-A845D986938E@gmail.com>
References: <157110930835.24708.13140748426444834467.idtracker@ietfa.amsl.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D93503A7B@DGGEMM532-MBX.china.huawei.com>
To: Lizhenbin <lizhenbin@huawei.com>
X-Mailer: Apple Mail (2.3601)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6bgULFLh11iHxyyjwo8d5iD94EU>
Subject: Re: [v6ops] 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: Thu, 17 Oct 2019 23:52:58 -0000


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

v2.23.0 | Report a Bug | By Email