- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Mon, 28 May 2007 21:01:31 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
* Julian Reschke wrote: >> Understanding these documents is required in order to understand the >> coding values defined for the coding registry established and used by >> the document; why would it be appropriate to cite them as informative? >I guess the reasoning is that RFC2616 compliant software does not need to >support content encodings "gzip" or "deflate". But it is not optional to implement them in accordance with the relevant specifications, and the IESG notes in [1]: Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work. ... Note 1: Even references that are relevant only for optional features must be classified as normative if they meet the above conditions for normative references. Unless we change the registry part of the draft in some way, I think the references need to be normative. [1] http://www.ietf.org/IESG/STATEMENTS/iesg-statement-normative-informative-references.txt -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Monday, 28 May 2007 19:01:47 UTC