[nvo3] Comments on draft-ietf-nvo3-mcast-framework-01
Lucy yong <lucy.yong@huawei.com> Fri, 29 January 2016 16:39 UTC
Return-Path: <lucy.yong@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B7D1A8749 for <nvo3@ietfa.amsl.com>; Fri, 29 Jan 2016 08:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 5d32LCWWcSFB for <nvo3@ietfa.amsl.com>; Fri, 29 Jan 2016 08:39:20 -0800 (PST)
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 AFE6F1A700A for <nvo3@ietf.org>; Fri, 29 Jan 2016 08:39:18 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDQ53686; Fri, 29 Jan 2016 16:39:14 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 29 Jan 2016 16:38:30 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0235.001; Fri, 29 Jan 2016 08:38:23 -0800
From: Lucy yong <lucy.yong@huawei.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, NVO3 <nvo3@ietf.org>
Thread-Topic: Comments on draft-ietf-nvo3-mcast-framework-01
Thread-Index: AQHRWrN4bPXC6fv6ZUiHhxoPqsaeWg==
Date: Fri, 29 Jan 2016 16:38:23 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D57239FDA@dfweml701-chm>
References: <D2C7CDD1.8ED28%matthew.bocci@nokia.com>
In-Reply-To: <D2C7CDD1.8ED28%matthew.bocci@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.134.55]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D57239FDAdfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.56AB95B4.02AA, 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: 565f6eaea4998cdc0077668d67d97890
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/4nacf45ML9tJQLKNi3Zo0NbqUwc>
Cc: "draft-ietf-nvo3-mcast-framework@tools.ietf.org" <draft-ietf-nvo3-mcast-framework@tools.ietf.org>
Subject: [nvo3] Comments on draft-ietf-nvo3-mcast-framework-01
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 29 Jan 2016 16:39:23 -0000
First of all, I support the draft to be published as RFC. It addresses a useful application. Here are some comments for the improvement. General: - NVO3 may have multi-homing NVE configuration, please address that each mcast method is able to support multi-homing NVEs. - It is necessary to elaborate security concerns in section 7 when using mcast methods in nvo3 environment - Several citations refer to old drafts, should point to the corresponding RFCs. - Terms: Tenant system, TSS, hosts, VM, are used in the draft here and there, suggest making consistent or state out at beginning that they mean the same entity. In Section 3.2, the following text is unclear: ….When the members of a multicast group are outside the NVO3 domain, it is necessary for NVO3 gateways to keep track of the remote members of each multicast group. The NVEs then communicate these mappings to the NVA. Even if the membership is not communicated to the NVA, if it is necessary to prevent hosts attached to an NVE that have not subscribed to a multicast group from receiving the multicast traffic, the NVE needs to maintain the multicast group membership. Suggested text as follow: …When the members of a multicast group are outside the NVO3 domain, it is necessary for NVO3 gateways to keep track of the remote members of each multicast group. The NVEs and gateways communicate the interested multicast groups to the NVA. To prevent hosts attached to an NVE that have not subscribed to a multicast group from receiving the multicast traffic, the NVE needs to maintain the multicast group membership. In section 3.4, need a reference to BIER solution. Section 5.1 case may happen to all mcast methods, not only to the method in 3.3, clarify which mcast solution still can work and which will not. In addition, clarify what are TSS router and TS’s router. Cheers, Lucy From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Friday, January 22, 2016 6:16 AM To: Bocci, Matthew (Nokia - GB); NVO3 Cc: draft-ietf-nvo3-mcast-framework@tools.ietf.org Subject: Re: [nvo3] WG last call for draft-ietf-nvo3-mcast-framework-01 WG I am going to let this last call run for a couple more weeks as I have not seen any comments. The new closing date is Friday 5th Feb 2016. Regards Matthew From: Dacheng Zhang <nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>> on behalf of Matthew Bocci <matthew.bocci@alcatel-lucent.com<mailto:matthew.bocci@alcatel-lucent.com>> Date: Tuesday, 5 January 2016 at 10:40 To: NVO3 <nvo3@ietf.org<mailto:nvo3@ietf.org>> Cc: "draft-ietf-nvo3-mcast-framework@tools.ietf.org<mailto:draft-ietf-nvo3-mcast-framework@tools.ietf.org>" <draft-ietf-nvo3-mcast-framework@tools.ietf.org<mailto:draft-ietf-nvo3-mcast-framework@tools.ietf.org>> Subject: [nvo3] WG last call for draft-ietf-nvo3-mcast-framework-01 This email begins a two week working group last call for draft-ietf-nvo3-mcast-framework-01.txt. Please review the draft and post any comments to the NVO3 working group list. If you have read the latest version of the draft but have no comments and believe it is ready for publication as an Informational RFC, please also indicate so to the WG email list. This working group last call will close on Friday 21st January 2016. Best regards Matthew and Benson
- [nvo3] WG last call for draft-ietf-nvo3-mcast-fra… Bocci, Matthew (Matthew)
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Bocci, Matthew (Nokia - GB)
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Huaimo Chen
- [nvo3] Comments on draft-ietf-nvo3-mcast-framewor… Lucy yong
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Nicolas Bouliane
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Linda Dunbar
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Linda Dunbar
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Bocci, Matthew (Nokia - GB)
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Linda Dunbar
- Re: [nvo3] WG last call for draft-ietf-nvo3-mcast… Bocci, Matthew (Nokia - GB)