Re: [multipathtcp] FW: mptcp - New Meeting Session Request for IETF 98
Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Tue, 28 February 2017 08:27 UTC
Return-Path: <nishida@sfc.wide.ad.jp>
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 D899D1289B0 for <multipathtcp@ietfa.amsl.com>; Tue, 28 Feb 2017 00:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no 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 namDbOZELI97 for <multipathtcp@ietfa.amsl.com>; Tue, 28 Feb 2017 00:27:40 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B2051294E4 for <multipathtcp@ietf.org>; Tue, 28 Feb 2017 00:27:38 -0800 (PST)
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9C2EB29C1D2 for <multipathtcp@ietf.org>; Tue, 28 Feb 2017 17:27:36 +0900 (JST)
Received: by mail-oi0-f41.google.com with SMTP id 2so2455242oif.0 for <multipathtcp@ietf.org>; Tue, 28 Feb 2017 00:27:36 -0800 (PST)
X-Gm-Message-State: AMke39l/Z1XPoCssfOv8RqhFJF5ApbWMhzsAPkEKjcxTbpm7ngiqgEtmuyaNunSWzpCjWULDsvlGh+qX93UrEQ==
X-Received: by 10.202.52.139 with SMTP id b133mr572851oia.168.1488270455277; Tue, 28 Feb 2017 00:27:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.82.27 with HTTP; Tue, 28 Feb 2017 00:27:34 -0800 (PST)
In-Reply-To: <63d88b3781064f9e8401abbf62160e4e@rew09926dag03b.domain1.systemhost.net>
References: <148421068590.19422.339989052893005525.idtracker@ietfa.amsl.com> <63d88b3781064f9e8401abbf62160e4e@rew09926dag03b.domain1.systemhost.net>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Tue, 28 Feb 2017 00:27:34 -0800
X-Gmail-Original-Message-ID: <CAO249ycmxohtKeur1bgbRDefXTubGFT5qc_tmLFB9+3be=QB6Q@mail.gmail.com>
Message-ID: <CAO249ycmxohtKeur1bgbRDefXTubGFT5qc_tmLFB9+3be=QB6Q@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d448cd113cb054992f7d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/rdvo3SchZRfaNGwQOFrT5MkVa5c>
Subject: Re: [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: Tue, 28 Feb 2017 08:27:43 -0000
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, <philip.eardley@bt.com> 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 > pers@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 mailing list > multipathtcp@ietf.org > https://www.ietf.org/mailman/listinfo/multipathtcp >
- [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