Opened 11 years ago

Closed 9 years ago

#122 closed editorial (fixed)

MIME-Version not listed in P1, general header fields

Reported by: julian.reschke@… Owned by: julian.reschke@…
Priority: normal Milestone: 11
Component: p3-payload Severity: Active WG Document
Keywords: Cc:

Description

Part 1, Section 4.5, currently doesn't list MIME-Version, defined in Part 3. Minimally, it should be added to the list.

Q: maybe its definition should be moved completely into Part 1?

Attachments (1)

i122.diff (4.7 KB) - added by julian.reschke@… 9 years ago.
proposed patches for P1 & P3 plus the IANA header reg extraction (this will also cause Content-Disposition to be listed as "standard")

Download all attachments as: .zip

Change History (16)

comment:1 Changed 11 years ago by mnot@…

  • Milestone changed from unassigned to 06
  • Type changed from design to editorial

Instruct IANA to remove the http-specific MIME-Version header from the registry.

comment:2 Changed 10 years ago by julian.reschke@…

  • Milestone changed from 06 to 08

comment:3 Changed 10 years ago by julian.reschke@…

  • Priority set to normal
  • Get rid of MIME-Version in Part 3.
  • Instruct IANA to remove it as HTTP header
  • augment relation to MIME appendix to explain non-http MIME headers in HTTP messages

comment:4 Changed 10 years ago by julian.reschke@…

  • Milestone changed from 08 to 09

comment:5 Changed 10 years ago by julian.reschke@…

  • Milestone changed from 09 to 10

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

1) just do it 2) add this to the IANA considerations

comment:7 Changed 9 years ago by julian.reschke@…

comment:8 Changed 9 years ago by julian.reschke@…

Back to the drawing board; see <http://tools.ietf.org/html/rfc3864#section-4.5>:

It is intended that entries in the Permanent Message Header Field Registry may be used in the construction of URNs (per RFC 2141 [13]) which have particular requirements for uniqueness and persistence (per RFC 1737 [8]). Therefore, once an entry is made in the Permanent Message Header Registry, the combination of the header name and applicable protocol MUST NOT subsequently be registered for any other purpose. (This is not to preclude revision of the applicable specification(s) within the appropriate IETF Consensus rules, and corresponding updates to the specification citation in the header registration.)

So if we want to change the registry all we can do update it.

comment:9 Changed 9 years ago by mnot@…

I'm not too worried about counting the angels to determine whether or not this is a HTTP header. P3 A.1 says:

   HTTP is not a MIME-compliant protocol.  However, HTTP/1.1 messages
   MAY include a single MIME-Version general-header field to indicate
   what version of the MIME protocol was used to construct the message.
   Use of the MIME-Version header field indicates that the message is in
   full compliance with the MIME protocol (as defined in [RFC2045])

.

Note that it's described as a general-header field.

I propose we just update the registration, point to the appropriate part (wherever it ends up) and allow people to dereference it to get to this text if they're interested.

comment:10 Changed 9 years ago by julian.reschke@…

  • Component changed from p1-messaging to p3-payload
  • Owner set to julian.reschke@…

Changed 9 years ago by julian.reschke@…

proposed patches for P1 & P3 plus the IANA header reg extraction (this will also cause Content-Disposition to be listed as "standard")

comment:11 Changed 9 years ago by julian.reschke@…

  • Milestone changed from 10 to 11

comment:12 Changed 9 years ago by julian.reschke@…

From [937]:

add MIME-Version to the ist of general header fields (see #122)

comment:13 Changed 9 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from new to closed

comment:14 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:15 Changed 9 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.