Re: [Sidrops] Reviewing conflicts from IETF 115 in session request tool
Jeff Tantsura <jefftant.ietf@gmail.com> Sat, 07 January 2023 16:06 UTC
Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7658C14CE2D; Sat, 7 Jan 2023 08:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQZs7LjEu44z; Sat, 7 Jan 2023 08:06:44 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44AE5C14CF17; Sat, 7 Jan 2023 08:06:44 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id c4-20020a1c3504000000b003d9e2f72093so797350wma.1; Sat, 07 Jan 2023 08:06:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ljV9kkKkagOvSls3MRLpz2SwSTmkyJYGn318njqy+3Q=; b=aAzKrrIcF4Mwu5cbK2knzL/gd6dwPesfvvqmA4xmrLumK3s+pEURWGAxmTNhqiyheU buSgUMAl3RamRYnZudoontusppEw5W27OXC9o6hstiYBzC35/T7aN6fdyrf+QP3u8Qul jNSqZpxN2U47FNrk6wo4NCgt8kfOxwJnNalhFzST3wu5p7rr8HKx4+l05HMEXQfwJ6JF 2qrr/hKNW4ROfSWxRH97cac2/P6yFzyULf4pVnzch0IZstkJkDRLHXkKpNCJc9w8DaYY j5ocIZ+3v3PvYdcUm4dSE1AvlnPFd47Nddt7uwRDsfpy9p2bDhA6tByA0pGQ2aZxCitQ F3Dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ljV9kkKkagOvSls3MRLpz2SwSTmkyJYGn318njqy+3Q=; b=teH8209d1LbAGOy4HNHhXYDYimbfA0zAqnDu4MH4PtvUiyd7Sg1dtSUhpWh+mJdTQ3 w2eRuqOW/xFiP5lk6NynJgpmNow9uz2XC6VjZHP2GSwesU49HHmsNqxOqoPzO3skkKSl 7qd0tASCsd9ivfTYvYm05uvIW01O4zJb29viICPWTFR1jaF06QRyfHOGRd9CTAtkaUb6 Pe1qcxHCAx9zYVUrSNEzuf1VVVZ8cJj/eQN2D2QtE4IITHovdoRG80yv7kfFdO6qVej+ 0VfWNyodbZ4CJl+zdWim4Q3rzsjU+ogwazKH++Jl7Li51DQcBBEP9saIsD4uUuv1IruJ CHKg==
X-Gm-Message-State: AFqh2kqzv5x/QIG1qBRy+fv1pQq3MGr2ABf0kac2VmR1Ch9XZNbBhnd/ twFPnhncp31UrCVFYUn9ME4iZGbji6R0jA==
X-Google-Smtp-Source: AMrXdXtU3C2cauYq2klOA0oMqBJzkUv7kelwPLpTIkGSez2L7/YcddyV8nigYDCSSJY3qY4831ns3w==
X-Received: by 2002:a05:600c:1e16:b0:3d1:d1a9:efde with SMTP id ay22-20020a05600c1e1600b003d1d1a9efdemr46201058wmb.12.1673107601881; Sat, 07 Jan 2023 08:06:41 -0800 (PST)
Received: from smtpclient.apple ([217.181.193.133]) by smtp.gmail.com with ESMTPSA id 2-20020a05600c228200b003d9e00dfccfsm3415178wmf.8.2023.01.07.08.06.40 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 07 Jan 2023 08:06:41 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 07 Jan 2023 17:06:25 +0100
Message-Id: <3DC2FF57-B957-41B9-98C8-3EF419561CCC@gmail.com>
References: <aa3055facb654ce0dfd2a19e2670f7c6@ripe.net>
Cc: Chris Morrow <morrowc@ops-netman.net>, Liz Flynn <lflynn@amsl.com>, rtgwg-chairs@ietf.org, sidrops-chairs@ietf.org, rtgwg@ietf.org, sidrops@ietf.org
In-Reply-To: <aa3055facb654ce0dfd2a19e2670f7c6@ripe.net>
To: ntrenaman <ntrenaman@ripe.net>
X-Mailer: iPhone Mail (20C65)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/QA3fLEvyBzHH26sF-DXfKxl_NNQ>
Subject: Re: [Sidrops] Reviewing conflicts from IETF 115 in session request tool
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jan 2023 16:06:48 -0000
Thanks Liz and Nathalie! For RTGWG we commonly ask to avoid any contention with Routing Area working groups, however without mentioning any other area wg’s (it is already complicated enough to find a non overlapping time slot). Liz - would it work if non Routing Area wg chairs mention RTGWG in their list of conflicts to avoid and you, when scheduling would take it into consideration? Cheers, Jeff > On Jan 6, 2023, at 22:13, ntrenaman <ntrenaman@ripe.net> wrote: > > Hi all, > > IETF115 was the first time we clashed, and that was indeed unfortunate. For the sidrops 116 session request, I already added rtgwg to the list of avoided clashes, so I hope we're good. > > Cheers, > Nathalie > > >> On 2023-01-06 21:46, Chris Morrow wrote: >>> On Fri, 06 Jan 2023 20:36:16 +0000, >>> Liz Flynn <lflynn@amsl.com> wrote: >>> Hi RTGWG and SIDROPS chairs and participants, >> I was going to say: "SO UNREASONABLE!" :) >> but .. nope, this is totes reasonable. >> I think I (at least) just keep clicking the 'get conflicts from last', because >> who has time for all that typing?? :) >> I'll try to do better. >> -chris >>> In the IETF 115 meeting survey six respondents called out RTGWG and SIDROPS when answering Q19, “How many times did you have a conflict between two sessions that were scheduled in the same time slot?" However, to date, these groups have not listed each other as Conflicts to Avoid in the Session Request tool. >>> As we start to plan for IETF 116, we are asking you to consider this feedback and update your Conflicts to Avoid as appropriate. If you need assistance, the Secretariat is happy to make updates in the Datatracker on your behalf, but we do need clear guidance on what changes to make, and how to record any new conflicts (i.e. chair conflict, technology overlap or key participant conflict). >>> Finally, we’d like to remind everyone that the wg mailing list receives a copy of each session request, and we encourage you to review the noted Conflicts to Avoid at the time of request, so that you can reach out to the working group chairs if you feel something is missing or incorrect. >>> Thank you, >>> Liz >>> IETF Secretariat
- [Sidrops] Reviewing conflicts from IETF 115 in se… Liz Flynn
- Re: [Sidrops] Reviewing conflicts from IETF 115 i… Chris Morrow
- Re: [Sidrops] Reviewing conflicts from IETF 115 i… Christopher Morrow
- Re: [Sidrops] Reviewing conflicts from IETF 115 i… ntrenaman
- Re: [Sidrops] Reviewing conflicts from IETF 115 i… Jeff Tantsura
- Re: [Sidrops] Reviewing conflicts from IETF 115 i… Alvaro Retana