Subject: Re: [multipathtcp] FW: mptcp - New Meeting Session Request for IETF 98

From: Yoshifumi Nishida <[email-masked]>
Date: Tue, 28 Feb 2017 00:27:34 -0800

Hi,
According to the preliminary agenda (https://datatracker.ietf.org/
meeting/98/agenda.html), we will have two meeting slots from 15:20-18:40 on
3/30. (Please note this might be changed)
If you have a plan to present something, please let us know the following
info to the chairs

   1: presenter's name
   2: title
   3: length of the presentation

Thanks,
--
Yoshi & Phil

On Mon, Jan 23, 2017 at 8:13 AM, <[email-masked]> wrote:

> 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/WQzJOE9V
> 0VAnCxNlW6teDh2Olg4) 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_develo
> [email-masked]]
> Sent: 12 January 2017 08:45
> To: [email-masked]
> Cc: [email-masked]; [email-masked]; Eardley,PL,Philip,TUB8 R <
> [email-masked]>; [email-masked]
> 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 mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/multipathtcp
>