[multipathtcp] I-D Action:draft-ietf-mptcp-architecture-04.txt

Internet-Drafts@ietf.org Tue, 11 January 2011 10:45 UTC

Return-Path: <Internet-Drafts@ietf.org>
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 B401D28C122; Tue, 11 Jan 2011 02:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level:
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 i2q90iif626I; Tue, 11 Jan 2011 02:45:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD17A28C114; Tue, 11 Jan 2011 02:45:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110111104501.25338.6182.idtracker@localhost>
Date: Tue, 11 Jan 2011 02:45:01 -0800
Cc: multipathtcp@ietf.org
Subject: [multipathtcp] I-D Action:draft-ietf-mptcp-architecture-04.txt
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: Tue, 11 Jan 2011 10:45:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multipath TCP Working Group of the IETF.


	Title           : Architectural Guidelines for Multipath TCP Development
	Author(s)       : A. Ford, et al.
	Filename        : draft-ietf-mptcp-architecture-04.txt
	Pages           : 28
	Date            : 2011-01-11

Hosts are often connected by multiple paths, but TCP restricts
communications to a single path per transport connection.  Resource
usage within the network would be more efficient were these multiple
paths able to be used concurrently.  This should enhance user
experience through improved resilience to network failure and higher
throughput.

This document outlines architectural guidelines for the development
of a Multipath Transport Protocol, with references to how these
architectural components come together in the development of a
Multipath TCP protocol.  This document lists certain high level
design decisions that provide foundations for the design of the MPTCP
protocol, based upon these architectural requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mptcp-architecture-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mptcp-architecture-04.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-mptcp-architecture-04.txt>