Re: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 13 September 2005 16:19 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFDVc-0008R9-43; Tue, 13 Sep 2005 12:19:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EF0dF-00009k-N3 for ietf@megatron.ietf.org; Mon, 12 Sep 2005 22:34:50 -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 WAA15409 for <ietf@ietf.org>; Mon, 12 Sep 2005 22:34:47 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EF0hW-00054f-Gg for ietf@ietf.org; Mon, 12 Sep 2005 22:39:17 -0400
Received: (qmail 82286 invoked from network); 13 Sep 2005 02:43:15 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134) by necom830.hpcl.titech.ac.jp with SMTP; 13 Sep 2005 02:43:15 -0000
Message-ID: <43263AA1.8080204@necom830.hpcl.titech.ac.jp>
Date: Tue, 13 Sep 2005 11:34:09 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
References: <198A730C2044DE4A96749D13E167AD375A2B1B@MOU1WNEXMB04.vcorp.ad.vr sn.com> <B8B239621892F4B6884B3BE0@bistromath.pc.cs.cmu.edu>
In-Reply-To: <B8B239621892F4B6884B3BE0@bistromath.pc.cs.cmu.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, Jari Arkko <jari.arkko@piuha.net>, 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
Jeffrey Hutzelman wrote: >>> If you have complicated requirements, you are wrong. >> >> >> You are only ever wrong if you do not listen to your customers and as a >> result fail to provide them with what they want. > > > This is a vast oversimplification. Even if you give your customers what > they want, you can still be wrong if your solution fails to behave > properly in relation to the rest of the world (stealing resources, > violating other people's rights, etc). Once upon a time, telephone industry listened to its customers (telephone companies) and provided them with what ehy want. As a result, telephone equipments becaome more and more complicated with more and more complicated specifications. Most of them are overtook by simpler equipments using IP. >> The world is complex, sometimes solutions must also be complex. In those >> cases the design choice is where you put the complexity. > This, however, is right on target. In theory, maybe. However, I have never seen such a design choice necessary for network protocols. We don't need 3GPP for the mobile internetworking. Masataka Ohta _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: "The IETF has difficulty solving complex prob… Hallam-Baker, Phillip
- RE: "The IETF has difficulty solving complex prob… Jeffrey Hutzelman
- Re: "The IETF has difficulty solving complex prob… Masataka Ohta
- Re: "The IETF has difficulty solving complex prob… JFC (Jefsey) Morfin