IETF Logo Mail Archive

[yam] scheduling conflicts for upcoming YAM meeting

Tony Hansen <tony@att.com> Mon, 31 August 2009 14:41 UTC

Return-Path: <tony@att.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D04893A6E13 for <yam@core3.amsl.com>; Mon, 31 Aug 2009 07:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.424
X-Spam-Level:
X-Spam-Status: No, score=-105.424 tagged_above=-999 required=5 tests=[AWL=-0.684, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tz1jTxr7p7Yh for <yam@core3.amsl.com>; Mon, 31 Aug 2009 07:41:47 -0700 (PDT)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id D48153A6E53 for <yam@ietf.org>; Mon, 31 Aug 2009 07:41:45 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-2.tower-161.messagelabs.com!1251729715!16055904!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [144.160.112.25]
Received: (qmail 1882 invoked from network); 31 Aug 2009 14:41:55 -0000
Received: from sbcsmtp3.sbc.com (HELO tlph064.enaf.dadc.sbc.com) (144.160.112.25) by server-2.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Aug 2009 14:41:55 -0000
Received: from enaf.dadc.sbc.com (localhost.localdomain [127.0.0.1]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id n7VEft9s003939 for <yam@ietf.org>; Mon, 31 Aug 2009 09:41:55 -0500
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by tlph064.enaf.dadc.sbc.com (8.14.3/8.14.3) with ESMTP id n7VEfnoR003701 for <yam@ietf.org>; Mon, 31 Aug 2009 09:41:49 -0500
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id n7VEfmQP011046 for <yam@ietf.org>; Mon, 31 Aug 2009 09:41:48 -0500
Received: from maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id n7VEfgSl010886 for <yam@ietf.org>; Mon, 31 Aug 2009 09:41:42 -0500
Received: from [135.70.84.30] (vpn-135-70-84-30.vpn.swst.att.com[135.70.84.30]) by maillennium.att.com (mailgw1) with ESMTP id <20090831144141gw1003ibrte> (Authid: tony); Mon, 31 Aug 2009 14:41:41 +0000
X-Originating-IP: [135.70.84.30]
Message-ID: <4A9BE125.40906@att.com>
Date: Mon, 31 Aug 2009 10:41:41 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Yet Another Mail Working Group <yam@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [yam] scheduling conflicts for upcoming YAM meeting
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2009 14:41:49 -0000

It's time to schedule the YAM meeting for Hiroshima. I'd rather get this 
done early rather than late in the cycle like last time. What conflicts 
does everyone want us to avoid?

My initial list is:

	APP	apparea
	APP	httpbis
	APP	idnabis
	APP	morg
	APP	ogpx
	APP	sieve
	APP	vcarddav
	SEC	sasl
	SEC	dkim

Any other conflicts we should avoid?

	Tony

v2.23.0 | Report a Bug | By Email