Concerning the 'SHOULD' for (*,G) in the underlay: What percentage of traffic in a DC (cloud or enterprise etc.) is actually non BUM/ARP multicast between VMs? Who has actual data that does not include BUM/ARP (which has to be solved with distributed control for these scales)?
We heard from some big DC/Cloud folks that they explicitly disable multicast by applications ... so clearly for them its 0. If it is in general a very very low percentage, then should we not drop (*,G) as a requirement of the underlay? This work could set the tone for DC/Cloud based applications for years to come and perhaps the applications would be better served by a reliable distributed control mechanism. Peter P.S. As a networking person I love the challenges of (*,G) (S,G) trees so I'm biased but objectively I'd like to understand exactly where the requirement is coming from to see if it is not better addressed by distributed control. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of LASSERRE, MARC (MARC) Sent: Thursday, May 17, 2012 4:32 AM To: [email protected] Subject: [nvo3] New dataplane requirements draft We have just posted a new draft on nvo3 data plane requirements: http://www.ietf.org/id/draft-bitar-lasserre-nvo3-dp-reqs-00.txt We welcome your feedback. Our intent is to submit a revised version by Vancouver addressing your comments and/or suggestions. Thanks, Marc
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
