Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
Jari Arkko <jari.arkko@piuha.net> Sun, 11 September 2005 20:59 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEYvV-0000rI-9b; Sun, 11 Sep 2005 16:59:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EEYv7-0000oR-6W for ietf@megatron.ietf.org; Sun, 11 Sep 2005 16:59:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22135 for <ietf@ietf.org>; Sun, 11 Sep 2005 16:58:54 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEYyh-0005Te-Qb for ietf@ietf.org; Sun, 11 Sep 2005 17:03:09 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 22BA189848; Sun, 11 Sep 2005 23:58:28 +0300 (EEST)
Message-ID: <43249A80.3020303@piuha.net>
Date: Sun, 11 Sep 2005 23:58:40 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
References: <20050804050502.GB6084@sbrim-wxp01> <42F89F9F.5070008@zurich.ibm.com> <C5A01F62-A076-46C7-8C67-6568E752A1E7@nomadiclab.com> <4321D5E9.9010609@shockey.us> <151701c5b570$052a25a0$0500a8c0@china.huawei.com> <C0DE65F6343F8BD987425795@B50854F0A9192E8EC6CDA126>
In-Reply-To: <C0DE65F6343F8BD987425795@B50854F0A9192E8EC6CDA126>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> standards bloat solution: > > anyone proposing a new feature has to propose two features to be retired. > anyone proposing a new standard has to propose two standards to be > retired. This is a fun thread, but if we ever decide to get serious about complexity, we can't assume a static Internet or static environment. When you keep on increasing the number of users by orders of magnitude, increasing the types of applications, and expanding to very different types of devices, you ARE going to need more functionality. Sign of success. There's no going back to the times of telnet and ftp, even if many of us may think of those times as the good old times when life was simple... A bad sign, however, would be if we were producing all this functionality in the wrong way, making it unnecessarily complicated or limited, or if the stuff that we produced would not match what people really use in the Internet. I'm sure we can come up with examples of all of these bad signs... but its harder to determine how serious the situation is or is not. Anyway, some of the tools that we can use going forward include - Good architecture and good design. Placement of functionality in the right place. I suspect that we don't do enough work in this area. Almost all of our activities are related to specific protocol pieces, not so much on how they work together, what the whole needs to do, what etc. - Generalization of point solutions. Even major new functionality often starts out as the need of a specialized group of users. If you always do only what is needed right now and don't think ahead -- you will get bloat and an architecture that does not work well. - Processes that ensure proposals and standards that don't get widely adopted are killed in a timely manner. We can decide that proposals don't have enough support behind them. We can deprecate standards. (Note that "widely" is relative term. I don't mean that we should never answer the needs of small groups. But if a solution for X does not appear to be used even in the potential user group, that's bad.) - Allowing paths for experimentation, innovation, and market forces. E.g., some protocol proposals may be better produced in IRTF and tested & evolved, rather than being cast from day 1 as standards that affect all devices. --Jari _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- "The IETF has difficulty solving complex problems" Scott W Brim
- Re: "The IETF has difficulty solving complex prob… JFC (Jefsey) Morfin
- RE: "The IETF has difficulty solving complex prob… Hallam-Baker, Phillip
- Re: "The IETF has difficulty solving complex prob… Brian E Carpenter
- Re: "The IETF has difficulty solving complex prob… JFC (Jefsey) Morfin
- Re: "The IETF has difficulty solving complex prob… Pekka Nikander
- Re: "The IETF has difficulty solving complex prob… Richard Shockey
- Re: "The IETF has difficulty solving complex prob… Spencer Dawkins
- Re: "The IETF has difficulty solving complex prob… Richard Shockey
- Re: "The IETF has difficulty solving complex prob… Harald Tveit Alvestrand
- Re: "The IETF has difficulty solving complex prob… Jari Arkko
- Re: "The IETF has difficulty solving complex prob… Henning Schulzrinne
- Re: "The IETF has difficulty solving complex prob… Harald Tveit Alvestrand
- Re: "The IETF has difficulty solving complex prob… Masataka Ohta
- Re: "The IETF has difficulty solving complex prob… Pekka Nikander
- Re: "The IETF has difficulty solving complex prob… Iljitsch van Beijnum
- Re: "The IETF has difficulty solving complex prob… Pekka Nikander
- Re: "The IETF has difficulty solving complex prob… JFC (Jefsey) Morfin
- Re: "The IETF has difficulty solving complex prob… Pekka Nikander
- HIP new possibilities JFC (Jefsey) Morfin
- Re: "The IETF has difficulty solving complex prob… Iljitsch van Beijnum
- Re: "The IETF has difficulty solving complex prob… Pekka Nikander