The following errata report has been verified for RFC9622,
"An Abstract Application Programming Interface (API) for Transport Services". 

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

--------------------------------------
Status: Verified
Type: Technical

Reported by: Ingebrigt Hovind <[email protected]>
Date Reported: 2025-10-30
Verified by: Gorry Fairhurst (IESG)

Section: 6.1.5

Original Text
-------------
      TransportProperties := ...
      SecurityParameters  := ...

      Preconnection := NewPreconnection(LocalSpecifier,
                                        RemoteSpecifier,
                                        TransportProperties,
                                        SecurityProperties)
      Listener := Preconnection.Listen()

Corrected Text
--------------
      TransportProperties := ...
      SecurityParameters  := ...

      Preconnection := NewPreconnection(LocalSpecifier,
                                        RemoteSpecifier,
                                        TransportProperties,
                                        SecurityParameters)
      Listener := Preconnection.Listen()

Notes
-----
There were four occurances in pseudocode of the variable name 
"SecurityParameters". The RFC is updated to replace each of these with the 
variable name "SecurityParameters", as used elsewhere in  this RFC.

--------------------------------------
RFC9622 (draft-ietf-taps-interface-26)
--------------------------------------
Title               : An Abstract Application Programming Interface (API) for 
Transport Services
Publication Date    : January 2025
Author(s)           : B. Trammell, Ed., M. Welzl, Ed., R. Enghardt, G. 
Fairhurst, M. Kühlewind, C. S. Perkins, P.S. Tiesel, T. Pauly
Category            : PROPOSED STANDARD
Source              : Transport Services
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
Taps mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to