IETF Logo Mail Archive

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

"Pal Martinsen (palmarti)" <palmarti@cisco.com> Thu, 19 March 2015 20:27 UTC

Return-Path: <palmarti@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 414AD1A905F for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 13:27:52 -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 zlcdnjqWJnCQ for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 13:27:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32DBB1A9064 for <spud@ietf.org>; Thu, 19 Mar 2015 13:27:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1726; q=dns/txt; s=iport; t=1426796871; x=1428006471; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WJzHZNvGEXBeGrPVc0pZOpnUBZ2V7Q/rR8t4yLfndtY=; b=Ojs6loG1/FX0CFI5ttB9/6TY/GvehFC0mFAB6XgqtwteLxV9DRHyDKEm zpKt2BKraVlhJLetXL+Z0rTG6JNjn0ioTA94KVa3xF6K0I0cRC9j3Jkxp vzy7DzBU+OuQeOVul70OVv1CyvWdf/yNaSrPHlXieCLkjahN0nldpi43u c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQA5MAtV/40NJK1cgwaBIAwEgwnJGAIcgStMAQEBAQEBfYQPAQEBAwEjEUUFCwIBCBgCAiYCAgIwFRACBA4FiCcIsjacBQEBAQEBAQEBAQEBAQEBAQEBAQEBAReBIYl2hHEHgmgvgRYBBIYXijWJbZQoIoNub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,432,1422921600"; d="scan'208";a="405030994"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-7.cisco.com with ESMTP; 19 Mar 2015 20:27:50 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t2JKRor6007517 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <spud@ietf.org>; Thu, 19 Mar 2015 20:27:50 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.40]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Thu, 19 Mar 2015 15:27:50 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Thread-Topic: [Spud] Multipath UDP as a SPUD usecase?
Thread-Index: AQHQYmb0I+k+DE334U20oTQe7OOZXJ0klVoA
Date: Thu, 19 Mar 2015 20:27:49 +0000
Message-ID: <BEA46C74-F084-4BE6-9E98-A50753A4A6CD@cisco.com>
References: <F817BF6D-974E-412E-B4CE-CDBB61F1DC6E@cisco.com>
In-Reply-To: <F817BF6D-974E-412E-B4CE-CDBB61F1DC6E@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.223.36]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5EF7E0714FE77546B7293954E04A09E3@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/zYdG33oVIQtKIcz7yuGwSOwTCPA>
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:27:52 -0000

> On 19 Mar 2015, at 18:05, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:
> 
> On 3/19/15, 9:57 AM, "Pal Martinsen (palmarti)" <palmarti@cisco.com> wrote:
> 
>> Another potential use-case SPUD could help solve is multipath UDP. I do not have enough insight regarding bits on the wire to accomplish this but to me it would be a compelling usecase.
>> 
>> It might:
>> - Provide easy “media mobility” when a device switches network.
>> - Better throughput (Not sure about this..)
>> 
>> Since we already have this for TCP and there is a multi-path RTP draft there seems to be some interest in solving this.
> 
> 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?

.-.
Pål-Erik


> -- 
> Joe Hildebrand
> 
> 
>

v2.8.7 | Report a Bug | By Email