Re: [sipcore] Bad Location Information in draft-ietf-sipcore-location-conveyance-03

"Richard L. Barnes" <rbarnes@bbn.com> Thu, 22 July 2010 23:30 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E1B63A6A99 for <sipcore@core3.amsl.com>; Thu, 22 Jul 2010 16:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLQlUxJ507Wq for <sipcore@core3.amsl.com>; Thu, 22 Jul 2010 16:30:42 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id B84C23A6A9B for <sipcore@ietf.org>; Thu, 22 Jul 2010 16:30:24 -0700 (PDT)
Received: from [128.89.252.227] (port=53109 helo=[192.168.1.43]) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Oc5Df-000Hs7-W6; Thu, 22 Jul 2010 19:30:28 -0400
Message-Id: <F22F24DB-6E29-456A-90D0-B5373FDA8D3D@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <A29736AF-DAF4-4BB4-B13D-16DEE3EDF123@cdt.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 22 Jul 2010 19:30:26 -0400
References: <A29736AF-DAF4-4BB4-B13D-16DEE3EDF123@cdt.org>
X-Mailer: Apple Mail (2.936)
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Bad Location Information in draft-ietf-sipcore-location-conveyance-03
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 22 Jul 2010 23:30:48 -0000

Like James notes, intermediaries have always had the power to block  
any request they please (e.g., with the 401 Unauthorized header).  In  
the case of location, the concern you note is just one more motivation  
for proxies to keep their hands off my INVITE; I don't think there's a  
technical solution.


On Jul 22, 2010, at 3:50 PM, Alissa Cooper wrote:

> Section 4.2 of draft-ietf-sipcore-location-conveyance-03 says:
>
>   A SIP intermediary can also reject a location it receives from a
>   Target when it understands the Target to be in a different location.
>   The proper handling of this scenario is for the SIP intermediary to
>   include the proper location in the 424 Response.  This SHOULD be
>   included in the response as a MIME message body (i.e., a location
>   value), rather than as a URI; however, in cases where the
>   intermediary is willing to share location with recipients but not
>   with a user agent, a reference might be necessary.
>
> Does this leave the Target's ability to spoof its location up to the  
> discretion of the SIP intermediary?
>
> Thanks,
> Alissa
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore