Protocol Action: Content-type header field for Internet messages to Historic

The IESG <iesg-secretary@ietf.org> Mon, 02 November 1998 16:25 UTC

Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id LAA19311 for ietf-123-outbound.10@ietf.org; Mon, 2 Nov 1998 11:25:02 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA19272; Mon, 2 Nov 1998 11:24:23 -0500 (EST)
Message-Id: <199811021624.LAA19272@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Content-type header field for Internet messages to Historic
Date: Mon, 02 Nov 1998 11:24:23 -0500
Sender: scoya@ns.cnri.reston.va.us


The IESG has approved reclassifying RFC 1049, Content-type header field
for Internet messages as Historic.

The IESG contact persons are Keith Moore and Patrik Faltstrom.

 
Technical Summary
 
 RFC 1049 describes an early means of including arbitrary typed
 (not just text) content to the RFC 822 message format.  Use of
 the content-type header field described in RFC 1049 has been
 almost entirely superseded in practice by the MIME standards,
 which use the content-type header field in a different way.

Working Group Summary

 All of the Last Call comments were supportive of moving this
 document to Historic.

Protocol Quality

 Keith Moore reviewed the spec for IESG.

Protocol Action: Content-type header field for In… The IESG