Person
Mark Nottingham
Internet standards contributor working across HTTP, URLs, RSS/Atom and QUIC; author of RFC 8890 and RFC 9518 and co-editor of RFC 9110. The IETF Datatracker profile reviewed on 31 August 2026 lists current HTTP, IAB and RFC Series responsibilities.
What to know first
- Public roleInternet standards contributor working across HTTP, URLs, RSS/Atom and QUIC; author of RFC 8890 and RFC 9518 and co-editor of RFC 9110. The IETF Datatracker profile reviewed on 31 August 2026 lists current HTTP, IAB and RFC Series responsibilities.Medium confidence
- Source basisPublic directory evidenceMedium confidence
- Last verifiedAug 30, 2026High confidence
Basic information
- NameMark NottinghamHigh confidence
- Public roleInternet standards contributor working across HTTP, URLs, RSS/Atom and QUIC; author of RFC 8890 and RFC 9518 and co-editor of RFC 9110. The IETF Datatracker profile reviewed on 31 August 2026 lists current HTTP, IAB and RFC Series responsibilities.Medium confidence
- Last verifiedAug 30, 2026High confidence
Related entities, projects, and resources
- Editorial contextA Standard Can Open the Exit Without Decentralising the Market, An open interface can make departure technically possible. It cannot, by itself, create a viable destination, preserve the relationships that give a service value or compel an incumbent to cooperate. RFC 9518 supplies a disciplined way to separate a useful switching affordance from a verdict about market power.Medium confidence
- Editorial contextMark Nottingham and the User Agent That Could Not Speak for Every User, The browser can deny a service direct access to a person's machine, carry a narrow preference and make another implementation possible. Those powers make the user agent a valuable intermediary. They do not turn software, its vendor or a standards participant into the authorized voice of every human affected by the Web.Medium confidence