- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Wed, 9 Jul 2025 16:45:04 +0900
- To: Mark Nottingham <mnot@mnot.net>, David Schinazi <dschinazi.ietf@gmail.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Hello Mark, others, Hard doesn't mean impossible, I hope. It may be worth another try. Regards, Martin. On 2025-07-09 16:26, Mark Nottingham wrote: > We asked for that when the original BIS work was done, but it turns out that changing the short name of a WG is Hard. The best we could do was changing the long name to "HTTP Working Group". > > >> On 9 Jul 2025, at 2:48 am, David Schinazi <dschinazi.ietf@gmail.com> wrote: >> >> This revised charter looks good to me. >> >> While you're cleaning up out of date things, any thoughts on updating the WG name? We've already gone past HTTPBIS to HTTPTER, I wouldn't suggest HTTPQUATER or HTTPQUINQUIES but perhaps just "HTTP"? >> >> David >> >> On Mon, Jul 7, 2025 at 10:14 AM Mark Nottingham <mnot@mnot.net> wrote: >> Hello everyone, >> >> Our Area Director noticed that our charter is woefully out of date, and suggested we think about rechartering. After a bit of discussion between the chairs and AD, this is what we're currently suggesting: >> >> ~~~ >> ## HTTP Working Group Charter >> >> This Working Group is charged with maintaining and developing the core specifications for HTTP and generic extensions to it (i.e., those that are not specific to one application). >> >> Beyond specification work, the Working Group is a forum for implementers, practitioners, and researchers to discuss the protocol, its operation and evolution, to improve interoperability and ecosystem health. However, the chairs may ask that some discussions be moved off-list to avoid interfering with specification work. >> >> ### Work Mode >> >> The Working Group may define extensions and other documents related to HTTP as work items, provided that: >> >> * They are generic; i.e., not specific to one application using HTTP. Note that Web browsing by definition is a generic use; >> >> * The Working Group Chairs judge that there is consensus to take on the item; and >> >> * The Area Director is informed of the addition. >> >> Work that may need substantial input from other areas (e.g., Security) should be coordinated through the appropriate bodies (such as the responsible Area Director or a general / 'dispatch' group). >> >> ~~~ >> >> Please take a look and share your thoughts. We'll reserve some time for discussion in Madrid. >> >> Cheers, >> >> >> -- >> Mark Nottingham https://www.mnot.net/ >> >> > > -- > Mark Nottingham https://www.mnot.net/ > > -- Prof. Dr.sc. Martin J. Dürst Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara 252-5258 Japan
Received on Wednesday, 9 July 2025 07:45:18 UTC