Mark Nottingham
Pronouns: he/him
Mark Nottingham has contributed to the design and maintenance of core Internet technologies for more than twenty-five years, focusing on HTTP, URLs, RSS/Atom, and QUIC. He has written more than thirty IETF RFCs and W3C Recommendations.
As Chair of the HTTP Working Group since 2007, he oversees the evolution of the foundational protocol of the Web. As Chair of the QUIC Working Group, he shepherded the evolution of Internet transport. He has previously served in leadership positions including the W3C Board of Directors, the Internet Architecture Board, and the W3C Technical Architecture Group.
Mark holds a Graduate Diploma of Communications Law from Melbourne Law School and is a Member of the Australian Institute of Company Directors. Currently, he is Standards Lead at Cloudflare and lives in Prahran, Australia.
Roles
Role | Group | |
---|---|---|
Chair | HTTP (httpbis) | mnot@mnot.net |
Chair | HTTP Directorate (httpdir) | mnot@mnot.net |
Chair | IAB Workshop on AI-CONTROL (aicontrolws) | mnot@mnot.net |
Chair | AI Preferences (aipref) | mnot@mnot.net |
Lead | Environmental Impacts of Internet Technology (eimpact) | mnot@mnot.net |
Member | Internet Architecture Board (iab) | mnot@mnot.net |
Member | IAB-ISOC Policy Coordination (iabisoc) | mnot@mnot.net |
Reviewer | HTTP Directorate (httpdir) | mnot@mnot.net |
Secretary | Building Blocks for HTTP APIs (httpapi) | mnot@mnot.net |
Secretary | HTTP Directorate (httpdir) | mnot@mnot.net |
External Resources
Name | Value |
---|---|
My Internet-Drafts | https://github.com/mnot/I-D |
GitHub Username | mnot |
My Home Page | https://www.mnot.net |
RFCs (40)
RFC | Date | Title | Cited by |
---|---|---|---|
RFC 3864 | Sep 2004 | Registration Procedures for Message Header Fields | 53 RFCs |
RFC 3902 | Sep 2004 | The "application/soap+xml" media type | 1 RFC |
RFC 4229 | Dec 2005 | HTTP Header Field Registrations | |
RFC 4287 | Dec 2005 | The Atom Syndication Format | 23 RFCs |
RFC 5005 | Sep 2007 | Feed Paging and Archiving | 3 RFCs |
RFC 5785 | Apr 2010 | Defining Well-Known Uniform Resource Identifiers (URIs) | 28 RFCs |
RFC 5861 | May 2010 | HTTP Cache-Control Extensions for Stale Content | 4 RFCs |
RFC 5988 | Oct 2010 | Web Linking | 29 RFCs |
RFC 6570 | Mar 2012 | URI Template | 19 RFCs |
RFC 6585 | Apr 2012 | Additional HTTP Status Codes | 11 RFCs |
RFC 6648 | Jun 2012 | Deprecating the "X-" Prefix and Similar Constructs in Application Protocols | 14 RFCs |
RFC 6901 | Apr 2013 | JavaScript Object Notation (JSON) Pointer | 7 RFCs |
RFC 6902 | Apr 2013 | JavaScript Object Notation (JSON) Patch | 3 RFCs |
RFC 7234 | Jun 2014 | Hypertext Transfer Protocol (HTTP/1.1): Caching | 39 RFCs |
RFC 7320 | Jul 2014 | URI Design and Ownership | 9 RFCs |
RFC 7807 | Mar 2016 | Problem Details for HTTP APIs | 9 RFCs |
RFC 7838 | Apr 2016 | HTTP Alternative Services | 13 RFCs |
RFC 8164 | May 2017 | Opportunistic Security for HTTP/2 | 5 RFCs |
RFC 8288 | Oct 2017 | Web Linking | 19 RFCs |
RFC 8336 | Mar 2018 | The ORIGIN HTTP/2 Frame | 3 RFCs |
RFC 8470 | Sep 2018 | Using Early Data in HTTP | 7 RFCs |
RFC 8586 | Apr 2019 | Loop Detection in Content Delivery Networks (CDNs) | 2 RFCs |
RFC 8615 | May 2019 | Well-Known Uniform Resource Identifiers (URIs) | 11 RFCs |
RFC 8674 | Dec 2019 | The "safe" HTTP Preference | |
RFC 8752 | Mar 2020 | Report from the IAB Workshop on Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE) | 1 RFC |
RFC 8820 | Jun 2020 | URI Design and Ownership | 2 RFCs |
RFC 8890 | Aug 2020 | The Internet is for End Users | 2 RFCs |
RFC 8941 | Feb 2021 | Structured Field Values for HTTP | 8 RFCs |
RFC 8959 | Jan 2021 | The "secret-token" URI Scheme | |
RFC 9110 | Jun 2022 | HTTP Semantics | 18 RFCs |
RFC 9111 | Jun 2022 | HTTP Caching | 8 RFCs |
RFC 9112 | Jun 2022 | HTTP/1.1 | 7 RFCs |
RFC 9205 | Jun 2022 | Building Protocols with HTTP | 1 RFC |
RFC 9209 | Jun 2022 | The Proxy-Status HTTP Response Header Field | 1 RFC |
RFC 9211 | Jun 2022 | The Cache-Status HTTP Response Header Field | |
RFC 9213 | Jun 2022 | Targeted HTTP Cache Control | |
RFC 9457 | Jul 2023 | Problem Details for HTTP APIs | |
RFC 9518 | Dec 2023 | Centralization, Decentralization, and Internet Standards | |
RFC 9651 | Sep 2024 | Structured Field Values for HTTP | |
RFC 9652 | Sep 2024 | The Link-Template HTTP Header Field |
Active Internet-Drafts (6)
- draft-ietf-httpbis-cache-groups
- draft-ietf-httpapi-link-hint
- draft-nottingham-public-resolver-errors
- draft-ietf-mediaman-6838bis
- draft-iab-ai-control-report
- draft-mediaman-6838bis
Expired Internet-Drafts (86)
- draft-nottingham-http-availability-hints
- draft-ietf-mediaman-standards-tree
- draft-nottingham-gateway-description
- draft-nottingham-http-invalidation
- draft-nottingham-gendispatch-discuss-criteria
- draft-cooper-policy-interactions
- draft-ietf-httpbis-retrofit
- draft-nottingham-iesg-review-workload
- draft-nottingham-binary-structured-headers
- draft-nottingham-feed-privacy
- draft-ietf-httpbis-variants
- draft-nottingham-scheduling-online-meetings
- draft-nottingham-where-does-that-come-from
- draft-nottingham-cache-trailers
- draft-nottingham-http-grease
- draft-nottingham-discussion-recharter
- draft-nottingham-bikeshed-length
- draft-arkko-iab-internet-consolidation
- draft-nottingham-doh-digests
- draft-ietf-httpbis-key
- draft-nottingham-wugh-services
- draft-nottingham-json-home
- draft-nottingham-httpbis-retry
- draft-nottingham-site-wide-headers
- draft-nottingham-capport-problem
- draft-nottingham-proxy-explanation
- draft-nottingham-transport-metadata-impact
- draft-nottingham-rss-media-type
- draft-nottingham-stakeholder-rights
- draft-nottingham-web-proxy-desc
- draft-nottingham-gin
- draft-nottingham-http-proxy-problem
- draft-nottingham-http-over-version
- draft-nottingham-http2-ops
- draft-nottingham-http-patch-status
- draft-nottingham-http-browser-hints
- draft-nottingham-linked-cache-inv
- draft-nottingham-registry-custodian
- draft-nottingham-appsawg-happiana
- draft-nottingham-http-pipeline
- draft-nottingham-http-portal
- draft-nottingham-atomtriples
- draft-nottingham-http-stale-if-error
- draft-nottingham-http-stale-while-revalidate
- draft-nottingham-atompub-fiql
- draft-nottingham-http-cache-channels
- draft-nottingham-http-poe
- draft-nottingham-dns-media-tree
- draft-nottingham-rss2
- draft-nottingham-http-auth-cache
- draft-nottingham-webi-warm
- draft-nottingham-http-header-reg
- draft-ietf-webi-idd-reqs
- draft-nottingham-cache-extensions
- draft-nottingham-surrogates
- draft-nottingham-http-roles