Re: [Sip] SIPit 20 survey summary

"Frank W. Miller" <fwmiller@cornfed.com> Sun, 29 April 2007 14:49 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiAhz-0000ND-TI; Sun, 29 Apr 2007 10:49:03 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HiAhy-0000N4-Tb for sip-confirm+ok@megatron.ietf.org; Sun, 29 Apr 2007 10:49:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiAhy-0000LB-JM for sip@ietf.org; Sun, 29 Apr 2007 10:49:02 -0400
Received: from smtpauth00.csee.onr.siteprotect.com ([64.26.60.144]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiAhx-0006Dn-BY for sip@ietf.org; Sun, 29 Apr 2007 10:49:02 -0400
Received: from [192.168.1.120] (c-67-162-139-200.hsd1.co.comcast.net [67.162.139.200]) (Authenticated sender: fwmiller@cornfed.com) by smtpauth00.csee.onr.siteprotect.com (Postfix) with ESMTP id 71BE375804E; Sun, 29 Apr 2007 09:49:00 -0500 (CDT)
Subject: Re: [Sip] SIPit 20 survey summary
From: "Frank W. Miller" <fwmiller@cornfed.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <17E3095D-AB53-4359-A5E2-4971527B26D2@cs.columbia.edu>
References: <075001c788fc$9f6a2be0$640fa8c0@cis.neustar.com> <001401c78976$5f8dc020$0601a8c0@BEMBUSTER> <17971.5486.819002.96466@tutpro.com> <CCACA85C-15C7-49F2-968B-1F12060CB271@cisco.com> <1177802622.3020.8.camel@localhost.localdomain> <20070429074034.224850@gmx.net> <003201c78a63$74cff690$0601a8c0@BEMBUSTER> <17E3095D-AB53-4359-A5E2-4971527B26D2@cs.columbia.edu>
Content-Type: text/plain
Date: Sun, 29 Apr 2007 08:48:43 -0600
Message-Id: <1177858123.3028.11.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6)
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: IETF SIP List <sip@ietf.org>, Robert Sparks <rjsparks@estacado.net>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sip-bounces@ietf.org

On Sun, 2007-04-29 at 09:58 -0400, Henning Schulzrinne wrote:
> For the record, I will note that I have made proposals for simple non- 
> multipart location conveyance (using the data: URL), but various  
> process-related arguments were made as to why we weren't allowed to  
> look at that. (I'd prefer even simpler solutions, such as the one  
> that XMPP uses, but that's beyond the political correctness limit in  
> GEOPRIV.)
> 

Would it be possible to see these extensions?  Keith asked for
alternative proposals, it seems like looking at that might be a good
idea now.


> I tend to agree that exhortations to developers generally achieve  
> little. On the other hand, I'm not sure that belly-aching about  
> multipart is all that helpful. After all, most email clients support  
> it and there are libraries in various languages to help with  
> implementation. Generating multipart bodies is pretty trivial (as  
> opposed to parsing them), and that's all embedded devices will  
> generally have to do for location conveyance.
> 

As I said, I and others will implement whatever we're directed to.
Personally, I've got Expat in there now for PIDF and even parsing MP
MIME isn't really that hard.

My question is more focused on the essence of the Jeron's off-the-cuff
proposal.  Does the location information belong in the body or in the
main SIP headers?  I believe its the latter primarily for the argument
that was put forth, i.e. the information is so important it deserves
first-class treatment in the message headers.  The fact that its
simplified comes primarily from the fact that you need to be more
compact in your representation if your in the headers.

Dropping the return address list to sip@ietf.org only to minimize
messages in my inbox...


FM





_______________________________________________
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