Re: NomCom 2019 Call for Community Feedback

Yoav Nir <> Mon, 04 November 2019 21:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 44ACD12007C for <>; Mon, 4 Nov 2019 13:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zcXTuozKBxEy; Mon, 4 Nov 2019 13:08:52 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1D4D9120052; Mon, 4 Nov 2019 13:08:52 -0800 (PST)
Received: by with SMTP id f2so9852999wrs.11; Mon, 04 Nov 2019 13:08:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IDsfQ+aYCYOX2yBunuvzHcxtkZvSDKqhqsyKTRXhBxE=; b=GcNabY6QtxiMCGNqYSPDXEAYfP2KcNxZlVqhkQNA7yZUNjBQt6edRXDTll9fHA6A8D gxcVZarQtIXGNLLuEFhn+P/609JwDhn4syhpu5Jn/Gi64QBdvtG7tXUbw+BxaRiO4VHB VuGIcWO7hIzZp/VKp6Hd2mOethLqS/83NSjw3kvoaGyfnKVm+JPn/Q3S6vMqfmlf89jJ n2Yi3IClRg2azWyfzUpVhE5F1nd5qOxZMULBC7bXN8iWtUJ85JspZNoEMn6bZ1EvZ82t nkCjXcrfhD2Zf9cq9Flm5gur1KeGNd3CfZ1EGlGc8WvI5VAb3ebFTgxzY+qtikvM3GrL Bddw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IDsfQ+aYCYOX2yBunuvzHcxtkZvSDKqhqsyKTRXhBxE=; b=PAaRxtqLNfcWYZJL6ViUdsdIUYTU3IrAKK1Z14nGNXkPSwIuCMS0CRoMQjPnT2tn5J aNOyYdWfnnTKLIUbC8Iks2ptpN1JesMLZ+T4Fdlljy5VrzJ76kAJy9WeyMbxASEvnTEt CdAY0hv4V/aFq2Y8Q5B0Hnxb0SQpywHEzuYC/sKkGtsSxswQlmnARBROhRBoI+G5saMZ NcPVqT+f8dLBLHjlOCMWG5+0flHyR+ycpgvLae5cC5pyqXnMU+Rxt1TURi8uVvs/J9TY 7LY7yLPSd7Q3rbVpVOJu7dV+xaJa+n+vvP+1mcy8EC9x5a9chavClwmFXJ52HCSyEqF+ f3Ow==
X-Gm-Message-State: APjAAAXRrihBUr9Z9nXQaS+AqtXLmWE+LD0V4A9c1RzSl/LUaNUR62BD +fLibM29FkcSxQv/dz1pmdQ=
X-Google-Smtp-Source: APXvYqzlqrR8ix+GubbEmXv4aBNC6rLtsuUa5Rc9CygUswM8RVaYcxbdVD9Qf/sO7ecFbJ8OHj44/g==
X-Received: by 2002:adf:9185:: with SMTP id 5mr26301825wri.389.1572901730657; Mon, 04 Nov 2019 13:08:50 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id c144sm17587760wmd.1.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Nov 2019 13:08:49 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: NomCom 2019 Call for Community Feedback
From: Yoav Nir <>
In-Reply-To: <>
Date: Mon, 4 Nov 2019 23:08:47 +0200
Cc: "Livingood, Jason" <>, Paul Wouters <>, Kyle Rose <>, "" <>, ietf <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Rich Salz <>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Nov 2019 21:08:54 -0000

> On 4 Nov 2019, at 21:54, Salz, Rich <> 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?

Five?  We barely manage to get two.  Where will we find five?

This WG chair gig that you and I do?  We can sell it to our respective employers as something we do in our spare time.  An AD’s job?  Not so much.

Yes, having five of them would mean that each supervises 1-2 working groups. It might make scheduling sessions in a meeting a bit easier. But the ADs will still have to attend all three meetings plus the retrieat, and most of them are still going to be reading every draft.  I can see this cutting the AD job down to 25 hours a week, maybe even 20. But that’s still a sizeable chunk of time, and it makes you not available for crunch time for your employer. 

It might get Kyle’s $600,000 down to $400,000.  A decent chunk of change, and now you want 30 such chunks rather than 14.  

I don’t think adding more management is the solution.