* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #8 (closed editorial: fixed)

Opened 7 years ago

Last modified 6 years ago

Media Type Registrations

Reported by: mnot@pobox.com Owned by:
Priority: Milestone: 01
Component: non-specific Severity:
Keywords: Cc:
Origin: http://lists.w3.org/Archives/Public/ietf-http-wg-old/2000SepDec/0013.html

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

comment:1 Changed 7 years ago by fielding@gbiv.com

  • Status changed from new to closed
  • version set to 00
  • Resolution set to fixed
  • Milestone set to 01

Fixed in [74]

comment:2 Changed 7 years ago by mnot@pobox.com

  • version changed from 00 to d00

comment:3 Changed 7 years ago by julian.reschke@gmx.de

From [152]:

Resolve #35: categorize RFC1737 (URN) as informative, RFC4288 (media type registration procedure) as normative (closes #35). Also update and re-organize media type registration for application/http and message/http to use RFC4288 template (relates to #8).

comment:4 Changed 7 years ago by fielding@gbiv.com

  • 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 6 years ago by julian.reschke@gmx.de

  • Origin set to http://lists.w3.org/Archives/Public/ietf-http-wg-old/2000SepDec/0013.html
  • Component changed from p7-auth to non-specific
Note: See TracTickets for help on using tickets.