> -----Original Message----- > From: Jan Zorz @ go6.si [mailto:[email protected]] > Sent: Monday, April 09, 2012 6:37 PM > To: Liubing (Leo) > Cc: Sheng Jiang; [email protected] > Subject: Re: [Softwires] Path to move forward with 4rdŠ 4rd-U as transparent > as MAP-E > > On 4/9/12 11:37 AM, Liubing (Leo) wrote: > >>> On 4/9/12 8:17 AM, Sheng Jiang wrote: > > ... > >> Operators have their own brains. They may listen to vendors, but > >> they do think by themselves and make decisions by themselves. > >> Vendors would implement whatever the operators order. > > ... > > > > +1 I believe most of the time operators understand their own networks > > much better than other engineers. Operators come to IETF with some > > requirements, if there're multiple solutions offered, finally they > > should make the choice by themselves. > > > > "rough consensus and running code" maybe is not sufficient for > > operators to have a decision of long-term deployment model, > > especially the "consensus" seems not so strong so far. > > This probably means the vendors fight for customers, each deploying > different not compatible solutions and CPE vendors will have to deploy > all of them in order to be able to sell to different operators. > > Vendors did it in the past and it looks like we did not learn.
[Bing] If operators' networks have different requirements, I guess we'll have to implement different CPEs. I think the networks' requirements should be the higher priority. I'm not a CPE expert, but as I learned, customized CPE is normal in current networks, is it a big problem? > I understand that VendorX would like to lock his customers to his > solution, but that's a trap. A walled garden. I buy solutionX from > VendorX and can't change it in the future, because my CPE base is locked > to solutionX. > [Bing] That's true, but it's not the situation of what we are discussing. In fact, if we hurry to make a choice right now, it is just like to be locked in one solution. We should open the choices to the operators, let them decide. > Can we please do it properly this time? > > Cheers, Jan > _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
