IETF Logo Mail Archive

Re: [nvo3] [MBONED] NVO3 Multicast Framework

Linda Dunbar <linda.dunbar@huawei.com> Mon, 30 January 2017 16:18 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 2B8C3129536; Mon, 30 Jan 2017 08:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.408
X-Spam-Level:
X-Spam-Status: No, score=-7.408 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, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 BlMc11x3oGry; Mon, 30 Jan 2017 08:18:47 -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 7B36812951D; Mon, 30 Jan 2017 08:18:45 -0800 (PST)
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 DFM42757; Mon, 30 Jan 2017 16:18:43 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 30 Jan 2017 16:18:41 +0000
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.133]) by SJCEML703-CHM.china.huawei.com ([169.254.5.69]) with mapi id 14.03.0235.001; Mon, 30 Jan 2017 08:17:29 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Joe Touch <touch@isi.edu>, Olufemi Komolafe <okomolaf@Brocade.com>, Anoop Ghanwani <anoop@alumni.duke.edu>, "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Thread-Topic: [nvo3] [MBONED] NVO3 Multicast Framework
Thread-Index: AQHRteC+NFF/VS0VHUej3IfjF8qBRp/IC/wAgAA0MwCAABTVAIAAAd+AgAAOzICAAACPgIAAMnkAgAAC9ACAAAM4gIAAAn+AgA7d2YCAAGWkAIAIlWCggW4HyHCAAJDhAIADpxxg
Date: Mon, 30 Jan 2017 16:17:27 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F659238E63@SJCEML702-CHM.china.huawei.com>
References: <20160512144607.T22764@sapphire.juniper.net> <17B47CE8-D558-4748-88D6-FEC17A02357A@gmail.com> <D36A11E1.9BBC8%matthew.bocci@nokia.com> <429D0BE5-C6A5-4AEE-975E-2A5C7ED65631@gmail.com> <807243401bcc4ca3a7e014690a920f96@PRDMSEXCH002.gsm1900.org> <F0088019-8A54-47B6-B600-303996B58C99@gmail.com> <CA+-tSzxH9OfUasUXssJRfP1ijXZYbAugeoSBGVErZ-smmtF1ww@mail.gmail.com> <1A4AB590-8E67-487A-8C32-FA0D701F20C1@gmail.com> <CA+-tSzwqwD4Jb+5bjoKFOmJh-pXODOty_tMHa=DcfBarZmZerg@mail.gmail.com> <1F87ED5D-C2D5-4308-9972-6671063D4F52@gmail.com> <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>
In-Reply-To: <de48f270-e8b3-41a9-f9cf-9fd4e7c4735d@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.184]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F659238E63SJCEML702CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.588F6763.02E2, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.133, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 5adef3dd4fee724d88d05845f3b90430
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/gd8Ckd1MWH5Ne9ZYG5NwsEWgiI0>
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
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
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, 30 Jan 2017 16:18:49 -0000

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

v2.23.0 | Report a Bug | By Email