IETF Logo Mail Archive

Re: [Spud] Multipath UDP as a SPUD usecase?

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 19 March 2015 20:32 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D03281A9072 for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 13:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 sO_7WDKEerKK for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 13:32:22 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A71451A9067 for <spud@ietf.org>; Thu, 19 Mar 2015 13:32:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1224; q=dns/txt; s=iport; t=1426797143; x=1428006743; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eM3SbRBTUhUU5wXL7GvolktQmj8rzK4n10XrjqjDRq0=; b=aofbsZvXmQm88x8y+nV2DdmZuZh8A+2t45VKc0LA1p7jmJVU3BTX/XZ5 yj4hFQJCfHlkJ7i67kxvmwLzQ39pGxn35TNwzjS9Sk+xULsWEf+K93Qq2 87b5it0JnOdguFFfxsVlTKz0ZirigH6QxBQw1SR0arUqVH9F4cc30+pX4 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ApDwAPMQtV/4wNJK1cgwaBIAwEgwnAaYgvAhyBK0wBAQEBAQF9hBABAQQjEUUQAgEIGgImAgICMBUQAgQOBYgvsjecBAEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIYl2hHEHgmgvgRYBBJBMiW2UKCKDbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,432,1422921600"; d="scan'208";a="405144150"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-4.cisco.com with ESMTP; 19 Mar 2015 20:32:22 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t2JKWMBb018855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <spud@ietf.org>; Thu, 19 Mar 2015 20:32:22 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.80]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Thu, 19 Mar 2015 15:32:21 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
Thread-Topic: [Spud] Multipath UDP as a SPUD usecase?
Thread-Index: AQHQYmb0I+k+DE334U20oTQe7OOZXJ0klVoA//+croA=
Date: Thu, 19 Mar 2015 20:32:21 +0000
Message-ID: <A20D5BF8-E33A-4814-8E1A-953B9F2D9E8B@cisco.com>
References: <F817BF6D-974E-412E-B4CE-CDBB61F1DC6E@cisco.com> <BEA46C74-F084-4BE6-9E98-A50753A4A6CD@cisco.com>
In-Reply-To: <BEA46C74-F084-4BE6-9E98-A50753A4A6CD@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/15.8.1.150311
x-originating-ip: [10.24.165.130]
Content-Type: text/plain; charset="utf-8"
Content-ID: <09EEAF712EBC26429422D629EB56274E@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/7HZ-ytv90Hn0nt21qUKHIyXQkNE>
Cc: "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] Multipath UDP as a SPUD usecase?
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 20:32:24 -0000

On 3/19/15, 2:27 PM, "Pal Martinsen (palmarti)" <palmarti@cisco.com> wrote:

>> 
>> This may be mostly an issue for the t' layer (t' = "transport prime"; the transport semantics inside of SPUD), particularly since we're leaning toward tube ID's being bound to a 5-tuple.  The t' code would create a new tube (probably with a new tube ID) for each address pair.  In the case of mptcp’, every time mptcp would have sent a new SYN, mptcp' would send a SPUD OPEN.
>> 
>That make sense. As long as we not decide on anythin that make this hard/impossible I am happy.Not even sure if this belongs to the core spec, maybe better suited as a extension?

I think we'll learn a lot more as we get a mptcp' implementation started.  My gut feel is that we just need a extra paragraph in the spec that says what the scope of a tube ID is, and when to start a new tube.

-- 
Joe Hildebrand

v2.8.7 | Report a Bug | By Email