Re: Comments on draft-carpenter-newtrk-questions-00.txt

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Thu, 13 July 2006 23:16 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1AQS-0006Yi-4L; Thu, 13 Jul 2006 19:16:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1AQP-0006Ya-Ni for ietf@ietf.org; Thu, 13 Jul 2006 19:16:53 -0400
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1AQO-0004sY-G4 for ietf@ietf.org; Thu, 13 Jul 2006 19:16:53 -0400
Received: from i03m-212-195-38-17.d4.club-internet.fr ([212.195.38.17] helo=asus.jefsey.com) by montage.altserver.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.52) id 1G1AQL-0007N3-Uv; Thu, 13 Jul 2006 16:16:50 -0700
Message-Id: <7.0.1.0.2.20060713234434.039363c8@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Fri, 14 Jul 2006 00:07:21 +0200
To: Eliot Lear <lear@cisco.com>, Tony Hansen <tony@att.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <44B69E1B.5050309@cisco.com>
References: <p06300025c0db326985f9@[142.131.134.210]> <2278C088-133C-4353-9CF1-AC47899ED409@cisco.com> <44B5EC23.6090303@cisco.com> <44B69AFF.3020504@att.com> <44B69E1B.5050309@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; x-avg-checked="avg-ok-E9C2197"
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-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ietf@ietf.org
Subject: Re: Comments on draft-carpenter-newtrk-questions-00.txt
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>
Errors-To: ietf-bounces@ietf.org

At 21:25 13/07/2006, Eliot Lear wrote:
>And I think we're at the point where I'm violating my own rule.  There
>is no concrete proposal here that I can argue in favor of or oppose, so
>I think I'd better shut up and wait for one.

Dear Eliot,
IMHO the ambiguity is in the IETF mission. This is why I oppose RFC 
3935 and the sentences I recently quoted about "influence" and a 
technology not being neutral to IETF values. The IETF should publish 
recipes. Not to want to provide guidance. Guidance should belong to 
groups committing to deliver comprehensive, consistant, and 
maintained network systems, with source code, updates, docs, faqs, 
support, etc. They should be the IETF deliverable users. Legitimately 
looking for user QA, and their needs to be considered.

Idealy Internet users should be provided every month a CD with the 
current release of their favorite netix brand. Like Red Hat, Debbian, 
etc. Let imagine the Linux situation if no distribution existed. The 
IETF is NOT "to influence people in the way they design, use and 
manage the Internet for it to work better" (cf. RFC 3935). It is to 
help development teams to better design solutions addressing the end 
users needs.

The only way to see an Internet architectural evolution is in having 
user internetwork operating systems, using the different IETF, IEEE, 
MPEG, ITU, ETSI, etc. propositions and the common bandwidth 
convergence in an innovative way. The danger in not preparing, 
supporting, and even opposing (as for the Multilingual Internet) such 
a necessary/observed evolution, is that these systems will cicumvent 
the IETF and will not benefit from its community/experience, and 
worse, to delay them.

jfc






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