Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <20260425113017.8D9D62CB41A@rfcpa.rfc-editor.org>
Date: Sat, 25 Apr 2026 19:22:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA08CFE6-2103-43C5-BF9E-F5299BE73FEA@ifi.uio.no>
References: <20260425113017.8D9D62CB41A@rfcpa.rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID-Hash: SHQZUKVVMIV3UWYNOOBBPDN35ZPHHVUN
CC: ing.hovind@hotmail.com, tpauly@apple.com, ietf@trammell.ch,
 anna.brunstrom@kau.se, Gorry Fairhurst <gorry@erg.abdn.ac.uk>,
 csp@csperkins.org, taps@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BTaps=5D_Re=3A_=5BEditorial_Errata_Reported=5D_RFC9621_=288889?=
	=?utf-8?q?=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/taps/QGx8P7izLh-B3npIk7srnSSOoQ8>

I think this is correct.

Cheers,
Michael


> On 25 Apr 2026, at 13:30, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC9621,
> "Architecture and Requirements for Transport Services".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8889
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Ingbrigt Hovind <ing.hovind@hotmail.com>
>=20
> Section: 4.
>=20
> 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               |
>   +-----------------------------------------------------+
>=20
> 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               |
>   +-----------------------------------------------------+
>=20
> 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
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it=20
> 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 =20
> will log in to change the status and edit the report, if necessary.
>=20
> --------------------------------------
> 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
>=20
> _______________________________________________
> Taps mailing list -- taps@ietf.org
> To unsubscribe send an email to taps-leave@ietf.org