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:[email protected]] > *Sent:* 2017年1月30日11:49 > *To:* Linda Dunbar <[email protected]>; Olufemi Komolafe > <[email protected]>; Anoop Ghanwani <[email protected]>; Bocci, > Matthew (Nokia - GB) <[email protected]> > *Cc:* MBONED WG <[email protected]>; Truman Boyes > <[email protected]>; <[email protected]> <[email protected]>; Williamson, > Beau <[email protected]>; Dino Farinacci <[email protected]> > *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:[email protected]] > *Sent:* 2017年1月27日18:20 > *To:* Linda Dunbar <[email protected]> > <mailto:[email protected]>; Olufemi Komolafe > <[email protected]> <mailto:[email protected]>; Anoop > Ghanwani <[email protected]> <mailto:[email protected]>; > Bocci, Matthew (Nokia - GB) <[email protected]> > <mailto:[email protected]> > *Cc:* MBONED WG <[email protected]> <mailto:[email protected]>; Truman > Boyes <[email protected]> <mailto:[email protected]>; > <[email protected]> <mailto:[email protected]> <[email protected]> > <mailto:[email protected]>; Williamson, Beau > <[email protected]> > <mailto:[email protected]>; Dino Farinacci > <[email protected]> <mailto:[email protected]> > *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 [email protected] https://www.ietf.org/mailman/listinfo/nvo3
