Re: [multipathtcp] Summary and more

Mark Handley <M.Handley@cs.ucl.ac.uk> Fri, 04 September 2009 10:38 UTC

Return-Path: <mark.j.handley@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 7F3CF3A6A01 for <multipathtcp@core3.amsl.com>; Fri, 4 Sep 2009 03:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.86
X-Spam-Level:
X-Spam-Status: No, score=-1.86 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 V+85aln9pVPG for <multipathtcp@core3.amsl.com>; Fri, 4 Sep 2009 03:38:41 -0700 (PDT)
Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by core3.amsl.com (Postfix) with ESMTP id 7C34C3A65A6 for <multipathtcp@ietf.org>; Fri, 4 Sep 2009 03:38:41 -0700 (PDT)
Received: by bwz19 with SMTP id 19so153974bwz.37 for <multipathtcp@ietf.org>; Fri, 04 Sep 2009 03:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=vCyXBQOrb/X7t1FAtzBsrez/GT4DKQf+T8h/RPzVuDs=; b=VSohxMfrxftmshBeL9MfDs+G/tao+fzPc3RY9eoU6xDxT5Jq6N5M+2NrTrvoLqersp Wq6GImaC1rkxghnT9M16DCF4SoA7ID1hpMiIOxgWoVnLRDU8NdAnkskyj81UVVlwUmG+ KOWx8UpTGYb5dmZ9qVpLoUz+2OhrZapVzPc4A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=iXNz+2aicAw6pQQ3OIovts5no3T+Q7HA5wP4+uKc8DQbIcqI0pIk67KQRUxgREdq3/ toD0BKjNSY5ZkHQAHhdyDT4qyu7nk/JcrGVCOBkdqAwmirgfQSDMjBHoHHbcAZ8XNyWv NdgRBrZvZfUaCyhUZ0vob9ANkgH0p6ffZvgfY=
MIME-Version: 1.0
Sender: mark.j.handley@gmail.com
Received: by 10.223.77.130 with SMTP id g2mr4555784fak.35.1252060291189; Fri, 04 Sep 2009 03:31:31 -0700 (PDT)
In-Reply-To: <4AA0E8D5.5010708@it.uc3m.es>
References: <2181C5F19DD0254692452BFF3EAF1D6808590891@rsys005a.comm.ad.roke.co.uk> <08543492-A65F-46A3-9217-55CF92E293D4@nokia.com> <20090902141815.GF8532@verdi> <65E7C1F2-19C7-4CC9-AE49-CB6B9ABBEE92@nokia.com> <85CFAF50-F886-400B-9975-2711A14F95C6@cs.ucl.ac.uk> <4AA0D928.4060909@it.uc3m.es> <E5F6DBDF-A91F-4FC0-8B76-CFE4F2BD976D@cs.ucl.ac.uk> <4AA0E165.5060502@it.uc3m.es> <84a612dd0909040312jf781199sac2df995f5f62e7@mail.gmail.com> <4AA0E8D5.5010708@it.uc3m.es>
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
Date: Fri, 04 Sep 2009 11:31:11 +0100
X-Google-Sender-Auth: 97adf001ddcbc8a9
Message-ID: <84a612dd0909040331s4accd8d5qd488e945bee5f865@mail.gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Multipath TCP Mailing List <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] Summary and more
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: Fri, 04 Sep 2009 10:38:42 -0000

Is there a more recent version?  That one expired a while back.  Is it dead now?

I agree there's a lot of overlap, but it isn't precisely the same
problem.  If the draft is dead, do you have any problem with me
re-using text from it, where appropriate?

 - Mark

2009/9/4 marcelo bagnulo braun <marcelo@it.uc3m.es>:
> Hi Mark,
>
> I think such a document exists, with proposed solutions as well.
>
> please see
>
> http://tools.ietf.org/html/draft-ietf-shim6-ingress-filtering-00
>
> Regards, marcelo
>
>
>
> Mark Handley escribió:
>>
>> Folks,
>>
>> It's clear from the ongoing discussion that we haven't yet documented
>> the options and issues for routing of outgoing packets with multi-path
>> TCP sufficiently.  I propose that I write a short document summarizing
>> the issues on this topic.  I expect this will become part of the
>> architecture document of the working group, but for now the important
>> thing is to gather the discussion together in one place so we can see
>> what do understand, what we don't understand,  and how host
>> requirements might change (if at all).
>>
>> Can I request that some of the energy currently going into this email
>> exchange be put into reviewing the document when I've written it, so
>> you can tell me what I've got wrong!
>>
>>  - Mark
>>
>>
>
>