Re: [Ietf-message-headers] Content-Disposition
Julian Reschke <julian.reschke@gmx.de> Thu, 05 June 2008 16:35 UTC
Return-Path: <ietf-message-headers-bounces@ietf.org>
X-Original-To: ietf-message-headers-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-message-headers-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79D8C3A69AC; Thu, 5 Jun 2008 09:35:26 -0700 (PDT)
X-Original-To: ietf-message-headers@core3.amsl.com
Delivered-To: ietf-message-headers@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1466C3A6C77 for <ietf-message-headers@core3.amsl.com>; Wed, 4 Jun 2008 05:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.145
X-Spam-Level:
X-Spam-Status: No, score=-4.145 tagged_above=-999 required=5 tests=[AWL=-1.546, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SWFGitsQ4GCE for <ietf-message-headers@core3.amsl.com>; Wed, 4 Jun 2008 05:00:46 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 117603A6CB9 for <ietf-message-headers@ietf.org>; Wed, 4 Jun 2008 05:00:26 -0700 (PDT)
Received: (qmail invoked by alias); 04 Jun 2008 12:00:29 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp004) with SMTP; 04 Jun 2008 14:00:29 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+e1B9CIK+ebBUUh8lZ5VF63YimbaxiMeqL8kf6Je /b+HpICO0yiimD
Message-ID: <484683DB.5010601@gmx.de>
Date: Wed, 04 Jun 2008 14:00:27 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
References: <484571F3.8050302@gmx.de> <g25ot0$s7s$1@ger.gmane.org> <484668CD.1090007@gmx.de> <g25vnv$j4g$1@ger.gmane.org>
In-Reply-To: <g25vnv$j4g$1@ger.gmane.org>
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Thu, 05 Jun 2008 09:35:26 -0700
Cc: ietf-message-headers@ietf.org, ietf-http-wg@w3.org
Subject: Re: [Ietf-message-headers] Content-Disposition
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ietf-message-headers>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-message-headers-bounces@ietf.org
Errors-To: ietf-message-headers-bounces@ietf.org
Frank Ellermann wrote: > ... > Reading it again, RFC 3864 from start to end tries to explain > why *redefining* MIME Content-* header fields in individual > protocols can be a seriously flawed idea. And it says that > the "status" for a permanent entry is set according to the > primary document defining it. > > IMO for a standards track RFC the default should be "standard". > Obviously it can be "deprecated" when the standard(s) say so, > e.g., "Lines". Maybe a standard can also say "informational", > but I think it's not the intention of RFC 3834: > > Forwarding to the message header list, Graham would know what > RFC 3864 wanted, and if a minor twist is okay or confusing. > ... Thanks. I just want to make sure that there is consistency; and RFC2616 currently makes it clear that although it contains documentation about C-D, it's not to be considered part of the HTTP standard. BR, Julian _______________________________________________ Ietf-message-headers mailing list Ietf-message-headers@ietf.org https://www.ietf.org/mailman/listinfo/ietf-message-headers
- Re: [Ietf-message-headers] Content-Disposition Julian Reschke