[tcpm] Summary of diffs in new version: draft-ietf-tcpm-generalized-ecn-13

Bob Briscoe <ietf@bobbriscoe.net> Mon, 23 October 2023 22:18 UTC

Return-Path: <ietf@bobbriscoe.net>
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 544D5C170608 for <tcpm@ietfa.amsl.com>; Mon, 23 Oct 2023 15:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 eEpkl_2HpGWR for <tcpm@ietfa.amsl.com>; Mon, 23 Oct 2023 15:18:17 -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 129FAC16F3EC for <tcpm@ietf.org>; Mon, 23 Oct 2023 15:17:57 -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:Cc:References: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=4+kIPsldNQ2MO9Rg8bGLQhOQ6ivpIqiZeckadLZNQEo=; b=gIAd/ObHYz9d9k4AdFLt5TSNIj 19n3t2AWqLUMUMQmiYXlhK1rgBsK1Tdsi+NdSNHycfVEmpe/tymmbkNHoqlx28r4J3zeiVAvJwCCV h27dPBmaLLjNRE3midKFmf6f27dXZ11o2AIW3BSqTjRjOiSxAr5rMApWVUKTJ7Pmb1CgSaftxx6my Qv4vleVGh+26+kFcZR9OOO9y1C5KTMbZIQmuDcF8QJNKJ5DRg2UYKsQaOBaxsqvWNzT6EswFjiBCw 9DO6YMXePY4ABzICuTA7Pqp5Z5pWrRj1WAD0ez/FdLNJyuWP6KLntBy4t0jK/tAEHhIIil4pvIIxA HGqNVttw==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:44434 helo=[192.168.1.29]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96.2) (envelope-from <ietf@bobbriscoe.net>) id 1qv3FG-0008Gm-13; Mon, 23 Oct 2023 23:17:55 +0100
Content-Type: multipart/alternative; boundary="------------hFVvaV0hdRPYpIVmqvweXHrf"
Message-ID: <9fb09601-c5df-49c9-82a0-041f594a63f8@bobbriscoe.net>
Date: Mon, 23 Oct 2023 23:17:52 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: tcpm IETF list <tcpm@ietf.org>
References: <169809758864.12395.4477595643585943297@ietfa.amsl.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
In-Reply-To: <169809758864.12395.4477595643585943297@ietfa.amsl.com>
X-MagicSpam-TUUID: a07fa3de-36bb-4905-948b-ef2417d3362e
X-MagicSpam-SUUID: 8b6ddbc9-3a09-4bdf-b9d5-c0b43684d29e
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/tcpm/rQZHLtlfWkRilCG4nxZY6muzJKI>
Subject: [tcpm] Summary of diffs in new version: draft-ietf-tcpm-generalized-ecn-13
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 23 Oct 2023 22:18:22 -0000

tcpm,

We've just posted a new rev of draft-ietf-tcpm-generalized-ecn-13
You can find a link to the full diff below. Here's a summary:

Normative:

  * Changed §3.3.1 "Additional DupACK Check" to solely specify the
    Additional DupACK Check by the *receiver* of an incoming Pure ACK,
    and only refer to the other conditions for *sending* an outgoing
    ECN-capable pure ACK in §3.2.3.2 (rather than re-stating them).

Editorial

  * Reversed the rather confusing logical flow of all the sentences
    which said (paraphrasing) "You can ignore the prohibition in Section
    abc of RFC3168 against setting ECT on an xyz packet, as per Section
    4.3 of RFC8311". Replaced with "Section 4.3 o RFC8311 allows setting
    ECT on an xyz packet, by updating Section abc of RFC3168".
  * Considerable edits to the rationale in §4.4.4 "Pure ACKs: DupACK
    Tests", to explain why an exception to the RFC5681 rule against
    repeating acknowledgement of a segment is necessary in this case,
    and adding each step of the example, rather than glossing over some
    that seemed obvious (to the authors) in the previous version.
  * Changed the description of the individual draft specifying ECN in
    SCTP, now that it has been updated (for the first time since Jan 2014).
  * Updated the ref to CUBIC now it has been published as an RFC.



Bob

On 23/10/2023 22:46, internet-drafts@ietf.org wrote:
> A new version of Internet-Draft draft-ietf-tcpm-generalized-ecn-13.txt has
> been successfully submitted by Bob Briscoe and posted to the
> IETF repository.
>
> Name:     draft-ietf-tcpm-generalized-ecn
> Revision: 13
> Title:    ECN++: Adding Explicit Congestion Notification (ECN) to TCP Control Packets
> Date:     2023-10-23
> Group:    tcpm
> Pages:    51
> URL:https://www.ietf.org/archive/id/draft-ietf-tcpm-generalized-ecn-13.txt
> Status:https://datatracker.ietf.org/doc/draft-ietf-tcpm-generalized-ecn/
> HTML:https://www.ietf.org/archive/id/draft-ietf-tcpm-generalized-ecn-13.html
> HTMLized:https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-generalized-ecn
> Diff:https://author-tools.ietf.org/iddiff?url2=draft-ietf-tcpm-generalized-ecn-13
>
> Abstract:
>
>     This document specifies an experimental modification to ECN when used
>     with TCP.  It allows the use of ECN in the IP header of the following
>     TCP packets: SYNs, SYN/ACKs, pure ACKs, Window probes, FINs, RSTs and
>     retransmissions.  This specification obsoletes RFC5562, which
>     described a different way to use ECN on SYN/ACKs alone.
>
>
>
> The IETF Secretariat
>
>

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