[sipcore] Content-ID header field not defined in SIP
Ivo Sedlacek <ivo.sedlacek@ericsson.com> Thu, 11 August 2016 17:59 UTC
Return-Path: <ivo.sedlacek@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7B812D8F2 for <sipcore@ietfa.amsl.com>; Thu, 11 Aug 2016 10:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 QvmAV9KiiQGv for <sipcore@ietfa.amsl.com>; Thu, 11 Aug 2016 10:59:38 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E94D612D0DB for <sipcore@ietf.org>; Thu, 11 Aug 2016 10:59:37 -0700 (PDT)
X-AuditID: c1b4fb2d-917ff700000019a3-f3-57acbd078ff8
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by (Symantec Mail Security) with SMTP id 70.73.06563.70DBCA75; Thu, 11 Aug 2016 19:59:36 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.187]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0301.000; Thu, 11 Aug 2016 19:59:35 +0200
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: Content-ID header field not defined in SIP
Thread-Index: AdHz7HbNjd2T8u7kRR29JnCw0ka2hQ==
Date: Thu, 11 Aug 2016 17:59:34 +0000
Message-ID: <39B5E4D390E9BD4890E2B31079006101164C5617@ESESSMB301.ericsson.se>
Accept-Language: en-US, cs-CZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyM2K7pS7H3jXhBt0zOSy+/tjE5sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujP61d1kKDnJWNOw4wNrAeIO9i5GDQ0LAROLzPtMuRi4OIYH1 jBI7f3UwQThLGCXO9Exj7mLk5GAT0JOYuOUIK4gtIqApsfzbVnYQW1jAWGLy8Q1sEHELiYsT PrBA2HoS9xuPMYLYLAKqEr9mTger4RXwlWg7dhmshlFAVuLqn16wGmYBcYlbT+YzgdgSAgIS S/acZ4awRSVePv7HCmErSazYfgmqXkdiwe5PbBC2tsSyha+ZIeYLSpyc+YRlAqPQLCRjZyFp mYWkZRaSlgWMLKsYRYtTi4tz042M9VKLMpOLi/Pz9PJSSzYxAkP54JbfujsYV792PMQowMGo xMO7IHt1uBBrYllxZe4hRgkOZiUR3r871oQL8aYkVlalFuXHF5XmpBYfYpTmYFES5/V/qRgu JJCeWJKanZpakFoEk2Xi4JRqYNQv3Jk/w3q2pcmMytqQxs8XH+ZMe7OE73TYtuecsivnHIqY Pn3x0beyiiG2C/WfxB15u5NxYe91TQebf9VXD3d2J13aly7cdvGglkpEi+V5yXlztl15Iqq/ w+CH5Z9E7pP/RJomzA88qmdQ/ovrUEO0/tlawYjScIsD4Q/WVV4WFIpd9tB4JaMSS3FGoqEW c1FxIgBELotHYQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Mlrg5NQQJ_CJE7st5t6_36pE-OU>
Subject: [sipcore] Content-ID header field not defined in SIP
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 11 Aug 2016 17:59:39 -0000
Hello, The Content-ID header field does not seem to be defined as a *SIP* header field - Content-ID cannot be found in in RFC3261 and Content-ID also cannot be found in http://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml#sip-parameters-2 NOTE: Content-ID header field is defined to be a *MIME multipart/mixed* header field. However, rfc5368 section 7 and Figure 3 describe REFER request: - with a single body (of application/resource-lists+xml MIME type) with a Content-ID *SIP* header field; and - with Refer-To header field referring to the body. Also, it is possible to send an INVITE request *without SDP offer* and with location information according to rfc6442. In such case, the INVITE request: - has a single body (of application/pidf+xml MIME type) with a Content-ID *SIP* header field; and - has Geolocation header field referring to the body. One can of course put a single body inside a multipart/mixed, but that is rather messy. I assume the proper solution is to define the Content-ID header field as *SIP* header field. Is there any support for such definition? If so, I would prepare a draft. Kind regards Ivo Sedlacek
- Re: [sipcore] Content-ID header field not defined… Ranjit Avasarala
- Re: [sipcore] Content-ID header field not defined… Dale R. Worley
- Re: [sipcore] Content-ID header field not defined… Ivo Sedlacek
- Re: [sipcore] Content-ID header field not defined… Drage, Keith (Nokia - GB)
- Re: [sipcore] Content-ID header field not defined… Paul Kyzivat
- [sipcore] Content-ID header field not defined in … Ivo Sedlacek