Re: [sipcore] Content-Disposition questions
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 10 March 2015 14:51 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06AA71A893B for <sipcore@ietfa.amsl.com>; Tue, 10 Mar 2015 07:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iclxw2bPXT-N for <sipcore@ietfa.amsl.com>; Tue, 10 Mar 2015 07:51:08 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E06301A8930 for <sipcore@ietf.org>; Tue, 10 Mar 2015 07:51:06 -0700 (PDT)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-08v.sys.comcast.net with comcast id 1qpL1q0022EPM3101qr6HF; Tue, 10 Mar 2015 14:51:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-07v.sys.comcast.net with comcast id 1qr51q00S3Ge9ey01qr5dW; Tue, 10 Mar 2015 14:51:05 +0000
Message-ID: <54FF04D9.7020609@alum.mit.edu>
Date: Tue, 10 Mar 2015 10:51:05 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: sipcore@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D73005D@ESESSMB209.ericsson.se> <F81CEE99482EFE438DAE2A652361EE121E2B6D17@MCHP04MSX.global-ad.net> <7594FB04B1934943A5C02806D1A2204B1D7335FB@ESESSMB209.ericsson.se> <F81CEE99482EFE438DAE2A652361EE121E2B7B82@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE121E2B7B82@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1425999066; bh=4PMglSaC0CkkOJ55EHRQcuFx0MsKdsmKm6NIc4bLDsI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=s4BP5JDpZCxcJMW0+/bdejy3xHYg6o/e074hPNUTJKW+6smdvg/RAlav01Ydt5eNj BSh0ejLse4pYJIYlwH2q3wI4O84lr56TzcLySLp7DFrcQGofANS995N7tl1aT0Lp+R OtM8VmXxTWIYR4YjbQoyz6JK22jOaJ4gsU2rgdQTXcWL+rqpUSZ04HC/IiqTNQYspM gTgxZ58Q/RgmFvRDx+RmRD+EF2n08SWc3YbHTT4WLcDXQSOhvoD1E3GwUS2bxABc04 t2duS1uovtj4vA+wXR/5wpkHgW+7sMsl8aYZgRTqtYenuak/XxLvk73eIYNjgGidEU 8qA1mvUOZcEMg==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/4i5w1Y_NGkXtxlz1FMBiow34dBI>
Subject: Re: [sipcore] Content-Disposition questions
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2015 14:51:09 -0000
On 3/10/15 5:45 AM, Stach, Thomas wrote: >> QUESTION_2: If, for a specific message body, the "render" default type can be >> overwritten, shouldn't that be mentioned in 3261? > > I think this is already written down. The last sentence in section 20.11 reads > " If this header field is missing, the MIME type determines the default > content disposition. If there is none, "render" is assumed." > > So, if the MIME type is understood, the default disposition from the > corresponding MIME definition applies. Of course, this default disposition > can be overwritten by sending a corresponding C-D header field, as e.g. ECMA-355 does for "qsig". > "render" kicks in, only if the MIME type is not understood and if C-D is omitted. > Does this make sense? That has a problem. It makes no sense to define a default handling parameter value for a specific mime type that applies when the C-D isn't present. Suppose you define a mime type where the default handling is "optional". Then a receiver that does understand the mime type will treat the handling as optional, but that is irrelevant because this only applies if the mime type is not understood. A receiver that does not understand the mime type will use the global default handling value "required". Thanks, Paul
- [sipcore] Content-Disposition questions Christer Holmberg
- Re: [sipcore] Content-Disposition questions Paul Kyzivat
- Re: [sipcore] Content-Disposition questions Christer Holmberg
- Re: [sipcore] Content-Disposition questions Stach, Thomas
- Re: [sipcore] Content-Disposition questions Christer Holmberg
- Re: [sipcore] Content-Disposition questions Stach, Thomas
- Re: [sipcore] Content-Disposition questions Paul Kyzivat
- Re: [sipcore] Content-Disposition questions Christer Holmberg
- Re: [sipcore] Content-Disposition questions Paul Kyzivat
- Re: [sipcore] Content-Disposition questions Stach, Thomas
- Re: [sipcore] Content-Disposition questions Christer Holmberg