Re: [Tools-discuss] Important dates in upcoming.ics

Robert Sparks <rjsparks@nostrum.com> Tue, 09 February 2021 22:09 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29E123A0DD5 for <tools-discuss@ietfa.amsl.com>; Tue, 9 Feb 2021 14:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level:
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 RQ3I0gCDJmst for <tools-discuss@ietfa.amsl.com>; Tue, 9 Feb 2021 14:09:32 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 E61733A0DD4 for <tools-discuss@ietf.org>; Tue, 9 Feb 2021 14:09:32 -0800 (PST)
Received: from unformal.localdomain ([47.186.1.92]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 119M9V26013666 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 9 Feb 2021 16:09:31 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1612908572; bh=LPZWYfBW06Y7HEtAn4sv7udw8AkUFgz20KbFPsGh1ZI=; h=Subject:To:References:From:Date:In-Reply-To; b=lgoik/suDO/L1+xyQ2gfhsbHBIz2AYkkdpmCV0sDW9Ypd8BiWHgYJTpaqVMqGlvWb Ksdl1WA9Kmm7yEhw9umA4LwNG8w1YlcZFgw4Bang6aBB0m4FqUzUFRLRCFHMzBZjWm XD0SJZfC1O1mfzk8SMjAx/0nO8B+KmgN8eKAwtDs=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.1.92] claimed to be unformal.localdomain
To: Michael Richardson <mcr+ietf@sandelman.ca>, Cindy Morgan <cmorgan@amsl.com>, tools-discuss@ietf.org
References: <7da79bcd-2931-4a0e-8f7e-3ba528fea0cc@nostrum.com> <20268.1612372060@localhost> <cac83fb6-2cbd-5037-e6d7-623d4e2c30b1@nostrum.com> <947.1612405162@localhost> <15ea5446-3f90-b3bf-f10e-d3e5b58592fc@nostrum.com> <28578.1612905766@localhost> <2EF86551-5EAD-4E29-9E92-B58D5E44B322@amsl.com> <16150.1612907494@localhost>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <95d5915c-49a0-61e3-4876-16f3be30dc62@nostrum.com>
Date: Tue, 09 Feb 2021 16:09:25 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <16150.1612907494@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/uZmY_MVDH1IwCEMtEDmbMM27Jdk>
Subject: Re: [Tools-discuss] Important dates in upcoming.ics
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2021 22:09:34 -0000

On 2/9/21 3:51 PM, Michael Richardson wrote:
> Cindy Morgan <cmorgan@amsl.com> wrote:
>      >> I thought that the last conversation we had between you, I and Ines, that
>      >> IoTDIR was not configured in the right way to do this. Did that change?
>      >> Maybe we just need to remind them again.
>      >>
>
>      > This actually came up today with IOTDIR. The chairs can’t schedule a
>      > meeting themselves—it looks like they can, but then it doesn’t actually
>      > work for them. However, from playing in the sandbox, the Secretariat
>      > can schedule interim meetings for Directorates.
That's a bug - it is intended that they be able to request them themselves.
>
> Ah.
>
>      > That said, when we got the request from Ines, we (Secretariat) checked
>      > with the IESG, and the IESG would prefer to not have Directorate
>      > meetings listed in the public calendar (and have the invite go to
>      > IETF-Announce), since those meetings aren’t open to everyone.
>
> I see.
> IOTDIR is now open. (IOT-Directorate wasn't. Or have I the names swapped)
>
> But, the point of having meetings in a calendar is so that people don't get
> double booked.  It seems that maybe we need to be able to mark the meeting as
> more private, so no meeting info is put in the calendar.
Indeed - We can change the code so that the announcements for teams like 
this don't go to ietf-announce. We could even talk about requirements 
about when they show on the upcoming page, and whether coordinates 
appear there (but keep Michael's point about conflicts in mind), but it 
would be _very_ useful for these teams to be able to use the materials 
management capabilities that they asked for.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>