Re: [arch-d] [Tech-plenary] IAB report to the community
S Moonesamy <sm+ietf@elandsys.com> Sun, 17 November 2019 08:21 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9CD1200C7; Sun, 17 Nov 2019 00:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=elandsys.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 bZAXR_4e1h2n; Sun, 17 Nov 2019 00:21:03 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 69DEA1200C4; Sun, 17 Nov 2019 00:21:03 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.196.83]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id xAH8Klok009023 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Nov 2019 00:20:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1573978860; x=1574065260; i=@elandsys.com; bh=WwECiW6DkzyT0SkGLffKjEClTWIlQxYQuAMrXpzJUvE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KF9TG32BDQWkMkq/uVDG6ikPFKZQbcN51gCjFeX3iFK/2bktBY5GaJqnCTxvkRAUv IW7mw6grgwa8+NVq9hvQ2QqQJiIiDfY5mTeDdtRNoo1HV2fjSpfNYnz1D/DeeWNHjZ tiN2pQt5iu8CwOx+GWvDjnFAwcsWMFFPNCOAppzs=
Message-Id: <6.2.5.6.2.20191117000609.11a7d1b8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 17 Nov 2019 00:20:24 -0800
To: Melinda Shore <melinda.shore@nomountain.net>, architecture-discuss@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: tech-plenary@iab.org
In-Reply-To: <cea1162a-97a2-8534-7d94-c08ff7050032@nomountain.net>
References: <7f516417-415b-367c-f8c5-a508942c034b@iab.org> <6.2.5.6.2.20191116065825.0de02ba0@elandnews.com> <cea1162a-97a2-8534-7d94-c08ff7050032@nomountain.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/TK9B59-Ati6Ibu48YNcNddcMl-4>
Subject: Re: [arch-d] [Tech-plenary] IAB report to the community
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2019 08:21:04 -0000
Hi Melinda, At 04:15 PM 16-11-2019, Melinda Shore wrote: >Trying to hit the sweet spot of 1) topics of broad interest, presented >by 2) great speakers who are 3) available during an IETF meeting is >surprisingly difficult. > >After a few tech plenaries that didn't work out as well as one might >have liked and on which we got substantial negative feedback, we decided >to not have technical plenaries unless we're pretty comfortable with the >quality. We had some tentative topics lined up during that period but >unfortunately speakers weren't available. We're also discussing >alternatives to the current format, including things like likely smaller >sessions of narrower interest at times outside the IETF plenary, etc. Thank you for the feedback. People usually find time if the event is relevant to them (please see (2) and (3)). Regards, S. Moonesamy
- Re: [arch-d] IAB report to the community S Moonesamy
- Re: [arch-d] [Tech-plenary] IAB report to the com… Melinda Shore
- Re: [arch-d] [Tech-plenary] IAB report to the com… S Moonesamy