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

Satoru Matsushima <satoru.matsushima@gmail.com> Fri, 18 October 2019 02:27 UTC

Return-Path: <satoru.matsushima@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 999231200F6; Thu, 17 Oct 2019 19:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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, MIME_QP_LONG_LINE=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 MHFcvAi8tH5T; Thu, 17 Oct 2019 19:27:17 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 1080D120044; Thu, 17 Oct 2019 19:27:17 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id r1so2442712pgj.12; Thu, 17 Oct 2019 19:27:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=UgNZyTSSJqvChe0TzIQHBXDktMW+SHTPrP4cSyAbC4E=; b=OseOrlMQJQtEdiV2NKwMIdzCX843aXD9ttjXdDbx7gv9W17r5X2H1GuEkallQcYER1 vdXwHFPiwXJ7oYq7pwEXjbB2yHeM/Dj2O7gy/mIVjrNEfVRumKNJ7V2+5tTBtr8977RU P8kb+gYQTPgxJZirgpUBAjyH6YjmV8qRssL/VeBdMBG9SUTVU7l9muDRFLCEIoO7lm5/ +cTIl/0aurbHSwinimvJCEpYRr91p9McqCIPHrxGxlpzcy266m1PD6gtjtwhTUQEZKAv esCEMCLuFYGCbJvc7X1TPrs4IDorAY/O+ygHKRXLn35hO5D2Z59fhkKTXZaRyYqp4NWM QJNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=UgNZyTSSJqvChe0TzIQHBXDktMW+SHTPrP4cSyAbC4E=; b=SWFE4QkPq7r8ACPdtxTXVD8isNAgwGYXouGU+YKjV9FmY4WVOZoocwnkkqEPae/S1H bGi2AFhHz4M6a3yltIJ9E9tuyB/Khu7ygau+elDCld6ermpdBRHBdkar2OybUjUuAi+8 fvrsN7ZJHYXH3r22iktnshKK0iMuFOThe/8vRXtMx1DljrXoV5aELljjG1AnL76vwX0l d92emidKFKmabMNMo+Es+MG4fYkHsr7LX50tULRySZf3+NgxUbNT57Br2D7itZIPwDgK gq5C5KLsIbnHriTbec3ZojRSsUtaKD9pgElZ5g9dUTpqVGrElGlP7qK6aCbPHdIv88Sm gn6w==
X-Gm-Message-State: APjAAAXMFiCfNFZoLRrsfSrdVX0eGrHrQ0Mvl/XJYZt3Zl5znZFtaF8u wGUgJAuqOEALZbaYQh2XZ4Q=
X-Google-Smtp-Source: APXvYqwlX7ORkBanq7zm3XkL0PnHs93ZL4qTtWnW9OtmsMP4UQyLB/G1qHSLUhIvoSOKsbH7TINShQ==
X-Received: by 2002:a17:90a:6583:: with SMTP id k3mr8071003pjj.50.1571365635244; Thu, 17 Oct 2019 19:27:15 -0700 (PDT)
Received: from [10.207.114.173] ([202.45.12.164]) by smtp.gmail.com with ESMTPSA id i37sm3703161pje.23.2019.10.17.19.27.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 17 Oct 2019 19:27:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-4578AEB5-C0BF-4A80-A3D8-A7E3454A7A1B"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Satoru Matsushima <satoru.matsushima@gmail.com>
In-Reply-To: <CAD6AjGRxFr1pg7W-9Y_F7PVX6WFhRfvazBhYRVF_qq_wnqYv8w@mail.gmail.com>
Date: Fri, 18 Oct 2019 11:27:13 +0900
Cc: Hirofumi Ichihara <ichihara.hirofumi@gmail.com>, Clarence Filsfils <cfilsfil@cisco.com>, Lizhenbin <lizhenbin@huawei.com>, Satoru Matsushima <satoru.matsushima@g.softbank.co.jp>, "ipv6@ietf.org" <ipv6@ietf.org>, SPRING WG List <spring@ietf.org>
Message-Id: <4E88B5A5-11A2-4258-82ED-5BC186CDD1A4@gmail.com>
References: <CAD6AjGRxFr1pg7W-9Y_F7PVX6WFhRfvazBhYRVF_qq_wnqYv8w@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
X-Mailer: iPad Mail (17A860)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/FU-H1gzwk58-HF1QX00mCSvpfVk>
Subject: Re: [spring] New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
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, 18 Oct 2019 02:27:21 -0000

Hi Cameron,

#get back SPRING list again since it is a use case under SR architecture.

> Its seems your scenario could be instructive for us , i think it is generally common to dual-stack the edge first, but LINE has a different path

AFAIK, the IP CLOS fabric in LINE DC also supported IPv4 while it is IPv6-only network which was used to connect the hypervisors with IPv4 addresses using RFC5549 based control-plane solution (i.e, v4 NLRI w/ v6 nhop).

It means that the LINE case is also an incremental SRv6 deployment onto existing IPv6 data-plane.

Cheers,
--satoru

> On Oct 18, 2019, at 11:20, Ca By <cb.list6@gmail.com> wrote:
> 
> 
> Hirofumi,
> 
> Dropping SPRING since this is strictly an ipv6 question. 
> 
> Do you happen to have a deck about LINE supporting ipv6 on the internet? I notice api.line.me does not have aaaa record. And it is curious that you have the ability to deploy SRv6 internally but not dual-stack client internet services. 
> 
> Its seems your scenario could be instructive for us , i think it is generally common to dual-stack the edge first, but LINE has a different path
>  
> thanks,
> CB
> 
>> On Thu, Oct 17, 2019 at 6:29 PM Hirofumi Ichihara <ichihara.hirofumi@gmail.com> wrote:
>> Hi,
>> 
>> Let me introduce LINE's SRv6 DC use case as well. We have already deployed SRv6 network with our private cloud on production environment. Please have a look at this slide( https://speakerdeck.com/line_developers/line-data-center-networking-with-srv6 ) if you're interested in our use case. And also we're interested in other DC use cases and implementations.. Please let me know if you have such information.
>> 
>> Thanks,
>> Hirofumi
>> 
>> 
>> 2019年10月17日(木) 21:31 Lizhenbin <lizhenbin@huawei.com>:
>>> Hi Folks,
>>> We updated the SRv6 deployment draft as follows. There are two new deployments of SRv6 from China for reference: 
>>> China Unicom and CERNET2. 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. Moreover the easy incremental deployment advantage of SRv6 (refer 
>>> to https://tools.ietf.org/html/draft-xie-spring-srv6-network-migration-00 ) facilitates the SRv6 deployments in the existing 
>>> network. Besides the SRv6 deployments proposed in the draft, there will be more SRv6 for different application scenariosin 
>>> the near future. These SRv6 deployments  are also promoting the IPv6 deployment and more IPv6 traffic will be beared by 
>>> these networks.  
>>> 
>>> 
>>> 
>>> Best Regards,
>>> Robin
>>> 
>>> 
>>> 
>>> ________________________________________
>>> 发件人: internet-drafts@ietf.org [internet-drafts@ietf.org]
>>> 发送时间: 2019年10月15日 11:15
>>> 收件人: Zafar Ali; Clarence Filsfils; Lizhenbin; Satoru Matsushima
>>> 主题: New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
>>> 
>>> A new version of I-D, draft-matsushima-spring-srv6-deployment-status-02.txt
>>> has been successfully submitted by Zafar Ali and posted to the
>>> IETF repository.
>>> 
>>> Name:           draft-matsushima-spring-srv6-deployment-status
>>> Revision:       02
>>> Title:          SRv6 Implementation and Deployment Status
>>> Document date:  2019-10-14
>>> Group:          Individual Submission
>>> Pages:          19
>>> URL:            https://www.ietf.org/internet-drafts/draft-matsushima-spring-srv6-deployment-status-02.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/
>>> Htmlized:       https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-02
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-matsushima-spring-srv6-deployment-status
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-matsushima-spring-srv6-deployment-status-02
>>> 
>>> Abstract:
>>>    This draft provides an overview of IPv6 Segment Routing (SRv6)
>>>    deployment status.  It lists various SRv6 features that have been
>>>    deployed in the production networks.  It also provides an overview of
>>>    SRv6 implementation and interoperability testing status.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>> 
>>> The IETF Secretariat
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------