Re: [Last-Call] Tsvart Last Call assignment: draft-ietf-masque-connect-ip

Bob Briscoe <ietf@bobbriscoe.net> Thu, 23 March 2023 22:36 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD7CC137383; Thu, 23 Mar 2023 15:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 0PJqKduEHRuT; Thu, 23 Mar 2023 15:36:50 -0700 (PDT)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (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 98F49C151719; Thu, 23 Mar 2023 15:36:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID: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=ttmm8Ej6Xgoi2KvWvpm55tWwBghzuISXbsi9DpdKbgQ=; b=YPXiRmidfcggtiF5/00S/BWXky nd9zvH3ly3Fk9Ju/KsXv0/Q6FqoiQyXTm300mD7J/45nHSem7nkfrqSbdTOcfKFbC3ybF9XNvPfcG 3112jnzCPLKNYlcnTK+9EhAwszdyt2JHF7GxrfkbePpySqcEySZ2/lXdx7J8VTIj4uJtGu820HxJE WRgjX94pGYCpXaDjNGBW99ZFZRDDu1qBVb0vTEkTwDsGvXkJ03bFXM169uk4XNTFVB14LqwHp1oQA Y5n7OlBuxZZ1gEKjeK/nLmScjpfSacgt5V3Z7aq1ND/klaE/7LH/Mm5cOOF12+P3mhI8z9Mh99oW2 +b47B0dw==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:60676 helo=[192.168.1.8]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from <ietf@bobbriscoe.net>) id 1pfTY3-0004nN-1H; Thu, 23 Mar 2023 22:36:43 +0000
Content-Type: multipart/alternative; boundary="------------2JMKaTfTziKGLy8ggozeDB0l"
Message-ID: <fcb10177-d35a-bce2-be1b-7e5bdbda61cd@bobbriscoe.net>
Date: Thu, 23 Mar 2023 22:36:40 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-GB
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Zaheduzzaman.Sarker@ericsson.com, martin.h.duke@gmail.com, wes@mti-systems.com, "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-masque-connect-ip.all@ietf.org, last-call@ietf.org, MASQUE <masque@ietf.org>
References: <167809217700.46817.1953496271912318949@ietfa.amsl.com> <4e76d590-1851-8ed9-a2bf-e1dcb9465188@bobbriscoe.net> <CAPDSy+5da+mJveohb2gvV=K+_DhPwFgt86t-0XUh4OctZnPF4w@mail.gmail.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
In-Reply-To: <CAPDSy+5da+mJveohb2gvV=K+_DhPwFgt86t-0XUh4OctZnPF4w@mail.gmail.com>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/aVoQm9Bfot1Z44Ms4_hFoCN5SX8>
Subject: Re: [Last-Call] Tsvart Last Call assignment: draft-ietf-masque-connect-ip
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2023 22:36:55 -0000

David,

On 23/03/2023 20:37, David Schinazi wrote:
> [ + usual email lists ]
>
> Hi Bob, thanks for your review!

[BB] That wasn't my review - working on it.


Bob

> Responses inline.
> David
>
> On Thu, Mar 23, 2023 at 2:27 AM Bob Briscoe <ietf@bobbriscoe.net> wrote:
>
>     masque-connect-ip authors,
>
>     My apologies. I do still intend to send in my tsv-art review of
>     masque-connect-ip, but I'm running over a week late now.
>     (It seems that my turn for review comes up more often than not just
>     before the IETF meeting.)
>
>     I've got a number of detailed comments. But the main thing that's
>     taking
>     time is thinking through the potential interaction problems there
>     might
>     be when running a connectionless protocol as generic as IP through a
>     connection-oriented tunnel. Particularly given there might be another
>     connection-oriented protocol within the inner IP datagram.
>
>
> FWIW, the issue here isn't the fact that anything is connection-oriented.
> I don't think there is any problem to be had by running connectionless
> protocols over connection-oriented ones or vice versa. That said, what
> can make things interesting performance-wise is whether there are
> nested congestion controllers or nested loss recovery mechanisms.
>
>     This probably
>     needs a section akin to §6 of RFC9298, but I'm trying to think more
>     widely of problems that might not have been considered when the IP
>     packet was constrained to only encapsulate UDP.
>
>
> That's a fair ask. Mentioning what we know about nested loss recovery
> and about PMTUD can't hurt. I don't expect there to be much here in
> addition to what he had in s6 of RFC 9298 though, since the switch
> from UDP to IP won't change much (modulo IPv6 minimum MTU, which
> is already covered).
>
>     I don't see any place for discussion of this in the draft, so I
>     wondered
>     whether there has been ML discussion somewhere that worked through
>     all
>     this and decided there were no issues. If you could point me to
>     that it
>     would greatly help me.
>
>
> We had some good WG conversations about MTU here:
> https://github.com/ietf-wg-masque/draft-ietf-masque-connect-ip/issues/45
> https://github.com/ietf-wg-masque/draft-ietf-masque-connect-ip/issues/62
> The discussions around performance happened around RFC 9298,
> but we can copy that text here.
>
>     This email was not sent via the review tool, so apologies if I
>     haven't
>     got the email distros correct.
>
>     Bob
>
>     On 06/03/2023 08:42, Magnus Westerlund via Datatracker wrote:
>     > Last Call review of: draft-ietf-masque-connect-ip (no specific
>     version)
>     > Deadline: 2023-03-15
>     > Pages: 36
>     > Requested by: (System)
>     >
>     >
>     https://datatracker.ietf.org/doc/draft-ietf-masque-connect-ip/reviewrequest/17185/login/
>     >
>     > Magnus Westerlund has assigned Bob Briscoe as a reviewer for
>     this document.
>     >
>     >
>     >
>     >
>     >
>
>     -- 
>     ________________________________________________________________
>     Bob Briscoe http://bobbriscoe.net/
>

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/