IETF Logo Mail Archive

[multipathtcp] charter discussion

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 31 March 2017 15:53 UTC

Return-Path: <sarikaya2012@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 CDCB51294C0 for <multipathtcp@ietfa.amsl.com>; Fri, 31 Mar 2017 08:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.428
X-Spam-Level:
X-Spam-Status: No, score=-1.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 wtEYbyOgOBcf for <multipathtcp@ietfa.amsl.com>; Fri, 31 Mar 2017 08:53:14 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 87C7F12998D for <multipathtcp@ietf.org>; Fri, 31 Mar 2017 08:53:02 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id v203so473187wmg.0 for <multipathtcp@ietf.org>; Fri, 31 Mar 2017 08:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:cc; bh=EJiAmvAicGAUhPsj9DkLpjCms/mIZvYBOWKTdfvNvww=; b=QXRKO1F8u1zRivMN5KDjGG+85yv6mzX/UiDY0NXGOG21TfNVq0HpgDmSgGK1Rh+HIk mTGKJjn54CHQT8am8rreT4PGgSFGWBGHILKxqdXXhMooB6mYJaBAO3ijZkDR8NiggA/n v6tZ1Pz+XjIyFZf/wOpYMYrOSHHXmK1jX2JRnJbFLHUuPBuUSnDvf9YXc2BWvNDNDB6B IG/wzWoNIuAoQAzNfAzxTa7kWMSBurs9SbglsTOEPoXnlvlC957QilJqy9MnyJsWhKUZ WiPGBCB+lAmc9OWrU7gT/VPwITWQRDk2Ep5nZp5qA+6xhVnSzopD59wV8JjMKmj8yMMU 5VOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:cc; bh=EJiAmvAicGAUhPsj9DkLpjCms/mIZvYBOWKTdfvNvww=; b=iyxRAU6fB7S6j/5KM0prDBwqdwiUmlVu/CnisYj8hpN9IaLYM/DbsyxaPnE3CG7DBl iijAWiiSS20KLq11R1qwgwvNLKCvPEOC4V5kSTrq7P6Wr35hX5Jh8DcokMVzH9QPwiVc 598KnNRWCo1cLXnt9GUOqwXduKSeyuAjC+6kED+sDSEjzFrDMlRNgJvu28X0ZRCW78WP ptXIlFSxjBrnhJbN+OuerlknHrIhbx03MBECqtG74ANXxbhMD6694TPwSYJpYOHxWEbD WERX0FoA8FqPQ6wUIWatfn2rwxpv3NtOiepsCWg5x574eAI3CW5PTbE9FCBYVut4JuCo 1RMg==
X-Gm-Message-State: AFeK/H33N+ogqvfqiv0ZiAL36/q5SVi9wdyS5gBFHuNiiKmWaF4W9qXeswAyjVNZTalDC3lMrkbQ4zg/QuYp4Q==
X-Received: by 10.28.168.130 with SMTP id r124mt4324661wme.34.1490975581025; Fri, 31 Mar 2017 08:53:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.169.228 with HTTP; Fri, 31 Mar 2017 08:53:00 -0700 (PDT)
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 31 Mar 2017 10:53:00 -0500
Message-ID: <CAC8QAcewg+z+xcJ80yrPPt7KPuvMye-aNzOuHKCjsJspocQKYA@mail.gmail.com>
Cc: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>, Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary="001a114cc7aee06c97054c08cd6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/UOqzvR9CsieepTkCZR-cVyq3OSc>
Subject: [multipathtcp] charter discussion
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: Fri, 31 Mar 2017 15:53:16 -0000

Hi all,

Regarding the charter discussions that happened at the mptcp session on
Thursday March 30, I asked a question but I could not understand the
answer, let me ask it again.

In chairs slides page 12, TCP SYN shown in Option 1 and Option 2 actually
were different although the slides seems to show that they are the same.

In Option 1, if the proxy sends TCP SYN than is it OK in a conversation the
destination does not know who the source is?

In Option 2, if TCP SYN sent was the original TCP SYN from the source then

how come the TCP-ACK goes through the proxy?
A node sending a packet without its address as source address means it is
router, right?

Regards,

Behcet




>

v2.23.0 | Report a Bug | By Email