Re: [nvo3] [MBONED] NVO3 Multicast Framework

[Joe Touch <[e-mail]>]

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' <[e-mail]>; Olufemi Komolafe
> <[e-mail]>; Anoop Ghanwani <[e-mail]>; Bocci,
> Matthew (Nokia - GB) <[e-mail]>
> *Cc:* MBONED WG <[e-mail]>; Truman Boyes
> <[e-mail]>; <[e-mail]> <[e-mail]>; Williamson,
> Beau <[e-mail]>; Dino Farinacci <[e-mail]>
> *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:[e-mail]]
> *Sent:* 2017年1月30日12:35
> *To:* Linda Dunbar <[e-mail]
> <mailto:[e-mail]>>; Olufemi Komolafe
> <[e-mail] <mailto:[e-mail]>>; Anoop Ghanwani
> <[e-mail] <mailto:[e-mail]>>; Bocci, Matthew
> (Nokia - GB) <[e-mail] <mailto:[e-mail]>>
> *Cc:* MBONED WG <[e-mail] <mailto:[e-mail]>>; Truman
> Boyes <[e-mail] <mailto:[e-mail]>>;
> <[e-mail] <mailto:[e-mail]>> <[e-mail]
> <mailto:[e-mail]>>; Williamson, Beau
> <[e-mail] <mailto:[e-mail]>>;
> Dino Farinacci <[e-mail] <mailto:[e-mail]>>
> *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:[e-mail]]
>     *Sent:* 2017年1月30日12:03
>     *To:* Linda Dunbar <[e-mail]>
>     <mailto:[e-mail]>; Olufemi Komolafe
>     <[e-mail]> <mailto:[e-mail]>; Anoop
>     Ghanwani <[e-mail]> <mailto:[e-mail]>;
>     Bocci, Matthew (Nokia - GB) <[e-mail]>
>     <mailto:[e-mail]>
>     *Cc:* MBONED WG <[e-mail]> <mailto:[e-mail]>; Truman
>     Boyes <[e-mail]> <mailto:[e-mail]>;
>     <[e-mail]> <mailto:[e-mail]> <[e-mail]>
>     <mailto:[e-mail]>; Williamson, Beau
>     <[e-mail]>
>     <mailto:[e-mail]>; Dino Farinacci
>     <[e-mail]> <mailto:[e-mail]>
>     *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:[e-mail]]
>         *Sent:* 2017年1月30日11:49
>         *To:* Linda Dunbar <[e-mail]>
>         <mailto:[e-mail]>; Olufemi Komolafe
>         <[e-mail]> <mailto:[e-mail]>; Anoop
>         Ghanwani <[e-mail]>
>         <mailto:[e-mail]>; Bocci, Matthew (Nokia - GB)
>         <[e-mail]> <mailto:[e-mail]>
>         *Cc:* MBONED WG <[e-mail]> <mailto:[e-mail]>;
>         Truman Boyes <[e-mail]>
>         <mailto:[e-mail]>; <[e-mail]>
>         <mailto:[e-mail]> <[e-mail]> <mailto:[e-mail]>;
>         Williamson, Beau <[e-mail]>
>         <mailto:[e-mail]>; Dino Farinacci
>         <[e-mail]> <mailto:[e-mail]>
>         *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:[e-mail]]
>             *Sent:* 2017年1月27日18:20
>             *To:* Linda Dunbar <[e-mail]>
>             <mailto:[e-mail]>; Olufemi Komolafe
>             <[e-mail]> <mailto:[e-mail]>;
>             Anoop Ghanwani <[e-mail]>
>             <mailto:[e-mail]>; Bocci, Matthew (Nokia -
>             GB) <[e-mail]> <mailto:[e-mail]>
>             *Cc:* MBONED WG <[e-mail]>
>             <mailto:[e-mail]>; Truman Boyes
>             <[e-mail]> <mailto:[e-mail]>;
>             <[e-mail]> <mailto:[e-mail]> <[e-mail]>
>             <mailto:[e-mail]>; Williamson, Beau
>             <[e-mail]>
>             <mailto:[e-mail]>; Dino Farinacci
>             <[e-mail]> <mailto:[e-mail]>
>             *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
>
>          
>
>      
>
>  
>