Re: [Sip] Binary Encoding for SIP

Paul Kyzivat <pkyzivat@cisco.com> Tue, 17 February 2004 14:31 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29767 for <sip-archive@odin.ietf.org>; Tue, 17 Feb 2004 09:31:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At6Fi-0003tR-FW for sip-archive@odin.ietf.org; Tue, 17 Feb 2004 09:31:10 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HEVABk014964 for sip-archive@odin.ietf.org; Tue, 17 Feb 2004 09:31:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At6Fb-0003qY-8X; Tue, 17 Feb 2004 09:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At6Ef-0003p6-QQ for sip@optimus.ietf.org; Tue, 17 Feb 2004 09:30:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29687 for <sip@ietf.org>; Tue, 17 Feb 2004 09:30:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At6Ee-00035l-00 for sip@ietf.org; Tue, 17 Feb 2004 09:30:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At6Dj-00032p-00 for sip@ietf.org; Tue, 17 Feb 2004 09:29:08 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx with esmtp (Exim 4.12) id 1At6Cy-0002xQ-00 for sip@ietf.org; Tue, 17 Feb 2004 09:28:20 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 17 Feb 2004 06:27:49 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i1HERmhu019474; Tue, 17 Feb 2004 09:27:48 -0500 (EST)
Received: from cisco.com ([161.44.79.87]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGC31025; Tue, 17 Feb 2004 09:27:47 -0500 (EST)
Message-ID: <403224E2.5070401@cisco.com>
Date: Tue, 17 Feb 2004 09:27:46 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
CC: sip@ietf.org
Subject: Re: [Sip] Binary Encoding for SIP
References: <BC5459B9.31568%fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Cullen,

This is an attractive proposal because it has potential to make sip 
implementations simpler. But before I can answer I need clarification on 
one thing:

Does this apply to content referenced and fetched via content-indirection?

This proposal only has value if my mime processor *never* needs to deal 
with any content-transfer-encoding other than binary. If content 
referenced by content indirection still might use other encodings, then 
that value is lost. Unfortunately, given the potential range of 
transports that might be used with content indirection, I don't know if 
requiring binary can be done in general.

	Paul

Cullen Jennings wrote:
>     
> I submitted a draft on binary encoding for SIP. This improves
> interoperability, improves speed, decreases sizes of messages, and generally
> makes life better for SIP which will no doubt eventually help with World
> Hunger. I need feedback, please let me know:
> 
> a) Yah, lets do it
> 
> b) No this is a stupid ideas and here are the reasons why
> 
> c) There has not been many list comments, this draft involves some very
> complex issues. I need a year or two to develop an opinion on the single
> sentence inside it.
> 
> d) I agree with Cowboy Willis
> 
> Until it arrives in the archives, you can find it at
> 
> http://www.employees.org/~fluffy/ietf/draft-jennings-sip-mime-01.html
> 
> or, if you prefer ASCII encodings of everything,
> 
> www.employees.org/~fluffy/ietf/draft-jennings-sip-mime-01.txt
> 
> Thanks, Cullen
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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 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