Re: [Sip] a question about IETF draft location conveyance 09

Dean Willis <dean.willis@softarmor.com> Thu, 22 November 2007 01:10 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 1Iv0aE-0007l1-Uk; Wed, 21 Nov 2007 20:10:22 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Iv0aD-0007kq-Mu for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 20:10:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv0aD-0007ia-5a for sip@ietf.org; Wed, 21 Nov 2007 20:10:21 -0500
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iv0aA-0007ik-OF for sip@ietf.org; Wed, 21 Nov 2007 20:10:21 -0500
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id lAM1AFuX006665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 21 Nov 2007 19:10:17 -0600
In-Reply-To: <p06240608c36a4849ecf3@[67.169.50.136]>
References: <4742BDF5.9040302@unibo.it> <XFE-SJC-212qXLFfJNw000012bf@xfe-sjc-212.amer.cisco.com> <p06240607c36a38613297@[67.169.50.136]> <XFE-SJC-211EAOeIiGX000013f8@xfe-sjc-211.amer.cisco.com> <p06240608c36a4849ecf3@[67.169.50.136]>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <F44A63BF-E390-4389-9F4D-DAC95C271735@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] a question about IETF draft location conveyance 09
Date: Wed, 21 Nov 2007 19:10:09 -0600
To: Ted Hardie <hardie@qualcomm.com>, "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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

On Nov 21, 2007, at 3:02 PM, Ted Hardie wrote:

> At 2:28 PM -0600 11/21/07, James M. Polk wrote:
>>
>> The "recipient=" within the Geolocation header is a SIP parameter,  
>> in a SIP document.  Everything discussed in Geopriv regarding this  
>> document needs to be approved in SIP too.  The SIP WG hasn't heard  
>> this part of the discussion because most members of SIP aren't  
>> subscribed to the Geopriv list.
>
> That SIP parameter in a SIP document relates to a PIDF-LO object  
> carried by
> SIP; in that context, SIP is a using protocol of the GEOPRIV  
> framework.  SIP
> folks should certainly understand the work they're reusing, or the  
> implementations
> won't do the right thing.  But re-starting the conversation in SIP  
> without
> reference to the discussions that have already occurred in GeoPRIV  
> is a
> recipe for conflict at IETF Last Call.  We might as well start  
> getting people
> on the same page now.  From my  perspective, the right way to do  
> that is
> to start the discussion from where it last left off, even if that  
> wasn't in
> the same group.  That tells people where the consensus of that  
> group was
> and informs the rest of the discussion.

Supposedly, the discussion in GEOPRIV was a joint SIP/GEOPRIV effort.

A brief recap of the conclusion in GEOPRIV might be reasonable, but  
I'd much rather not revisit the thousands of emails on the topic in  
GEOPRIV. If we notice now that it is broken in some horrible way we  
didn't, before, that might change the situation, but we shouldn't  
rehash the entire design rationale.

--
Dean 


_______________________________________________
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