Re: [multipathtcp] FW: New Version Notification for draft-ford-mptcp-multiaddressed-02

Scott Brim <scott.brim@gmail.com> Thu, 05 November 2009 04:08 UTC

Return-Path: <scott.brim@gmail.com>
X-Original-To: multipathtcp@core3.amsl.com
Delivered-To: multipathtcp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DF0C3A67E6 for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 20:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lE+BeJwzlxnC for <multipathtcp@core3.amsl.com>; Wed, 4 Nov 2009 20:08:45 -0800 (PST)
Received: from mail-yw0-f183.google.com (mail-yw0-f183.google.com [209.85.211.183]) by core3.amsl.com (Postfix) with ESMTP id 768B63A67A3 for <multipathtcp@ietf.org>; Wed, 4 Nov 2009 20:08:45 -0800 (PST)
Received: by ywh13 with SMTP id 13so8231353ywh.29 for <multipathtcp@ietf.org>; Wed, 04 Nov 2009 20:09:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=IV1AMGo/BRg/yShHdY8GEGfeTRI7sjtD684LnZ4svlo=; b=iBbHzlRdVON7VlFvb77luP+HcI9JiBLeBaC8wwppccfKP78dNZ3AHIrppFzN68gew2 3Lbt8LZOHOPDwp2VfhFVya3a99SjCDNEnviavC0OVshikQU341iJzdRZzGzbOAa1csXL 7EETn+y8eLOXpQDCImzEx3KM/vURNcMCZ1c3g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=KZ9h/V5phz6zI3UE3St6wlSyDdgshNSbskpjdv7vh5QTewIfNbVAL86K2+qQMyNXJe eu64rtO0v9j4N/XDN6fKmWVwrOVOAbqF5b9MuM37GW+/B628mVXPId8gzJmnUdo2iJxy XlaYnPG1zTPTLm8pauAD59NhGlkPRSHEbEnhI=
Received: by 10.150.90.17 with SMTP id n17mr4330780ybb.71.1257394143470; Wed, 04 Nov 2009 20:09:03 -0800 (PST)
Received: from 12-187-221-19.att-inc.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id 6sm632934ywc.9.2009.11.04.20.09.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 04 Nov 2009 20:09:02 -0800 (PST)
Message-ID: <4AF24FDB.6000601@gmail.com>
Date: Wed, 04 Nov 2009 20:08:59 -0800
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
References: <2181C5F19DD0254692452BFF3EAF1D6808B826E2@rsys005a.comm.ad.roke.co.uk> <20091027221853.GO78898@verdi>
In-Reply-To: <20091027221853.GO78898@verdi>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] FW: New Version Notification for draft-ford-mptcp-multiaddressed-02
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 05 Nov 2009 04:08:46 -0000

John Leslie allegedly wrote on 10/27/2009 3:18 PM:
> Ford, Alan <alan.ford@roke.co.uk> wrote:
>> We now have a new version of the MPTCP protocol draft available, which
>> will be presented in Hiroshima.
>>
>> http://www.ietf.org/id/draft-ford-mptcp-multiaddressed-02.txt
> 
>    Very nicely done!
> 
>    I stumbled over the term "TCP Session" in section 1.3. I'm not sure
> whether there might be a better name for that concept, but in any case
> I'd recommend a "glossary" entry for whatever term is used.

Agree.  In some contexts a "session" can involve multiple, possibly only
loosely coordinated, transport "connections" between different
applications..