Re: NomCom 2019 Call for Community Feedback

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Tue, 05 November 2019 16:35 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A359C12001A for <ietf@ietfa.amsl.com>; Tue, 5 Nov 2019 08:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=emTjAoXC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Eo7rCoi5
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 tAO0y3Ecdof7; Tue, 5 Nov 2019 08:35:16 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 912651200D8; Tue, 5 Nov 2019 08:35:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3548; q=dns/txt; s=iport; t=1572971716; x=1574181316; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=m5UpNuz6Ps4fHENNfWYEWxdIzJa5A6YWfJekzF8xuoU=; b=emTjAoXCp/AuEyd8A/FzGYlXxZ8JKTvLnC0STlrd13bn7JYHLztCtlbX uQBWmwACjF0fjB6I8RPf0IkeFFTeKncNmwe83TRT764YU8Wgx19HfEkl/ uJ0qnHnaFDgBVIZPTanIiquuUGEeieA5p1ABSeVorOJm2DhFPz7cY8I7x 8=;
IronPort-PHdr: =?us-ascii?q?9a23=3Al9IV0BTqfFXiUQ8LQeSwVe5X+Npsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BdCQCFo8Fd/5NdJa1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgX6BS1AFgUQgBAsqhCmDRgOKe4I5JYlWjiiBQoEQA1QJAQEBDAE?= =?us-ascii?q?BLQIBAYRAAheDdyQ4EwIDCwEBBAEBAQIBBQRthTcMhVEBAQEBAgESCwYRDAE?= =?us-ascii?q?BKQ4BDwIBCBgCAiYCAgIfERUQAgQOBRQLA4MAgkcDDiABpg0CgTiIYHWBMoJ?= =?us-ascii?q?+AQEFgkmCNw0LghcJgQ4ojBMYgUA/gREnDBOBTn4+ghuBdwESAR8Xgnkygiy?= =?us-ascii?q?QAJ05QQqCJJErhBEbmWmZA48cAgQCBAUCDgEBBYFpImdxcBVlAYJBUBEUgwa?= =?us-ascii?q?Dc4pTdIEoji2CMAEB?=
X-IronPort-AV: E=Sophos;i="5.68,271,1569283200"; d="scan'208";a="645966144"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Nov 2019 16:35:15 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id xA5GZF1o011367 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 5 Nov 2019 16:35:15 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 5 Nov 2019 10:35:15 -0600
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 5 Nov 2019 11:35:13 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 5 Nov 2019 10:35:13 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HDpn8qfvykYck8FqnY+P6P/hawQmng2pjl8FJW/Vgw8QHb5LWdX6rTUOZhTUl75PAT4n9z9M+PTxwNi/4SleDn7DHUerXP+3ztgvpYDf6NrRZVpX3AMntw3E8UFkak2bB9EZJ8I/TNyKn2E7JoRj9l2SEpYelyzRXhwi+hhIWj7dhj+uJ7WdBYD+Qm5YIp/kLCss8DLq/CWtM6CXqdBocefqXQ/qkiMWsSEoFIUXnkQZJqCzpr4E2dg/Lpd4wcUr3LX6NYWTDqCoSEkFk92oA0BsIO2AXxzUr85qDJdHIiAKxXthfCzno5Jnm4XhS+PAH0xUHZrTvabKS7QhY+WNVg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m5UpNuz6Ps4fHENNfWYEWxdIzJa5A6YWfJekzF8xuoU=; b=NKWlNmMCvjqfs+2dSLn/Gg5rqhKS+Prg0bjJ00xUBjxSRbBItedDbeJwrH+pPzC4bNUavYt0ACic/fc+KsNeukEO3nDkV5UaeL528Y2WSubRsgw/ze3OGH1oawXxrciG83AZb7ETbp+Og+l3h+XTgTvKl5WFPesF14scDlnLGFy5Iw8GLmPKnTz74j71WxRdb5N2Fbg8+bJND+9V4xxr21+95ug+17PknXA0Qg3EGpJR0WfyNu5f+UwaXtuhMGDVBlVGkBRpn7m/5LmPvESDJ3B+SamnCtnL1WZbqZxgjS0EHda2cb0pVT4Vp1qBf/aM3ngds3zdOrQSMP6jMX1DdQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m5UpNuz6Ps4fHENNfWYEWxdIzJa5A6YWfJekzF8xuoU=; b=Eo7rCoi50e0KT79gvBNW+lUutmNtodxagBqDEW9m9zmP14Eswbu1wsNIRMBZYKXMmXN4t+5s/VGfEefLKQFkK0wwI+eT21PuvZ5L+Dacatg1jX58IhzO85oLi1DfzwoPT+i0N+HgNQycH2FogEBItVbQzo/zMl9c7fjOpP4ugGc=
Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1770.namprd11.prod.outlook.com (10.175.88.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.20; Tue, 5 Nov 2019 16:35:12 +0000
Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39%7]) with mapi id 15.20.2408.024; Tue, 5 Nov 2019 16:35:12 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: IETF <ietf@ietf.org>
CC: "nomcom-chair-2019@ietf.org" <nomcom-chair-2019@ietf.org>
Subject: Re: NomCom 2019 Call for Community Feedback
Thread-Topic: NomCom 2019 Call for Community Feedback
Thread-Index: AQHVkllsQsmyoBEM6EmqzoxICvl3V6d6vluAgABDYACAAAVVgIAAZu0AgAAAwQCAAU6ZAIAAHLWA
Date: Tue, 5 Nov 2019 16:35:12 +0000
Message-ID: <0AADFBC3-74E1-4994-A89F-5CEC608E3254@cisco.com>
References: <157279399807.13506.13363770981495597049.idtracker@ietfa.amsl.com> <0EF64763-BA25-468A-B387-91445A61D318@gmail.com> <CAJU8_nUovmFmgNiYx0ez_1f+GPdU9xGViDYWfowEEomrn0pyDw@mail.gmail.com> <alpine.LRH.2.21.1911040841160.27600@bofh.nohats.ca> <CE06CC6D-E37F-4C90-B782-D14B1D715D4B@cable.comcast.com> <38E47448-63B4-4A5D-8A9D-3AB890EBDDDD@akamai.com> <730534A0-2ADC-46B8-BB40-9EEDFCE08910@gmail.com>
In-Reply-To: <730534A0-2ADC-46B8-BB40-9EEDFCE08910@gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c0:1007::34c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4b246c32-b288-4fe9-2285-08d7620e2132
x-ms-traffictypediagnostic: DM5PR11MB1770:
x-microsoft-antispam-prvs: <DM5PR11MB177094939449CF651F941B42A97E0@DM5PR11MB1770.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(39860400002)(366004)(396003)(136003)(199004)(189003)(469094003)(53484002)(129404003)(86362001)(33656002)(2906002)(316002)(53546011)(8936002)(66574012)(486006)(476003)(71200400001)(71190400001)(6512007)(76176011)(6506007)(186003)(6486002)(36756003)(14454004)(25786009)(5660300002)(305945005)(6116002)(46003)(229853002)(14444005)(256004)(7736002)(58126008)(66476007)(4326008)(66556008)(76116006)(64756008)(66946007)(450100002)(6436002)(6916009)(66446008)(11346002)(91956017)(99286004)(446003)(81156014)(81166006)(6246003)(2616005)(102836004)(8676002)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1770; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Bg4UCuM7p8STROT+9cTPdMYZjV6/h8jkseu6iKzOFQtHw2Z67jTKiD6q2RMBTJbNO+uOBEYqdHSkNe1oo41LgMJUf4FN7H8HMYWlRjXWVU2fg1VRgIG8Y76u8BAz68eGh6yyPNAju9PRHx6puLhDIYEhdO4TNK6wALQoaKyjbsKbFhA3kiWUg1HFPcDDWbW9EC9BOxepqxUpRy+LfCf8anxaafWXM6P2awQFrmENahn3pdXRJIF4YOkSNY2utHARscvbQQgJDHTNVQZthfMKULM5AOAVB7vcuDQlsqHW49j+B8KQUDSepqpRIZNr0mjkd9uzjs2gFa6IjM1YvWYIO8jl65Qxb/oLuBELlstmPv+NRDFtBYPwUW7H911v1rTdkHIxqrFMS39X0expzdJQ6G0lfI4p4GuIg/RJttWsqRd+51DF7LotOBUB9uR5onCvr+nbqAC/XYuEeHbWo4T9qw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <876E1B6414C0A74EACC9CBB87805D1FE@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4b246c32-b288-4fe9-2285-08d7620e2132
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 16:35:12.1522 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: GXA+tjS//+FT/+weRUzikiUZSbklDftwGN2fU6ejDDRtVL7RPhrjxq+vsPJhY1dUF0T7eUhVaUwH1wvVMFE/gw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1770
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i_aKDrk0FV3WrHh7JuypsDU80HU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 16:35:18 -0000

As a "junior" IESG member, I have been reading this open thread with great interest.

Replying to Bob's email because he nailed a lot of valid points:

1) AD are 'responsible' so they do need to check the intensive work of WG, shepherd, IETF last call and directorate
2) sometimes the directorate reviews come too late for the IESG ballot for approval
3) and the IESG review is an interesting step because it is a common decision by different ADs with different background and expertise (BTW, do not consider the IESG as monolithic => we tend to politely and respectfully disagree among ourselves but we always manage to come to a position)
4) the review is of course deeper when it is the WG where you are the responsible AD __, for others I look of the overall readability, some process oriented things (such as RFC 8174), conflicts with other drafts/WG/areas, and issues related to my area (internet)
5) indeed, the expertise coverage of an AD should aim for breadth and not for depth for the reviews (in addition to the
6) reviews are probably 50% of our time
7) several AD (including myself) are not English-speaking natives, how would we dare to have editorial comments ;-) but I am improving my English by reading those comments :-)

And as Kathleen wrote, while this requires a lot of time and energy, the reward is excellent: you learn a LOT and most of the time this is really interesting :-) 

Hope this helps

-éric	


On 05/11/2019, 16:53, "ietf on behalf of Bob Hinden" <ietf-bounces@ietf.org on behalf of bob.hinden@gmail.com> wrote:

    Rich,
    
    > On Nov 4, 2019, at 11:54 AM, Salz, Rich <rsalz@akamai.com> wrote:
    > 
    > I wonder what people think would break if we moved to 5 AD's per area, and they could divide the WG's and IESG concalls amongst themselves?
    > 
    
    Why stop there, how about one AD per working group?
    
    I hope this helps makes it clear that more authority should go to the w.g. chairs, adding more AD won’t scale.   The NomCom needs to be selecting people who are not the best technical experts in an area, but who know enough to make sure that adequate review has been done in the working groups, verify directorate reviews, and that last call comments have been addressed.   They don’t need to do detailed technical reviews themselves.   They especially don’t need to do editorial reviews.
    
    This might also allow the ADs to spend more time on working group charters to insure that the working group has the appropriate scope.
    
    Bob