[multipathtcp] Agenda for Berlin meeting

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Fri, 24 June 2016 03:15 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 []) by ietfa.amsl.com (Postfix) with ESMTP id C9D9C12D882 for <multipathtcp@ietfa.amsl.com>; Thu, 23 Jun 2016 20:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KViGEoM5IF6n for <multipathtcp@ietfa.amsl.com>; Thu, 23 Jun 2016 20:15:29 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFC4712D87D for <multipathtcp@ietf.org>; Thu, 23 Jun 2016 20:15:29 -0700 (PDT)
Received: from mail-yw0-f176.google.com (mail-yw0-f176.google.com []) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A1AB527848D for <multipathtcp@ietf.org>; Fri, 24 Jun 2016 12:15:27 +0900 (JST)
Received: by mail-yw0-f176.google.com with SMTP id v77so89409589ywg.0 for <multipathtcp@ietf.org>; Thu, 23 Jun 2016 20:15:27 -0700 (PDT)
X-Gm-Message-State: ALyK8tJwGBn+bkKRpKcxgQGsIdafVnd8XI+FLC/Ton8VN/Ddj2rCQH2yln4chu0siXurXFrwUxXtaGybmecFzw==
X-Received: by with SMTP id o80mr1396843ywd.296.1466738126215; Thu, 23 Jun 2016 20:15:26 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 23 Jun 2016 20:15:25 -0700 (PDT)
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Thu, 23 Jun 2016 20:15:25 -0700
X-Gmail-Original-Message-ID: <CAO249yfT13iAV_pp8uM7SBn4U-PoDw5jJvCHT4NP4RKZyBiKaw@mail.gmail.com>
Message-ID: <CAO249yfT13iAV_pp8uM7SBn4U-PoDw5jJvCHT4NP4RKZyBiKaw@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary=001a114e3f08fde1cb0535fd94a6
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/bOEO4mL7nEkTMXpdoE1h2pN8ea0>
Subject: [multipathtcp] Agenda for Berlin meeting
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: Fri, 24 Jun 2016 03:15:32 -0000


As the current agenda (https://datatracker.ietf.org/meeting/96/agenda.html)
shows we are current having a 2 hour slot and a 1.5 hour slot.
We are thinking that the first slot will be used to discuss charter items
and progressing RFC6824bis, and the second slot will be used for other
items such as new ideas or sorting out the remaining stuff from the first

If you're planning to present something, please provide us the following

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

Also, please suggest us if you have some idea of the topics to be discussed
at the venue.
Ideas or opinions for hackathon are also welcome.

Yoshi & Phil