| CARVIEW |
Select Language
HTTP/2 200
content-location: ietf_transparency.html.gzip
vary: negotiate,accept-encoding
tcn: choice
last-modified: Sat, 12 Jul 2025 08:31:38 GMT
etag: "623-639b74152cfd3;636054302a84d
content-length: 1571
cache-control: max-age=10800
strict-transport-security: max-age=15552000
content-security-policy: default-src 'self'; img-src 'self' data: *.twitter.com *.twimg.com; style-src 'self' *.twitter.com; script-src 'self' *.twitter.com *.twimg.com; frame-src data: *.twitter.com www.youtube.com; frame-ancestors 'none'; report-uri https://mnot.report-uri.com/r/d/csp/enforce
link: ; rel=preload;as=font;type=font/woff2;crossorigin=anonymous;nopush, ; rel=preload;as=fetch;crossorigin=anonymous;nopush
link: ; rel=preload;as=font;type=font/woff2;crossorigin=anonymous;nopush
content-type: text/html; charset=utf-8
content-encoding: gzip
content-language: en
date: Fri, 10 Oct 2025 10:03:49 GMT
server: Apache
IETF Transparency
mark nottingham
recent entries all entries feed
Hi, I’m Mark Nottingham. I write about the Web, protocol design, HTTP, Internet governance, and more. This is a personal blog, it does not represent anyone else. Find out more.
Comments? Let's talk on Mastodon. @mnot@techpolicy.social
other Standards posts
- The Nature of Internet Standards (series)
- RFC 9518 - What Can Internet Standards Do About Centralisation?
Tuesday, 19 December 2023 - RFC 8890 - The Internet is for End Users
Friday, 28 August 2020 - How to Read an RFC
Tuesday, 31 July 2018
IETF Transparency
Sunday, 10 November 2002
Finally, the IESG puts its money where its mouth is; this tool allows you to see the status and individual AD’s comments about a particular I-D. It’s only a start, but at least you have some idea of what’s going on, instead of being left out in the cold.