Re: Next steps on re-organisation of areas

Alissa Cooper <alissa@cooperw.in> Fri, 20 February 2015 15:44 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554751A6FED for <ietf@ietfa.amsl.com>; Fri, 20 Feb 2015 07:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 eiDLyR52b1yM for <ietf@ietfa.amsl.com>; Fri, 20 Feb 2015 07:44:11 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D4FB1A0267 for <ietf@ietf.org>; Fri, 20 Feb 2015 07:44:11 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 566D320E8D for <ietf@ietf.org>; Fri, 20 Feb 2015 10:44:09 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 20 Feb 2015 10:44:09 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= x-sasl-enc:content-type:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; s= mesmtp; bh=l31DhsIHS/Ys7+ZV9QebwLbNO+U=; b=c6iKVDo5y8oMcAzjoc3de cK4NiBugFzMaZS+Ts2xf4BEgXJeVERkn4vp47VijXMM8a1AMRR0pfQ6zoUPK32o3 5a/SN0+FaGTobi85ubXUlyo6vLAyo24gy0UiLxLcNPbclx+b1ffIvMg+/1HEPc3z SXQoUP+tyfTSXD3M6BL/ig=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=l31DhsIHS/Ys7+ZV9QebwLb NO+U=; b=XXOQXN269Xi10m9ZZ44XvnnIia0LtVXAL4+e7gxBatgoVy6h9U6gaKC kWcoap6x3KIRJ9trglns0osTu07WvI1InD36dr+ih50j0pDSZzM2DCJP2QthzkIB q3Y2nKo9uMx07k7bwNl4bU9eLEqFscS4NeSQNaJo0Y/ZbSgPCfps=
X-Sasl-enc: 0rLuYX93ZZKgH7I5sa3LhX42noOiXAiQUnKxQ0880rIJ 1424447049
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.239.233]) by mail.messagingengine.com (Postfix) with ESMTPA id 2C3AA6801A8; Fri, 20 Feb 2015 10:44:08 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Next steps on re-organisation of areas
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <23326.1424387540@sandelman.ca>
Date: Fri, 20 Feb 2015 07:44:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <86E8A2A2-8076-4853-AEFD-EF1434CE3960@cooperw.in>
References: <7FF71DAB-016C-4409-8A15-010D882BB889@ietf.org> <23326.1424387540@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/O4rzRUR0DOHXksKhc2r3bEM0qYg>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 20 Feb 2015 15:44:13 -0000

Hi Michael,

On Feb 19, 2015, at 3:12 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> 
> IETF Chair <chair@ietf.org> wrote:
>> DESIRED EXPERTISE
> 
>> Given the amount of work encompassed by real-time and non-real-time
>> applications, it is expected that the ART area will be initially
>> shepherded by the three area directors from RAI and APP who will be
>> serving on the IESG from March 2015. Going forward, we would expect ART
>> ADs to serve two-year terms as usual.
> 
> I'm unclear if the ART area will continue with two or three ADs in 2016.

Three.

Alissa

> Perhaps that is a TBD?
> 
>> communities of interest. The ART ADs should make every effort not to
>> schedule DISPATCH and APATCH against each other at in-person meetings.
> 
> APATCH sounds a lot like Apache (the "patchy" web server), so it will be
> funny for it to deal with HTTP extensions :-)
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
>