RFC 8803 on 0-RTT TCP Convert Protocol

rfc-editor@rfc-editor.org Tue, 28 July 2020 23:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2F013A0AAC; Tue, 28 Jul 2020 16:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FZm1JH7CFvp4; Tue, 28 Jul 2020 16:22:03 -0700 (PDT)
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 57F3E3A0A9A; Tue, 28 Jul 2020 16:22:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BB4F7F4073D; Tue, 28 Jul 2020 16:21:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4MDMgb24gMC1SVFQgVENQIENvbnZlcnQgUHJvdG9jb2w=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpm@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200728232137.BB4F7F4073D@rfc-editor.org>
Date: Tue, 28 Jul 2020 16:21:37 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gcAeBsNmfcnko2yx7mJ9dxdsVHI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2020 23:22:05 -0000

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

        
        RFC 8803

        Title:      0-RTT TCP Convert Protocol 
        Author:     O. Bonaventure, Ed.,
                    M. Boucadair, Ed.,
                    S. Gundavelli,
                    S. Seo,
                    B. Hesmans
        Status:     Experimental
        Stream:     IETF
        Date:       July 2020
        Mailbox:    Olivier.Bonaventure@tessares.net, 
                    mohamed.boucadair@orange.com, 
                    sgundave@cisco.com,
                    sh.seo@kt.com, 
                    Benjamin.Hesmans@tessares.net
        Pages:      47
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpm-converters-19.txt

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

        DOI:        10.17487/RFC8803

This document specifies an application proxy, called Transport
Converter, to assist the deployment of TCP extensions such as
Multipath TCP. A Transport Converter may provide conversion service
for one or more TCP extensions. The conversion service is provided by
means of the 0-RTT TCP Convert Protocol (Convert).

This protocol provides 0-RTT (Zero Round-Trip Time) conversion
service since no extra delay is induced by the protocol compared to
connections that are not proxied. Also, the Convert Protocol does not
require any encapsulation (no tunnels whatsoever).

This specification assumes an explicit model, where the Transport
Converter is explicitly configured on hosts. As a sample
applicability use case, this document specifies how the Convert
Protocol applies for Multipath TCP.

This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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