Re: [Iasa20] IASA 2.0 outcome properties

"Livingood, Jason" <Jason_Livingood@comcast.com> Tue, 25 April 2017 00:38 UTC

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15E61270AC for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 17:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 HUxyU0J_1IT0 for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 17:38:34 -0700 (PDT)
Received: from vaadcmhout01.cable.comcast.com (vaadcmhout01.cable.comcast.com [96.114.28.75]) (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 8EB4F126B72 for <iasa20@ietf.org>; Mon, 24 Apr 2017 17:38:34 -0700 (PDT)
X-AuditID: 60721c4b-6b7ff70000008bf6-a0-58fe9a865423
Received: from VAADCEX39.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id EC.99.35830.68A9EF85; Mon, 24 Apr 2017 20:38:33 -0400 (EDT)
Received: from VAADCEX37.cable.comcast.com (147.191.103.214) by VAADCEX39.cable.comcast.com (147.191.103.216) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 24 Apr 2017 20:38:29 -0400
Received: from VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0]) by VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0%19]) with mapi id 15.00.1263.000; Mon, 24 Apr 2017 20:38:29 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Randy Bush <randy@psg.com>
CC: "iasa20@ietf.org" <iasa20@ietf.org>
Thread-Topic: [Iasa20] IASA 2.0 outcome properties
Thread-Index: AQHSuSMo5fmbLW44OEOokoUUDvVNpKHNxoIAgAd/u4A=
Date: Tue, 25 Apr 2017 00:38:29 +0000
Message-ID: <5F3378E5-D812-4966-828F-4DD0F5E9297F@cable.comcast.com>
References: <42E39015-D0B6-4464-8792-9F3A7089975F@cooperw.in> <m2r30n6dct.wl-randy@psg.com>
In-Reply-To: <m2r30n6dct.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170409
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1555A2ACC74D6C44A479DFEFFC17B861@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsWSUOxpods561+EwdZOGYsl0zcyWTxrfcnk wOSxZMlPJo+pM2czBjBFcdmkpOZklqUW6dslcGXM32tQsIOv4uTf9SwNjB18XYycHBICJhL7 X3xi72Lk4hAS2M4kcX3BHiYI5xCjxI5Ph6AyJxklPl19ywzSwiZgJnF34RUwW0RATuLiiXeM IDazgLrE7zMHwGxhAUOJJzPfsUDUGElM2n+OCcK2kni6bhPQUA4OFgFViUPTY0FMXgEXibtn wkBMIYFYiYYLoiDFnAJaErfm9YANZBQQk/h+ag0TxCJxiVtP5jNB3C8gsWTPeWYIW1Ti5eN/ rCC2qICexLUPK1kg4joSZ68/YYSwDSS2Lt0HFVeU+DXvChvIWmYBTYn1u/QhxjtIXJt9DGqV osSU7ofsIDavgKDEyZlPoFrFJQ4f2cE6gVF6FpKLZiFMmoVk0iwkk2YhmbSAkXUVo1xZYmJK cm5GfmmJgaFecmJSTqpecn5ucmJxCYjexAiK7CIZ7x2M6366H2IU4GBU4uH1nvovQog1say4 MhcYTRzMSiK8evZAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4ryOz75HCAmkJ5akZqemFqQWwWSZ ODilGhjVJswN/7LtVkVRygW113G+hsfz4iUkDfo+H573MP5zWewbvsAlU4717V7YZRPP1ZNo UhVdKZXbHstszXuldsayNxHTmdaZ8C9cEbCgJUT/7xqL3DKdzw8mqU0W2uETHdNkELBp87eU 2y7i4cGa+5bkPGb6v+yB5Y0XP9ymcee0rxJ+sNn0z24lluKMREMt5qLiRABSMIRO6AIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/-_HO5Hg0PLbanSxps0P-eDCuG64>
Subject: Re: [Iasa20] IASA 2.0 outcome properties
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 00:38:36 -0000

Randy – I think you make 2 good points below. The nomcom process is a key differentiator, and we don’t have company-designated representatives as in some other SDOs (nor voting or weighted voting by membership contribution). And the arms-length separation of financial support from the standards process is also a differentiator.

On 4/19/17, 10:07 PM, "iasa20 on behalf of Randy Bush" <iasa20-bounces@ietf.org on behalf of randy@psg.com> wrote:
> imiho, there are two major factors keeping the ietf from becoming just
    another hidebound sdo.
    
>  one is the nomcom process instead of a popularity election process.
    while not perfect (what is?), we actually have a somewhat fair method of
    selecting for merit and quality.  though, in an organization run by paid
    bureaucrats, the quality of the ostensible leadership maybe be less of
    an issue.
    
> the second is being arm's length from money, HR, ...  yes, we need to
    have oversight and authority; but the level of indirection through the
    secretariat, rfc, isoc, ... keeps us out of some very serious mud.  some
    of these, namely the relationship with the isoc, we need to manage
    better.  i think the ietf's relationships to the rfc process and the
    secretariat show that we can do this quite well; we just have to apply
    it.