Re: [yam] YAM - Requested session has been scheduled for IETF 78

Tony Hansen <tony@att.com> Tue, 29 June 2010 15:46 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 511763A6BC6 for <yam@core3.amsl.com>; Tue, 29 Jun 2010 08:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.298
X-Spam-Level:
X-Spam-Status: No, score=-106.298 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599, 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 aI95gETYhCqL for <yam@core3.amsl.com>; Tue, 29 Jun 2010 08:46:47 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id 700F73A6B98 for <yam@ietf.org>; Tue, 29 Jun 2010 08:46:47 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-9.tower-129.messagelabs.com!1277826413!41047256!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 23521 invoked from network); 29 Jun 2010 15:46:54 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Jun 2010 15:46:54 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o5TFkTJk014056 for <yam@ietf.org>; Tue, 29 Jun 2010 11:46:30 -0400
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o5TFkQ70013999 for <yam@ietf.org>; Tue, 29 Jun 2010 11:46:26 -0400
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 o5TFkn2q030542 for <yam@ietf.org>; Tue, 29 Jun 2010 10:46:49 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.3/8.14.3) with ESMTP id o5TFkiF0030424 for <yam@ietf.org>; Tue, 29 Jun 2010 10:46:44 -0500
Received: from [135.70.25.139] (vpn-135-70-25-139.vpn.west.att.com[135.70.25.139]) by maillennium.att.com (mailgw1) with ESMTP id <20100629154643gw100s4pv8e> (Authid: tony); Tue, 29 Jun 2010 15:46:43 +0000
X-Originating-IP: [135.70.25.139]
Message-ID: <4C2A1561.8090205@att.com>
Date: Tue, 29 Jun 2010 11:46:41 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <20100624210950.74B703A69D6@core3.amsl.com> <4C24353B.1050605@att.com> <4C290EA5.8090501@isode.com>
In-Reply-To: <4C290EA5.8090501@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] YAM - Requested session has been scheduled for IETF 78
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: Tue, 29 Jun 2010 15:46:48 -0000

Works for me. I had originally asked for a 1 hour slot.

     Tony Hansen

On 6/28/2010 5:05 PM, Alexey Melnikov wrote:
> Tony Hansen wrote:
>
>> FYI, our WG session at Maastricht has been scheduled for
>
> This is not yet final.
>
> I would like to suggest to move the YAM's meeting till after the IESG 
> plenary on Wednesday. This will help the WG to spend the meeting time 
> more productively.
> For example we can move YAM to Thursday 15:10-16:10 (it is a shorter 
> slot, but do we really need 1.5 hours?).
>
> Thoughts?
>