[Taps] [Editorial Errata Reported] RFC9621 (8889)

RFC Errata System <rfc-editor@rfc-editor.org> Sat, 25 April 2026 11:30 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id AA373E2E8DA9; Sat, 25 Apr 2026 04:30:17 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8D9D62CB41A; Sat, 25 Apr 2026 04:30:17 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260425113017.8D9D62CB41A@rfcpa.rfc-editor.org>
Date: Sat, 25 Apr 2026 04:30:17 -0700
Message-ID-Hash: WOWDBDMZRD55T75OCL2OROMWA4OA2SEJ
X-Message-ID-Hash: WOWDBDMZRD55T75OCL2OROMWA4OA2SEJ
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-taps.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ing.hovind@hotmail.com, tpauly@apple.com, ietf@trammell.ch, anna.brunstrom@kau.se, gorry@erg.abdn.ac.uk, csp@csperkins.org, taps@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Taps] [Editorial Errata Reported] RFC9621 (8889)
List-Id: "IETF Transport Services (TAPS) Working Group" <taps.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/lOwjhTgeC_qLbDgIvWJ98VAr48Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Owner: <mailto:taps-owner@ietf.org>
List-Post: <mailto:taps@ietf.org>
List-Subscribe: <mailto:taps-join@ietf.org>
List-Unsubscribe: <mailto:taps-leave@ietf.org>

The following errata report has been submitted for RFC9621,
"Architecture and Requirements for Transport Services".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8889

--------------------------------------
Type: Editorial
Reported by: Ingbrigt Hovind <ing.hovind@hotmail.com>

Section: 4.

Original Text
-------------
     +-----------------------------------------------------+
     |                    Application                      |
     +-+----------------+------^-------+--------^----------+
       |                |      |       |        |
     pre-               |     data     |      events
     establishment      |   transfer   |        |
       |        establishment  |   termination  |
       |                |      |       |        |
       |             +--v------v-------v+       |
     +-v-------------+   Connection(s)  +-------+----------+
     |  Transport    +--------+---------+                  |
     |  Services              |                            |
     |  API                   |  +-------------+           |
     +------------------------+--+  Framer(s)  |-----------+
                              |  +-------------+
     +------------------------|----------------------------+
     |  Transport             |                            |
     |  System                |        +-----------------+ |
     |  Implementation        |        |     Cached      | |
     |                        |        |      State      | |
     |  (Candidate Gathering) |        +-----------------+ |
     |                        |                            |
     |  (Candidate Racing)    |        +-----------------+ |
     |                        |        |     System      | |
     |                        |        |     Policy      | |
     |             +----------v-----+  +-----------------+ |
     |             |    Protocol    |                      |
     +-------------+    Stack(s)    +----------------------+
                   +-------+--------+
                           V
   +-----------------------------------------------------+
   |               Network-Layer Interface               |
   +-----------------------------------------------------+

Corrected Text
--------------
     +-----------------------------------------------------+
     |                    Application                      |
     +-+----------------+------^-------+--------^----------+
       |                |      |       |        |
     pre-               |     data     |      events
     establishment      |   transfer   |        |
       |        establishment  |   termination  |
       |                |      |       |        |
       |             +--v------v-------v+       |
     +-v-------------+   Connection(s)  +-------+----------+
     |  Transport    +--------+---------+                  |
     |  Services              |                            |
     |  API                   |  +-------------+           |
     +------------------------+--+  Framer(s)  |-----------+
                              |  +-------------+
     +------------------------|----------------------------+
     |  Transport             |                            |
     |  Services              |        +-----------------+ |
     |  Implementation        |        |     Cached      | |
     |                        |        |      State      | |
     |  (Candidate Gathering) |        +-----------------+ |
     |                        |                            |
     |  (Candidate Racing)    |        +-----------------+ |
     |                        |        |     System      | |
     |                        |        |     Policy      | |
     |             +----------v-----+  +-----------------+ |
     |             |    Protocol    |                      |
     +-------------+    Stack(s)    +----------------------+
                   +-------+--------+
                           V
   +-----------------------------------------------------+
   |               Network-Layer Interface               |
   +-----------------------------------------------------+

Notes
-----
In figure 3 the internal implementation is referred to as a "Transport System Implementation" instead of a "Transport Services Implementation" as in the rest of the document

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9621 (draft-ietf-taps-arch-19)
--------------------------------------
Title               : Architecture and Requirements for Transport Services
Publication Date    : January 2025
Author(s)           : T. Pauly, Ed., B. Trammell, Ed., A. Brunstrom, G. Fairhurst, C. S. Perkins
Category            : PROPOSED STANDARD
Source              : Transport Services
Stream              : IETF
Verifying Party     : IESG