[Sip] Binary Encoding for SIP

Cullen Jennings <fluffy@cisco.com> Sun, 15 February 2004 07:14 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 CAA26194 for <sip-archive@odin.ietf.org>; Sun, 15 Feb 2004 02:14:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsGTv-00059N-00 for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 02:14:23 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1F7EMlj019735 for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 02:14:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsGTa-00051H-8x; Sun, 15 Feb 2004 02:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsGSr-0004lC-B0 for sip@optimus.ietf.org; Sun, 15 Feb 2004 02:13:17 -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 CAA24816 for <sip@ietf.org>; Sun, 15 Feb 2004 02:13:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsGSn-0005mg-00 for sip@ietf.org; Sun, 15 Feb 2004 02:13:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsGRp-0005j8-00 for sip@ietf.org; Sun, 15 Feb 2004 02:12:14 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AsGQu-0005dA-00 for sip@ietf.org; Sun, 15 Feb 2004 02:11:16 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 14 Feb 2004 23:19:48 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1F7Am1m018477 for <sip@ietf.org>; Sat, 14 Feb 2004 23:10:49 -0800 (PST)
Received: from [10.0.1.3] (rtp-vpn1-45.cisco.com [10.82.224.45]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AMJ51930; Sat, 14 Feb 2004 23:10:47 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Sat, 14 Feb 2004 23:03:21 -0800
From: Cullen Jennings <fluffy@cisco.com>
To: sip@ietf.org
Message-ID: <BC5459B9.31568%fluffy@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
Subject: [Sip] Binary Encoding for SIP
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

    
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