Re: [multipathtcp] Summary and more

marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 04 September 2009 10:37 UTC

Return-Path: <marcelo@it.uc3m.es>
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 066C83A6A03 for <multipathtcp@core3.amsl.com>; Fri, 4 Sep 2009 03:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.557
X-Spam-Level:
X-Spam-Status: No, score=-6.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2NHSA2dq3rmH for <multipathtcp@core3.amsl.com>; Fri, 4 Sep 2009 03:37:42 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id EC0103A69FA for <multipathtcp@ietf.org>; Fri, 4 Sep 2009 03:37:41 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (wlap006.it.uc3m.es [163.117.139.189]) by smtp03.uc3m.es (Postfix) with ESMTP id 2FEF17F3772; Fri, 4 Sep 2009 12:35:27 +0200 (CEST)
Message-ID: <4AA0ED6E.1040601@it.uc3m.es>
Date: Fri, 04 Sep 2009 12:35:26 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Mark Handley <M.Handley@cs.ucl.ac.uk>
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> <84a612dd0909040331s4accd8d5qd488e945bee5f865@mail.gmail.com>
In-Reply-To: <84a612dd0909040331s4accd8d5qd488e945bee5f865@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16866.003
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:37:43 -0000

Mark Handley escribió:
> Is there a more recent version?  That one expired a while back.  Is it dead now?
>
>   
the draft is dead

> I agree there's a lot of overlap, but it isn't precisely the same
> problem.
how come is not the same problem?
I mean, what is the difference that you see?

>   If the draft is dead, do you have any problem with me
> re-using text from it, where appropriate?
>
>   
sure, no problem

Regards, marcelo

>  - 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
>>>
>>>
>>>       
>>     
>
>