Wireshark-bugs: [Wireshark-bugs] [Bug 9681] Support interpreting message/cpim (RFC3862)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 14 Mar 2014 12:18:07 +0000

Comment # 5 on bug 9681 from 
First help would be to have the header values for the CPIM block separated from
the XML part.
The header contains the important information in the Content-type. The trace
analyst needs to know the TYPE that is in the CPIM message and in the second
step he/she needs to know the CONTENT itself.
So, a first implementation only for the headers as described in detail in RFC
3862 would be very helpful.

The XML schema for vnd.gsma.rcs-ft-http+xml is descibed in more detail in [1],
chapter ID_4_13.

Looking forward to your output and first compilations to test it,

Daniel



[1] GSMA RCS IOT joyn Blackbird Implementation Guidelines, Version 1.0, 15
November 2013,
http://www.gsma.com/network2020/wp-content/uploads/2012/10/joyn_Blackbird_Implementation_guidelines_v1_0_15_11_13.pdf

You are receiving this mail because:
  • You are watching all bug changes.