Re: [arch-d] IAB report to the community

S Moonesamy <sm+ietf@elandsys.com> Sat, 16 November 2019 16:26 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 8DF0B12011C; Sat, 16 Nov 2019 08:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level:
X-Spam-Status: No, score=-0.598 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 7dJf34eWDUhe; Sat, 16 Nov 2019 08:26:33 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 77A9312008C; Sat, 16 Nov 2019 08:26:33 -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 xAGGQGjq012621 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Nov 2019 08:26:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1573921589; x=1574007989; i=@elandsys.com; bh=4z1VndO5L+c81v6WaKz6DQBRndxslNithvuWVCUYdBc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=F1pkjiMQCRJjTBZV6dkt04TM4Vefk42HEdkqjbqIb1W2Ye1c8UrQ4AHve1UcrAV6w RWjCRTuMpFawojCuQ2cC9CjyabzPc1I1uiQIXLFZ3RzhF/IrS1AziU8NjQt8nIHMHM hinODdsQc7q0KQ9TpZQpf+8UX79UyzbohCzyhQ3c=
Message-Id: <6.2.5.6.2.20191116065825.0de02ba0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 16 Nov 2019 07:19:01 -0800
To: architecture-discuss@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: tech-plenary@iab.org
In-Reply-To: <7f516417-415b-367c-f8c5-a508942c034b@iab.org>
References: <7f516417-415b-367c-f8c5-a508942c034b@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/QEu6vh1qxIdVZ9kd5hPb2uMFNEQ>
Subject: Re: [arch-d] 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: Sat, 16 Nov 2019 16:26:34 -0000

Hello,
At 05:23 PM 15-11-2019, Ted Hardie wrote:
>Here is the IAB report for the period between IETF 105 and IETF 
>106.  If you have topics or issues you want to discuss by email, 
>feel free to send your comments to architecture-discuss@iab.org (our 
>public discussion list) or iab@iab.org (to reach just the IAB).

The Tech Plenary is expected to be on a topic of interest to at least 
several IETF Areas and to "inform our work".  I went through the past 
plenaries and noticed that there wasn't any Tech Plenary for three 
consecutive IETF meetings.  Is it because it was difficult to get 
interesting speakers?

Regards,
S. Moonesamy