- From: Matthew Kerwin <matthew@kerwin.net.au>
- Date: Sun, 5 Nov 2017 14:15:00 +1000
- To: Andy Green <andy@warmcat.com>
- Cc: Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>, Kazuho Oku <kazuhooku@gmail.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>, HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CACweHNBbDsxTrxzG4_Rp6-DvjXwyi8tVXaZcwkJw_SeBLcHEcg@mail.gmail.com>
On 5 Nov. 2017 12:27 pm, "Andy Green" <andy@warmcat.com> wrote: So maybe that should be recognized, that things wanting to use this new standard may choose not to be able to internalize the values that come, but they must all be able to judge them as able to be internalized or not. Those who want to use this new standard are authors of new header field values, not implementers (who have to honour the header field's definition no matter how it's specified.) And not all new header fields need to use this standard. Cheers -- Matthew Kerwin
Received on Sunday, 5 November 2017 04:15:24 UTC