> > As has been pointed out a number of times, pure data plane learning > leads > > to a lot of BUM traffic flooding, so a combination of data plane and > control > > plane can work better with existing systems and improve scalability. > > Data plane learning, l2 header transparency, bridging interoperability > are all very reasonable requirements for one type of data-centers. But > also an unacceptable burden for a different class of DC designs. In my > view you and Maria are just looking at different types of DC designs. > They are different problems.
Precisely. And my comment was that the sentence in draft: "Often a combination of data plane and control based learning is necessary" seems to be assuming that pretty much all data centers must use (some) data plane learning. I have suggested to clarify it. Maria > Pedro. > > > > > Thanks, > > --David > > > > > >> -----Original Message----- > >> From: [email protected] [mailto:[email protected]] On Behalf > Of > >> NAPIERALA, MARIA H > >> Sent: Friday, June 29, 2012 2:14 PM > >> To: [email protected] > >> Subject: Re: [nvo3] call for adoption: draft-lasserre-nvo3- > framework-02 > >> > >> A comment on section 4.2.2 "Coordination between data plane and > control plane" > >> > >> "Often a combination of data plane and control based learning is > >> necessary." > >> > >> I think this statement is too strong since in a solution proposed in > draft- > >> marques-l3vpn-end-system, for example, there is no data plane > learning in a > >> virtual network. Maybe it should be explain when such combination is > >> necessary. > >> > >> Maria > >> > >> > >>> On 6/18/2012 11:51 PM, Benson Schliesser wrote: > >>> Dear NVO3 Participants - > >>> > >>> This message begins a two week Call for Adoption of > >>> http://tools.ietf.org/html/draft-lasserre-nvo3-framework-02 > >>> by the NVO3 working group, ending on 02-July-2012. > >>> > >>> Please respond to the NVO3 mailing list with any statements > >>> of approval or disapproval, along with any additional > >>> comments that > >>> might explain your position. Also, if any NVO3 participant > >>> is aware > >>> of IPR associated with this draft, please inform the mailing list > >>> and/or the NVO3 chairs. > >>> > >>> Thanks, > >>> -Benson& Matthew > >>> > >>> > >> > >> _______________________________________________ > >> nvo3 mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/nvo3 > > > > _______________________________________________ > > nvo3 mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/nvo3 > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
