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

Ticket #55 (closed editorial: fixed)

Opened 9 years ago

Last modified 9 years ago

Updating to RFC4288

Reported by: mnot@pobox.com Owned by: fielding@gbiv.com
Priority: Milestone: 02
Component: non-specific Severity:
Keywords: Cc:
Origin: http://www.w3.org/mid/459E5791.10305@gmx.de


The update from RFC2048 to RFC4288 requires minor modifications for the media type registrations for "message/http", "application/http" and "multipart/byteranges".

Change History

comment:1 Changed 9 years ago by mnot@pobox.com

  • Component set to non-specific
  • Milestone set to unassigned

comment:2 Changed 9 years ago by fielding@gbiv.com

  • Owner set to fielding@gbiv.com
  • Status changed from new to assigned
  • Milestone changed from unassigned to 02

comment:3 Changed 9 years ago by julian.reschke@greenbytes.de

The modifications were done in [152], but it wouldn't hurt to review them (and maybe fill out the "Applications that use this media type:" field (see <http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-01#appendix-A>).

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

From [197]:

RFC4288 is not a normative ref; related to #55

comment:5 Changed 9 years ago by fielding@gbiv.com

  • Status changed from assigned to closed
  • Resolution set to fixed

The templates look fine. I don't have a list of applications. The types are primarily used for archives of message traffic and some forms of protocol encapsulation.

I made the same changes to p5 for multipart/byteranges in [196]. Note that 4288 is not a normative dependency [197].

I don't think that there is anything more we need to do here, so i am closing the issue.

comment:6 Changed 9 years ago by julian.reschke@gmx.de

From [200]:

Note changes wrt to RFC4288, make reference to RFC4288 informative in Part 3, too; related to #55.

Note: See TracTickets for help on using tickets.