Re: [Sip] SIPit 20 survey summary

Cullen Jennings <fluffy@cisco.com> Sat, 28 April 2007 23:45 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 1Hhwbj-0001kA-Hs; Sat, 28 Apr 2007 19:45:39 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hhwbh-0001hY-Nz for sip-confirm+ok@megatron.ietf.org; Sat, 28 Apr 2007 19:45:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hhwbh-0001g0-DT for sip@ietf.org; Sat, 28 Apr 2007 19:45:37 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhwZE-0007Xr-SW for sip@ietf.org; Sat, 28 Apr 2007 19:43:06 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 28 Apr 2007 16:43:04 -0700
X-IronPort-AV: i="4.14,465,1170662400"; d="scan'208"; a="416726212:sNHT52926176"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l3SNh4QE008560; Sat, 28 Apr 2007 16:43:04 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-3.cisco.com (8.12.10/8.12.6) with SMTP id l3SNh2A9014492; Sat, 28 Apr 2007 23:43:02 GMT
In-Reply-To: <1177802622.3020.8.camel@localhost.localdomain>
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>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <03CA4D91-9D78-4AB0-9DC0-4030AD23E2B5@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] SIPit 20 survey summary
Date: Sat, 28 Apr 2007 16:42:27 -0700
To: "Frank W. Miller" <fwmiller@cornfed.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3091; t=1177803784; x=1178667784; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Sip]=20SIPit=2020=20survey=20summary |Sender:=20; bh=id70XH1lon9ValxygX56FBpR9hxuoyv+h+8Q2x2obgY=; b=JI4H0EBTiFbwYfUuRQApGoNwqgwGG4FkBf9RDZO2hadxLbWLAsuTtLRm1Co1S2Ro7as+ejoO 256yij9UJywXGP/lgqXKaLK9y4VtzB+Gn4ehIV7m1u+0uJNX9Tt91QPW;
Authentication-Results: sj-dkim-6; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim6002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: IETF SIP List <sip@ietf.org>
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

Fair enough - I just want to try and keep the right parts of the  
discussion in the right place.


On Apr 28, 2007, at 4:23 PM, Frank W. Miller wrote:

>
> 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