Amos Jeffries
Asbjørn Ulsberg
Atul Tulshibagwale
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- New issue: Header type for JWT format values
- New issue: Header type for JWT format values
Austin Wright
Ben Schwartz
- CONNECT-TCP: Abrupt stream closure in HTTP/1.1
- Re: AD Review: draft-ietf-httpbis-optimistic-upgrade
- Re: I-D Action: draft-ietf-httpbis-connect-tcp-08.txt
- Re: [External] Register easy-proxy Well-Known URI
- Re: I-D Action: draft-ietf-httpbis-wrap-up-01.txt
- Re: 426 Upgrade: HTTP/3.0
Brian Campbell
Cory Benfield
Daniel Veditz
Darrel Miller
David Benjamin
David Schinazi
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: PTTH (aka Reverse HTTP) BoF in Madrid
- PTTH (aka Reverse HTTP) BoF in Madrid
- Re: Rechartering
Demi Marie Obenour
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Re: Suspected ambiguity in H1 around Expect: 100-continue
Glenn Strauss
- draft-ietf-httpbis-resumable-upload-09: not ready: impl details
- draft-ietf-httpbis-resumable-upload-09: not ready: design
- Re: Suspected ambiguity in H1 around Expect: 100-continue
Hesham ElBakoury
- Re: Updated invitation: Optimum - Developing the Memory Layer for Web3. @ Thu Aug 7, 2025 3:30pm - 4:30pm (PDT) (ietf-http-wg@w3.org)
- Updated invitation: Optimum - Developing the Memory Layer for Web3. @ Thu Aug 7, 2025 2pm - 3pm (PDT) (ietf-http-wg@w3.org)
- Updated invitation: Optimum - Developing the Memory Layer for Web3. @ Thu Aug 7, 2025 3:30pm - 4:30pm (PDT) (ietf-http-wg@w3.org)
- Invitation: Optimum - Developing the Memory Layer for Web3. @ Thu Aug 7, 2025 2pm - 3pm (PDT) (ietf-http-wg@w3.org)
- Re: Rechartering
IETF Meeting Session Request Tool
internet-drafts@ietf.org
- I-D Action: draft-ietf-httpbis-optimistic-upgrade-05.txt
- I-D Action: draft-ietf-httpbis-unencoded-digest-01.txt
- I-D Action: draft-ietf-httpbis-wrap-up-01.txt
- I-D Action: draft-ietf-httpbis-unencoded-digest-00.txt
Jan Schaumann
Julian Reschke
Lars Eggert
Lucas Pardue
- Re: Working Group Last Call: draft-ietf-httpbis-resumable-upload-09
- Re: draft-ietf-httpbis-resumable-upload-09: not ready: impl details
- Re: draft-ietf-httpbis-resumable-upload-09: not ready: design
- Re: Handling multiple Host header fields in HTTP/2 and HTTP/3
- Handling multiple Host header fields in HTTP/2 and HTTP/3
- Re: 426 Upgrade: HTTP/3.0
- Re: Rechartering
Marius Kleidl
Mark Nottingham
- DRAFT minutes from IETF 123 Madrid
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: draft-ietf-httpbis-safe-method-w-body-11 early Httpdir review
- Re: [External] Register easy-proxy Well-Known URI
- Re: Rechartering
- Re: Rechartering
- Rechartering
- Re: draft-ietf-httpbis-safe-method-w-body-11 early Httpdir review
Mark Nottingham via Datatracker
Martin J. Dürst
Martin Thomson
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: New issue: Header type for JWT format values
- Re: Rechartering
Melvin Carvalho
Michael Toomim
Mike Bishop
- Re: Working Group Last Call: draft-ietf-httpbis-resumable-upload-09
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- AD Review: draft-ietf-httpbis-optimistic-upgrade
Nico Williams
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
Poul-Henning Kamp
rachid bouziane
- Draft OODA-HTTP — Behavioral Extension to HTTP (with TLS Runtime Coordination)
- Approval Request – OODA-HTTP Draft Submission to HTTP WG Mailing List
- Draft OODA-HTTP — Behavioral Extension to HTTP (with TLS Runtime Coordination)
Rahul Gupta
RFC Errata System
Ricky Perez
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Binary HTTP [RFC 9292] header name behavior
Rory Hewitt
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
- Re: New issue: Header type for JWT format values
Roy T. Fielding
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: New issue: Header type for JWT format values
- Re: draft-ietf-httpbis-safe-method-w-body-11 early Httpdir review
- Re: 426 Upgrade: HTTP/3.0
Salz, Rich
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: [httpapi] Fw: New Version Notification for draft-gupta-httpapi-events-query-00.txt
Sean McArthur
Steven Bingler
- Re: Secdir telechat review of draft-ietf-httpbis-rfc6265bis-19
- Re: Genart last call review of draft-ietf-httpbis-rfc6265bis-19
- Re: Genart last call review of draft-ietf-httpbis-rfc6265bis-19
The IESG
Tim Bray
- Re: draft-ietf-httpapi-privacy-02 early Httpdir review
- Re: New issue: Header type for JWT format values
Tommy Pauly
- Re: Working Group Last Call: draft-ietf-httpbis-resumable-upload-09
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Re: Binary HTTP [RFC 9292] header name behavior
- Working Group Last Call: draft-ietf-httpbis-resumable-upload-09
- Re: Detecting Outdated Proxy Configuration
Tommy Pauly via Datatracker
Watson Ladd via Datatracker
Willy Tarreau
- Re: Working Group Last Call: draft-ietf-httpbis-resumable-upload-09
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Re: Suspected ambiguity in H1 around Expect: 100-continue
- Suspected ambiguity in H1 around Expect: 100-continue
- Re: DRAFT minutes from IETF 123 Madrid
- Re: Handling multiple Host header fields in HTTP/2 and HTTP/3
- Re: Handling multiple Host header fields in HTTP/2 and HTTP/3
- Re: Rechartering