IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 19 March 2015 17:05 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 803171A1EFF for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 10:05:58 -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 Mm1KlOQr72WW for <spud@ietfa.amsl.com>; Thu, 19 Mar 2015 10:05:57 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07CEB1A1AFC for <spud@ietf.org>; Thu, 19 Mar 2015 10:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1282; q=dns/txt; s=iport; t=1426784753; x=1427994353; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=zv2dEMdlbJIffx13po5Rs/nMP8spD8mUuwuonBsPzcI=; b=CEgKIYE7U7016YnyVCnZHnEvGi/BWxWjAEyIJHcvQ1o1SC2pYY9gV/hX ZmCDSB0v5esvbXSGzWvcnpVSUPbN+lyQawJgcm+XJy+0Nhjs0TEZg6OFy 59z+XjRcPBmd95QMR2caA9Qx35LR+yErimboo7qld9/2pL+0tbMzCc8TZ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BUCgBVAQtV/4UNJK1cgwaBLASDCcBfiC8egTBMAQEBAQEBfYQQAgQjEVcBCBoCJgIEMBUSBAESiC+yMJwAAQEBAQEBBAEBAQEBAQEBGoEhiXaEPoMiL4EWBYYVijSJbZQoIoNub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,430,1422921600"; d="scan'208";a="405015925"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-3.cisco.com with ESMTP; 19 Mar 2015 17:05:52 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t2JH5q7Q002956 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <spud@ietf.org>; Thu, 19 Mar 2015 17:05:52 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.80]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0195.001; Thu, 19 Mar 2015 12:05:52 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>, "spud@ietf.org" <spud@ietf.org>
Thread-Topic: [Spud] Multipath UDP as a SPUD usecase?
Thread-Index: AQHQYmb0I+k+DE334U20oTQe7OOZXA==
Date: Thu, 19 Mar 2015 17:05:51 +0000
Message-ID: <F817BF6D-974E-412E-B4CE-CDBB61F1DC6E@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.129.24.156]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E5FDB2022B773148AF2ACC8E54094955@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/eG8Zcq3bY8zwi77Hvrqw2ejjOtg>
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 17:05:58 -0000

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.

-- 
Joe Hildebrand

v2.8.7 | Report a Bug | By Email