Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol

Iljitsch van Beijnum <iljitsch@muada.com> Wed, 14 September 2005 21:12 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFeYH-0003Oj-Gq; Wed, 14 Sep 2005 17:12:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFeYC-0003O8-0U for ietf@megatron.ietf.org; Wed, 14 Sep 2005 17:12:16 -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 RAA11998 for <ietf@ietf.org>; Wed, 14 Sep 2005 17:12:13 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFecr-000054-HZ for ietf@ietf.org; Wed, 14 Sep 2005 17:17:06 -0400
Received: from [82.192.90.27] (alumange.muada.com [82.192.90.27]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id j8ELBdvZ023879 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 14 Sep 2005 23:11:39 +0200 (CEST) (envelope-from iljitsch@muada.com)
In-Reply-To: <BB8C050D-B298-4A8A-9325-45B149FC04AD@nomadiclab.com>
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> <43249A80.3020303@piuha.net> <4324A849.4060509@cs.columbia.edu> <BB8C050D-B298-4A8A-9325-45B149FC04AD@nomadiclab.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <4A763861-D4E9-44DD-A193-8E73EC4E03A7@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 14 Sep 2005 23:11:50 +0200
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
X-Mailer: Apple Mail (2.734)
X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, ILJQX_SUBJ_QUOTE autolearn=no version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <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

On 13-sep-2005, at 14:32, Pekka Nikander wrote:

> So, as I state in my little web page, I think we really should work  
> hard to create a new waist for the architecture.   I, of course,  
> have my own theory where the new waist should be and how it should  
> be implemented,

Well, don't be shy: where can we absorb these insights?

(As far as I can tell the "architecture" that so many IETFers ignore  
is "anything that doesn't cause too much visible breakage goes",  
against which resistance is exactly the right response.)

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf