[tcpm] Fwd: RFC 9187 on Sequence Number Extension for Windowed Protocols

"touch@strayalpha.com" <touch@strayalpha.com> Tue, 01 February 2022 16:45 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C92943A15BD; Tue, 1 Feb 2022 08:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.523
X-Spam-Status: No, score=-0.523 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=0.795, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id woECd-ym4JSL; Tue, 1 Feb 2022 08:45:04 -0800 (PST)
Received: from server217-1.web-hosting.com (server217-1.web-hosting.com []) (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 3353F3A15B1; Tue, 1 Feb 2022 08:45:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Message-Id:To:References:Subject:Date: Mime-Version:Content-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ySUtlGARcRUoGCweYgNwTebWkHDDP08/6rHSHFdd79k=; b=CL9/1/+vQlWEkFHVYrGTw3kiUe /qZKIi4Q8eXjkeU/H804tG9RYI0CtrGpzAPQc/duIIZKgxd1iX5pYNq6NNWhDGqFKrDOQqQi9j5l5 lAZTLUFpDg8a/Qa/aWR6jRC7UGw8dpYELxLD9tpfHykIuq/N7l8RC4r/2zTKyOi72KASE3oifDbSV vXn0ZGj6YGL1YzWTsxAYhghjYBfhWsROZ6o5dVcUeY+rJUFUeHEztzpnC51uphoxmOmmdKLUTdFFA v3f0de970MtjGo2w/w1T5Q3BftcdcJJBrQ21vWfUI8f6uGhZlRAn0tQ21NXx/hfxU+2CmrSmswsux C7NKCcWQ==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([]:52043 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <touch@strayalpha.com>) id 1nEwH5-000OJk-AY; Tue, 01 Feb 2022 11:45:03 -0500
From: "touch@strayalpha.com" <touch@strayalpha.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AB10C52F-6964-4CDD-A555-E575BA521B6A"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
Date: Tue, 01 Feb 2022 08:44:58 -0800
References: <20220201071749.E12CBECB8D@rfc-editor.org>
To: tcpm IETF list <tcpm@ietf.org>, TSVWG <tsvwg@ietf.org>
Message-Id: <13D17C3E-85B7-4832-87B7-7244529795E6@strayalpha.com>
X-Mailer: Apple Mail (2.3693.
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-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/NwAhRid_SuewgrfHkBJmz0WDCpk>
Subject: [tcpm] Fwd: RFC 9187 on Sequence Number Extension for Windowed Protocols
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: Tue, 01 Feb 2022 16:45:09 -0000

Hi, all,

The following may be of interest.


Joe Touch, temporal epistemologist

> Begin forwarded message:
> From: rfc-editor@rfc-editor.org
> Subject: RFC 9187 on Sequence Number Extension for Windowed Protocols
> Date: January 31, 2022 at 11:17:49 PM PST
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
> A new Request for Comments is now available in online RFC libraries.
>        RFC 9187
>        Title:      Sequence Number Extension for Windowed Protocols 
>        Author:     J. Touch
>        Status:     Informational
>        Stream:     Independent
>        Date:       January 2022
>        Mailbox:    touch@strayalpha.com
>        Pages:      10
>        Updates/Obsoletes/SeeAlso:   None
>        I-D Tag:    draft-touch-sne-02.txt
>        URL:        https://www.rfc-editor.org/info/rfc9187
>        DOI:        10.17487/RFC9187
> Sliding window protocols use finite sequence numbers to determine
> segment placement and order. These sequence number spaces wrap around
> and are reused during the operation of such protocols. This document
> describes a way to extend the size of these sequence numbers at the
> endpoints to avoid the impact of that wrap and reuse without
> transmitting additional information in the packet header. The
> resulting extended sequence numbers can be used at the endpoints in
> encryption and authentication algorithms to ensure input bit patterns
> do not repeat over the lifetime of a connection.
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  https://www.ietf.org/mailman/listinfo/ietf-announce
>  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> The RFC Editor Team
> Association Management Solutions, LLC
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce