- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 19 May 2020 22:20:43 +1000
- To: "Julian F. Reschke" <julian.reschke@gmx.de>
- Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, draft-ietf-httpbis-header-structure@ietf.org, httpbis-chairs@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Tommy Pauly <tpauly@apple.com>
On 19 May 2020, at 8:04 pm, Julian Reschke <julian.reschke@gmx.de> wrote: > > It really doesn't help a lot with the case of: > > Foo: > > What's the point in disallowing this in the ABNF (and on the wire) when > the normative parsing algorithm will accept it? As has been said many times, the ABNF in the specification is not normative; it's illustrative. The proposed edit clarifies that. If that's still felt to be confusing, the right thing to do would be to remove ABNF from the spec completely, to avoid the confusion. I'm happy to do that if the IESG wishes so. Julian, you've had many opportunities to bring this up before (having participated in the original issue about empty lists). It would have been much more helpful if you'd expressed your concerns earlier -- even during WGLC -- instead of after IETF LC. Regards, -- Mark Nottingham https://www.mnot.net/
Received on Tuesday, 19 May 2020 12:21:13 UTC