- From: Mike Bishop <mbishop@evequefou.be>
- Date: Wed, 1 Jul 2026 20:17:31 +0000
- To: Rahul Gupta <cxres@protonmail.com>, Mark Nottingham <mnot@mnot.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>, Tommy Pauly <tpauly@apple.com>
- Message-ID: <IA0PPF726CD7A1FC5E62E58460A079D8F75DAF62@IA0PPF726CD7A1F.namprd22.prod.outlook.>
QUERY does not need to update core HTTP, because the base spec already considers method names an extension point. There's a registry, and there are handling procedures for what to do if you get one you don't understand. QUERY defined and registered a new one, which doesn't change anything about the underlying protocol, hence no Updates. We had a discussion about whether it would need to, because there are some ways in which 9110 treats GET as unique from all other methods; if we'd simply said all of those were now "GET and QUERY", that would have been an update. ________________________________ From: Rahul Gupta Sent: Wednesday, July 1, 2026 6:35 AM To: Mark Nottingham Cc: HTTP Working Group; Tommy Pauly Subject: Re: DRAFT Agenda for IETF 126 Vienna Hi Mark, Thanks for pointing that out :) Please indulge my ignorance here, but does QUERY, RFC10008 update RFC 9110 (the original reason for the comment)? Am I correct in presuming it is not meant to, from the datatracker page? BR/Rahul On Wednesday, July 1st, 2026 at 3:33 PM, Mark Nottingham <mnot@mnot.net> wrote: Hi Rahul, It appears they just missed it; from the linked page: [cid:e579637b5c1c4b2e] Cheers, > On 1 Jul 2026, at 7:53 pm, Rahul Gupta <cxres@protonmail.com<mailto:cxres@protonmail.com>> wrote: > > Hi HTTP Chairs, > > I had come across the following comment on the LWS repo https://github.com/w3c/lws-protocol/pull/179#issuecomment-4846547310 (See the parenthetical, ignore the sarcasm). Essentially the claim is that obsoletes, updates, obsoleted by and updated by labels are not consistent across HTTP WG specifications. > > > I am not sure how RFC labels are updated. But it might be a useful housekeeping exercise to add the missing labels to past and present HTTP WG specifications (assuming you are actually allowed to). > > BR/Rahul > > > On Tuesday, June 30th, 2026 at 12:52 PM, Mark Nottingham <mnot@mnot.net<mailto:mnot@mnot.net>> wrote: > >> ... is at: >> https://httpwg.org/wg-materials/ietf126/agenda.html >> > >> If you have suggestions for other topics, please bring them to the list. Keep in mind both the scope of our charter, and our preference for mailing list discussion (and ideally a draft) first. >> > >> Cheers, >> > >> -- >> Mark Nottingham https://mnot.net/ >> > >> > >> > <publickey - cxres@protonmail.com<mailto:cxres@protonmail.com> - 0x0CEC7748.asc> -- Mark Nottingham https://mnot.net/
Attachments
- image/png attachment: utf-8__Screenshot_2026-07-01_at_8.00.30_pm.png
Received on Wednesday, 1 July 2026 20:17:42 UTC