Re: [nvo3] Mirja Kühlewind's Discuss on draft-ietf-nvo3-mcast-framework-10: (with DISCUSS)

Linda Dunbar <linda.dunbar@huawei.com> Mon, 09 October 2017 21:35 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22ED9134218; Mon, 9 Oct 2017 14:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 7MiiaxnJqpL0; Mon, 9 Oct 2017 14:35:10 -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 8BB82133049; Mon, 9 Oct 2017 14:35:09 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DXF52082; Mon, 09 Oct 2017 21:35:07 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 9 Oct 2017 22:35:06 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.207]) by SJCEML703-CHM.china.huawei.com ([169.254.5.15]) with mapi id 14.03.0301.000; Mon, 9 Oct 2017 14:35:00 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-nvo3-mcast-framework@ietf.org" <draft-ietf-nvo3-mcast-framework@ietf.org>, Sam Aldrin <aldrin.ietf@gmail.com>, Matthew Bocci <matthew.bocci@alcatel-lucent.com>, "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>, "aldrin.ietf@gmail.com" <aldrin.ietf@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: Mirja Kühlewind's Discuss on draft-ietf-nvo3-mcast-framework-10: (with DISCUSS)
Thread-Index: AQHTQRdIZYlmYQN1bESV9QrLr38SMaLcB3zg
Date: Mon, 09 Oct 2017 21:34:59 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F6594A7DA2@SJCEML702-CHM.china.huawei.com>
References: <150756462789.31930.11118274476065231866.idtracker@ietfa.amsl.com>
In-Reply-To: <150756462789.31930.11118274476065231866.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.95.74]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F6594A7DA2SJCEML702CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59DBEB8B.0268, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.207, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 35ffd8bd55ac6529d1e88512a0158010
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/iVpQ2kX13B_8dGZKSDIh1HqEL-I>
Subject: Re: [nvo3] Mirja Kühlewind's Discuss on draft-ietf-nvo3-mcast-framework-10: (with DISCUSS)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Oct 2017 21:35:13 -0000

Mirja,

Actually sending more copies of the same packet, especially multicast packets, rarely cause congestion.
Congestion only occurs when links’ utilization reach close to 100% as most switches/routers today can handle wire speed forwarding. The rule of thumb of deploying network is 50% link utilization, especially in data center where links can be added very easily.

In addition, Application based multicast is less than 2% of total traffic. Anyway, to make Collin happy, I already inserted one sentence in the following original paragraph (in purple) in -10 version which has been uploaded:

      “This method requires multiple copies of the same packet to all NVEs that participate in the VN.  If, for example, a tenant subnet is spread across 50 NVEs, the packet would have to be replicated 50 times at the source NVE.  Obviously, this approach creates more traffic to the network that can cause congestion when the network load is high. This also creates an issue with the forwarding performance of the NVE.”

ECN for NVO3 network is totally different subject. It will take a lot to describe ECN clearly for NVO3 network. To the least, it is not even clear of the scenario, use cases, and implication for ECN for NVO3.

Therefore, we don’t believe it is within the scope of this draft to discuss or reference ECN for this draft.

Linda Dunbar

-----Original Message-----
From: Mirja Kühlewind [mailto:ietf@kuehlewind.net]
Sent: Monday, October 09, 2017 10:57 AM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-nvo3-mcast-framework@ietf.org; Sam Aldrin <aldrin.ietf@gmail.com>; Matthew Bocci <matthew.bocci@alcatel-lucent.com>; nvo3-chairs@ietf.org; aldrin.ietf@gmail.com; nvo3@ietf.org
Subject: Mirja Kühlewind's Discuss on draft-ietf-nvo3-mcast-framework-10: (with DISCUSS)

Mirja Kühlewind has entered the following ballot position for
draft-ietf-nvo3-mcast-framework-10: Discuss

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-nvo3-mcast-framework/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Based on the feedback provided by the tsv-art review (Thanks Colin!) I would like to see a paragraph or short section that discusses how replication as used in section 3.2 and 3.3 can impact multicast congestion control and also provides a pointer to draft-ietf-tsvwg-ecn-encap-guidelines-09 in case ECN is supported in the NVO network which can likely be the case in data center scenarios.