IETF Logo Mail Archive

Re: [Int-dir] [Last-Call] Intdir telechat review of draft-ietf-masque-connect-ip-10

"touch@strayalpha.com" <touch@strayalpha.com> Thu, 20 April 2023 02:30 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF972C13736E; Wed, 19 Apr 2023 19:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.316
X-Spam-Level:
X-Spam-Status: No, score=-1.316 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gN_wzwKnNVs; Wed, 19 Apr 2023 19:30:30 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6315FC16B5C0; Wed, 19 Apr 2023 19:30:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+lziFa/Q3NLnWJMw0c9KK3f39olsKOY2MTXvmxFmvtA=; b=21NaCfGtr+NgdLDebfh8I1fU42 b4qes8SInQdNHGUgvI99lXKYB0iXw4bGnKRwC4/H1rhEcMaYJLtF5c5ceZTNDUKlf0gY+00y8zxhZ jNK4b4MtRGuOWlXOn96LReNmPPIrMYoVx3naD8whySBv/KcBHC3sUNO0pu+5k3nnqNPlRCdiA/1KO xG8+shQUbvFgo6W1ekahGvvyU74KMX4zruNGmCOwSL+Mr04FpArLQKPyel+2/+87fb9wB6ORyd2jH hDKUcLnw35ZxW+csSl/vpWeXz59YINwcCVK0ekJJWY7MheMBRiMqovzzEnd2EClgqMeZS7gss0I7i aPchdMzQ==;
Received: from [172.58.208.248] (port=28588 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1ppK3z-009jtN-MK; Wed, 19 Apr 2023 22:30:28 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_496DE800-1300-48B7-9769-6E02911678B1"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <CAPDSy+6m2n1EHrT4KYe1_AhwgBpsybEb_nZHvFHYwuu+h6S2aw@mail.gmail.com>
Date: Wed, 19 Apr 2023 19:30:10 -0700
Cc: Christian Huitema <huitema@huitema.net>, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "int-dir@ietf.org" <int-dir@ietf.org>, "draft-ietf-masque-connect-ip.all@ietf.org" <draft-ietf-masque-connect-ip.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "masque@ietf.org" <masque@ietf.org>
Message-Id: <89BD4D6B-6B8A-427F-85F5-8A4418481F05@strayalpha.com>
References: <168152936276.58402.12408511926010382248@ietfa.amsl.com> <CAPDSy+5ZOnK02VgJY7giVD0uNM4ao7-gHXUhrf6BG9RWxzC+RQ@mail.gmail.com> <19AB5170-D789-491C-B748-7AD5CE26B58C@strayalpha.com> <DU0PR07MB8970FC2DDE02B2BBB78D6E33959D9@DU0PR07MB8970.eurprd07.prod.outlook.com> <CAPDSy+72wpWzsQur=Bsvf7bUAxCAzq=OnXDS6Uxr7-k-3ZS-0Q@mail.gmail.com> <DA3F26DF-5B5F-4045-AA67-2BDEDCCA7975@strayalpha.com> <CAPDSy+7cf=ONtQw4Sfy4u51i6txk9K7axhyz6nx=_vic35DWtQ@mail.gmail.com> <4F486987-90BB-480A-9A0E-2E09BC4F1B72@strayalpha.com> <70EF67A5-7C4D-4E0E-8058-15EBA4A59095@ericsson.com> <ccc1a295-fa5e-0a97-98e1-1291e74fc6f7@huitema.net> <F8A3BB50-D471-430C-A1BE-4D2CEE9E3130@strayalpha.com> <9e918a1a-1741-c978-9099-be1a4f3d09df@huitema.net> <CAPDSy+6m2n1EHrT4KYe1_AhwgBpsybEb_nZHvFHYwuu+h6S2aw@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
X-Mailer: Apple Mail (2.3731.500.231)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/ylFzOHW47IqHbWVCE_ONgSnI2NU>
Subject: Re: [Int-dir] [Last-Call] Intdir telechat review of draft-ietf-masque-connect-ip-10
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2023 02:30:35 -0000

Hi, David…

(See below)

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Apr 19, 2023, at 2:30 PM, David Schinazi <dschinazi.ietf@gmail.com> wrote:
> 
> Hi Joe,
> 
> I think we're all in agreement that TCP-in-TCP leads to poor performance. And the document normatively recommends against doing that:
> ...
> 
> So if what you're asking is "SHOULD NOT do TCP-in-TCP", then we're in agreement and that's already in the doc. But "nested congestion control" means something else.

Fair enough, but the best that can be stated at this time is “we don’t know”. It would be unwise to deploy this as a standard while allowing potentially unknown interactions.

So it’s still “SHOULD NOT” use nested congestion control, just for a different reason - i.e.,l until its behavior is better known.

Joe

v2.23.0 | Report a Bug | By Email