Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3864.500.155\))
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <AA08CFE6-2103-43C5-BF9E-F5299BE73FEA@ifi.uio.no>
Date: Wed, 29 Apr 2026 18:35:40 -0700
Content-transfer-encoding: quoted-printable
Message-id: <E772B428-88AA-408D-8CE5-15A05B602B4D@apple.com>
References: <20260425113017.8D9D62CB41A@rfcpa.rfc-editor.org>
 <AA08CFE6-2103-43C5-BF9E-F5299BE73FEA@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
Message-ID-Hash: 53RB3GEO2H6EPWBOWA4Z6RQ3CTZFUEOX
CC: RFC Errata System <rfc-editor@rfc-editor.org>, ing.hovind@hotmail.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/piqpDCtIIvFlexT0RIsJpFK5KP0>

Agreed, this looks correct, and can be verified.

Thanks,
Tommy

> On Apr 25, 2026, at 10:22=E2=80=AFAM, Michael Welzl =
<michawe@ifi.uio.no> wrote:
>=20
> I think this is correct.
>=20
> Cheers,
> Michael
>=20
>=20
>> 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
>=20
> _______________________________________________
> Taps mailing list -- taps@ietf.org
> To unsubscribe send an email to taps-leave@ietf.org