I don't see the point you are trying to make here.
If we need some expertise and don't feel we have it in the ietf we go find
someone who does. We have the ability to tap into any of the top universities
economics departments and this stuff is surely understood somewhere in the
fortune 500 companies here.
We are in the business of communication, of collaboration. If we can't do
either shame on us.
What is worse, to think we are expert economists or that because we are not
economists the whole field must be irrelevant? I don't think we need to go too
deep here, just thinking in terms of deployment as the challenge is a start.
As for defining marketting as bending of facts. There are two processes that
can be thought of as marketting. Shifting product is really a form of sales. I
am talking about the processes you go through to determine whether your product
meets a genuine market need. Fudging such a study is self deception and only
leads to tears.
I always thought that the point of engineering was that you define yourself by
the ends you are seeking to achieve, not a particular skill set. If you need a
skill you seek to acquire it.
Sent from my GoodLink Wireless Handheld (www.good.com)
From: Brian E Carpenter
Sent: Wednesday, December 26, 2007 12:32 PM Pacific Standard Time
To: Hallam-Baker, Phillip
Subject: Re: Deployment Cases
On 2007-12-24 07:32, Hallam-Baker, Phillip wrote:
Problem: We have a lot of specifications that work fine, but have not seen
Examples: Most security specifications, IPv6, etc. etc.
Cause: The economic case for deployment is not made. This is a particular
concern when the protocol deplends on the network effect. Until the network
is established the protocol has minimal value.
Proposed Solution: Deployment Cases
As engineers we are now used to considering use cases, that is representative
use scenarios that illustrate particular intendeded uses. The output of use
cases are requirements.
Deployment cases are similar except that we consider the economic incentives
IMHO, whenever the IETF has tried to do anything like this, we've
failed. A good (er, bad) example was draft-ietf-iab-case-for-ipv6,
which had so many issues that it was allowed to curl up and die.
Basically, we aren't business-oriented people or economists,
and we don't tolerate marketing-style bending of the facts.
I'm pessimistic about trying this in the IETF, even for
technologies that are aimed at the greater good, where the
economic arguments are not about short term returns for
Ietf mailing list