Re: [Sip] Binary Encoding for SIP
neil quiogue <neil@quiogue.com> Sun, 15 February 2004 21:09 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 QAA24936 for <sip-archive@odin.ietf.org>; Sun, 15 Feb 2004 16:09:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsTVo-0008Ff-8B for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 16:09:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1FL9CRj031655 for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 16:09:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsTVe-0008DR-CT; Sun, 15 Feb 2004 16:09:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsTVL-0008D3-5h for sip@optimus.ietf.org; Sun, 15 Feb 2004 16:08: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 QAA24929 for <sip@ietf.org>; Sun, 15 Feb 2004 16:08:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsTVJ-0003ID-00 for sip@ietf.org; Sun, 15 Feb 2004 16:08:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsTUP-0003Fv-00 for sip@ietf.org; Sun, 15 Feb 2004 16:07:45 -0500
Received: from mail19b.dulles19-verio.com ([198.170.241.3]) by ietf-mx with smtp (Exim 4.12) id 1AsTTq-0003DN-00 for sip@ietf.org; Sun, 15 Feb 2004 16:07:10 -0500
Received: from www1913.dulles19-verio.com (161.58.134.174) by mail19b.dulles19-verio.com (RS ver 1.0.90vs) with SMTP id 0-0658889215; Sun, 15 Feb 2004 16:06:56 -0500 (EST)
Date: Mon, 16 Feb 2004 05:06:50 +0800
From: neil quiogue <neil@quiogue.com>
To: Marc Petit-Huguenin <petithug@acm.org>
cc: sip@ietf.org
Subject: Re: [Sip] Binary Encoding for SIP
Message-ID: <140639390.1076908010@[192.168.1.101]>
In-Reply-To: <402FA64B.2060907@acm.org>
References: <BC5459B9.31568%fluffy@cisco.com> <402FA64B.2060907@acm.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Loop-Detect: 1
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=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
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: quoted-printable
I think what Cullen is proposing is to only send one type of MIME body part encoding (i.e., binary) instead of having multiple possible MIME encoding as specified on RFC3261/7.1.4. Regards, Neil --On dimanche 15 février 2004 09:03 -0800 Marc Petit-Huguenin <petithug@acm.org> wrote: > I thought that binary body was already supported: RFC3261 section 7.4.1, > third paragraph. > > 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
- [Sip] Binary Encoding for SIP Cullen Jennings
- RE: [Sip] Binary Encoding for SIP Raphael Tryster
- Re: [Sip] Binary Encoding for SIP Henning Schulzrinne
- Re: [Sip] Binary Encoding for SIP Marc Petit-Huguenin
- Re: [Sip] Binary Encoding for SIP neil quiogue
- RE: [Sip] Binary Encoding for SIP George Foti (QC/EMC)
- Re: [Sip] Binary Encoding for SIP Paul Kyzivat
- Re: [Sip] Binary Encoding for SIP Rohan Mahy
- Re: [Sip] Binary Encoding for SIP Bryan Thale
- Re: [Sip] Binary Encoding for SIP Cullen Jennings
- Re: [Sip] Binary Encoding for SIP Kumiko Ono
- Re: [Sip] Binary Encoding for SIP Bryan Thale
- Re: [Sip] Binary Encoding for SIP Cullen Jennings
- Re: [Sip] Binary Encoding for SIP Cullen Jennings