Re: [Sip] Binary Encoding for SIP

Rohan Mahy <rohan@cisco.com> Wed, 18 February 2004 12:55 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 HAA08827 for <sip-archive@odin.ietf.org>; Wed, 18 Feb 2004 07:55:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtREJ-0002tS-EX for sip-archive@odin.ietf.org; Wed, 18 Feb 2004 07:55:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1ICt7bw011105 for sip-archive@odin.ietf.org; Wed, 18 Feb 2004 07:55:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtREE-0002s4-MC; Wed, 18 Feb 2004 07:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtRE2-0002rQ-Jo for sip@optimus.ietf.org; Wed, 18 Feb 2004 07:54:50 -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 HAA08823 for <sip@ietf.org>; Wed, 18 Feb 2004 07:54:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtRE1-0003sn-00 for sip@ietf.org; Wed, 18 Feb 2004 07:54:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtRD9-0003qX-00 for sip@ietf.org; Wed, 18 Feb 2004 07:53:56 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AtRCi-0003o2-00 for sip@ietf.org; Wed, 18 Feb 2004 07:53:28 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 18 Feb 2004 05:01:53 +0000
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i1ICqt4U026050; Wed, 18 Feb 2004 04:52:56 -0800 (PST)
Received: from [127.0.0.1] (ssh-sjc-1.cisco.com [171.68.225.134]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AQJ62714; Wed, 18 Feb 2004 04:52:46 -0800 (PST)
In-Reply-To: <9A64A99CD3F2BD4582BE4FB63FC1F38101661A@MAILSERVER>
References: <9A64A99CD3F2BD4582BE4FB63FC1F38101661A@MAILSERVER>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: multipart/alternative; boundary="Apple-Mail-21-17346777"
Message-Id: <6A557CF2-6211-11D8-9B6B-0003938AF740@cisco.com>
Cc: 'Cullen Jennings' <fluffy@cisco.com>, sip@ietf.org
From: Rohan Mahy <rohan@cisco.com>
Subject: Re: [Sip] Binary Encoding for SIP
Date: Wed, 18 Feb 2004 04:53:14 -0800
To: Raphael Tryster <raphael@tdsoft.com>
X-Mailer: Apple Mail (2.612)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE autolearn=no version=2.60
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>

Hi Raphael,

Just as an FYI:  The "unpopular" encoding for H.248 is ASN.1 encoding 
of the entire protocol.  What Cullen is proposing is sending all *MIME 
bodies* in SIP as a stream of raw binary data (like HTTP). This is 
instead of sending SIP MIME bodes as a stream of base64-encoded data 
for example, which is unnecessary in modern protocols, but was required 
in email for backwards compatibility reasons.

(btw: I vote for a)

thanks,
-rohan


On Feb 15, 2004, at 12:13 AM, Raphael Tryster wrote:

> Hello Cullen,
>
> Given that this is my first venture into the SIP email forum, and the 
> first response to your posting, it is only fitting that I should vote 
> for option c:).
>
> During the coming year or two, I hope to develop an opinion on whether 
> the issues of backward compatibility and ease of debugging, which seem 
> to make the binary option rather unpopular in Megaco, apply to SIP as 
> well.  If they do, it could have an adverse affect on World Hunger, as 
> those with the right tools to debug binary messages will eat more, at 
> the expense of the rest.
>
> Raphael Tryster
>
> -----Original Message-----
> From:   Cullen Jennings [SMTP:fluffy@cisco.com]
> Sent:   Sunday, 15 February 2004 9:03
> To:     sip@ietf.org
> Subject:        [Sip] Binary Encoding for SIP
>
>    
> 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