RE: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
"Hallam-Baker, Phillip" <pbaker@verisign.com> Mon, 12 September 2005 17:14 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EErsi-0000hT-MU; Mon, 12 Sep 2005 13:14:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EErsf-0000gX-Fy for ietf@megatron.ietf.org; Mon, 12 Sep 2005 13:14:09 -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 NAA02792 for <ietf@ietf.org>; Mon, 12 Sep 2005 13:14:06 -0400 (EDT)
Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EErwt-0002I4-Vf for ietf@ietf.org; Mon, 12 Sep 2005 13:18:32 -0400
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by colibri.verisign.com (8.13.1/8.13.1) with ESMTP id j8CHDrGm007871; Mon, 12 Sep 2005 10:13:53 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 12 Sep 2005 10:13:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Sep 2005 10:13:52 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD375A2B1B@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Thread-Topic: "The IETF has difficulty solving complex problems" or alternatively Why IMS is a big fat ugly incomprehensiable protocol
Thread-Index: AcW3tuQIiAEsUVyCRA6uYhfXXjrvuQABdBPQ
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, Henning Schulzrinne <hgs@cs.columbia.edu>
X-OriginalArrivalTime: 12 Sep 2005 17:13:53.0285 (UTC) FILETIME=[59C71B50:01C5B7BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
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
> Behalf Of Masataka Ohta > 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. The world is complex, sometimes solutions must also be complex. In those cases the design choice is where you put the complexity. I have seen plenty of systems that have become complex and baroque because the design was too simple. SMTP is a prime example, the complexity of the modern email system is the direct result of failing to acknowledge and make provision for important use cases such as mailing lists and forwarders. _______________________________________________ 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