IETF Logo Mail Archive

Re: IETF 110 schedule update

Hugo Salgado <hsalgado@nic.cl> Mon, 04 January 2021 20:07 UTC

Return-Path: <hsalgado@nic.cl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4F83A1011; Mon, 4 Jan 2021 12:07:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 hB4BsL7rfkgm; Mon, 4 Jan 2021 12:07:49 -0800 (PST)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CDFD3A100F; Mon, 4 Jan 2021 12:07:49 -0800 (PST)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id C45F9195D6091; Mon, 4 Jan 2021 17:07:45 -0300 (-03)
Received: from pepino (pc-10-37-215-201.cm.vtr.net [201.215.37.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nic.cl (Postfix) with ESMTPSA id A16D0195D608A; Mon, 4 Jan 2021 17:07:45 -0300 (-03)
Date: Mon, 04 Jan 2021 17:07:44 -0300
From: Hugo Salgado <hsalgado@nic.cl>
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: IETF 110 schedule update
Message-ID: <20210104200744.GK3481@pepino>
References: <1324823E-EEDC-4633-A6BB-978BE9D55252@ietf.org> <67AFF440-70DF-46C0-AD77-58BB0847C725@mnot.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="NZiXfHLGvOGtDZMn"
Content-Disposition: inline
In-Reply-To: <67AFF440-70DF-46C0-AD77-58BB0847C725@mnot.net>
X-Virus-Scanned: ClamAV using ClamSMTP on Mon Jan 4 17:07:45 2021 -0300 (-03)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T0ETQsOpeSWno5TPr-e2MaNJ71c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 20:07:52 -0000

On 16:34 26/12, Mark Nottingham wrote:
> Could this information be placed somewhere on <https://www.ietf.org/how/meetings/110/>?
> 

Back in June 2020 I asked the same question to mtd@ietf.org and was
directed to a blog post that mentioned the relevant times. I believe
that this information should go in the official page of the meeting,
in a place of the same importance as the dates.

Hugo

v2.23.0 | Report a Bug | By Email