RE: Cost Discussions
What's happening in 802.3af right now is the result of a number of new
people who have joined the group who missed the "cost/price" lecture. We
have found that doing things with relative costs (dimensionless numbers)
works well. For example, if Solution A has a cost of 1.0, then adding
Feature B increases the cost by 2%, or something. This worked for us.
Steven B. Carlson
Co-Chair, ESTA Control Protocols Working Group
Chair, ESTA ACN Task Group
Chair, IEEE 802.3af DTE Power via MDI Task Force
High Speed Design, Inc.
11929 NW Old Quarry Road
Portland, OR 97229
From: firstname.lastname@example.org [mailto:email@example.com]On
Behalf Of Mike Takefman
Sent: Friday, March 23, 2001 2:41 PM
To: Geoff Thompson; jcarlo
Subject: Re: Cost Discussions
I hate to sound stupid my first time out, but isn't one person's
cost the previous person's price ? So I cannot talk about optics
module costs, or ASIC costs since I purchase those components at a price.
What rule can I use as chair to determine whether people are
truely talking about the cost of something?
Geoff Thompson wrote:
> As far as I am concerned, it has been a "Chair's Guideline" ever since it
> was put up by Don Loughry in 1988. I have the original slide and have been
> using it for years when the occasion is appropriate. The only difference
> that David has transcribed the slide verbatim and posted it on our web
> I guess the problem is that even though it has been there all along no one
> else knew/remembered it.
> At 12:34 PM 3/23/01 -0600, Jim Carlo wrote:
> >Steve Carlson referred his task force to a note below. Should we make
> >Chair's guideline?
> >Jim Carlo(firstname.lastname@example.org) Cellular:1-214-693-1776 Voice&Fax:1-214-853-5274
> >TI Fellow, Networking Standards at Texas Instruments
> >Vice Chair, IEEE-SA Standards Board
> >Chair, IEEE802 LAN/MAN Standards Committee