Re: [nvo3] [MBONED] NVO3 Multicast Framework
Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 30 January 2017 22:25 UTC
Return-Path: <sarikaya2012@gmail.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 7B948129640; Mon, 30 Jan 2017 14:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 B-M5RonVSv2c; Mon, 30 Jan 2017 14:25:14 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 8E9F612963D; Mon, 30 Jan 2017 14:25:13 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id c85so235712451wmi.1; Mon, 30 Jan 2017 14:25:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=S16zX+YNmhM0Dlfes+8vS1+t//0VWSUx15xHg8norL8=; b=IMmjQG2t+P4fz/FU6b/Rd3SYjhZQyUEdmTUKiCZk8hCYIhMWc+uthBvGjuq2LTBOH8 duXNkiqfAd1jJluH/GAq/MxNxXIZ8ujPqPPDo09+P4SSTEW2cK/Lo4SHv5N/47mJuQ8a n5OVUCVkQftv5aEinlombax52le3yPuAxcuYaaC1mtZEDU/euGK2HA5k4zDd5cXRhvuP YzSMuLYJreM8VY+za+XXjx5YPPhSWey+Dihaf9SKi7m0RVQAPgIXYtrHD3ttKqqkGodS ydU58tIg4U6Wuns2zBeJ2havs2Ez1Vo65U4iGuUl7uS5f8okbbLrAwUbPlSSPxTiNhva 3Ovw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=S16zX+YNmhM0Dlfes+8vS1+t//0VWSUx15xHg8norL8=; b=GzdbX9yMAlbXbm8vBW3Div7n4cdHJldJiAzk2M6gG0TZURK8ChFlJcZBeiAj7XLUoZ 2WB2x3IbH4e0Gk5Hk2lHSiJrfVfWoXlB8CV1WtLpgl9jZWv7oBFEg+jmy3IzvaQ30HDb prhK67WzUpGbKCcR7rpv+4+zeypXTlyW9ulSwyXGNSHTmPySOW39OjgYMcIx+EAEOSBU ZDpC5O/LNM/rIVlfmgPeal1lHBMrfhBZpzFzfgcIo/7ngoWxoKFRtvd2EG2TnKkyw9Q8 Z0eH6/sGHZxZvhYknkLAo+o6KQXI9rceMne7/QgNYKd9IPncKYgPmSyQaanef1XEtVjo iAkA==
X-Gm-Message-State: AIkVDXLwQBlP6MtjrNOKWTZ1O+TKtnh87DGa6pNVcwfeEE8DPclXdRapHKITa6ISFJIoTF8M1ZkGvOVuwItWhg==
X-Received: by 10.223.138.220 with SMTP id z28mr20182233wrz.26.1485815111883; Mon, 30 Jan 2017 14:25:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.138.146 with HTTP; Mon, 30 Jan 2017 14:25:11 -0800 (PST)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F6592395EB@SJCEML702-CHM.china.huawei.com>
References: <20160512144607.T22764@sapphire.juniper.net> <CAOZewqawSpSyR_HeqafmEZbWYgwX4zV38C4f_-6BcducLiR=Fg@mail.gmail.com> <4AB9E624-D344-420F-A474-10C0BD59F512@gmail.com> <D37706A7.9C91F%matthew.bocci@nokia.com> <CA+-tSzxQVXLa6_+sDzJqN+7Axsbx-fAuG70dv+CDpkT8z4VNYw@mail.gmail.com> <4481e65fecfc4962839023e162521980@EMEAWP-EXMB11.corp.brocade.com> <4A95BA014132FF49AE685FAB4B9F17F6592388CE@SJCEML702-CHM.china.huawei.com> <de48f270-e8b3-41a9-f9cf-9fd4e7c4735d@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F659238E63@SJCEML702-CHM.china.huawei.com> <6211c9af-38fb-d8d5-7c85-ad5712be26e6@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F6592392FB@SJCEML702-CHM.china.huawei.com> <cbfacff3-dce1-b19c-8017-ecd901466d31@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F659239350@SJCEML702-CHM.china.huawei.com> <004bdb88-ce49-8c8d-3eac-1865c77b00a9@isi.edu> <ea1c9344-aac1-05ce-2fda-c0a6db02a691@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F659239409@SJCEML702-CHM.china.huawei.com> <51d4494d-ddf9-2667-9caa-6b35c34e7ff1@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F6592395EB@SJCEML702-CHM.china.huawei.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 30 Jan 2017 16:25:11 -0600
Message-ID: <CAC8QAcei+iwcUtEvLeQpXLpLMZLOqdkCMTRqwj3Zzzyb++EiLA@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/WyULoehxrG8q4PT5HOXsuoWrCU8>
Cc: "<nvo3@ietf.org>" <nvo3@ietf.org>, Joe Touch <touch@isi.edu>, "Williamson, Beau" <Beau.Williamson@t-mobile.com>, Anoop Ghanwani <anoop@alumni.duke.edu>, Olufemi Komolafe <okomolaf@brocade.com>, "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, Dino Farinacci <farinacci@gmail.com>, MBONED WG <mboned@ietf.org>, Truman Boyes <truman@versionsix.org>
Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: sarikaya@ieee.org
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, 30 Jan 2017 22:25:16 -0000
On Mon, Jan 30, 2017 at 4:17 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote: > Joe, > > > > Thanks for your suggestion. > > > > I added the following sentence in the Section 3 (Multicast Mechanisms in > networks that use NVO3): > > > > What makes NVO3 different from any other network is that some NVEs, > especially the NVE implemented on server, might not support PIM or other > multicast mechanisms. They might just encapsulate the data packets from VMs > with an outer header. Therefore, it is important for networks using NVO3 to > have mechanisms for NVEs, especially the ones that do not support multicast, > to map multicast traffic from VMs (users/applications) to proper Outer > Header, e.g. figuring out the outer destination address if NVE does not > support multicast (e.g. PIM). > PIM support is needed at the NVE only if any of the VMs is a multicast source which is usually a rare situation. Otherwise MLD/IGMP Proxy would normally need to be supported at the NVE level. Regards, Behcet > > > > > If it is Okay with you, I will upload the draft. > > > > Thanks, Linda > > > > From: Joe Touch [mailto:touch@isi.edu] > Sent: 2017年1月30日 14:02 > > > To: Linda Dunbar <linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Bocci, > Matthew (Nokia - GB) <matthew.bocci@nokia.com> > Cc: MBONED WG <mboned@ietf.org>; Truman Boyes <truman@versionsix.org>; > <nvo3@ietf.org> <nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com>; Dino Farinacci <farinacci@gmail.com> > Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > > > > > On 1/30/2017 11:38 AM, Linda Dunbar wrote: > > Joe, > > > > You asked: > > What makes NVO3 different from any other network? > > > > Answer: Some NVEs, especially the NVE implemented on server, don’t support > PIM or other multicast mechanism. They just encapsulate the data packets > from VMs with an outer header. > > Then the requirement would be: > NVO3 does not require native multicast, but does require supported > multicast capability. > > > The “UNIQUE needs of NVO3” is to have the mechanism for NVEs (especially > the ones that don’t support multicast) to map multicast traffic from VMs > (users/applications) to proper Outer Header. E.g. if NVE doesn’t support > multicast (PIM), what outer destination address should be. > > > That needs to be explained in detail, especially for ways to support > multicast without PIM. > > > All we need is to differentiate multicast messages originated from > users/applications from the infrastructure multicast at the introduction > section. Not intended to describe in detail of the Infrastructure multicast. > > > > I don’t understand how RFC3819 (Advice for Internet Subnetwork Designs) can > be used. RFC 3819 talks about MTU, TCP/link retransmission, etc. > > > See sections 5 and 6. > > Joe > > > > > > > Linda Dunbar > > > > > > From: Joe Touch [mailto:touch@isi.edu] > Sent: 2017年1月30日 12:42 > To: Linda Dunbar <linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Bocci, > Matthew (Nokia - GB) <matthew.bocci@nokia.com> > Cc: MBONED WG <mboned@ietf.org>; Truman Boyes <truman@versionsix.org>; > <nvo3@ietf.org> <nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com>; Dino Farinacci <farinacci@gmail.com> > Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > Note: most of what you want to say about multicast has already been observed > in RFC 3819. > > The discussion in section 1.1 should refer to LANE (RFC1577) as an example. > > However, before we get down into this in detail, I have to ask: what makes > NVO3 different from any other network? > > This WG doesn't need one doc for everything an NVO3 network needs that a > network already needs. The docs should focus on the UNIQUE needs of NVO3 or > ways in which NVO3 provides multicast that are not available in generic > networks. > > The rest of the discussion of the need for multicast, etc., ought to cite > existing RFCs. > > Joe > > On 1/30/2017 10:35 AM, Joe Touch wrote: > > Hi, Linda, > > This isn't correct grammar. > > Do you want to say: > > Infrastructure multicast is a capability needed by networking services, such > as Address Resolution Protocol (ARP), Neighbor Discovery (ND), Dynamic Host > Configuration Protocol (DHCP), multicast Domain Name Server (mDNS), etc.. > > Joe > > On 1/30/2017 10:21 AM, Linda Dunbar wrote: > > Joe, > > > > Are you ok with the following? > > > > Infrastructure multicast are for networking services, such as Address > Resolution Protocol (ARP), Neighbor Discovery (ND), Dynamic Host > Configuration Protocol (DHCP), multicast Domain Name Server (mDNS), etc.. > > > > Linda > > > > From: Joe Touch [mailto:touch@isi.edu] > Sent: 2017年1月30日 12:03 > To: Linda Dunbar <linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Bocci, > Matthew (Nokia - GB) <matthew.bocci@nokia.com> > Cc: MBONED WG <mboned@ietf.org>; Truman Boyes <truman@versionsix.org>; > <nvo3@ietf.org> <nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com>; Dino Farinacci <farinacci@gmail.com> > Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > I'd suggest "networking services", only to avoid the implication that these > are all L3. > > Joe > > > > On 1/30/2017 9:58 AM, Linda Dunbar wrote: > > Joe, > > > > Do you mean the following? > > > > Infrastructure multicast are originated by network services for the purpose > of establishing network topology and reachability, such as Address > Resolution Protocol (ARP), Neighbor Discovery (ND), Dynamic Host > Configuration Protocol (DHCP), multicast Domain Name Server (mDNS), etc.. > > > > Linda > > > > From: Joe Touch [mailto:touch@isi.edu] > Sent: 2017年1月30日 11:49 > To: Linda Dunbar <linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Bocci, > Matthew (Nokia - GB) <matthew.bocci@nokia.com> > Cc: MBONED WG <mboned@ietf.org>; Truman Boyes <truman@versionsix.org>; > <nvo3@ietf.org> <nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com>; Dino Farinacci <farinacci@gmail.com> > Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > Hi, Linda, > > These are not all "network protocols", as I noted already. > > It might be useful to describe them all as "services", though. > > I.e., to replate "network protocols" with "services" (or maybe even > "networking services" - to distinguish them from OS services, but not give > the impression they belong at the "network" layer). > > Joe > > > > On 1/30/2017 8:17 AM, Linda Dunbar wrote: > > Joe, > > > > Thank you very much for articulating a more precise definition. > > > > How about this: > > Infrastructure multicast are originated by network protocols for the purpose > of establishing network topology and reachability, such as Address > Resolution Protocol (ARP), Neighbor Discovery (ND), Dynamic Host > Configuration Protocol (DHCP), multicast Domain Name Server (mDNS), etc.. > > > > Application-specific multicast traffic are originated and consumed by user > applications. > > Linda > > > > From: Joe Touch [mailto:touch@isi.edu] > Sent: 2017年1月27日 18:20 > To: Linda Dunbar <linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Bocci, > Matthew (Nokia - GB) <matthew.bocci@nokia.com> > Cc: MBONED WG <mboned@ietf.org>; Truman Boyes <truman@versionsix.org>; > <nvo3@ietf.org> <nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com>; Dino Farinacci <farinacci@gmail.com> > Subject: Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > > > > > On 1/27/2017 4:03 PM, Linda Dunbar wrote: > > [Linda] Infrastructure multicast are originated by network nodes for the > purpose of establishing network topology and reachability, such as Address > Resolution Protocol (ARP), Neighbor Discovery (ND), Dynamic Host > Configuration Protocol (DHCP), multicast Domain Name Server (mDNS), etc.. > > + Also, how would you classify protocols like OSPF, PIM, VRRP etc that are > dependent on multicast? Even if you do not consider them relevant for this > framework, perhaps you should briefly mention them? > > [Linda] I don’t think we can enumerate all network protocols (many of them > use multicast). The purpose is to differentiate multicast originated by > network nodes and the multicast originated by applications. > > DHCP and mDNS are applications ("L7"). > > Network nodes don't originate anything; their protocol layers do (link, > network, transport, application). > > It might be useful to focus on the difference being "network infrastructure" > vs "user applications" as the better way to describe the difference. I don't > think "network nodes vs. applications" is clear or meaningful. > > Joe > > > > > > > > > > > > > _______________________________________________ > nvo3 mailing list > nvo3@ietf.org > https://www.ietf.org/mailman/listinfo/nvo3 >
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Williamson, Beau
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Anoop Ghanwani
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Anoop Ghanwani
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Anoop Ghanwani
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Truman Boyes
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Bocci, Matthew (Nokia - GB)
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Anoop Ghanwani
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Olufemi Komolafe
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Behcet Sarikaya
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Joe Touch
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar
- Re: [nvo3] [MBONED] NVO3 Multicast Framework Linda Dunbar