IETF Logo Mail Archive

Re: WG Conflict Clarity

Fred Baker <fredbaker.ietf@gmail.com> Mon, 01 July 2019 06:29 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F58F12019D for <wgchairs@ietfa.amsl.com>; Sun, 30 Jun 2019 23:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.659
X-Spam-Level:
X-Spam-Status: No, score=-0.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 J_4OgNbZ5F9b for <wgchairs@ietfa.amsl.com>; Sun, 30 Jun 2019 23:29:26 -0700 (PDT)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878AF1201FA for <wgchairs@ietf.org>; Sun, 30 Jun 2019 23:29:26 -0700 (PDT)
Received: by mail-ot1-x32d.google.com with SMTP id l15so12297125otn.9 for <wgchairs@ietf.org>; Sun, 30 Jun 2019 23:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=vxx78bdqY4eDew/q58iV6f4HWx0MRcGQDNQmnTrf0fI=; b=uHRxZW6h5PUmiqmhb+6MRnzPflW2dIJrYYlmZIolTruHWFhbfPI/G/Wf2xaCxw1jL8 vq/BTtSG4pvcPIpKHucFBtH8ZXgmR9th6tItqF5j3QKvQTBmlqn+yJfifUEkB9zLTvfJ RCFcs536DBakbZjH5r02+vTAmVMFQizLezRtdb8PQqrvGIuCtdwa7I8wrslaijg9zRkD +dZ647DoeMWaOeTDqL/nVAAm2ghzJM1tXTxDAwR3IjHYYofslnRFscdlx0e/U+V9mHxm XoLQ11WhJlIdTUoOqsmQLcQV2EwMtPC5fDb3sZOUElyuOG7nzXsfsSDyN5XlOUepp31V qIDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=vxx78bdqY4eDew/q58iV6f4HWx0MRcGQDNQmnTrf0fI=; b=SE9Vlxj+i/9N7Z4TLbBUtkJUbI+YexOBEz0NY/ruk8hgELHMUsTHwlcUO+05B4ERap WMPUrOjuKXvMloNoaOZXcZKsTgsEwGdhCI0iKXOwJ3ysKYi7GAc8uTRNqBIIUra0cBp2 nCi5uZ3e1877KO78aRizJtHCweJCfoVQhq0uTMT+n0SX+o3q8i1UsWdDp/JN9+uarxOs nF4Dn68W99kf8a4yP+MLbBIhCw4n8AcHjgL/5Q000eI4J9Ny4xAZMi7aZxdA1cc8/qVD Ih6k6CS+1rBcQlsEiv9UmEXIgXaIwajMT56GdsCi4jTwbtSIwY3ieMiBDdlG/LO9QWWl fFxA==
X-Gm-Message-State: APjAAAU8g1cLwEwfvR2VTfGHh8wmYD8bxcBNwFGZdI1GKI5T88D6+Ah6 TT86pty2tZimkEu2C+qsAFw=
X-Google-Smtp-Source: APXvYqzLyoM+nHaeJy2sJewx+qKPj89DU9F4KfKpdmccuEkl/uCjbJKJRnV3t2hu8JITX/x8noZRaA==
X-Received: by 2002:a9d:7f0f:: with SMTP id j15mr19298634otq.156.1561962565852; Sun, 30 Jun 2019 23:29:25 -0700 (PDT)
Received: from ?IPv6:2600:8802:5903:df16::1019? ([2600:8802:5903:df16::1019]) by smtp.gmail.com with ESMTPSA id a20sm3658725otl.44.2019.06.30.23.29.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jun 2019 23:29:25 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <9037B22D-2C29-466F-B149-20EB24F6B841@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_383C5B66-EE70-4459-A352-4F98E80D50A7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: WG Conflict Clarity
Date: Sat, 29 Jun 2019 12:23:34 -0400
In-Reply-To: <CANk3-NDmx07nK6th6=sxKnb6Md8qyPXAa==HrtcYh0NBZqiZ+Q@mail.gmail.com>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, IETF WG Chairs <wgchairs@ietf.org>
To: Wes Hardaker <hardaker@isi.edu>
References: <CAMMESsyxUbrVnV71wO-+-R-xNsPagdZStouWG9UsjBamz_0yOQ@mail.gmail.com> <CE6758DF-812F-4BB1-BDB5-3395AED5DA74@gmail.com> <CANk3-NDmx07nK6th6=sxKnb6Md8qyPXAa==HrtcYh0NBZqiZ+Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ods0btSpKdihGzvZWIy6gOAMuSo>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2019 06:29:29 -0000


> On Jun 28, 2019, at 11:48 PM, Wes Hardaker <hardaker@isi.edu> wrote:
> 
> On Fri, Jun 28, 2019 at 7:52 AM Fred Baker <fredbaker.ietf@gmail.com> wrote:
>> Makes sense to me, and confirms the ways I have been using the field - if some has an active role in my meeting (presenter, chair, etc), then I have listed their other working groups as conflicts. This will just make that more explicit.
> 
> I've never, in many years of presenting at IETFs, had a chair ask me what other groups I'm active in.  And trust me, they likely couldn't have guessed the full list easily as I've dabbled in lots of areas and their view of me has likely been associated with a single sub-area.  I would suggest that chairs be encouraged to make sure and ask likely speakers for such a list?

Well, perhaps I should clarify. I look up my presenter's drafts, and determine from that what working groups they are in. I absolutely agree that's not conclusive or complete, but my theory is that the person is presenting in my working group and has a draft in another group; there is at least some possibility of a conflict there.

v2.23.0 | Report a Bug | By Email