Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9681] New: Support interpreting message/cpim (RFC3862)

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9681
Summary	Support interpreting message/cpim (RFC3862)
Classification	Unclassified
Product	Wireshark
Version	1.10.5
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Enhancement
Priority	Low
Component	Dissection engine (libwireshark)
Assignee	bugzilla-admin@wireshark.org
Reporter	druit@druit.net

Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.

Running on 32-bit Windows 7 Service Pack 1, build 7601, without WinPcap, GnuTLS
2.12.18, Gcrypt 1.4.6, without AirPcap,  from the PortableApps U3 device in
drive C:.
       Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, with 3333MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
Motivation:
Services like RCS, standardized by GSMA, [1] make use of the MIME type
message/cpim in the SIP INVITE Message body.
The structure of this MIME encapsulation is done according to [2].
In addition, MSRP is used in combination with CPIM in RCS / RCSe.

Request:
The dissector library should identify "message/cpim" as a known content type
and split the following data according to the RFC, chapter 2, into two blocks: 
a) Message/CPIM MIME header
b) Message/CPIM message body

In the header section, each "key: value" pair should be displayed as a separate
line in the wireshark packet details pane.

An RCS SIP example (for with file transfer via CPIM) could look like:

-----------------
INVITE tel:+491621300000 SIP/2.0
Via: SIP/2.0/UDP
10.150.209.115:44859;rport;branch=z9hG4bKPjPT06095OtfRzdKMzBEu.nRsucXX3Oiyu
Max-Forwards: 70
From: <tel:+491735610000>;tag=JPndacvaX3FT7dMVpNcEhAL8MpQPMSJu
To: <tel:+491621300000>
Contact:
<sip:+491735612467@10.150.209.115:44859;ob>;+g.oma.sip-im;+sip.instance="<urn:gsma:imei:36684405-239596-0>"
Call-ID: w8RFSwfhzXFyAt.QOq4SFksz8ikSjhRU
CSeq: 25486 INVITE
Route: <sip:188.7.154.88:5090;transport=udp;lr>
Allow: PRACK, INFO, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER,
MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
Accept-Contact: *;+g.oma.sip-im
User-Agent: IM-client/OMA1.0 RCSAndrd/3.3.10 - COMLib/2.4.19
P-Preferred-Identity: <tel:+491735610000>
P-Preferred-Identity: <sip:+491735610000@rcse.examplecom.de>
Content-Type: multipart/mixed;boundary="boundary22"
Content-Length:  1582

--boundary22
Content-Type: application/sdp

v=0
o=- 3598766269 3598766269 IN IP4 10.150.209.115
s= 
c=IN IP4 10.150.209.115
t=0 0
m=message 9 TCP/MSRP *
a=setup:active
a=accept-types:message/cpim application/im-iscomposing+xml
a=path:msrp://10.150.209.115:9/n4O00avUAL;tcp
a=sendrecv
a=accept-wrapped-types:text/plain application/vnd.gsma.rcspushlocation+xml
message/imdn+xml application/vnd.gsma.rcs-ft-http+xml

--boundary22
Content-Type: message/cpim

From: <sip:anonymous@anonymous.invalid>
To: <sip:anonymous@anonymous.invalid>
DateTime: 2014-01-15T10:17:49.727+01:00
NS: imdn <urn:ietf:params:imdn>
imdn.Message-ID: 7QsgkAl8QZvr9XPFtiiCtLj3sls0oNok
imdn.Disposition-Notification: positive-delivery, display

Content-Type: application/vnd.gsma.rcs-ft-http+xml
Content-Length: 748

<?xml version="1.0" encoding="UTF-8"?>
<file>
      <file-info type="thumbnail">
            <file-size>8555</file-size>
<content-type>$ {thumbnail.content_type}</content-type>
            <data
url="" href="https://ftcontentserver.org/fsf-437a150d-fbac-4fb9-a54b-991505e6d1b0">https://ftcontentserver.org/fsf-437a150d-fbac-4fb9-a54b-991505e6d1b0"
until="2014-01-23T10:17:17+0100" />
      </file-info>
      <file-info type="file">
            <file-size>28011</file-size>
             <file-name>card_save_1381759223212.png</file-name>
             <content-type>image/png</content-type>
            <data
url="" href="https://ftcontentserver.org/fsf-e16f7095-ab4d-4dbf-8e15-c28bb04daf77">https://ftcontentserver.org/fsf-e16f7095-ab4d-4dbf-8e15-c28bb04daf77"
until="2014-01-23T10:17:18+0100" />
      </file-info>
</file>

--boundary22--
-----------------



[1] RCS specification,
http://www.gsma.com/futurecommunications/rcs/specs-and-product-docs/
[2] RFC 3862, Common Presence and Instant Messaging (CPIM): Message Format,
http://tools.ietf.org/search/rfc3862

---

      You are receiving this mail because:

• You are watching all bug changes.