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

Hirofumi Ichihara <ichihara.hirofumi@gmail.com> Fri, 18 October 2019 02:58 UTC

Return-Path: <ichihara.hirofumi@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 8A85B1201DC; Thu, 17 Oct 2019 19:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, 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 Q_2TNU3RrffC; Thu, 17 Oct 2019 19:58:17 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 DE481120044; Thu, 17 Oct 2019 19:58:16 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id b1so3030670vsr.10; Thu, 17 Oct 2019 19:58:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EqJcQPXKYMknnU25uVueqvxlg+7WRV7B8mp7U2Ea+gw=; b=fc3tSGS5xzTONhowV9ASIDJIxg9Qp6E03WiMJnviTSKyuaB5bpDGUKQNw3+1CS8lgS DCTN2CnQwaZl21VFH2paJ4LTCYh/iAqPEhc57N+r1WgZPW9sjPiMv6UmsFc0MoKlKOdP tx5QzFc4Pfk/xp1q02hPSSNHDfMzkC2a2mrE291sKuh0GaHoFtBT73gpoN+oSlL9V0/T jiyxwH9CXpfAHzjNYsmUwaQH40/QfOFQpjd/Oz7MlVA8UqjGP0MYK+KNKSB61zHO/Kc/ jKo14i7rzvroBrlkPxfaMv0z4s9LHok0G18LGWAF/fqYa7enZHhGEjtlQe4On1CezF4A KN3w==
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; bh=EqJcQPXKYMknnU25uVueqvxlg+7WRV7B8mp7U2Ea+gw=; b=T4KIKe0aDI7N98JyTcr/46YtpKLEH0qQKs5iFzk0GKO5Dxk8BmNyG0p7etsK9vFGp3 S7RrEld5iWqUAnqXUVUcJFC1fRyocHixwxeX7K6M61LdNFK2uoKZ84+jix/DfBfuoc0G ZeOFGFvoJ59MMrrwnaCMILJxWpFdsDHEIvtH0XFhYSsZH4W217fUDDhWX2/Z9M7btlRb FL6L9WxXovY6nTjF3BfR4K3jFCIYUP57SrrhVz1b/yssctDxebhR4yTOrcS4C34Vmd+f GEGrEkBocvdwzL6Ojy5WMD+ejW/HvyPKaN0aGiUZUATiCENv9zrfEMTs/kHb2yBwYf2T vbHQ==
X-Gm-Message-State: APjAAAV6EDBBXtPmxCSHxV6pMl4NnXohnIA/B3HtmgshqgbotEzWw8f7 ic81jIsYpZQruK2tCnO3tmPcGAGZJan98Teap6c=
X-Google-Smtp-Source: APXvYqyJiBRBG9sDm5grTc9leWsOzMxN69VNe+TwnaG+WPjyHsc//W5QEbAE1B7S/D87lx3sLbM7qmRNhcA+2RUarPY=
X-Received: by 2002:a67:d785:: with SMTP id q5mr4148410vsj.190.1571367495953; Thu, 17 Oct 2019 19:58:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAD6AjGRxFr1pg7W-9Y_F7PVX6WFhRfvazBhYRVF_qq_wnqYv8w@mail.gmail.com> <4E88B5A5-11A2-4258-82ED-5BC186CDD1A4@gmail.com>
In-Reply-To: <4E88B5A5-11A2-4258-82ED-5BC186CDD1A4@gmail.com>
From: Hirofumi Ichihara <ichihara.hirofumi@gmail.com>
Date: Fri, 18 Oct 2019 11:58:04 +0900
Message-ID: <CAKrd4DNLrBfQ0uWjw0ceRunBMfTGe7gvsHv7TsbUVX0Qp6021w@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
Cc: Clarence Filsfils <cfilsfil@cisco.com>, Satoru Matsushima <satoru.matsushima@gmail.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>
Content-Type: multipart/alternative; boundary="00000000000068717c05952681fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/IMavej8RS3VKQAAGpX_GX96pbHo>
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:58:21 -0000

Hi Cameron,

I believe that we'll support IPv6 for our LINE service on the internet but
it's different from this use case like Satoru mentioned. In this case, we
focus on providing multi-tenant network for our users with SRv6.

Thanks,
Hirofumi

2019年10月18日(金) 11:27 Satoru Matsushima <satoru.matsushima@gmail.com>:

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