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

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Wed, 14 September 2005 16:26 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFa5F-0005BB-6a; Wed, 14 Sep 2005 12:26:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFa5D-0005B2-6x for ietf@megatron.ietf.org; Wed, 14 Sep 2005 12:26:03 -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 MAA19861 for <ietf@ietf.org>; Wed, 14 Sep 2005 12:26:00 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFa9n-0006Vm-IA for ietf@ietf.org; Wed, 14 Sep 2005 12:30:50 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1EFa50-00047E-CE for ietf@ietf.org; Wed, 14 Sep 2005 09:25:50 -0700
Message-Id: <6.2.3.4.2.20050914173454.0540b440@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 14 Sep 2005 17:44:14 +0200
To: ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA19861
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 14:32 13/09/2005, Pekka Nikander said:
>OTOH, maybe I am just a  dreamer and totally off the ground here?

No, you are not!

However the problem with a "vision" is to know where the boarder is 
between dreams and real future. This is why I prefer a more prosaïc 
"model" which gives a simple image everyone can easily understand in 
the same way.

For example, everyone - knowing the e2e principles can escalate it to 
a b2b concept of brain to brain interintelligibility when it comes to 
human languages (inter-brains protocols). And understand very simply 
why internationalisation is e2e and multilingualisation is b2b. Two 
different layers.

For example, everyone - knowing the e2e principles car enlarge their 
"mono" vision to a 'n.(e2e)' "multi" vision:
- where e2e principles are respected in multilple parallel [split, 
into simpler - as per RFC 1958] relations,
- where link ends are welded together and the edges (OPES) to provide 
real final "added" value:  not on the wire [as an impossible "e2e 
added value" ] but as an "added e2e's value".
And understand that an OPESed SMTP does not need to read an e2e mail 
when a parallel e2e link told it the mail did not originate from the 
other end it claims.

Another way to be sure you are not a dreamer is to look if your idea 
worked in the preceding public international network deployments 
(Tymnet, OSI). Obviously you have to translate it in/from IETF words 
... and be opposed many "this is not an Internet way" ....

Another way to discriminate between dreams and reality: if you are 
really alone of your opinion, you are right. Because it is not 
possible the words counts so many wise people. This is the 80/20 
rule. As long as the true majority is less than 80 the situation is 
stable. Over that the minority is probably the coming revolution. 
This is the difficulty in reaching a consensus. If 100% more or less 
the noise(rough consensus): we all agree, right or wrong. A 5 to 20% 
opposition is probably right. The big difficulty is to discriminate 
between noise and less than 5%. We are back to your question....

jfc


PS. Here is a quote of a mail to a WG-Chair who prefers to stick to 
his charter and see his WG die, instead of working on its revamp 
based on the WG's acquired expeirence. Conflict between requested 
engineering and lack of IAB exciting architectural proposition.

"This is why I have decided to proceed in parallel, using IETF Drafts 
so information will continue to flow. May be will this increase the 
ad-hominems as the economics will also increase. But at least we will 
go ahead. The architectural error is democracy. I never asked my 
phone or my computer to be democratic: I ask them to work.

Reseach is not democractic. The error is the IETF "consensus": the 
consensus was OK in the early days when everyone was standardiser, 
experimenter and user. Now when seven employees of the members of a 
commercial consortium represent a "consensus" for a "BCP" against 
(RFC 3863 included) the users, the only solution for the users is to 
renew with the old system and to specify, test and use by themselves. 
The problem is that users are disorganised, so they will develop in 
parallel, and we will have balkanisation. Too bad."









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