# \[Networking Workgroup\] Public meeting — Monday, August 31, 2026 — Agenda and call for topics **URL:** \ **Category:** Networking\ **Tags:** networking-workgroup, meeting-announcement\ **Created:** [August 22, 2026, 6:03am UTC](https://forums.swift.org/t/networking-workgroup-public-meeting-monday-august-31-2026-agenda-and-call-for-topics/89124 "2026-08-22T06:03:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ekinnear](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ekinnear/32/45200_2.png) [@ekinnear](https://forums.swift.org/u/ekinnear)\ **Post date:** [August 22, 2026, 6:03am UTC](https://forums.swift.org/t/networking-workgroup-public-meeting-monday-august-31-2026-agenda-and-call-for-topics/89124/1 "2026-08-22T06:03:11Z")
The Networking Workgroup meets again on **Monday, August 31, 2026** , and everyone is welcome. ## Logistics - When: **Monday, August 31, 2026, 8:30–9:30 AM PDT** ([see this time in your local timezone](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Swift+Networking+Workgroup+Meeting&iso=20260831T0830&p1=224&ah=1)) - Where: [WebEx](https://appleinc.webex.com/appleinc/j.php?MTID=m5161679546ff61f397951c7bfe84d7e6) ## Draft agenda - Welcome and recap of action items from the last meeting (5 min) - Workgroup focus items (5 min) - Update: Currency types: IP Addresses and Ports (15 min) - [Requirements thread](https://forums.swift.org/t/requirements-for-ip-address-and-port-apis/88514) - Deep dive: Swift HTTP APIs — how we got here (25 min) - Short presentation, then discussion - The design journey - Framing the open HTTP API issues - Community agenda items and open discussion (as time permits) - Wrap-up and action items (5 min) ### Propose an agenda item We'd love the agenda to reflect what the community wants to discuss. Please reply to this thread with topics you'd like to cover, ideally with a sentence or two of context and roughly how much time you think it needs. To keep the meeting focused, we'll include some agenda topics from the replies received for discussion as time permits and include anything else in the list of potential topics for future meetings. A few notes so the meeting stays productive with a larger group: - Most decisions happen asynchronously on the forums, [Slack](https://swift-open-source.slack.com/archives/C0BJMU6842G), and GitHub. The meeting is for discussion and alignment, so you can participate fully asynchronously if you wish or if you cannot attend a particular timeslot. - We'll use a raised-hand queue and chat for questions and discussions. Please take note of your position in the queue and try to avoid collisions with others when speaking. - We'll post the notes from the meeting here on the forums afterwards. Note that we're piloting AI note-taking tools but won't be recording the meeting, and you can ask us to turn them off at any time. - We follow the [Swift Code of Conduct](https://www.swift.org/code-of-conduct/). This is a public meeting, so please keep discussion to public, non-confidential topics. Looking forward to seeing you there! ---
**Author:** ![ekinnear](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ekinnear/32/45200_2.png) [@ekinnear](https://forums.swift.org/u/ekinnear)\ **Post date:** [August 31, 2026, 5:53pm UTC](https://forums.swift.org/t/networking-workgroup-public-meeting-monday-august-31-2026-agenda-and-call-for-topics/89124/2 "2026-08-31T17:53:57Z")
# **Swift Networking Workgroup Meeting Notes** ## **Meeting Details** - **Date:** August 31, 2026 ## **Summary** The meeting featured a deep dive into the evolution of the Swift HTTP APIs, outlining key design decisions and open questions around restartable bodies and client configuration. The group also reviewed an API sketch for IP address types, discussing the use of enums and the process for evolving APIs within the forthcoming `swift-network-types` repository. Action items were set to advance dependencies like async streaming and to formally shepherd the HTTP API design discussions. ## **Notes** - **Swift Network Types Repository Update** - **Repository Mechanics and API Evolution** - **IP Address and Port Types Proposal Review** - **HTTP API Deep Dive (presentation by Guoye)** - **HTTP API Discussion and Next Steps** - **WebSockets and WebTransport** ## **Next Steps & Action Items** - Franz will monitor the progress of the `swift-network-types` repository with the core team. - Franz will follow up with the language steering group on the dependent `async` streaming interfaces. - Eric and Franz will work with volunteers to document the API evolution process for the new repository. - Guoye will share a list of top open HTTP API design issues to spur discussion. - Jon and Nakul will begin shepherding the HTTP API design process, organizing discussions on GitHub and for future meetings. - Jon will prepare a potential presentation on Alamofire’s API design for a future meeting. - Francesco will continue his work on a Swift client for WebTransport and share updates with the group. ---
**Author:** ![MahdiBM](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mahdibm/32/45271_2.png) [@MahdiBM](https://forums.swift.org/u/MahdiBM)\ **Post date:** [September 8, 2026, 3:42pm UTC](https://forums.swift.org/t/networking-workgroup-public-meeting-monday-august-31-2026-agenda-and-call-for-topics/89124/3 "2026-09-08T15:42:25Z")
> [@ekinnear](#): > > - Eric and Franz will work with volunteers to document the API evolution process for the new repository. I'd like to volunteer for the API evolution process document. I don't anticipate there will be many controversial points in there as there is good precedent for library evolutions in Swift, but It looks like I'll be contributing to `swift-network-types` so hopefully we can add that "contributor" POV as well to the document.