- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Thu, 13 Oct 2016 06:23:59 +0000
- To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- cc: HTTP working group mailing list <ietf-http-wg@w3.org>, Martin Thomson <martin.thomson@gmail.com>
-------- In message <20161013042318.8C70F166C2@welho-filter4.welho.com>, Kari Hurtta wri tes: >So *new* header fields are form > >new-field: >value< > >where syntax of value is h1_common_structure. Yes. >> But if this draft goes forward, the WG essentially promises "This >> is the last header field parser/serializer we ever ask you to write, >> and you can already use it for these 19 headers". > >And you can autodetect that syntax from new header fields because > and < -characters. > >This was idea, right? Yes, exactly. That means installations can have private headers also in common structure without having to register those with IANA etc. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 13 October 2016 06:24:30 UTC