Re: WG Conflict Clarity

Alvaro Retana <aretana.ietf@gmail.com> Fri, 28 June 2019 20:15 UTC

Return-Path: <aretana.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 DA5861202DB for <wgchairs@ietfa.amsl.com>; Fri, 28 Jun 2019 13:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 1yvi7YYJ_j_j for <wgchairs@ietfa.amsl.com>; Fri, 28 Jun 2019 13:15:27 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 9B68512018F for <wgchairs@ietf.org>; Fri, 28 Jun 2019 13:15:26 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id s49so12401548edb.1 for <wgchairs@ietf.org>; Fri, 28 Jun 2019 13:15:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=fILFPMx1UiW3dRH7UDfuXztQ2Q4awZp+M0niw5TEbC8=; b=P/S3Tv6CO3XIF02eJ1Vbz0qxaNB2OVDntkg/ZeM/kxyVhS8dPndtqlZEepWugYdkxj Tlm0+6xcrw8EHeGCIDyaFHrE0svmNgdAkhZTAEACflpISvUwgQb24F2bB/HnKkOlSvhN elrls4D3AExehdfaSUMP4CEBJDoEXGHMLoTSCxuthk4fHBEwW/y1dcomoquAjHSUeozT ssgMcvk6O99bpir7wGOsa138JUIiQZ/lUrN3GpoEdwAGEEoDL+M48H8WDTTP6W60QM9H s4b0P3Ho15FY06hD0UcdlfS2lJKLPD/rcY3NrzcnB3XZqJ8GJocYvS7x3VVorX3RSFCa Q49w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=fILFPMx1UiW3dRH7UDfuXztQ2Q4awZp+M0niw5TEbC8=; b=FtMapj4Sck6sDmybGRZOLuxFAZHgXc5pz0I7w7YcPDCluqcS/4iE16Ih6S30si9DyQ ht67E9acT7u28QfRbtu+N62Pr9dHoaL0Y2KwaMMGt3p3qoOcQOkHL6HNWMDtCoyQENOn 5BAc7+u+5TS8ikmK1zIbB4Kw16/lGBPIy3BJ9H7owxPOo3JM6jrI4gzyFzatYKDyxHxW 2QZhQJtfh7HxSmIELAx3z257KA1z2lJneuzXoVDPs1MsAJD8Y+VA45rvLhD93ZhW014n uEB/lJ+LfR4Ns3Jac5nYqfdnpL/TUSeW0ZhExCZiWA2q2uZUj+g+PhTTkwImFX7uQDBS l0Jg==
X-Gm-Message-State: APjAAAVP/lV863cEF6rLeGNka4UpUhb7wbkr5G7D1pa839LXAQTHj+tl igwiKiYnYwGNH3Ek8vgQ/4qvf4JJZJWc4bzEIJMc4w==
X-Google-Smtp-Source: APXvYqxiRsRAIj0n1NteUT/83XWKFn0CqDYIczwJKZhav2re/nr/qY7Ef2EExfw81z3+Mt9rIXhsOjHrCn5jrdewDkM=
X-Received: by 2002:a17:906:401a:: with SMTP id v26mr10691376ejj.62.1561752925139; Fri, 28 Jun 2019 13:15:25 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 28 Jun 2019 15:15:24 -0500
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <10658.1561749435@localhost>
References: <CAMMESsyxUbrVnV71wO-+-R-xNsPagdZStouWG9UsjBamz_0yOQ@mail.gmail.com> <10658.1561749435@localhost>
MIME-Version: 1.0
Date: Fri, 28 Jun 2019 15:15:24 -0500
Message-ID: <CAMMESsxewQ40y3XsMDQKq_D=pvCuM7kDwAvcfvzc0E_uF312ig@mail.gmail.com>
Subject: Re: WG Conflict Clarity
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: wgchairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005475fc058c67f071"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/td0iC9nKLM0j-B-4s8XMycPnLc8>
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: Fri, 28 Jun 2019 20:15:29 -0000

On June 28, 2019 at 3:17:17 PM, Michael Richardson (mcr+ietf@sandelman.ca)
wrote:

Michael:

Hi!

Alvaro Retana <aretana.ietf@gmail.com> wrote:
> - Chair Conflict: to indicate other WGs the Chairs also lead, or will be
> active participants in the upcoming meeting

> - Technology Overlap: to indicate WGs with a related technology or a
> closely related charter

> - Key Participant Conflict (e.g., presenter, Secretary, etc.): to indicate

> WGs with which key participation may overlap in the upcoming meeting

Given two WG, "A" and "B" with chairs "A1", "A2" and "B1" and "B2"

If A1==B1, that's clearly a chair conflict, as the chair can't be in both
places.

If A1 is a Key Participant in group B, what kind of conflict is that?

Is it a Chair Conflict for A and a Key Participant conflitct for B?

That is how we intended it.

...

Would Technology Overlap conflicts be explicitely stated in WG charters?
(Often they say, "will coordinate with WG XYZ" already)


I think that is a related but independent question.

There may be some indication in the Charters of necessary coordination.
But that is not a requirement to call out a conflict, and the indication of
the conflict is not meant to be confirmed in the Charter nor to trigger an
update.  As an example, sometimes a WG will discuss a specific topic that
may benefit from expertise from a specific set of people; I think that
could be expressed as a Technology Overlap for that session.

Thanks!

Alvaro.