Re: [tcpm] draft-ietf-tcpm-converters

<> Thu, 20 June 2019 05:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8F84312047F; Wed, 19 Jun 2019 22:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6FIPDaNtjHtz; Wed, 19 Jun 2019 22:19:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 43ABC120440; Wed, 19 Jun 2019 22:19:53 -0700 (PDT)
Received: from (unknown [xx.xx.xx.6]) by (ESMTP service) with ESMTP id 45TqrR2GJJz30cS; Thu, 20 Jun 2019 07:19:51 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) by (ESMTP service) with ESMTP id 45TqrR19Cdz1xp2; Thu, 20 Jun 2019 07:19:51 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM23.corporate.adroot.infra.ftgroup ([fe80::9108:27dc:3496:8db3%21]) with mapi id 14.03.0439.000; Thu, 20 Jun 2019 07:19:51 +0200
From: <>
To: "Scharf, Michael" <>
CC: " Extensions" <>, "" <>, "" <>
Thread-Topic: draft-ietf-tcpm-converters
Thread-Index: AdUkHWlwWAVA12efRnCFBwL9n6nkWAArZURgAAJqz1QAlKNUYA==
Date: Thu, 20 Jun 2019 05:19:49 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EAA9B66@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <>, <787AE7BB302AE849A7480A190F8B93302EAA7AD7@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302EAA9B66OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [tcpm] draft-ietf-tcpm-converters
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Jun 2019 05:19:57 -0000

Hi Michael,

FWIW, these changes are now implemented in -08. We also fixed some nits (thanks Adi).

Looking forward the WGLC.

Olivier & Med

De : Scharf, Michael []
Envoyé : lundi 17 juin 2019 08:20
Cc : Extensions
Objet : Re: draft-ietf-tcpm-converters

Hi Med,

The proposed text would address my concern.



Gesendet: Montag, 17. Juni 2019 08:11
An: Scharf, Michael<>;<>
Cc: Extensions<>
Betreff: RE: draft-ietf-tcpm-converters

Hi Michael,

Please see inline.


De : Scharf, Michael []
Envoyé : dimanche 16 juin 2019 10:28
À :
Cc : Extensions
Objet : draft-ietf-tcpm-converters

Hi all,

In preparation of a planned WGLC (heads-up to all) I have read draft-ietf-tcpm-converters-07 again.

As a result, I have two further questions (as individual contributor, if that matters). Ideally I should have already noted when reading the document last time...

1/ The handling of the three-way handshake is well specified in the document, and this is what the convert protocol is about. Yet, I really wonder if some words are needed on what the endpoints can expect from the converter once the connection is established? In section 1, the document specifies that the converters "relay control messages and data between the client and the server". While I believe most of us have an idea what this means, I wonder if it is formally clear what that implies for acknowledgements and connection management (e.g., FIN, RST, keepalives). For instance, if the client receives an ACK for a segment with FIN flag, can the client assume that the server has received a FIN from the converter and that the converter has received an ACK from the Server for that FIN? My understanding is that a converter is not required to guarantee these end-to-end semantics. If that is true, wouldn't it be better to be explicit about that? This may also relate to what happens in case of failures inside the converter.

[Med] We can add some details if you thnk this is useful. A first attempt to address your comment is available at: We will further tweak the text and release a new revision soon.

2/ The document uses the term "TCP extended header", e.g. on page 10 and 23. As far as I know, we typically don't use this term for the standard TCP header, either with or without options. draft-ietf-tcpm-tcp-edo uses a similar term, but as far as I understand the converter protocol does not rely on EDO. Wouldn't it be more reasonable to replace "TCP extended header" by a more common term, e.g. by "TCP header"?

[Med] Will be fixed.