[sipcore] Content-Disposition questions
Christer Holmberg <christer.holmberg@ericsson.com> Mon, 09 March 2015 12:26 UTC
Return-Path: <christer.holmberg@ericsson.com>
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 3A93B1A887E for <sipcore@ietfa.amsl.com>; Mon, 9 Mar 2015 05:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 D6QPpVlUR3vv for <sipcore@ietfa.amsl.com>; Mon, 9 Mar 2015 05:26:25 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B60A1A8884 for <sipcore@ietf.org>; Mon, 9 Mar 2015 05:26:24 -0700 (PDT)
X-AuditID: c1b4fb2d-f79aa6d00000359d-00-54fd916dd984
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 1E.42.13725.D619DF45; Mon, 9 Mar 2015 13:26:22 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.214]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0210.002; Mon, 9 Mar 2015 13:26:21 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: Content-Disposition questions
Thread-Index: AdBaY9SoDDjiuJSCSNy+9rzo9dcbww==
Date: Mon, 09 Mar 2015 12:26:21 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D73005D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D73005DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+JvjW7exL8hBu3NvBZff2xic2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtlFXawFHdYV21tfsDUwXjTuYuTkkBAwkbjSf4sRwhaTuHBv PVsXIxeHkMARRolZs68xQTiLGSWWztrP2sXIwcEmYCHR/U8bpEFEQFNi+bet7CC2sICaxKOD TewQcW2J2/vmMkPYehJnvq4GW8AioCLRP2UzC4jNK+ArsXTSYjCbEWjx91NrmEBsZgFxiVtP 5jNBHCQgsWTPeWYIW1Ti5eN/rBC2ksSPDZdYIOrzJRbufckEMVNQ4uTMJywTGIVmIRk1C0nZ LCRlEHEdiQW7P7FB2NoSyxa+Zoaxzxx4zIQsvoCRfRWjaHFqcXFuupGxXmpRZnJxcX6eXl5q ySZGYEwc3PJbdwfj6teOhxgFOBiVeHgLrvwJEWJNLCuuzD3EKM3BoiTOa2d8KERIID2xJDU7 NbUgtSi+qDQntfgQIxMHp1QDo1SxgqJ5zJd/mg9tt2ldmtgVcZRRuyyFc/XPx2tTfd1WqZct z+7oWCB+cpGPcP2NSYYRBg/0Jggndz8WKL8Q12x/5OfptS8+/Q8xzHwv9Mtj47LDru4/1Qp3 3A5wbPZv19/24MvBt/waGyK5rPV3yXAal192ZuPnZmnJVLJ9LhgkduJx9j8xJZbijERDLeai 4kQAs9wV7WoCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/yQANMHIvq6hF_W0eV-CbNY6HfWU>
Subject: [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: Mon, 09 Mar 2015 12:26:30 -0000
Hi,
Section 20.11 of RFC 3261 says:
"For backward-compatibility, if the Content-Disposition header field
is missing, the server SHOULD assume bodies of Content-Type
application/sdp are the disposition "session", while other content
types are "render"."
Section 20.11 also says:
"The handling parameter, handling-param, describes how the UAS should
react if it receives a message body whose content type or disposition
type it does not understand. The parameter has defined values of
"optional" and "required". If the handling parameter is missing, the
value "required" SHOULD be assumed. The handling parameter is
described in RFC 3204 [19].
QUESTION_1: If the C-D header field is missing, and the default disposition type value ("render") is assumed, shall then the default handling value ("required") also be assumed?
RFC 3204, which RFC 3261 refers to, says that the default disposition type value for ISUP and QSIG bodies are "signal".
QUESTION_2: If, for a specific message body, the "render" default type can be overwritten, shouldn't that be mentioned in 3261?
Regards,
Christer
- [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