[e2e] Are we doing sliding window in the Internet?

[Lynne Jolitz]

Yes, Greg. You're right. Buy-in is difficult to achieve and maintain, especially in open source. As I also went on to say in that same email you quote:
"But if it's not worth the time and effort for the academic side to take on this charge, the marketplace will have to serve instead."

People are very good at finding reasons to justify inaction on their part, and it is frustrating to even try for something better. That takes vision and risk.

If one were to set up such an arrangement with any eye towards the long-term, wouldn't it be wise to find an approach that would bring in parties and allow them to all benefit from an accord? Isn't it in the best interests of OS and networking developers, academics, and scientists to make sure things work well?

But that would require people to reach out to others, put skin in the game, and take a risk. It requires trust and mutual respect. It's much easier to complain and expect someone else to do the work. And it's much easier to ignore complaints because there is too much work to do already.

And that's why the marketplace is the default. It's not the best solution, but it is a solution.

Lynne Jolitz.

----
We use SpamQuiz.
If your ISP didn't make the grade try http://lynne.telemuse.net


> -----Original Message-----
> From: end2end-interest-bounces at postel.org
> [mailto:end2end-interest-bounces at postel.org]On Behalf Of Greg Skinner
> Sent: Saturday, January 06, 2007 1:38 PM
> To: Lynne Jolitz
> Cc: end2end-interest at postel.org
> Subject: Re: [e2e] Are we doing sliding window in the Internet?
> 
> 
> On Fri, Jan 05, 2007 at 02:19:20PM -0800, Lynne Jolitz wrote:
> > The days where IETF RFCs and tested releases were done by many of
> > the same people are long gone. If it's important enough, perhaps it's
> > time to take on the responsibility for correctness of operating
> > systems and networking implementations within an accredited
> > organization and certify such.   
> 
> Doesn't this just push the problem onto the accredited organization?
> What would make the Linux communities more likely to interact with it?
> Either they have their own accreditation/certification, or it's not an
> issue WRT development/deployment.
> 
> --gregbo
>