Re: [tcpm] 793bis ready to go?

Joe Touch <touch@strayalpha.com> Sun, 21 February 2021 19:39 UTC

Return-Path: <touch@strayalpha.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 6FB0F3A1028 for <tcpm@ietfa.amsl.com>; Sun, 21 Feb 2021 11:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.24
X-Spam-Level:
X-Spam-Status: No, score=0.24 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, HAS_X_OUTGOING_SPAM_STAT=2.339, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BoCT2M4hxRDU for <tcpm@ietfa.amsl.com>; Sun, 21 Feb 2021 11:39:45 -0800 (PST)
Received: from server217-5.web-hosting.com (server217-5.web-hosting.com [198.54.116.226]) (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 222EC3A0FFA for <tcpm@ietf.org>; Sun, 21 Feb 2021 11:39:45 -0800 (PST)
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-Transfer-Encoding:Content-Type:Sender: Reply-To: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=VsgK2cSCN03uxvEtp1wsDRW6Vh47lNqK+T5Rt0RLmjg=; b=GwHE5wq7lulpkBUSMv71jitIIg t+IUIF+olsMRLBdFX4Ro/yOvSgB8x0qnAXdgtkC0ab/OZ2hb4Vo/PFOB5WLML9SU1Bth2XSoHhxBs 4qJ6DKLeq0chZneeLFyfSyOrC2DcCrgq9zcMJ2RGdc3H40jBrp6AZOuW36ux4MHUUCfNUNT6gtksT bSHJjM77Em/3FKwfD31+YVNuHt1w4b+9Yvob/dRP/AzL+iHsNO6eXdpOl8lXCTAT/VilO7eCw1RNg Hh6v57vIycjdeAAp3bfq+XARhCJCp45IVMCsOZKQcb2NISuJyPD+ZLqHdYpQsTLKLWTVC//qDfFz7 dfL845QA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:55595 helo=[192.168.1.17]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1lDuZr-001Fih-GX; Sun, 21 Feb 2021 14:39:40 -0500
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <D7F636DC-E133-47F6-87A5-5BBEBB5D5C85@lurchi.franken.de>
Date: Sun, 21 Feb 2021 11:39:34 -0800
Cc: tcpm IETF list <tcpm@ietf.org>, Markku Kojo <kojo=40cs.helsinki.fi@dmarc.ietf.org>
Message-Id: <37D123C4-03F5-4D14-84C2-849C5B7B94F1@strayalpha.com>
References: <D7F636DC-E133-47F6-87A5-5BBEBB5D5C85@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Mailer: iPhone Mail (18D52)
X-OutGoing-Spam-Status: No, score=-1.0
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/tcpm/IraR1t2NnfWrz2I_jUmjWYRgDY0>
Subject: Re: [tcpm] 793bis ready to go?
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: Sun, 21 Feb 2021 19:39:50 -0000

Works for me. 

> On Feb 21, 2021, at 11:16 AM, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
> 
> 
>> 
>> On 21. Feb 2021, at 19:38, Joseph Touch <touch@strayalpha.com> wrote:
>> 
>>> On Feb 20, 2021, at 1:53 PM, Michael Tuexen <michael.tuexen@lurchi.franken.de> wrote:
>>> 
>>> 
>>> 
>>>> On 20. Feb 2021, at 22:37, Joseph Touch <touch@strayalpha.com> wrote:
>>>> 
>>>> Even if you prefer the FreeBSD variant, the text below doesn’t appear to fix this; it will end up sending the SYN-ACK of the received data *and a second ACK* at the end of the sixth step.
>>> I think the idea of Richard is that if the text is
>>> 
>>>        If SND.UNA > ISS (our SYN has been ACKed), change the
>>>        connection state to ESTABLISHED, form an ACK segment
>>>        <SEQ=SND.NXT><ACK=RCV.NXT><CTL=ACK>
>>>        and should send it.
>>> 
>>> Then NOT following the should, but only send the ACK at the end of step 6.
>>> Wouldn't that work?
>> 
>> FWIW, I think the case of combining the bare ACK with the ACK of the received SYN-ACK data is already covered in the sixth step below in the following text:
>> 
>>        This acknowledgment should be piggybacked on a segment being
>>        transmitted if possible without incurring undue delay.
>> 
> I agree, this covers it. But it would be good to have it a bit more explicit.
>> 
>> If this needs to be made more explicit, here’s my suggestion:
>> 
>> OLD:
>> 
>>        If SND.UNA > ISS (our SYN has been ACKed), change the connection
>>        state to ESTABLISHED, form an ACK segment
>> 
>>          <SEQ=SND.NXT><ACK=RCV.NXT><CTL=ACK>
>> 
>>        and send it.  Data or controls which were queued for
>>        transmission may be included.  If there are other controls or
>>        text in the segment then continue processing at the sixth step
>>        below where the URG bit is checked, otherwise return.
>> 
>> 
>> 
>> NEW:
>> 
>>        If SND.UNA > ISS (our SYN has been ACKed), change the connection
>>        state to ESTABLISHED, form an ACK segment
>> 
>>          <SEQ=SND.NXT><ACK=RCV.NXT><CTL=ACK>
>> 
>>        Data or controls which were queued for
>> 
>>        transmission MAY be included in this segment.  If there are no 
>>    other controls or text in the segment then send the ACK segment 
> Maybe:
>         other controls or text in the received segment then send the ACK segment 
>>    and return. Otherwise, continue processing at the sixth step below 
>>    where the URG bit is checked, either sending the ACK segment now or 
>>    piggybacking it with the response from that continued processing
>>    (as noted therein).
> I like your proposal (maybe with the above suggestion).
> 
> Best regards
> Michael
>> 
>> Joe
>