[multipathtcp] q about draft-bonaventure-mptcp-converters
Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Wed, 19 July 2017 07:45 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 EF816131C05 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Jul 2017 00:45:34 -0700 (PDT)
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 EYf5gJvUVId5 for <multipathtcp@ietfa.amsl.com>; Wed, 19 Jul 2017 00:45:33 -0700 (PDT)
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 B3AC912ECC3 for <multipathtcp@ietf.org>; Wed, 19 Jul 2017 00:45:33 -0700 (PDT)
Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.52]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A52AD278317 for <multipathtcp@ietf.org>; Wed, 19 Jul 2017 16:45:31 +0900 (JST)
Received: by mail-it0-f52.google.com with SMTP id h199so25396097ith.1 for <multipathtcp@ietf.org>; Wed, 19 Jul 2017 00:45:31 -0700 (PDT)
X-Gm-Message-State: AIVw111U6x+9rSwgzMeNkZcrM4KEE0HGDTUj2sFGOMcMP0aSUDbTZ98p aafsiIX5E5TrIolb6K7XUNzZUFgW2A==
X-Received: by 10.36.39.77 with SMTP id g74mr1012697ita.89.1500450330402; Wed, 19 Jul 2017 00:45:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.167.19 with HTTP; Wed, 19 Jul 2017 00:45:29 -0700 (PDT)
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Wed, 19 Jul 2017 00:45:29 -0700
X-Gmail-Original-Message-ID: <CAO249yfHWHpvboUoPhSN4RU+pVD29juiPMYETsUgb=rUmvGyqw@mail.gmail.com>
Message-ID: <CAO249yfHWHpvboUoPhSN4RU+pVD29juiPMYETsUgb=rUmvGyqw@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="001a11474b8cf2c4690554a6d0eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/e9ndN9o1ZJ0UgcLk4KHi-cN3XW8>
Subject: [multipathtcp] q about draft-bonaventure-mptcp-converters
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Jul 2017 07:45:35 -0000
Hi Olivier, I am sorry that my question was not clear during the meeting. I think one use case we had before was a client which doesn't support mptcp can still utilize mptcp in some part of the path. Could you explain how to handle this case? Thanks, -- Yoshi
- [multipathtcp] q about draft-bonaventure-mptcp-co… Yoshifumi Nishida
- Re: [multipathtcp] q about draft-bonaventure-mptc… Olivier Bonaventure