Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

JFC Morfin <jefsey@jefsey.com> Wed, 05 November 2014 19:06 UTC

Return-Path: <jefsey@jefsey.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D950E1A1B5C; Wed, 5 Nov 2014 11:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.631
X-Spam-Level: *
X-Spam-Status: No, score=1.631 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id le9IBjVIXtMi; Wed, 5 Nov 2014 11:06:56 -0800 (PST)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64771A1A30; Wed, 5 Nov 2014 11:06:56 -0800 (PST)
Received: from 183.213.130.77.rev.sfr.net ([77.130.213.183]:43898 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.82) (envelope-from <jefsey@jefsey.com>) id 1Xm5ux-0004r7-9a; Wed, 05 Nov 2014 11:06:55 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 05 Nov 2014 20:06:47 +0100
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ianaplan@ietf.org
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <20141105180238.GX30379@mx1.yitter.info>
References: <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <9FDE1247-717D-487F-BC0E-E30FEA33536F@gmail.com> <545A5859.1060505@meetinghouse.net> <D07F9A64.1367AE%jon.peterson@neustar.biz> <545A6358.1000304@meetinghouse.net> <20141105180238.GX30379@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: jefsey+jefsey.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/EerDUvUc5QRCImpTSABCa3qcj20
Cc: gene@iuwg.net, "iucg@ietf.org" <iucg@ietf.org>
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 19:06:58 -0000
X-Message-ID:
Message-ID: <20141105190706.13773.32597.ARCHIVE@ietfa.amsl.com>

At 19:02 05/11/2014, Andrew Sullivan wrote:
>I'm sorry, but for the purposes of stating what "the IETF wants", the
>IETF is not more than the consensus-calling process that we use for
>everything else.  There is exactly one way for the IETF to say what
>"it" wants, and that is to do a consensus call.

Dear Andrew,

I have no problem with you not understanding what your different
colleagues may say, and in expessing your our thinking as a reference
other may oppose, etc. This is a philosophical form of more emotive
debate (beliefs vs beliefs). I must confess I prefer a scientific form
of debate, where critics are meant to add to a common progress.
However, both approaches are blocked when the accepted consensus is
opposed like you do here.

I think it is worth to underline it when it clearly occurs such in
your position above, when compared with the RFC 3935 (IETF mission
statement) section 3 which is the base of most's reasoning in terms of
decision preparation by this WG

"3.  The Need for a Mission Statement

    The IETF has to make decisions.  And in some cases, people acting on
    behalf of the IETF have to make decisions without consulting the
    entire IETF first.

    There are many reasons for this, including the near-impossibility of
    getting an informed consensus opinion on a complex subject out of a
    community of several thousand people in a short time.

    Having a defined mission is one of the steps we can take in order to
    evaluate alternatives: Does this help or hinder the mission, or is it
    orthogonal to it? If there are limited resources, are there things
    that they could be invested in that help the mission better?

    (Another step is to choose leaders that we trust to exercise their
    good judgement and do the right thing.  But we're already trying to
    do that.)"

Which position should we accept as accept as a reference for this WG's work?
jfc