[Banana] FW: New Version Notification for draft-zuo-banana-mptcp-integration-00.txt

"Zuojing (2012 Laboratories)" <jing.zuo@huawei.com> Fri, 09 June 2017 07:52 UTC

Return-Path: <jing.zuo@huawei.com>
X-Original-To: banana@ietfa.amsl.com
Delivered-To: banana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69077129534 for <banana@ietfa.amsl.com>; Fri, 9 Jun 2017 00:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kmaQxW2zXW7z for <banana@ietfa.amsl.com>; Fri, 9 Jun 2017 00:51:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 746F9129526 for <banana@ietf.org>; Fri, 9 Jun 2017 00:51:58 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DIE44850; Fri, 09 Jun 2017 07:51:57 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 9 Jun 2017 08:51:56 +0100
Received: from DGGEMM508-MBX.china.huawei.com ([169.254.2.209]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Fri, 9 Jun 2017 15:51:32 +0800
From: "Zuojing (2012 Laboratories)" <jing.zuo@huawei.com>
To: "banana@ietf.org" <banana@ietf.org>
Thread-Topic: New Version Notification for draft-zuo-banana-mptcp-integration-00.txt
Thread-Index: AQHS4DQ71ibvJu/qJkaaiwHZwehz6aIcKWOg
Date: Fri, 09 Jun 2017 07:51:31 +0000
Message-ID: <4AD902A48032F745A3D7866E6CAE8CB0655981C5@dggemm508-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.74.162.113]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.593A539D.006C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.209, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 032586b7964586c20a379a30685b6bf9
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/Pjk78Gq7a78hfgL0_-4b4X8Ifig>
Subject: [Banana] FW: New Version Notification for draft-zuo-banana-mptcp-integration-00.txt
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Bandwidth Aggregation for interNet Access: Discussion of bandwidth aggregation solutions based on IETF technologies." <banana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/banana>, <mailto:banana-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/banana/>
List-Post: <mailto:banana@ietf.org>
List-Help: <mailto:banana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/banana>, <mailto:banana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jun 2017 07:52:00 -0000

Dear All,

As a follow up of the discussion we carried out on this mailing list (https://mailarchive.ietf.org/arch/msg/banana/rgItU_-OM_-FYFJMtFD12Pnj68w), we posted a draft on the “Integration of Bonding Tunnels and MPTCP” which specifies the extensions for tunnel bonding protocols to realize integrative deployment of tunnel boding solutions and MPTCP. 

The main goal of the integration is to make use of advantages of both technologies. As we know, MPTCP excels at conducting TCP traffic since its flow/congestion control scheme have been well developed while tunnel bonding protocols support not only TCP traffic but also UDP traffic.
 

More details are described in the draft. Comments are welcome. 

Kind regards,
Jing



-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, June 08, 2017 4:49 PM
To: Cornelius Heidemann; Geng Liang; Liang Geng; Zuojing (2012 Laboratories); Vero Zheng; Nicolai Leymann
Subject: New Version Notification for draft-zuo-banana-mptcp-integration-00.txt


A new version of I-D, draft-zuo-banana-mptcp-integration-00.txt
has been successfully submitted by Jing Zuo and posted to the IETF repository.

Name:		draft-zuo-banana-mptcp-integration
Revision:	00
Title:		Integration of Bonding Tunnels and MPTCP
Document date:	2017-06-08
Group:		Individual Submission
Pages:		12
URL:            https://www.ietf.org/internet-drafts/draft-zuo-banana-mptcp-integration-00.txt
Status:         https://datatracker.ietf.org/doc/draft-zuo-banana-mptcp-integration/
Htmlized:       https://tools.ietf.org/html/draft-zuo-banana-mptcp-integration-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-zuo-banana-mptcp-integration-00


Abstract:
   BANdwidth Aggregation for interNet Access (BANANA) based on tunnel
   bonding protocols and Multipath TCP (MPTCP) are two different
   technology suites that offer subscribers with higher bandwidth and
   reliability. MPTCP excels at conducting TCP traffic since its
   flow/congestion control scheme has been well developed while tunnel
   bonding protocols support not only TCP traffic but also UDP traffic.
   The integration of the two kinds of technologies can be considered to
   make use of advantages of both. Moreover, extensions made to the
   tunnel bonding protocols can simplify the MPTCP stack and keep it
   intact. This document specifies the extensions for tunnel bonding
   protocols to realize integrative deployment of tunnel bonding
   solutions and MPTCP.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat