[multipathtcp] RFC 8041 on Use Cases and Operational Experience with Multipath TCP

rfc-editor@rfc-editor.org Thu, 12 January 2017 23:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F291129434; Thu, 12 Jan 2017 15:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 WIY5ZzaSDh7N; Thu, 12 Jan 2017 15:33:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6080C1294EA; Thu, 12 Jan 2017 15:33:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2A23AB8100D; Thu, 12 Jan 2017 15:33:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170112233350.2A23AB8100D@rfc-editor.org>
Date: Thu, 12 Jan 2017 15:33:50 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/S00H3LZlPJivQ0EsD1WUKQilLZQ>
Cc: multipathtcp@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [multipathtcp] RFC 8041 on Use Cases and Operational Experience with Multipath TCP
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 12 Jan 2017 23:33:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8041

        Title:      Use Cases and Operational Experience 
                    with Multipath TCP 
        Author:     O. Bonaventure, C. Paasch, G. Detal
        Status:     Informational
        Stream:     IETF
        Date:       January 2017
        Mailbox:    Olivier.Bonaventure@uclouvain.be, 
                    cpaasch@apple.com, 
                    gregory.detal@tessares.net
        Pages:      30
        Characters: 75260
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mptcp-experience-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8041

        DOI:        10.17487/RFC8041

This document discusses both use cases and operational experience
with Multipath TCP (MPTCP) in real networks.  It lists several
prominent use cases where Multipath TCP has been considered and is
being used.  It also gives insight to some heuristics and decisions
that have helped to realize these use cases and suggests possible
improvements.

This document is a product of the Multipath TCP Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC