#8 closed editorial (fixed)
Media Type Registrations
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | Milestone: | 01 | |
Component: | non-specific | Severity: | |
Keywords: | Cc: |
Description
In the description of Internet Media Types in [section 3.7], the wrong RFC is cited for the media type registration process. The text says:
Media-type values are registered with the Internet Assigned Number Authority (IANA [19]). The media type registration process is outlined in RFC 4288 [17]. Use of non-registered media types is discouraged.
But should be:
Media-type values are registered with the Internet Assigned Number Authority (IANA [19]). The media type registration process is outlined in RFC 2048 [17]. Use of non-registered media types is discouraged.
The cited Reference [section 17] is also incorrect; it is:
[17] Postel, J., "Media Type Registration Procedure", RFC 1590,
November 1996.
(oddly, the date cited is wrong for that RFC and correct for the right one) It should be:
[17] Freed, N., Klensin, J., and Postel, J., "Mulitpurpose Internet Mail
Extensions (MIME) Part Four: Registration Procedure", RFC 2048,
November 1996.
Change History (5)
comment:1 Changed 15 years ago by fielding@…
- Milestone set to 01
- Resolution set to fixed
- Status changed from new to closed
- version set to 00
comment:2 Changed 15 years ago by mnot@…
- version changed from 00 to d00
comment:3 Changed 15 years ago by julian.reschke@…
comment:4 Changed 15 years ago by fielding@…
- Component set to auth
RFC4288 is not normative -- it specifies an administrative procedure, not a protocol, and thus does not set any HTTP requirements.
comment:5 Changed 14 years ago by julian.reschke@…
- Component changed from p7-auth to non-specific
- origin set to http://lists.w3.org/Archives/Public/ietf-http-wg-old/2000SepDec/0013.html
Fixed in [74]