RE: [Sip] Support for Multipart/MIME

"Dan Wing" <dwing@cisco.com> Tue, 29 May 2007 19:38 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 1Ht7W9-0005rM-5U; Tue, 29 May 2007 15:38:05 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Ht7W7-0005rG-HO for sip-confirm+ok@megatron.ietf.org; Tue, 29 May 2007 15:38:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht7W7-0005r8-7e for sip@ietf.org; Tue, 29 May 2007 15:38:03 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ht7W5-0005al-Td for sip@ietf.org; Tue, 29 May 2007 15:38:03 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-5.cisco.com with ESMTP; 29 May 2007 12:37:57 -0700
X-IronPort-AV: i="4.14,589,1170662400"; d="scan'208"; a="158546110:sNHT40456620"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l4TJbveR030847; Tue, 29 May 2007 12:37:57 -0700
Received: from dwingwxp ([10.32.240.194]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l4TJbuV1011572; Tue, 29 May 2007 19:37:56 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Paul Kyzivat' <pkyzivat@cisco.com>, 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>
Subject: RE: [Sip] Support for Multipart/MIME
Date: Tue, 29 May 2007 12:37:55 -0700
Message-ID: <093d01c7a228$db7a85e0$c6f0200a@amer.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.3028
In-Reply-To: <465A6313.4030304@cisco.com>
Thread-Index: Aceg5c2Od5RC/CkdRaOLzE7s/msx7ABQmsaw
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1108; t=1180467477; x=1181331477; c=relaxed/simple; s=sjdkim8002; 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]=20Support=20for=20Multipart/MIME |Sender:=20; bh=6N1xbN5wSVSL5oFGUgC8G8KNbdmQNtOJwFgjwDZ5IeU=; b=sJaxISLIITzBIMPndIgk9tpA1fpp2744ogLSPJeYIHqBozucYKicgNnMbmauMQtF+Nyd8OQP NWchTTke13/RM8+r9rvgaimOadJ/i2Z6W0sYx+FpBHq9pL5wt93KL54o;
Authentication-Results: sj-dkim-8; header.From=dwing@cisco.com; dkim=pass (s ig from cisco.com/sjdkim8002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: sip@ietf.org, 'Francois Audet' <audet@nortel.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

Paul Kyzivat wrote: 
...
> >    OPEN ISSUE 2: we know that we do not want two SDPs in a 
> > 'multipart/
> >    alternative', but is this valid generally with any content type?
> >    Would it be possible to provide two alternative body 
> > parts using the
> >    same format and, thus, the same content type but in, 
> > say, different
> >    languages?
> 
> Its my understanding that the distinction is based on which can be 
> understood, relative to Content-Type. It isn't apparent to me that 
> making this decision based on other attributes is valid. For 
> one thing the parts are supposed to be ordered by increasing 
> richness.  If they differed by language this wouldn't be true.

Multipart/alternative is the best we have, though.  And who is to say that
image/jpeg is richer than image/gif, or that english is richer than latin?  

Anyway, the following RFCs standardize the use of Content-Language and refer
to using multipart/alternative when providing support for multiple
languages:

  http://tools.ietf.org/html/rfc3282
  http://tools.ietf.org/html/rfc3066

-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