Re: [tcpm] no meeting at Maastricht?

"Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov> Fri, 25 June 2010 12:14 UTC

Return-Path: <wesley.m.eddy@nasa.gov>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A23A3A6981 for <tcpm@core3.amsl.com>; Fri, 25 Jun 2010 05:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.866
X-Spam-Level:
X-Spam-Status: No, score=-4.866 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 aCHEfHQ8hhRU for <tcpm@core3.amsl.com>; Fri, 25 Jun 2010 05:14:14 -0700 (PDT)
Received: from ndjsnpf02.ndc.nasa.gov (ndjsnpf02.ndc.nasa.gov [198.117.1.122]) by core3.amsl.com (Postfix) with ESMTP id A5AAC3A685C for <tcpm@ietf.org>; Fri, 25 Jun 2010 05:14:14 -0700 (PDT)
Received: from ndjsppt05.ndc.nasa.gov (ndjsppt05.ndc.nasa.gov [198.117.1.104]) by ndjsnpf02.ndc.nasa.gov (Postfix) with ESMTP id 6AAA7A80D0; Fri, 25 Jun 2010 07:14:23 -0500 (CDT)
Received: from ndjshub04.ndc.nasa.gov (ndjshub04-pub.ndc.nasa.gov [198.117.1.34]) by ndjsppt05.ndc.nasa.gov (8.14.3/8.14.3) with ESMTP id o5PCENjm020897; Fri, 25 Jun 2010 07:14:23 -0500
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub04.ndc.nasa.gov ([10.202.202.163]) with mapi; Fri, 25 Jun 2010 07:14:23 -0500
From: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>
To: Jerry Chu <hkchu@google.com>, "tcpm@ietf.org" <tcpm@ietf.org>
Date: Fri, 25 Jun 2010 07:14:21 -0500
Thread-Topic: [tcpm] no meeting at Maastricht?
Thread-Index: AcsT+Pn6nhthJrNjRHW/ASpHj8HRoQAZu3+A
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB4810873BDA@NDJSSCC01.ndc.nasa.gov>
References: <AANLkTilUogjoOVRKiFSQdfTt2xdSZEPQBVvcABbCs6Rc@mail.gmail.com>
In-Reply-To: <AANLkTilUogjoOVRKiFSQdfTt2xdSZEPQBVvcABbCs6Rc@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-06-25_06:2010-02-06, 2010-06-25, 2010-06-24 signatures=0
Subject: Re: [tcpm] no meeting at Maastricht?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2010 12:14:16 -0000

>-----Original Message-----
>From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On Behalf Of
>Jerry Chu
>Sent: Thursday, June 24, 2010 7:57 PM
>To: tcpm@ietf.org
>Subject: [tcpm] no meeting at Maastricht?
>
>Just saw the draft agenda but did not see tcpm? Are we not meeting at
>Maastricht?
>
>Thanks,
>
>Jerry
>

Hi Jerry, we originally submitted a request for a meeting slot, but
withdrew it in the last couple days after looking at a few things,
including:

- much of our work is in the phase where it's nearing completion
- among the active WG documents, tcp-security is the main one that
  could use face-time, but the editor can't make it to Maastricht
- availability of webex to IETF WGs seemed like a good way to make
  progress on tcp-security and other potential new documents
- we had seen reports that the agenda slots were heavily over-requested
  for Maastricht
- both WG chairs were having difficulty scheduling Maastricht travel

So, with the combination of those factors, we decided it would be
more beneficial to setup a webex to work on tcp-security, at least,
and use the mailing list to close out any issues on the other documents.
I hope that makes sense; I had planned on communicating it to the list
in the next couple days, but your question pushed it out today :).

--
Wes Eddy
MTI Systems