IETF Logo Mail Archive

Re: [Sip] Support for Multipart/MIME

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Wed, 16 May 2007 08:13 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 1HoEdC-000227-Lh; Wed, 16 May 2007 04:13:10 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HoEdC-00021x-2z for sip-confirm+ok@megatron.ietf.org; Wed, 16 May 2007 04:13:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoEdB-00021o-OF for sip@ietf.org; Wed, 16 May 2007 04:13:09 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoEdA-0000p2-5C for sip@ietf.org; Wed, 16 May 2007 04:13:09 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 9F1D3203B3; Wed, 16 May 2007 10:13:07 +0200 (CEST)
X-AuditID: c1b4fb3e-ad9eabb0000061ca-4c-464abd13b773
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 8610C2009C; Wed, 16 May 2007 10:13:07 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 10:13:07 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 10:13:06 +0200
Received: from [131.160.36.58] (E000FB0F665DD.lmf.ericsson.se [131.160.36.58]) by mail.lmf.ericsson.se (Postfix) with ESMTP id CBE6B2495; Wed, 16 May 2007 11:13:06 +0300 (EEST)
Message-ID: <464ABD12.1010004@ericsson.com>
Date: Wed, 16 May 2007 11:13:06 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Support for Multipart/MIME
References: <7374777208BDC7449D5620EF9423256703F85957@esealmw113.eemea.ericsson.se> <0ee901c7931e$dd43f9b0$c4a36b80@amer.cisco.com> <1ECE0EB50388174790F9694F77522CCF106564B4@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF106564B4@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 May 2007 08:13:06.0980 (UTC) FILETIME=[08AB1E40:01C79792]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>, "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.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

Hi,

> Section 6 would be OK, but now that SDPng is gone, it's irrelevant.

I have seen a few statements like this on the list lately. SIP intends 
to be, by design, session-description-format agnostic. Therefore, we 
need a mechanism that allows endpoints to try and use different 
session-description formats even if SDPng is dead.

Experimenting with new session-description formats is part of the 
innovation process we want to have in SIP.

In short, I do not think such a mechanism is irrelevant only because 
SDPng did not succeed. We still need such a mechanism.

Cheers,

Gonzalo



_______________________________________________
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

v2.23.0 | Report a Bug | By Email