[pim] WG session scheduling and conflicts

Stig Venaas <stig@venaas.com> Tue, 04 April 2017 17:28 UTC

Return-Path: <stig@venaas.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5C011287A3 for <pim@ietfa.amsl.com>; Tue, 4 Apr 2017 10:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=venaas-com.20150623.gappssmtp.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 qYS8DCHZV4ic for <pim@ietfa.amsl.com>; Tue, 4 Apr 2017 10:28:21 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 47E73127A97 for <pim@ietf.org>; Tue, 4 Apr 2017 10:28:18 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id d10so148439233qke.1 for <pim@ietf.org>; Tue, 04 Apr 2017 10:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=Z6K7So5daOKi/ieiDzNv6TyVmssEvpfL00qRVvCw3Fs=; b=afNNgrhLvAuvln/8Ib/VyxkOUfsY/20jzTaBG2wlsPbqfP7BGbWpwNen5JvlOlwcZ3 UVLEqS3K5bIHZddvyBBiUndFQhiXpGmXMsrYWyiEVIGgyqOleJCGO6snHw3GqNvepf4E 1+U3Y1cbS68WWtfVWqtd3VmqntjtKtHWW1CjGMmbaEV1S4CXKyN1r0YLNKzQBZyaq2zB sfrDuORQSLAxn1VKPMl1qmKhKKLXFRwgTe/rQEGhi/IgwIEtZhjsC/l45/XBdF35Xo4w s3vUDG0+kXueF/4/zFvzlZQJCJjjS97KouN9oHh+bptldxgl7RiQ/+kqCRF+6yTRHwdq 6ydQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Z6K7So5daOKi/ieiDzNv6TyVmssEvpfL00qRVvCw3Fs=; b=f8KvFawLIauOapRRWZ3nCu1FuUZGMTLfeAPnOzdoGbNkQKmRMSoU4NgtZWat3KclLV DGCJLz01l0DC98CzjbLVJ/KsBbYpsjeP2IzVXFyefSZauM4tf7YakNwZgYsFCxmlxXdr 18A5rvqD5ZgUv1Dd9BPN9dRMqk2a3kYGY1RG3swtiJ1co74rQTTUsSCfqX1HTNPNHnm+ dwzXzoC5GotIfOuRuBmc5hhOZ2L8HYPPcK/0eI23lgusL8KE/oflxnpVtbQJYgqU5ij8 4rAsAjbPVzZ6+kCGFZt+fxI0UkxBP0GHmOH2enl8O+sozjTq5L+sdQUCq0KXnhpIAw75 eD1A==
X-Gm-Message-State: AFeK/H1SyQp56wObq3igZl6eI2kgY1kkelGWf+X9/YsXDos4bYSYywjxZvMKfeqBzxLRfvULCsDQTAfXUznD8A==
X-Received: by 10.55.112.6 with SMTP id l6mr10387638qkc.187.1491326897074; Tue, 04 Apr 2017 10:28:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.102.151 with HTTP; Tue, 4 Apr 2017 10:28:16 -0700 (PDT)
From: Stig Venaas <stig@venaas.com>
Date: Tue, 04 Apr 2017 10:28:16 -0700
Message-ID: <CAHANBtLiCZV5nr+Jw2w11UPjyRMxGMkcMXqa+Z9Ybsp2TGB5Cg@mail.gmail.com>
To: "pim@ietf.org" <pim@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/CTnJysG0LNEcZzrgZmnBF7c0gJ8>
Subject: [pim] WG session scheduling and conflicts
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 17:28:23 -0000

Hi

When we request a slot for pim WG we get to specify conflicts.
Basically other WGs that should not meet at the same time, since there
might be many people that want to attend both the meetings.

Mike and I are generally trying to list what seems obvious to us, but
a few people told me about conflicts we didn't consider. E.g. for YANG
work there are some conflicts we forgot to consider.

If you are aware of conflicts you believe will affect many people in
the pim WG, please let us know and we will take it into consideration.
It is impossible to avoid that a few participants will encounter
conflicts, but we can report what we think are larger conflicts, and
the secretariat does their best at coming up with an agenda that
minimizes the conflicts overall for all the WGs.

Stig