[bess] 答复: Lack of implementation for draft-ietf-bess-virtual-subnet-fib-reduction - submit to IESG?

Xuxiaohu <xuxiaohu@huawei.com> Thu, 13 October 2016 09:38 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4D012970F for <bess@ietfa.amsl.com>; Thu, 13 Oct 2016 02:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.217
X-Spam-Level:
X-Spam-Status: No, score=-7.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HGbFSgx0U8YJ for <bess@ietfa.amsl.com>; Thu, 13 Oct 2016 02:38:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90839127076 for <bess@ietf.org>; Thu, 13 Oct 2016 02:37:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CTC46062; Thu, 13 Oct 2016 09:37:56 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.5.93) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 13 Oct 2016 10:37:55 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Thu, 13 Oct 2016 17:37:51 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Martin Vigoureux <martin.vigoureux@nokia.com>, BESS <bess@ietf.org>
Thread-Topic: [bess] Lack of implementation for draft-ietf-bess-virtual-subnet-fib-reduction - submit to IESG?
Thread-Index: AQHSI9CAMxhRpI49lkaEqAUVJVjcm6CmG3yA
Date: Thu, 13 Oct 2016 09:37:51 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB21BE1@NKGEML515-MBX.china.huawei.com>
References: <57FCFEA8.3070400@nokia.com>
In-Reply-To: <57FCFEA8.3070400@nokia.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.184.181]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.57FF55F5.0007, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 574c18ad15d43dabb6684189f0c9ef3b
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/o3EkNE1eTicweXnj7fT5VITBqhU>
Subject: [bess] 答复: Lack of implementation for draft-ietf-bess-virtual-subnet-fib-reduction - submit to IESG?
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Oct 2016 09:38:03 -0000

Hi Martin,

We have just implemented RFC7814 a couple of months before in response to the demands of some of our customers, and those customers have deployed this L3-based overlay technology within their hyper-scale cloud data center network environment recently. We are planning to implement draft-ietf-bess-virtual-subnet-fib-reduction in the next step.

I have just noticed the following statement from (https://www.ravellosystems.com/blog/cloud-networking-layer-2-access-amazon-ec2/):

"... All major clouds, including Amazon EC2, Amazon VPC, Google Compute Engine and Microsoft Azure, allow only unicast datagrams with IP payloads. Broadcast datagrams and non-IP payloads are not allowed (with very limited exceptions to make parts of the essential ARP and DHCP protocols work). "

IMHO, when the L3 overlay technology is more widely deployed in hyper-scale data centers, the on-demand FIB installation mechanism as described in draft-ietf-bess-virtual-subnet-fib-reduction would become significantly important to the operators of those hyper-scale data centers . Once this mechanism becomes an IETF standard, those operators would ask their vendors to implement it. In fact, this is the case of our implementation of RFC7814. Hence, I strongly suggest to move this to IESG.

BTW, since it has become a fact that various data plane encapsulation schemes could be used for the L3VPN solution, hence I wonder whether the implementation of L3 Conversational Learning of DFA as described on page 36 of (http://www.valleytalk.org/wp-content/uploads/2013/08/ciscoDFA.pdf) could be looked as an existing implementation:)

Best regards,
Xiaohu

> -----邮件原件-----
> 发件人: BESS [mailto:bess-bounces@ietf.org] 代表 Martin Vigoureux
> 发送时间: 2016年10月11日 23:01
> 收件人: BESS
> 主题: [bess] Lack of implementation for
> draft-ietf-bess-virtual-subnet-fib-reduction - submit to IESG?
> 
> WG,
> 
> we have recently LCed draft-ietf-bess-virtual-subnet-fib-reduction and there was
> sufficient support to move forward. However we haven't received any input on
> existing implementations.
> 
> As per [1] we are thus asking the WG whether we should nevertheless move this
> to IESG or wait until implementations exist.
> 
> Please respond. Thank you.
> 
> 
> M&T
> 
> [1]:
> https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess