Re: [Sip] Support for Multipart/MIME

Paul Kyzivat <pkyzivat@cisco.com> Fri, 11 May 2007 12:25 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmUBP-00061k-00; Fri, 11 May 2007 08:25:15 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HmUBN-00061f-VN for sip-confirm+ok@megatron.ietf.org; Fri, 11 May 2007 08:25:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmUBN-00061X-Ll for sip@ietf.org; Fri, 11 May 2007 08:25:13 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmUBM-0001pF-EZ for sip@ietf.org; Fri, 11 May 2007 08:25:13 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 11 May 2007 08:25:12 -0400
X-IronPort-AV: i="4.14,522,1170651600"; d="scan'208"; a="59984305:sNHT44141524"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l4BCPCoD001522; Fri, 11 May 2007 08:25:12 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l4BCPC5f022965; Fri, 11 May 2007 12:25:12 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 May 2007 08:25:12 -0400
Received: from [10.86.243.60] ([10.86.243.60]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 May 2007 08:25:11 -0400
Message-ID: <464460A6.3060408@cisco.com>
Date: Fri, 11 May 2007 08:25:10 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Support for Multipart/MIME
References: <7374777208BDC7449D5620EF9423256703F85F39@esealmw113.eemea.ericsson.se> <118a01c79372$29fc3da0$c4a36b80@amer.cisco.com> <7374777208BDC7449D5620EF9423256703F85F6E@esealmw113.eemea.ericsson.se> <4643F0E3.5040802@cisco.com> <7374777208BDC7449D5620EF9423256703F8608C@esealmw113.eemea.ericsson.se>
In-Reply-To: <7374777208BDC7449D5620EF9423256703F8608C@esealmw113.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 May 2007 12:25:11.0537 (UTC) FILETIME=[6B8A9E10:01C793C7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1026; t=1178886312; x=1179750312; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20Support=20for=20Multipart/MIME |Sender:=20 |To:=20=22Christer=20Holmberg=20(JO/LMF)=22=20<christer.holmberg@ericsson .com>; bh=+ndUwLmHkfCcGvW0j1TNI9VFUwhgqeonV8KLBdPwa9k=; b=TPwa+zhmJnWXWS0wkuafeJMkWcnA8TIzpI6ZvvvOkTIQqVx6RyVuF/YRIAvOXdwEYzgt9Hu2 xqkiDnXUNmsDXaP0GpgXvXi1hxxbmCfP6TV3BZekOtDRKJTG/usFBn6b;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org


Christer Holmberg (JO/LMF) wrote:

> My point was that you can't determine what types of MIME bodies you have
> simply by taking the whole SIP message and performing a string search on
> "Content-Type". Because, some of the Content-Types you will find may not
> describe what is in a MIME body - it may be part of the MIME body data.

All that you need to do is reduce unnecessary parsing to an acceptable 
degree. If all you care about is sdp, then it is probably sufficient to 
search the body for the string "application/sdp", and only parse the 
body looking for sdp if you find that. Now and then you may encounter a 
body that contains "application/sdp" without actually containing an 
offer or answer. But as long as that is rare there will probably be no 
problem.

This puts the optimization entirely on the parser without requiring any 
changes by those that add bodies. That is a good thing. It also keeps 
the size of the message from increasing further, which is also a good thing.

	Paul


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip