IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-boucadair-mptcp-dhc-05.txt

Ted Lemon <mellon@fugue.com> Thu, 12 May 2016 13:50 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA1C12D12F for <dhcwg@ietfa.amsl.com>; Thu, 12 May 2016 06:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jF3eblps4Lyg for <dhcwg@ietfa.amsl.com>; Thu, 12 May 2016 06:50:54 -0700 (PDT)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF7D12B013 for <dhcwg@ietf.org>; Thu, 12 May 2016 06:50:53 -0700 (PDT)
Received: by mail-lb0-x231.google.com with SMTP id ww9so3064451lbc.2 for <dhcwg@ietf.org>; Thu, 12 May 2016 06:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k5BLKm4K0bL7OdX+I1T8DxZXr10HieHROcMVguXRkAc=; b=HOxxvm8e5J/9Aa6EOFgpRQ5k6w7fPpxGALjXnSQz0LcCYhsw57OKoKb6QegOsbqZRU yDhFxwremIyEhgrL5/4HsfBfX78aU3hwzrCXs0Xd2CWxk8o0m869fBIATiL6RBKjmzVU WHTxOqx9eQD2FTU9kLDswr4GnpNf/GewghSL/Kqh2ulVtXw2Cv8AzxhxJ265QcROhbHN 8ntteyxd/Mk+A+Xo0Hzd63O1yqeths5r+N6gov0OO4qPMtYa+TjzhqTv0zYmwSgLlFwM c90jZ38V1eAAIEfxyCrtiMpkqLTU4vnGYwBiTtyObKmmQ8TESkEXM7TvAKJCGVWqJvVP t9Cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k5BLKm4K0bL7OdX+I1T8DxZXr10HieHROcMVguXRkAc=; b=WuYfSdwDW/T5oWMYnU8yRYaWEQCU4iCov/NpudV+GzEjdkdBbABRpB9CvVHQP2yCUw NFiSyIPiLL2yhJyGcA01SG/zBJk2GYTTuznk+gsCVO3oJv9d+cO8ataxb+LsQTl01YdB 1CQwZ+p0beYucCz+5jSv4pN5EWgybPWZZB58+2xElkLhfCWtfbkKtuQe65w/a9H9gEhl 2f9pW64o14bfZDndQlvhuyph5nfmn1EhUOCCeFfs7/y+32Zp7OOwyaohYLRAf0M+0ur4 vOo0ecTvoxIaIbky7otdqE3aq6LZ9HPVeIF9Nwah4bogNrNPVsGto5U7zzPPzQpkxVU0 wk0Q==
X-Gm-Message-State: AOPr4FWyMdXQYqyyFJ1Ac3rGktqELpUR3y2JWdz455QSqYI+M7AO92zrwTtTAGRQfYcMpL97yhdrd67QFaAvgw==
X-Received: by 10.112.77.2 with SMTP id o2mr4331374lbw.83.1463061051669; Thu, 12 May 2016 06:50:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.153.135 with HTTP; Thu, 12 May 2016 06:50:12 -0700 (PDT)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933008D73EF6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <20160509122456.4958.6416.idtracker@ietfa.amsl.com> <CAPt1N1no3N3ETQnza6g-Kw31cHGBmzOTYyyC-k9QXyuKy-yz_w@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933008D73EF6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 12 May 2016 09:50:12 -0400
Message-ID: <CAPt1N1nbrvVH+cVdG8BAHTJjjRSTr0CEt1ArdNgkYq2J+d1=YA@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary="001a11c3a6f445189d0532a5725c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/BlxeMAKO_g8UIZrq_xuXWEP_JLk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-boucadair-mptcp-dhc-05.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 13:50:56 -0000

Okay, but I was really asking about the deployment model, not about which
connections would be eligible for mptcp.   I'm trying to understand how
this would actually work.   Is this something you guys have working in the
lab?

On Thu, May 12, 2016 at 7:25 AM, <mohamed.boucadair@orange.com> wrote:

> Hi Ted,
>
>
>
> This draft specifies DHCP options to tell a CPE how to contact its MPTCP
> concentrator(s).
>
>
>
> Not all TCP connections issued from the LAN side are eligible to be
> relayed into MPTCP connections to benefit from WAN aggregation features.
> Only a subset of them will be selected according to a set of policies that
> are provisioned to the CPE and/or the concentrator. These polices are out
> of scope of this draft.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* dhcwg [mailto:dhcwg-bounces@ietf.org] *De la part de* Ted Lemon
> *Envoyé :* lundi 9 mai 2016 19:25
> *À :* dhcwg@ietf.org
> *Obje**t :* Re: [dhcwg] I-D Action: draft-boucadair-mptcp-dhc-05.txt
>
>
>
> On Mon, May 9, 2016 at 8:24 AM, <internet-drafts@ietf.org> wrote:
>
>    This document focuses on the explicit deployment scheme where the
>    identity of the MPTCP Concentrator(s) is explicitly configured on
>    connected hosts.  This document specifies DHCP (IPv4 and IPv6)
>    options to configure hosts with Multipath TCP (MPTCP) parameters.
>
>
>
> It occurs to me that in principle you don't actually need (and probably
> don't want the security implications of) explicit configuration of MPTCP.
>
>
>
> Why not instead just have an intelligent gateway that is aware that its
> network is multihomed.   When it sees a TCP connection come from a node on
> the network that solicits MPTCP, and sees a reply back from the target
> server that does not support MPTCP, it drops the SYN+ACK and redirects the
> connection through an MPTCP concentrator on the provider network using both
> available links.
>
>
>
> Oh, or is that what you actually had in mind, and the DHCP option is just
> to tell the edge routers how to contact the concentrator?
>

v2.23.0 | Report a Bug | By Email