Re: [Sip] Binary Encoding for SIP

Cullen Jennings <fluffy@cisco.com> Fri, 20 February 2004 07:04 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 CAA27127 for <sip-archive@odin.ietf.org>; Fri, 20 Feb 2004 02:04:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au4hM-0003nV-BC for sip-archive@odin.ietf.org; Fri, 20 Feb 2004 02:03:44 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K73iDu014524 for sip-archive@odin.ietf.org; Fri, 20 Feb 2004 02:03:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au4gq-0003YB-Ss; Fri, 20 Feb 2004 02:03:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au4gN-0003PQ-HV for sip@optimus.ietf.org; Fri, 20 Feb 2004 02:02:43 -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 CAA25451 for <sip@ietf.org>; Fri, 20 Feb 2004 02:02:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au4gJ-0002iB-00 for sip@ietf.org; Fri, 20 Feb 2004 02:02:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au4fN-0002fZ-00 for sip@ietf.org; Fri, 20 Feb 2004 02:01:42 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1Au4ee-0002aJ-00 for sip@ietf.org; Fri, 20 Feb 2004 02:00:56 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 19 Feb 2004 23:00:54 -0800
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i1K70Rcw002278; Thu, 19 Feb 2004 23:00:27 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn2-34.cisco.com [10.21.112.34]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AMN08350; Thu, 19 Feb 2004 23:00:26 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Thu, 19 Feb 2004 22:21:19 -0800
Subject: Re: [Sip] Binary Encoding for SIP
From: Cullen Jennings <fluffy@cisco.com>
To: Paul H Kyzivat <pkyzivat@cisco.com>
CC: sip@ietf.org
Message-ID: <BC5AE75F.322F0%fluffy@cisco.com>
In-Reply-To: <403224E2.5070401@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
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.1 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

Good point. 

I think that all they ways I can imagine getting indirect content, HTTP,
FTP, TFTP, NFS, SMB, file are all 8 bit safe so I think this argument
probably still holds.

Cullen


On 2/17/04 6:27 AM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:

> 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