Skip to main content
  • IETF@40

    Forty years ago today, 21 people gathered in San Diego, California for the first meeting of what became the Internet Engineering Task Force.

    16 Jan 2026
  • Launch of the IETF Community Survey 2025

    The IETF Community survey is our major annual survey of the whole of the IETF community and is used to inform the actions of IETF leadership throughout the year. The 2025 IETF Community Survey is live and we want to hear from you!

    23 Dec 2025
  • IETF Administration LLC 2026 Draft Budget

    The IETF Administration LLC has prepared its draft budget for 2026 and now seeks community feedback.

    19 Dec 2025
  • Net zero update for 2025

    As 2025 comes to a close, we want to provide an update on the IETF’s carbon footprint for this year and share information about further steps we took to increase IETF operations’ sustainability.

    17 Dec 2025
  • IETF 124 post-meeting survey

    The IETF 123 Madrid meeting was held 19-25 July 2025 and the results of the post-meeting survey are now available on a public report.

    11 Dec 2025

Filter by topic and date

Filter by topic and date

SEMI Workshop

3 Feb 2015

I’m on the train this morning after the two-day Stack Evolution in a Middlebox Internet (SEMI) workshop at the Swiss Federal Institute of Technology (ETH) in Zürich.

We had a very successful discussion sponsored by the IAB, the Internet Society, and the Communication Systems Group at ETH. Many thanks to the sponsors, organizers, and participants. Each played a vital role in making the workshop a success.

The IAB Stack Evolution Program provided the vision for the workshop, and some served on the workshop program committee. The forty attendees were selected based on position papers and expertise, allowing the program committee to bring together many viewpoints.

The problems we explored have been discussed before at the IETF, but not all at the same time. They included:

  • Application developers have tried to use UDP, but find that many middleboxes, including corporate firewalls, block or degrade the performance of their protocols. This has been particularly evident with WebRTC deployment experience.
  • There are a variety of new services that desire a more direct communication between applications and the network path. This has proven difficult in the past because each protocol that uses UDP requires special handling, often needing custom code in each middlebox on the path.
  • Network operators sometimes find UDP challenging because it is hard to determine flow context on a per-datagram basis. Information about the flow would improve their ability to reason about the flow with respect to policy and performance.
  • In November, the IAB issued a Statement on Internet Confidentiality. Increasing levels of encryption will amplify the above problems. As we noted in that statement, hard work will be needed to reach confidential operation by default.

During the workshop, we discussed what information could be exposed outside an end-to-end encryption context that would allow good policy decisions by middleboxes on the path without compromising the confidentiality or privacy of end-user data.

We concluded that there must be clear incentives for application developers, network operators, and equipment vendors to spur real-world deployment. Possible incentives might include:

  • Easier to deploy new Internet applications
  • More effective use of UDP by applications on more networks
  • Increased confidence for firewall administrators in the coherence of UDP flows
  • Ability for network operators to add value to traffic transiting their networks
  • Improved user confidentiality and privacy

We will write a workshop report to describe the discussion in detail. Several people signed up to write Internet-Drafts, which will hopefully lead to one or more BoFs in the next year.


Share this page