Re: [sipcore] I-D Action:draft-ietf-sipcore-location-conveyance-07.txt

"Elwell, John" <john.elwell@siemens-enterprise.com> Thu, 05 May 2011 08:58 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32975E06CE for <sipcore@ietfa.amsl.com>; Thu, 5 May 2011 01:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.19
X-Spam-Level:
X-Spam-Status: No, score=-105.19 tagged_above=-999 required=5 tests=[AWL=1.409, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41dvaEOXMGUl for <sipcore@ietfa.amsl.com>; Thu, 5 May 2011 01:58:25 -0700 (PDT)
Received: from mail27.messagelabs.com (mail27.messagelabs.com [193.109.254.147]) by ietfa.amsl.com (Postfix) with SMTP id E2208E0720 for <sipcore@ietf.org>; Thu, 5 May 2011 01:58:23 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1304585899!24275640!1
X-StarScan-Version: 6.2.16; banners=-,-,-
X-Originating-IP: [62.134.46.10]
Received: (qmail 23063 invoked from network); 5 May 2011 08:58:19 -0000
Received: from unknown (HELO senmx12-mx) (62.134.46.10) by server-13.tower-27.messagelabs.com with SMTP; 5 May 2011 08:58:19 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 83E0523F03DB for <sipcore@ietf.org>; Thu, 5 May 2011 10:58:22 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 5 May 2011 10:58:22 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Thu, 05 May 2011 10:58:21 +0200
Thread-Topic: [sipcore] I-D Action:draft-ietf-sipcore-location-conveyance-07.txt
Thread-Index: AcwKrO5na17yCOMpRkGjovdqETPJDwAUqC9A
Message-ID: <A444A0F8084434499206E78C106220CA08760791A1@MCHP058A.global-ad.net>
References: <20110504224502.1492.71401.idtracker@ietfa.amsl.com>
In-Reply-To: <20110504224502.1492.71401.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] I-D Action:draft-ietf-sipcore-location-conveyance-07.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2011 08:58:27 -0000

I noticed the following:

Modified text in section 4.2:
"If no Geolocation-Routing header field is present in a SIP request, 
   a SIP intermediary MAY insert this header. Without knowledge from a 
   Rulemaker, the SIP intermediary inserting this header-value SHOULD 
   NOT set the value to "yes", as this could allow the Target's 
   location to be forwarded to third parties without the Target's 
   explicit permission. An easy way around this is to have the Target 
   always insert this header-value as "no"."
Even if the value is set to "no", the target's location could end up being forwarded to third parties without the target's explicit permission. Normal SIP routing (without taking location into account) can result in a request being forwarded to another destination. So the words:
"as this could allow the Target's 
   location to be forwarded to third parties without the Target's 
   explicit permission"
should be deleted, as this can arise anyway and is not impacted by the value of the Geolocation-Routing header field.

John


> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of 
> Internet-Drafts@ietf.org
> Sent: 04 May 2011 23:45
> To: i-d-announce@ietf.org
> Cc: sipcore@ietf.org
> Subject: [sipcore] I-D 
> Action:draft-ietf-sipcore-location-conveyance-07.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol 
> Core Working Group of the IETF.
> 
> 
> 	Title           : Location Conveyance for the Session 
> Initiation Protocol
> 	Author(s)       : J. Polk, et al.
> 	Filename        : draft-ietf-sipcore-location-conveyance-07.txt
> 	Pages           : 30
> 	Date            : 2011-05-04
> 
> This document defines an extension to the Session Initiation 
> Protocol (SIP) to convey geographic location information from one 
> SIP entity to another SIP entity.  The SIP extension covers 
> end-to-end conveyance as well as location-based routing, where SIP 
> intermediaries make routing decisions based upon the location of the
> Location Target.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sipcore-locatio
> n-conveyance-07.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>