RE: [Sip] Editorial question on MIME example
"Dan Wing" <dwing@cisco.com> Thu, 20 December 2007 17:07 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 1J5OrQ-0000Un-Nf; Thu, 20 Dec 2007 12:07:04 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J5OrO-0000UQ-45 for sip-confirm+ok@megatron.ietf.org; Thu, 20 Dec 2007 12:07:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5OrN-0000UB-QU for sip@ietf.org; Thu, 20 Dec 2007 12:07:01 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5OrN-0005iG-FU for sip@ietf.org; Thu, 20 Dec 2007 12:07:01 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 20 Dec 2007 09:07:01 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lBKH70lW021713; Thu, 20 Dec 2007 09:07:00 -0800
Received: from dwingwxp01 ([10.32.240.198]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id lBKH7032027588; Thu, 20 Dec 2007 17:07:00 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, sip@ietf.org
References: <CA9998CD4A020D418654FCDEF4E707DF03C4FD1B@esealmw113.eemea.ericsson.se><22c301c842e8$fcdb1040$c6f0200a@cisco.com> <CA9998CD4A020D418654FCDEF4E707DF03C50141@esealmw113.eemea.ericsson.se>
Subject: RE: [Sip] Editorial question on MIME example
Date: Thu, 20 Dec 2007 09:07:02 -0800
Message-ID: <2a2301c8432a$bdb65630$c6f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF03C50141@esealmw113.eemea.ericsson.se>
Thread-Index: AchC5DzADDOM9rrzTRaLkpP5dutlHgAAZ98gAAE1sAAAD+au4A==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=757; t=1198170420; x=1199034420; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[Sip]=20Editorial=20question=20on=20MIM E=20example |Sender:=20; bh=Kq+ULRkhQzQsIFw6eft4odUeoNERRP3Cry0Uqrm7Hhc=; b=rvn3hxvFARmz/MM4BObJn41akrTlM98SX34+S8PR41zqwJbleXjTXd9sNB +Twr5WjkIZV3ONfILGE7whu0qJD4i9sX6GXcjatMlfNmIlCt8bacq/ljSQs9 dX2Pg5MeCP;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc:
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
> >I guess you're saying SIP should have used something like > >"Length:" instead of "Content-Length:" to avoid collision > >with MIME's self-claimed ownership of all field names that > >begin with "Content-"? > > No no. > > I am not talking about the usage of Content-Lenght (or any other > Content- header) in the SIP part of the message. I was > referring to the > usage of Content-Length in the MIME part of the message body. Ah - thanks for clarifying. So you are referring to the second Content-Length field in the example at http://tools.ietf.org/html/rfc3261#page-212 -- the Content-Length field with the value 231. I agree it shouldn't be in that example. Looks like something to add to the Essential Corrections. -d _______________________________________________ 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
- [Sip] Editorial question on MIME example Christer Holmberg
- RE: [Sip] Editorial question on MIME example Dan Wing
- RE: [Sip] Editorial question on MIME example Christer Holmberg
- RE: [Sip] Editorial question on MIME example Dan Wing
- RE: [Sip] Editorial question on MIME example Christer Holmberg