IETF Logo Mail Archive

Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis

Alan Ford <alan.ford@gmail.com> Thu, 19 July 2018 19:29 UTC

Return-Path: <alan.ford@gmail.com>
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 225EA130F6C for <multipathtcp@ietfa.amsl.com>; Thu, 19 Jul 2018 12:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 L9cZbUXEEPFp for <multipathtcp@ietfa.amsl.com>; Thu, 19 Jul 2018 12:29:07 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 0666E130EDA for <multipathtcp@ietf.org>; Thu, 19 Jul 2018 12:29:07 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id 203-v6so9031551ljj.13 for <multipathtcp@ietf.org>; Thu, 19 Jul 2018 12:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=198O4iggAD6dtCY9fRm0QbqZEfL21vKHVnm4pG+NsMc=; b=IpLFZQvKgUsahrZ3GY8UTMRxdJpAv9EH+tL6onTdVLHa+IDy9rw1z64V5YpXsPLqZ2 Af7rjQQ/j29EvfLQOukTLTKu4ZE5DTsnAcTRx/rBe+8DYOrc8ZrBauICnS4QBTri1TQF 4qT4C/OsNx6SWItexhHQNO6LtblskZdoIUQmc0TMgkgw3embngjJkOLz5MHznCGEbyjz KUTBxSakEcya68W8Vy+38IZLuO+MSxA3956t09/ry4zf7+upqUnAWiAgyUX6c6/UDg3v E7Vq/5l6qTRruTBQpEy0hbZJrJhnSzALMSzGr3T6IgnlMHO3OHFFGoJx+gybZL7JuNMI EyJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=198O4iggAD6dtCY9fRm0QbqZEfL21vKHVnm4pG+NsMc=; b=CeVbY79yw0lr+QP898L3g3QK4f1sKbOZmZ40d0uQOfsoDA1irsgNPJpYtJdK5kjH4u 3mVD4DxDLqgCi5s0QqWgMJriyqwesUZbD5rQ/sKQEjbAQxL+Y6/YCtJM4V5wRq9qtBjU An9FfaAAwKWcw2k08/J+3VS13qYcRCta7BEt/bGLh4I7tcl+udPfSZ7hDLPe9I8Kf1GH EdZWuA51kr+r+A41qeGKj8aBhGlCt3yLqO9N9Zs3pSyiWSdcahcNXrKHs3zMkdIARDrM Ml7RPNVeUd/v32KWx0Ixt4BnSWiJQEXBWo8xAnX/7LsgLB11DmioS7nABrXoYtajqr3p KF5Q==
X-Gm-Message-State: AOUpUlHHGOxtrpmyO6+Pv47LnHJejXhW4e45QrqqG70TimciUW4nN+C6 u6phfRE+PKbL+S9NwowZ7aA=
X-Google-Smtp-Source: AAOMgpeYBDZHQUvOGnWFOquzff9ss+0GDGMZbcCguNrwr4xeMgwxCsTrJ42MHUDwupV2LRpV1u2lXQ==
X-Received: by 2002:a2e:8807:: with SMTP id x7-v6mr8471445ljh.98.1532028545342; Thu, 19 Jul 2018 12:29:05 -0700 (PDT)
Received: from [192.168.1.66] ([83.216.157.26]) by smtp.gmail.com with ESMTPSA id h7-v6sm1228376ljk.27.2018.07.19.12.29.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 19 Jul 2018 12:29:04 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <b90520f39bea4fc9a5bf22b011ec4ac0@rew09926dag03b.domain1.systemhost.net>
Date: Thu, 19 Jul 2018 20:29:03 +0100
Cc: cpaasch@apple.com, multipathtcp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC7D1FE4-4E78-400C-9EEB-21EA7165F28B@gmail.com>
References: <0dd5e48298ed4b4fb7344630abc794b7@rew09926dag03b.domain1.systemhost.net> <f64af1576d994d888a7b82fb75dc8318@rew09926dag03b.domain1.systemhost.net> <20180715201445.GU1471@MacBook-Pro-19.local> <b90520f39bea4fc9a5bf22b011ec4ac0@rew09926dag03b.domain1.systemhost.net>
To: philip.eardley@bt.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/R2dOkOxtqcdAE2GUSw8yY_l8chg>
Subject: Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 19 Jul 2018 19:29:09 -0000

Hi Phil,

Catching up on these comments, re this:

> On 18 Jul 2018, at 00:30, philip.eardley@bt.com wrote:
> 
> << Note that new subflows MUST NOT be established
>   (using the process documented in Section 3.2) until a Data Sequence
>   Signal (DSS) option has been successfully received across the path
>   (as documented in Section 3.3).>>
> In the case where A sends data first, then the MP-CAPABLE is sent instead of the DSS. Does the text quoted mean that new subflows are not allowed (until an actual DSS is sent) or are they allowed because DSS has kind of been inferred?

I think the text still holds. We need a DSS to be received (as a DATA ACK) in order to know the path is fully MPTCP capable.

Regards,
Alan

v2.23.0 | Report a Bug | By Email