[multipathtcp] MPTCP Interim (audio) - doodle for date

<philip.eardley@bt.com> Wed, 25 May 2016 00:44 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F412112B025 for <multipathtcp@ietfa.amsl.com>; Tue, 24 May 2016 17:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.028
X-Spam-Level:
X-Spam-Status: No, score=-4.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 OlsRz_qrMr4o for <multipathtcp@ietfa.amsl.com>; Tue, 24 May 2016 17:44:14 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0A1012D5E2 for <multipathtcp@ietf.org>; Tue, 24 May 2016 17:44:14 -0700 (PDT)
Received: from EVMHT03-UKBR.domain1.systemhost.net (193.113.108.56) by EVMED01-UKBR.bt.com (10.216.161.31) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 25 May 2016 01:44:10 +0100
Received: from rew09926dag03a.domain1.systemhost.net (10.55.202.18) by EVMHT03-UKBR.domain1.systemhost.net (193.113.108.56) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 25 May 2016 01:44:11 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03a.domain1.systemhost.net (10.55.202.18) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 25 May 2016 01:44:11 +0100
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1104.000; Wed, 25 May 2016 01:44:11 +0100
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
Thread-Topic: MPTCP Interim (audio) - doodle for date
Thread-Index: AQHRth6Nemh+Uzfxw028rjLRhnBDPw==
Date: Wed, 25 May 2016 00:44:10 +0000
Message-ID: <1464137048262.13874@bt.com>
References: <260545774.2496927.1463995812803.POLL_ADMIN_PARTICIPATELINK@worker2.doodle.com>
In-Reply-To: <260545774.2496927.1463995812803.POLL_ADMIN_PARTICIPATELINK@worker2.doodle.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.187.101.38]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/ESToufLSldSssnhyB4rpbw-Y2B8>
Subject: [multipathtcp] MPTCP Interim (audio) - doodle for date
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 00:44:17 -0000

Hi,
http://doodle.com/poll/9ne8wz67tdrtxzk2 

In order to try and make good progress on draft-ietf-mptcp-rfc6824bis, we'd like to have an interim meeting by audio. The proposal is sometime week of 20th June. In the past we've found that 3pm GMT/UTC is a reasonable compromise for the time (we can adjust this if it isn't a suitable time). Hopefully we can complete the call in less than 1 hour, but we'll book a timeslot of 1.5 hours. Please fill in the doodle with the dates you can make. 

The topic for the call will be the proposal for a generic alternative keying mechanism (support for front-end proxies) from Alan F & Christoph P - the topic has been discussed before, and the detailed proposal will be distributed soon. 

We believe that this is  the only significant functional addition that has wide-scale interest (ie beyond what's already in the bis doc) (*). Therefore our proposal is to hold a WG Last Call on the draft after the interim and in the period leading up to the IETF. So that we can discuss issues during the Berlin meeting. Beyond that, our current thinking is that we should have some implementation before progressing the doc to the IESG (and that experience may of course lead to mods to the doc). 

(*) one of the things we'll ask in the WGLC is whether people think the doc does include all the additional functionality that people want. Of course you can raise things before the wglc. 

Best wishes,
phil & Yoshi