State of the Transport Area @ IETF 115

[Martin Duke <[e-mail]>]

Greetings, Transport Area:

As promised, in lieu of holding a tsvarea session, the ADs have elected to
share our report on the state of the area over email.

If you have any open mic-type subjects, you are welcome to use this mailing
list, or come to our office hours at 1200 Monday in "Hybrid 1". If you need
remote access, let us know and we will set it up.

*On to the status report:*

*Working Group Updates*
*ALTO *hopes to wrap up its deliverables early next year, at which point
the community will discuss rechartering or closing.

*DTN *made progress on IPN naming schemes and network
management architecture

*IPPM *has delivered almost all of its IOAM docs. It is returning to its
usual work of defining new metrics (notably draft-ietf-ippm-responsiveness)
and tweaking STAMP.

*MASQUE *is concluding the CONNECT-IP work and will almost certainly
recharter to tie up loose ends. The recharter will come up at IETF 115.

*NFSv4 *has made significant progress on documents and errata. Docs about
protocol security and a bis of the base specs are in adoption call.
*Welcome Christopher
Inacio* as the third chair!

*QUIC *published the applicability and manageability RFCs. V2 and Version
Negotiation are through the IESG, and the emphasis is now on QLOG and
multipath.

*RMCAT *The last document is through the IESG

*TAPS *is finishing up the three core documents.

*TCPM *updated Slow Start and Cubic, and is now working on getting the ECN
changes out the door to support L4S. We will start talking about the future
of Appropriate Byte Counting (RFC3465) at IETF 115.

*TSVWG *The main theme is DSCP drafts but MP-DCCP is also almost done. *Welcome
Marten Seemann as chair, and thanks to David Black* for his years of
service in that role!

And finally, *CONGRESS (CONGestion RESpones and Signaling). *Martin is
working on the charter and, when ready, Zahed will run a consensus call on
it. Once the charter is locked down, we will solicit -00 drafts on the key
deliverables. Only when those exist will we form a working group; if they
don't materialize, neither will the group. There will be a *side meeting on
this at 1700 Thursday in Richmond 6.*

*Documents*
A very successful interval for the area!
*New RFCs*:
*9274* A Cost Mode Registry for the Application-Layer Traffic Optimization
(ALTO) Protocol
*9275 *An Extension for Application-Layer Traffic Optimization (ALTO): Path
Vector
*9287* Greasing the QUIC Bit
*9289* Towards Remote Procedure Call Encryption by Default
*9293* Transmission Control Protocol (TCP)
*9297* HTTP Datagrams and the Capsule Protocol
*9298* Proxying UDP in HTTP
*9308* Applicability of the QUIC Transport Protocol
*9312* Manageability of the QUIC Transport Protocol
[Not Transport Area, but of note]
*9265* Forward Erasure Correction (FEC) Coding and Congestion Control in
Transport [iccrg]

*Delivered to the RFC Editor:*
ippm-ioam-direct-export
ippm-ioam-flags
ippm-rfc8321bis
ippm-rfc8889bis
tcpm-yang-tcp
tsvwg-aqm-dualq-coupled
tsvwg-ecn-l4s-id
tsvwg-l4s-arch

There's only one document still sitting in the RFCEd queue from before IETF
114:
alto-performance-metrics

*TSVART Review Team Update*
As always, thanks to the TSVART review team, which greatly reduces the
workload for ADs by catching transport-layer problems early. You are highly
encouraged to contact Magnus Westerlund or Wes Eddy about joining: it is a
great way to help the IETF publish quality documents and get a taste of the
broader IETF. Typically, you would review about two documents per year, so
it's not a huge commitment.

Thanks to the 19 members of the team. We'd especially like to recognize
those who completed a review since IETF 114:
David Black
Bob Briscoe
Spencer Dawkins
Wes Eddy
Gorry Fairhurst
Jorg Ott
Brian Trammell

*Your Next Area Director*
It appears that Zahed will be the only candidate for the Transport AD slot
opening in March.

It is a bad thing for the area that there is frequently only one candidate
for this position. I strongly encourage you to consider running 2023, and
using the existing ADs as a resource to understand the commitment. There's
no prerequisite -- Martin jumped straight from Individual Contributor to
AD, and you can too.

Thanks for everything that all of you are doing for Transport,
Martin and Zahed