Re: [tcpm] WGLC comments addressed in draft-ietf-tcpm-converters-09?

<mohamed.boucadair@orange.com> Fri, 27 September 2019 08:55 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B973312009C; Fri, 27 Sep 2019 01:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 YymzN_aDAw3X; Fri, 27 Sep 2019 01:55:57 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8651512004C; Fri, 27 Sep 2019 01:55:57 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 46fly411Lhzyh3; Fri, 27 Sep 2019 10:55:56 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 46fly403lzzDq7l; Fri, 27 Sep 2019 10:55:56 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM24.corporate.adroot.infra.ftgroup ([fe80::b43f:9973:861e:42af%21]) with mapi id 14.03.0468.000; Fri, 27 Sep 2019 10:55:55 +0200
From: <mohamed.boucadair@orange.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "Michael.Scharf@hs-esslingen.de" <Michael.Scharf@hs-esslingen.de>, "tcpm@ietf.org" <tcpm@ietf.org>
CC: "tcpm-chairs@ietf.org" <tcpm-chairs@ietf.org>
Thread-Topic: WGLC comments addressed in draft-ietf-tcpm-converters-09?
Thread-Index: AdVAY18GkuWfECVqQWaaLZInx1aQaQHJQcVQAAH6llAALWUTAAP9U2QAArkhrTAAONYfcAAftv/AAm5pb3AAHad1QAGXvS0g
Date: Fri, 27 Sep 2019 08:55:55 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031327733@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <6EC6417807D9754DA64F3087E2E2E03E2D3C0FC8@rznt8114.rznt.rzdir.fht-esslingen.de> <CWXP123MB2583E113996E40BCC57F62FBEBDF0@CWXP123MB2583.GBRP123.PROD.OUTLOOK.COM> <787AE7BB302AE849A7480A190F8B9330312ECAD3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <787AE7BB302AE849A7480A190F8B9330312F9DD4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <LNXP123MB25870E38482B5A045323ABEBEBAA0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <787AE7BB302AE849A7480A190F8B93303130B945@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <LNXP123MB2587A9B7D20B9BB53997D218EBBB0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <787AE7BB302AE849A7480A190F8B93303131A663@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <LNXP123MB2587A40F62BB6F4941036B4FEB8E0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <787AE7BB302AE849A7480A190F8B933031323026@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933031323026@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/7tJOL04cozyjm1_js_b2QjQ4FCo>
Subject: Re: [tcpm] WGLC comments addressed in draft-ietf-tcpm-converters-09?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Sep 2019 08:56:00 -0000

Hi Phil, 

We submitted -11 with this NEW text to address your comment: 

   The use of a Transport Converter means that there is no end-to-end
   transport connection between the client and server.  This could
   potentially create problems in some scenarios such as those discussed
   in Section 4 of [RFC3135].  Some of these problems may not be
   applicable, for example, a Transport Converter can inform a client by
   means of Network Failure (65) or Destination Unreachable (97) error
   messages (Section 4.2.8) that it encounters a failure problem; the
   client can react accordingly.  An endpoint, or its network
   administrator, can assess the benefit provided by the Transport
   Converter service versus the risk.  This is one reason why the
   Transport Converter functionality has to be explicitly requested by
   an endpoint.

Cheers,
Med

> -----Message d'origine-----
> De : tcpm [mailto:tcpm-bounces@ietf.org] De la part de
> mohamed.boucadair@orange.com
> Envoyé : jeudi 19 septembre 2019 08:20
> À : philip.eardley@bt.com; Michael.Scharf@hs-esslingen.de; tcpm@ietf.org
> Cc : tcpm-chairs@ietf.org
> Objet : Re: [tcpm] WGLC comments addressed in draft-ietf-tcpm-converters-
> 09?
> 
> Hi Phil,
> 
> Will add these notes. Thanks.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : philip.eardley@bt.com [mailto:philip.eardley@bt.com]
> > Envoyé : mercredi 18 septembre 2019 18:12
> > À : BOUCADAIR Mohamed TGI/OLN; Michael.Scharf@hs-esslingen.de;
> > tcpm@ietf.org
> > Cc : tcpm-chairs@ietf.org
> > Objet : RE: WGLC comments addressed in draft-ietf-tcpm-converters-09?
> >
> > A specific point
> >
> > -----Original Message-----
> >
> > >
> > > Note that the use of a Transport Converter means that there is no
> > > end-to- end transport connection between the Client and Server.
> >
> > [Med] Will add this.
> >
> >  This could
> > > potentially create problems in some scenarios, for example a failure
> > > mode of the Converter where data was correctly received by the
> > > converter from the client, but then it failed to forward the data on
> to
> > the server.
> >
> > >[Med] This is not an issue for the Converter because it can inform the
> > client by means of Network Failure (65) or Destination Unreachable (97).
> > The Client can react to this error. This is not possible with PEPs.
> >
> > [phil] It would be good to point this out.
> > But note this doesn't work if the Converter can't send these msgs. The
> > point is that the potential failure modes are slightly different for the
> > Converter case vs the e2e transport connection.
> >
> >
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm