[multipathtcp] FW: mptcp - New Meeting Session Request for IETF 98
<philip.eardley@bt.com> Mon, 23 January 2017 16:13 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 B26A6129644 for <multipathtcp@ietfa.amsl.com>; Mon, 23 Jan 2017 08:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.956
X-Spam-Level:
X-Spam-Status: No, score=-6.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, 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 JlTN_q8Dgr42 for <multipathtcp@ietfa.amsl.com>; Mon, 23 Jan 2017 08:13:33 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.137]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56F3E129601 for <multipathtcp@ietf.org>; Mon, 23 Jan 2017 08:13:33 -0800 (PST)
Received: from E07HT04-UKBR.domain1.systemhost.net (193.113.197.162) by EVMED03-UKBR.bt.com (10.216.161.33) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 23 Jan 2017 16:13:30 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by E07HT04-UKBR.domain1.systemhost.net (193.113.197.162) with Microsoft SMTP Server (TLS) id 8.3.342.0; Mon, 23 Jan 2017 16:13:30 +0000
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 23 Jan 2017 16:13:30 +0000
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.1210.000; Mon, 23 Jan 2017 16:13:30 +0000
From: philip.eardley@bt.com
To: multipathtcp@ietf.org
Thread-Topic: mptcp - New Meeting Session Request for IETF 98
Thread-Index: AQHSbLAiXGaMEIc5nESZlswarabbwKFGSQRw
Date: Mon, 23 Jan 2017 16:13:29 +0000
Message-ID: <63d88b3781064f9e8401abbf62160e4e@rew09926dag03b.domain1.systemhost.net>
References: <148421068590.19422.339989052893005525.idtracker@ietfa.amsl.com>
In-Reply-To: <148421068590.19422.339989052893005525.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.202.242]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/r-16nmHbUgIZBq5wXGtPeNZRcuA>
Subject: [multipathtcp] FW: mptcp - New Meeting Session Request for IETF 98
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: Mon, 23 Jan 2017 16:13:35 -0000
We requested a 2 hour meeting slot for Chicago. Please start sending us requests for timeslots. Firstly, it would be good to have some proposals /discussion about our new Milestone (added before Christmas): >>Nov 2017 Enhanced API (Informational) to IESG and something close to this text will be added to the Charter: << RFC6897 defined an optional, basic application interface for MPTCP-aware applications as well as requirements for future extensions. There is now more experience of how MPTCP is being used - in particular by the Siri application, and limited take-up by other end hosts. The WG will re-visit this work, with the aim of allowing applications to make better use of MPTCP's capabilities via enhanced APIs, and hence promote wider MPTCP deployment in end hosts. The document will be informational, and build on the work in RFC6897 in the light of the implementation and operational experience so far.>> Secondly, we're hoping that the proxy item will be added to the Charter, so we may need to allow extra time for this discussion. The proposal (https://mailarchive.ietf.org/arch/msg/multipathtcp/WQzJOE9V0VAnCxNlW6teDh2Olg4) is that we have an initial phase of <<Open for solution proposals. First step is to analyse proposals and reach consensus on one we go ahead with.>> So the Chicago meeting would be a good time to discuss proposals - please start planning your ideas! Best wishes, Phil & Yoshi -----Original Message----- From: "IETF Meeting Session Request Tool" [mailto:session_request_developers@ietf.org] Sent: 12 January 2017 08:45 To: session-request@ietf.org Cc: multipathtcp@ietf.org; ietf@kuehlewind.net; Eardley,PL,Philip,TUB8 R <philip.eardley@bt.com>; mptcp-chairs@ietf.org Subject: mptcp - New Meeting Session Request for IETF 98 A new meeting session request has just been submitted by Philip Eardley, a Chair of the mptcp working group. --------------------------------------------------------- Working Group Name: Multipath TCP Area Name: Transport Area Session Requester: Philip Eardley Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 60 Conflicts to Avoid: First Priority: ippm tcpinc tcpm tsvarea tsvwg lmap tls Second Priority: taps iccrg rtcweb Third Priority: nfvrg quic maprg Special Requests: please avoid any transport area BoFs ---------------------------------------------------------
- [multipathtcp] mptcp - New Meeting Session Reques… "IETF Meeting Session Request Tool"
- [multipathtcp] FW: mptcp - New Meeting Session Re… philip.eardley
- Re: [multipathtcp] FW: mptcp - New Meeting Sessio… Yoshifumi Nishida