RE: [Sip] Editorial question on MIME example

"Christer Holmberg" <christer.holmberg@ericsson.com> Fri, 21 December 2007 10:52 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 1J5fUh-0004Xw-Iv; Fri, 21 Dec 2007 05:52:43 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J5fUg-0004Xp-8b for sip-confirm+ok@megatron.ietf.org; Fri, 21 Dec 2007 05:52:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5fUf-0004Xh-V6 for sip@ietf.org; Fri, 21 Dec 2007 05:52:41 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5fUf-0004VF-H5 for sip@ietf.org; Fri, 21 Dec 2007 05:52:41 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E62C720B42; Fri, 21 Dec 2007 11:52:40 +0100 (CET)
X-AuditID: c1b4fb3c-b0798bb0000030cf-a0-476b9af841d4
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id C239C20857; Fri, 21 Dec 2007 11:52:40 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 21 Dec 2007 11:52:40 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Editorial question on MIME example
Date: Fri, 21 Dec 2007 11:52:39 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF03CCE8AE@esealmw113.eemea.ericsson.se>
In-Reply-To: <2a2301c8432a$bdb65630$c6f0200a@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Editorial question on MIME example
Thread-Index: AchC5DzADDOM9rrzTRaLkpP5dutlHgAAZ98gAAE1sAAAD+au4AAlSJDQ
References: <CA9998CD4A020D418654FCDEF4E707DF03C4FD1B@esealmw113.eemea.ericsson.se><22c301c842e8$fcdb1040$c6f0200a@cisco.com><CA9998CD4A020D418654FCDEF4E707DF03C50141@esealmw113.eemea.ericsson.se> <2a2301c8432a$bdb65630$c6f0200a@cisco.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Dan Wing <dwing@cisco.com>, sip@ietf.org
X-OriginalArrivalTime: 21 Dec 2007 10:52:40.0645 (UTC) FILETIME=[9B7BB750:01C843BF]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

Hi, 

>>>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. 

Yes.

>I agree it shouldn't be in that example.  Looks like something to add
to 
>the Essential Corrections.

Ok.

Thanks!

Regards,

Christer


_______________________________________________
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