Re: [MBONED] [nvo3] NVO3 Multicast Framework
Joe Touch <touch@isi.edu> Tue, 31 January 2017 15:56 UTC
Return-Path: <touch@isi.edu>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D63F128B37; Tue, 31 Jan 2017 07:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.088
X-Spam-Level:
X-Spam-Status: No, score=-10.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199, T_KAM_HTML_FONT_INVALID=0.01] 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 cpUCm6_NCLRr; Tue, 31 Jan 2017 07:55:58 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 1AFF612947D; Tue, 31 Jan 2017 07:55:58 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v0VFt8Ch029973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 31 Jan 2017 07:55:09 -0800 (PST)
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>
References: <20160512144607.T22764@sapphire.juniper.net> <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> <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> <4A95BA014132FF49AE685FAB4B9F17F659239659@SJCEML702-CHM.china.huawei.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <dd605e7b-1927-ea85-6530-767163c3cc6f@isi.edu>
Date: Tue, 31 Jan 2017 07:55:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F659239659@SJCEML702-CHM.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------46B1EBEC88AB4A869D311EDF"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Wxb2jVZlxpaNrSAYd2sOSgkusP4>
Cc: MBONED WG <mboned@ietf.org>, Truman Boyes <truman@versionsix.org>, "<nvo3@ietf.org>" <nvo3@ietf.org>
Subject: Re: [MBONED] [nvo3] NVO3 Multicast Framework
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2017 15:56:01 -0000
That looks good. Joe On 1/30/2017 2:51 PM, Linda Dunbar wrote: > > Joe, > > > > I will also add the reference to RFC 3819 as it has good description > of the “infrastructure multicast”. > > > > /Infrastructure multicast /*is a capability needed by */networking > services//, such as Address Resolution Protocol (ARP), Neighbor > Discovery (ND). RFC3819 Section 5 & 6 have detailed description for > some of the infrastructure multicast [RFC 3819]. / > > > > Please let me know if it is good enough. > > > > Linda > > > > *From:*Linda Dunbar > *Sent:* 2017年1月30日13:41 > *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> > *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 > > > > Joe, > > > > To close the loop and make the document forward, we simply say the > following: > > > > /Infrastructure multicast /*is a capability needed by */networking > services//, such as Address Resolution Protocol (ARP), Neighbor > Discovery (ND). / > > / / > > 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. > > > > > > Linda > > > > *From:*Joe Touch [mailto:touch@isi.edu] > *Sent:* 2017年1月30日12:35 > *To:* Linda Dunbar <linda.dunbar@huawei.com > <mailto:linda.dunbar@huawei.com>>; Olufemi Komolafe > <okomolaf@Brocade.com <mailto:okomolaf@Brocade.com>>; Anoop Ghanwani > <anoop@alumni.duke.edu <mailto:anoop@alumni.duke.edu>>; Bocci, Matthew > (Nokia - GB) <matthew.bocci@nokia.com <mailto:matthew.bocci@nokia.com>> > *Cc:* MBONED WG <mboned@ietf.org <mailto:mboned@ietf.org>>; Truman > Boyes <truman@versionsix.org <mailto:truman@versionsix.org>>; > <nvo3@ietf.org <mailto:nvo3@ietf.org>> <nvo3@ietf.org > <mailto:nvo3@ietf.org>>; Williamson, Beau > <Beau.Williamson@t-mobile.com <mailto:Beau.Williamson@t-mobile.com>>; > Dino Farinacci <farinacci@gmail.com <mailto:farinacci@gmail.com>> > *Subject:* Re: [nvo3] [MBONED] NVO3 Multicast Framework > > > > 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> > <mailto:linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com> <mailto:okomolaf@Brocade.com>; Anoop > Ghanwani <anoop@alumni.duke.edu> <mailto:anoop@alumni.duke.edu>; > Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com> > <mailto:matthew.bocci@nokia.com> > *Cc:* MBONED WG <mboned@ietf.org> <mailto:mboned@ietf.org>; Truman > Boyes <truman@versionsix.org> <mailto:truman@versionsix.org>; > <nvo3@ietf.org> <mailto:nvo3@ietf.org> <nvo3@ietf.org> > <mailto:nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com> > <mailto:Beau.Williamson@t-mobile.com>; Dino Farinacci > <farinacci@gmail.com> <mailto: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> > <mailto:linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com> <mailto:okomolaf@Brocade.com>; Anoop > Ghanwani <anoop@alumni.duke.edu> > <mailto:anoop@alumni.duke.edu>; Bocci, Matthew (Nokia - GB) > <matthew.bocci@nokia.com> <mailto:matthew.bocci@nokia.com> > *Cc:* MBONED WG <mboned@ietf.org> <mailto:mboned@ietf.org>; > Truman Boyes <truman@versionsix.org> > <mailto:truman@versionsix.org>; <nvo3@ietf.org> > <mailto:nvo3@ietf.org> <nvo3@ietf.org> <mailto:nvo3@ietf.org>; > Williamson, Beau <Beau.Williamson@t-mobile.com> > <mailto:Beau.Williamson@t-mobile.com>; Dino Farinacci > <farinacci@gmail.com> <mailto: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> > <mailto:linda.dunbar@huawei.com>; Olufemi Komolafe > <okomolaf@Brocade.com> <mailto:okomolaf@Brocade.com>; > Anoop Ghanwani <anoop@alumni.duke.edu> > <mailto:anoop@alumni.duke.edu>; Bocci, Matthew (Nokia - > GB) <matthew.bocci@nokia.com> <mailto:matthew.bocci@nokia.com> > *Cc:* MBONED WG <mboned@ietf.org> > <mailto:mboned@ietf.org>; Truman Boyes > <truman@versionsix.org> <mailto:truman@versionsix.org>; > <nvo3@ietf.org> <mailto:nvo3@ietf.org> <nvo3@ietf.org> > <mailto:nvo3@ietf.org>; Williamson, Beau > <Beau.Williamson@t-mobile.com> > <mailto:Beau.Williamson@t-mobile.com>; Dino Farinacci > <farinacci@gmail.com> <mailto: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 > > > > > > >
- [MBONED] NVO3 Multicast Framework Leonard Giuliano
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Manfredi, Albert E
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Leonard Giuliano
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] NVO3 Multicast Framework Williamson, Beau
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Truman Boyes
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Dino Farinacci
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Bocci, Matthew (Nokia - GB)
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Anoop Ghanwani
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Olufemi Komolafe
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Behcet Sarikaya
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Joe Touch
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar
- Re: [MBONED] [nvo3] NVO3 Multicast Framework Linda Dunbar