Re: WG Conflict Clarity

Alvaro Retana <aretana.ietf@gmail.com> Mon, 19 August 2019 01:04 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 DD82512013B; Sun, 18 Aug 2019 18:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 MBEHwxByDDmw; Sun, 18 Aug 2019 18:04:04 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 9F8A812007A; Sun, 18 Aug 2019 18:04:03 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id g8so137122edm.6; Sun, 18 Aug 2019 18:04:03 -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=SoVIpZhGxZmJPcvxGsTbhkVeLXSgcPF3Rtk2onlK5Ok=; b=iPli6KmZSAcCoLBL/FmV6P90Kwhap+3CBwzKs7y7eT19KXWfP1nL0+ar6rY9ZNH6Tr XwrVhyg4VJPXCCN7tHiRbTHzPYx2a/XGkLUwdn/Sc3pPLA42PMn+J/OrCUzBjdFYg30T Ya0YOgrAi/uZvM33+ABXYOhivN1d5jgRwRg0W/LHIfS0/snfL/kLRpEuZ1LyMiwM0L7S McK5nwIqv2wiOEQ2hXP4/rLyE+mmNPLN5DHOJP75ddkmFXp1mERx7R80yrfiF9h2IKBc tzl7xcQSzxQAd2u1VKoeMK5ZjUwDu4jWIEDYeQASVGGKigYrL0TDJ7oZZiB0BsXLEc2c /EIQ==
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=SoVIpZhGxZmJPcvxGsTbhkVeLXSgcPF3Rtk2onlK5Ok=; b=k3O8VCDNN7tKHlV2uqbrW0rK+17mOYrZyXj/OEaEPH0ysF0T9CB6zDMTvupEjriDeJ mZL1HIOCgpywre+XPxxBzK62TFJi/EWaUL06Gl6n7yddVt1g3Fs1zen6aukWjDJsZ99L JAx+Sco4Zu2hdtcAw7/zVaxvLD2npii7NFNaoid5Bp8Ya0ZNEIMrpqxCnK9GO2C4YvYk OYKZ745ekXt/jdtVDFYarKALhG2MQGiIDqDp43KV3Th2nLb2wiNE7sIJ/zTRVIMo9UIE KCHfxtBLs65F1+AyqSBNYLLrCd0LEeHZ15A3tvpfaAgo334dHMbo7roJkKmAtCrvQSk1 zQTA==
X-Gm-Message-State: APjAAAUg2ABHdIye94ClcEF8DrwGMMGFs3dYpAh54TCJPWDczOtfXM6k 3IKOHdCwofvjlQiJ5vAERJPLtu7WZ3/OWXO4f33f2g==
X-Google-Smtp-Source: APXvYqxOM20vxNEz7QCx7nubOPVFEytOvoi5IEZo3NDeA8mMn/fboqwTHFyr3pHyFn2B+CZnrcjC6ZqgqSoxTomQE0w=
X-Received: by 2002:aa7:c655:: with SMTP id z21mr4694657edr.87.1566176641992; Sun, 18 Aug 2019 18:04:01 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Sun, 18 Aug 2019 18:04:00 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CAMMESsweDzD58YsoamAR_bitE5ufNMh=J_sN5F5c78rYnoHTmA@mail.gmail.com>
References: <CAMMESsyxUbrVnV71wO-+-R-xNsPagdZStouWG9UsjBamz_0yOQ@mail.gmail.com> <CAMMESsweDzD58YsoamAR_bitE5ufNMh=J_sN5F5c78rYnoHTmA@mail.gmail.com>
MIME-Version: 1.0
Date: Sun, 18 Aug 2019 18:04:00 -0700
Message-ID: <CAMMESswQqSXUPxy5v_=2pXWGuZxVvB5Q_voxqPbzZijGJOvJdQ@mail.gmail.com>
Subject: Re: WG Conflict Clarity
To: wgchairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000066cdfb05906dea90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/54ES05MGItgTqkIkUpIIsrr1tcw>
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, 19 Aug 2019 01:04:06 -0000

Hi!

As discussed before, the labels for the Type of Conflict will go live for
session requests for IETF 106.  The Secretariat will announce the opening
of the request period tomorrow.

You will notice the new options, as listed below.  Note that you will be
able to import the information from the last meeting, but the information
may not map as expected.  Please take a minute to consider the new
categories.

Thanks!

Alvaro.

On July 12, 2019 at 2:41:07 PM, Alvaro Retana (aretana.ietf@gmail.com)
wrote:

Hi!

Thank you for the feedback and the support for this initiative.

As the implementation moves forward, we will keep the list informed.

Alvaro.

On June 28, 2019 at 10:27:00 AM, Alvaro Retana (aretana.ietf@gmail.com)
wrote:

Dear WG Chairs:

As all of you know, a conflict-free IETF agenda is virtually impossible to
achieve.  Yet, the Secretariat always pulls off a wonderful job in dealing
with all the constraints.

The inconsistent use of priorities to indicate conflicts is an issue that
comes up every time the agenda is worked on: the intent is not always clear
to the Secretariat, the ADs...or sometimes even the Chairs.

To address this issue and provide Conflict Clarity, we are planning to
replace the priority options with an explicit indication of the type of
conflict.

- 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

The Special Request field will continue to be available for more specific
needs.  Responsible AD Conflicts are already taken into consideration.


The result will be a clear representation of the needs of each WG.  We
intend for these changes to be effective in time for IETF 106.

Please reply with any comments.

Thanks!!

Alvaro (for the IESG).