W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2020

Re: [Technical Errata Reported] RFC7230 (5964)

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 24 Jan 2020 09:29:09 +1100
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Roy Fielding <fielding@gbiv.com>, "Julian F. Reschke" <julian.reschke@greenbytes.de>, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, tpauly@apple.com, ietf-http-wg@w3.org
Message-Id: <6387E079-ED85-4A3F-BD3F-CA71367BEC0E@mnot.net>
To: Rick van Rein <rick@openfortress.nl>
Hi Rick,

I'm saying that those documents are actively under revision now, so the appropriate place to discuss it is in that effort, not as an erratum against the soon-to-be-obsoleted specification.


> On 24 Jan 2020, at 9:26 am, Rick van Rein <rick@openfortress.nl> wrote:
> Hello Mark,
>> This is better filed as an issue on the HTTP core revisions [1] than as an erratum.
>> Recommending REJECT.
>> 1. https://github.com/httpwg/http-core#draft-http-core-documents
> It is a mixture of technically incorrect application of RFC 3986 and
> suggestions how HTTP should handle this; is what you are saying that
> this is too much a mixture?
> I was not sure how to bring this forward, and still am not sure.  I am
> writing a positive alternative in draft-vanrein-http-unauth-user -- is
> that more in line with your take on this?
> Cheers,
> Rick van Rein
> InternetWide.org

Mark Nottingham   https://www.mnot.net/
Received on Thursday, 23 January 2020 22:29:23 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 23 January 2020 22:29:24 UTC