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

Hirofumi Ichihara <ichihara.hirofumi@gmail.com> Sat, 19 October 2019 02:36 UTC

Return-Path: <ichihara.hirofumi@gmail.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 CF58B120086; Fri, 18 Oct 2019 19:36:00 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 uAQ8BlfvUpDa; Fri, 18 Oct 2019 19:35:56 -0700 (PDT)
Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (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 933E112010F; Fri, 18 Oct 2019 19:35:56 -0700 (PDT)
Received: by mail-vk1-xa33.google.com with SMTP id d126so1680030vkf.7; Fri, 18 Oct 2019 19:35:56 -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=W8RL/JMEMPECt70fYwxjy7Av330hTdSixtcalODM7xQ=; b=rHATt0ds2ZYgNFOp+lQhv9m2MTK6ZGePuCfwRvkiFSoDWZawFS4QrJdhV06ef5RZWI t5rYnwNJMfl98XmgdNjxVIuIuaYtiBJpAF8tGO1qozzp4KUMJjd34DUurF3PpPLTQ2Am FjhUH6GpmgVysbfQuudZFaFetF7wrJVZK8nsE1AH0pvaGLy7Snst+VLChr7DSUFOfuJl CTmIqp5jjYNLMLAAvf92RoyQNEjOd4ohgjI1+NgMjpnCDCqNfr6KMVw84uhlLns3idl7 MP97lWxypwlFHphbc4rizSDnwfLGAyI9n80ab1NRH/nI2LPABf5uA3mQ60qQRHfXmQYJ 3H4w==
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=W8RL/JMEMPECt70fYwxjy7Av330hTdSixtcalODM7xQ=; b=uBbz0u3vlAPJZnDp3Z9zOFIX2jGD3cMunkcLkox73uOV5807lv9P9epBRUsPmHmOmS KQit1YuqqjPanwfEhJYm21duevNBMVck9OPiG+U8Pamh4R9Wm4K+XTfFsYrrxJwMEXal 7yu4iRcfrhLftqGt+9Az9sNM3n3FHFI8XCNoIN0Xl6RrG8Xg+DcJ1xAnLRculw7rcs2X Y3r0kfkgFIUDSXP3SK20r3b+x2NrHUSrRaYwNPYK3601Ur9dciwkzTRcUlpNQ9EDFVHb Ia4K8X93fjKBnVp+hsqqejet886jZlaz1LBLfNT5Kg5w42GyBoI03SVrEqHsXENx6Qmf VFdg==
X-Gm-Message-State: APjAAAWBwctY2CcinTEY97YMrqpqB5/RKVegV2jer9upPFlpf2vJXGVn 2bgCQsZEXeAOMB5knER5prQ9KcjQCHUSEYc1AYM=
X-Google-Smtp-Source: APXvYqz6XQmFvqsKhOEcZvUlO67wLrVicKMMVgPgwFRgfcYC9oD6gc97i9/BL13Wxqet86BAH6nS0yiwxEpv5iAJ+GA=
X-Received: by 2002:a1f:c441:: with SMTP id u62mr498274vkf.88.1571452555432; Fri, 18 Oct 2019 19:35:55 -0700 (PDT)
MIME-Version: 1.0
References: <157110930835.24708.13140748426444834467.idtracker@ietfa.amsl.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D93503A7B@DGGEMM532-MBX.china.huawei.com> <CAKrd4DP3hO7eGu7Rb9oNAdvg==BoZ25L6_ANoaZ9pqAENma0xw@mail.gmail.com> <fb5a3c31-8e50-4ad1-95a1-9cb79e7fbc0d@Spark> <CAOj+MMEjSwLi05Bake6Xp1bNs5-OpZvE4nd41=2cdYWiSJX+Gw@mail.gmail.com> <00267e23-07f2-40c0-9158-6a61217a7b91@Spark>
In-Reply-To: <00267e23-07f2-40c0-9158-6a61217a7b91@Spark>
From: Hirofumi Ichihara <ichihara.hirofumi@gmail.com>
Date: Sat, 19 Oct 2019 11:35:44 +0900
Message-ID: <CAKrd4DN+QFfnfXex=D3TXjQpTsETJzRB-oz8pob5NGtdwvuwTg@mail.gmail.com>
Subject: Re: [spring] Fw: New Version Notification for draft-matsushima-spring-srv6-deployment-status-02.txt
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, "spring@ietf.org" <spring@ietf.org>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="00000000000059189205953a4fe3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RCKnCe2bnVP5dUKxBWWjVELI8a8>
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: Sat, 19 Oct 2019 02:36:01 -0000

Hi,

> Reading your slides, it looks like completely host based overlay design
Right. We use SRv6 for overlay only now and there are just two kind of SR
aware nodes, that is Hypervisor and NetworkNode. We'd like to extend SR to
fabric switch and NFV device in future so that we use other SR
features(e.g. SFC, TI-LFA)

Thanks,
Hirofumi

2019年10月19日(土) 6:00 Jeff Tantsura <jefftant.ietf@gmail.com>:

> No, I don’t, waste of resources, in a leaf-spine network any ECMP path is
> loop-free per definition.
> My questions is really about use of SRv6 in the fabric (not on the hosts)
>
> Cheers,
> Jeff
> On Oct 18, 2019, 1:56 PM -0700, Robert Raszuk <robert@raszuk.net>, wrote:
>
> Hi Jeff,
>
> > In case of link/node failure it would use fast-rehash over ECMP rather
> that TI-LFA?
>
> Do you think that this is a good idea to consider using TI-LFA in a Clos
> fabric ?
>
> Thx,
> R.
>
> On Fri, Oct 18, 2019 at 10:53 PM Jeff Tantsura <jefftant.ietf@gmail.com>
> wrote:
>
>> Hello Hirofumi,
>>
>> Many thanks for sharing the use case.
>> Reading your slides, it looks like completely host based overlay design,
>> e.g. no fabric switch is SRv6 aware, not using any of SRv6 functionality
>> (TE, IPFRR, etc) and their solely function is to forward traffic towards
>> destinations of remote hosts over L3 IP fabric? In case of link/node
>> failure it would use fast-rehash over ECMP rather that TI-LFA?
>>
>> Thanks in advance!
>>
>> Cheers,
>> Jeff
>> On Oct 17, 2019, 6:30 PM -0700, 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
>> --------------------------------------------------------------------
>>
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring
>>
>