Re: [Sip] SIPit 20 survey summary

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Sun, 29 April 2007 07:40 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 1Hi41P-000487-7H; Sun, 29 Apr 2007 03:40:39 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hi41N-00047v-Eh for sip-confirm+ok@megatron.ietf.org; Sun, 29 Apr 2007 03:40:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hi41N-00047m-1b for sip@ietf.org; Sun, 29 Apr 2007 03:40:37 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hi41K-0001pn-Vg for sip@ietf.org; Sun, 29 Apr 2007 03:40:37 -0400
Received: (qmail 24265 invoked by uid 0); 29 Apr 2007 07:40:34 -0000
Received: from 90.186.63.85 by www024.gmx.net with HTTP; Sun, 29 Apr 2007 09:40:34 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 29 Apr 2007 09:40:34 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <1177802622.3020.8.camel@localhost.localdomain>
Message-ID: <20070429074034.224850@gmx.net>
MIME-Version: 1.0
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>
Subject: Re: [Sip] SIPit 20 survey summary
To: "Frank W. Miller" <fwmiller@cornfed.com>, fluffy@cisco.com
X-Authenticated: #29516787
X-Flags: 0001
X-Mailer: WWW-Mail 6100 (Global Message Exchange)
X-Priority: 3
X-Provags-ID: V01U2FsdGVkX1/tikAp+ZHtxl9sRz+Xr2USOPVU9b1OOG0utE2Hcq Q4WosGewywSO9ALdst6QJFZO/jhFAlyScCrQ==
Content-Transfer-Encoding: 7bit
X-GMX-UID: kyJBdeFiODB6UZkCsWVMAoU9Ji9SWpJD
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: sip@ietf.org, discussion@sipforum.org, jh@tutpro.com, sip-implementors@cs.columbia.edu, 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

Hi Frank, 
Hi Jeroen, 
Hi Juha, 
Hi all 

what exactly is your complaint? Are you unhappy about
* XML encoding of location information
* location information carried in the body instead of the header
* number of location shapes (see http://www.ietf.org/internet-drafts/draft-ietf-geopriv-pdif-lo-profile-06.txt)
* the inability of GPS to work in certain environments
* Geopriv location and privacy architecture
* Ecrit emergency services architecture
?

Ciao
Hannes

-------- Original-Nachricht --------
Datum: Sat, 28 Apr 2007 17:23:42 -0600
Von: "Frank W. Miller" <fwmiller@cornfed.com>
An: Cullen Jennings <fluffy@cisco.com>
CC: \'IETF SIP List\' <sip@ietf.org>, discussion@sipforum.org, Juha Heinanen <jh@tutpro.com>, sip-implementors@cs.columbia.edu, \'Robert Sparks\' <rjsparks@estacado.net>
Betreff: Re: [Sip] SIPit 20 survey summary

> 
> Acknowledged.  However, if we're talking about adding messaging
> infrastructure to SIP, then the discussion is quite relevant here.  I
> for one would vote for a simpler mechanism than multipart MIME XML blah
> blah blah.  With regards to Keith's comments, I would love to sit down
> and provide an alternative proposal but I just don't have the time to do
> it.  With all due respect, I'll implement whatever the standards
> committee comes up with, but I don't think its unreasonable for me or
> anyone else to express concern about protocol that is obviously designed
> by committee and obviously more complicated that it probably has to be.
> 
> FM
> 
> 
> On Sat, 2007-04-28 at 15:23 -0700, Cullen Jennings wrote:
> > There has been an incredible amount of work on this topic across many  
> > standard organizations including the IETF. Before people start in on  
> > discussing this in - I strongly suggest they might want to read some  
> > of the requirements, uses cases, drafts, and mailing list discussions  
> > in ECRIT and GEOPRIV. Please keep in mind the charters of ECRIT/ 
> > GEOPRIV/SIP and take the discussion to the right working group.
> > 
> > 
> > On Apr 28, 2007, at 2:35 AM, Juha Heinanen wrote:
> > 
> > > Jeroen van Bemmel writes:
> > >
> > >> Especially for the use case of emergency calls, would it not be  
> > >> wise to
> > >> select a much more simple approach/syntax, e.g.:
> > >> Emergency-Location: lat=x; lon=y
> > >>
> > >> So no XML, no mime/multipart, as simple as possible (no complex  
> > >> semantics,
> > >> usage-rules etc), something to reduce the barrier of
> > >> implementation/deployment, and to reduce the risk for interop issues?
> > >
> > > i fully agree with this.  we should follow KISS principle here.  it is
> > > highly unlikely that sip ua vendors will even TRY implement such a
> > > complex protocol.
> > >
> > > another reason why it will not get implemented is that sip uas don't
> > > know where they are located.  gps does not work well indoors and  
> > > mobile
> > > operators at least here have refused to make public coordinates of  
> > > their
> > > base stations.
> > >
> > > -- juha
> > >
> > >
> > > _______________________________________________
> > > 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 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