Re: [sipcore] New Version Notification for draft-winterbottom-sipcore-locparam-01.txt

Brian Rosen <br@brianrosen.net> Tue, 23 May 2017 19:51 UTC

Return-Path: <br@brianrosen.net>
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 0463112EAE1 for <sipcore@ietfa.amsl.com>; Tue, 23 May 2017 12:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5BDzid7Meei for <sipcore@ietfa.amsl.com>; Tue, 23 May 2017 12:51:32 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43FD1127866 for <sipcore@ietf.org>; Tue, 23 May 2017 12:51:32 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id v27so137797232qtg.2 for <sipcore@ietf.org>; Tue, 23 May 2017 12:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DmZC7jK9PB1YOGf8LBIDGUYJXZ+r979ReDhq9q535pE=; b=blkYjmPHVPgkSY7ockvqiV63UpTg45sRwidG29/5jko6bE8Ims0oHJNBpds+c5Cfwr cNPO57j6ekvdFDDhApRELDu5Kz/SVqOhzYNR4z4Rh8E7egPb2pIbzUbJy7p3JIHC849p wqolxB+wyEVUe1U994IpiV4/EpcVykV92ML5a7GEflWAlq0VQ5rrw1bAw0mJ/Bqmq+eG i4zlRuKxawTpctvxS7yMtV3HMSREkd5CyeIuUjp4+ezqxaQBchlFvrE35gEqEEUgzgUE E5tuJqd+coXhbc9i4ypWwvMDmqBiVr/z/4hlF0R1j1fyLEBZVH6jac0PSb566TBVvCoD 0MXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DmZC7jK9PB1YOGf8LBIDGUYJXZ+r979ReDhq9q535pE=; b=Aye4mSRKhplqhEdx5xFZmTTilfBwCZ4egNqy9pDTF4Mc47foo8Phekv6YrimJtiNmz GfWQzBy47b/I5803w6IEbc8Ljt/NGlx5lqLyElX0KgQ4Fcb3UXdZuN07otEwGLMyyu+X m01yvBPln01dUwYDFqC4PYMAIpFpczQh1LMVOwHxMrrtbhqkjpAkN7GLgJRyOnxvr6E6 67PcGT746RT+MspV2tdLo2c+KhHUP0z0rLVHY7oxDjnS7sCMLukCEF9pgmkBp6gHtPSN KG+CJIjW5hLTW3yzL9CO0++/Nrd+YS09Gn3MoR9eYXNQk7QGyjxeEgsZ7Hnj3NZ1KCm1 HmIg==
X-Gm-Message-State: AODbwcAFAxlh37beZuzy1JOYFfnRoPqiyijqK+7AHngnvE401d6gNuPL wlRWah8uJQnrklrAgr3r2A==
X-Received: by 10.200.49.194 with SMTP id i2mr31645686qte.156.1495569091382; Tue, 23 May 2017 12:51:31 -0700 (PDT)
Received: from [10.96.43.88] (neustar-sthide-nat1.neustar.biz. [156.154.81.54]) by smtp.gmail.com with ESMTPSA id l14sm1112787qtf.40.2017.05.23.12.51.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 May 2017 12:51:30 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <75D7EE00-BE2B-4C6E-91DE-819AF015542F@gmail.com>
Date: Tue, 23 May 2017 15:51:27 -0400
Cc: Brian Rosen <brtech99@icloud.com>, "Hutton, Andrew" <andrew.hutton@unify.com>, sipcore@ietf.org, bruno.chatras@orange.com, R.Jesske@telekom.de
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FE4ADF5-7C50-4BEE-A3AA-2CCAED505EE5@brianrosen.net>
References: <149554350753.16443.17633151256632718640.idtracker@ietfa.amsl.com> <159c97974a8749d4ab71016f57a768db@HE105828.emea1.cds.t-internal.com> <D774393E-2CCF-4ED9-83CC-0C0060C2C86A@icloud.com> <75D7EE00-BE2B-4C6E-91DE-819AF015542F@gmail.com>
To: James Winterbottom <a.james.winterbottom@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/5ti7mlvcCR3Yrw-gk8HeQ3vnlWk>
Subject: Re: [sipcore] New Version Notification for draft-winterbottom-sipcore-locparam-01.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 23 May 2017 19:51:34 -0000

Is there a practical difference between who determined location and who put it in the header?

Is there a reason you can’t (or even more likely, wouldn’t normally) dereference the URI, and thus get the <provided-by> 
in every circumstance where the locparam would be used?

Brian

> On May 23, 2017, at 3:35 PM, James Winterbottom <a.james.winterbottom@gmail.com> wrote:
> 
> Hi Brian,
> 
> Provided-by doesn’t work for two reasons.
> 
> 1) Provided-by says who determined the location, not who put the thing into the geolocation header
> 2) provided-by only works if you sending location by value, which in the European case we are not.
> 
> 
> Cheers
> James
> 
> 
> 
> 
> 
>> On 23 May 2017, at 11:40 pm, Brian Rosen <brtech99@icloud.com> wrote:
>> 
>> <as individual>
>> I had asked a question on this, which was, why isn’t <provided-by> an acceptable solution to the problem?
>> 
>> I didn’t see an answer.
>> 
>> Brian
>>> On May 23, 2017, at 9:04 AM, R.Jesske@telekom.de wrote:
>>> 
>>> Dear all,
>>> 
>>> After reworking the draft due to the comments made by Dale, I have uploaded a new version
>>> https://www.ietf.org/internet-drafts/draft-winterbottom-sipcore-locparam-01.txt
>>> 
>>> I didn't get any comments on my answers given to Dales mail which also covered the comments made within the meeting report.
>>> 
>>> ETSI is still looking forward on processing this document for their solution on Emergency Call due to the Project of  the European Union Mandate: M493.
>>> 
>>> Comments and improvements are welcome.
>>> 
>>> Question is how to proceed further since I did not get any further comments since my last mail on 4th April.
>>> 
>>> Best Regards
>>> 
>>> Roland
>>> 
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>> Gesendet: Dienstag, 23. Mai 2017 14:45
>>>> An: Jesske, Roland; Bruno Chatras; James Winterbottom; Andrew Hutton
>>>> Betreff: New Version Notification for draft-winterbottom-sipcore-
>>>> locparam-01.txt
>>>> 
>>>> 
>>>> A new version of I-D, draft-winterbottom-sipcore-locparam-01.txt
>>>> has been successfully submitted by Roland Jesske and posted to the IETF
>>>> repository.
>>>> 
>>>> Name:		draft-winterbottom-sipcore-locparam
>>>> Revision:	01
>>>> Title:		Location Source Parameter for the SIP Geolocation
>>>> Header Field
>>>> Document date:	2017-05-23
>>>> Group:		Individual Submission
>>>> Pages:		8
>>>> URL:            https://www.ietf.org/internet-drafts/draft-winterbottom-
>>>> sipcore-locparam-01.txt
>>>> Status:         https://datatracker.ietf.org/doc/draft-winterbottom-
>>>> sipcore-locparam/
>>>> Htmlized:       https://tools.ietf.org/html/draft-winterbottom-sipcore-
>>>> locparam-01
>>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-
>>>> winterbottom-sipcore-locparam-01
>>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-winterbottom-
>>>> sipcore-locparam-01
>>>> 
>>>> Abstract:
>>>> There are some circumstances where a geolocation header field may
>>>> contain more than one location value.  Knowing the identity of the
>>>> node adding the location value allows the recipient more freedom in
>>>> selecting the value to look at first rather than relying solely on
>>>> the order of the location values.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission until the htmlized version and diff are available at
>>>> tools.ietf.org.
>>>> 
>>>> The IETF Secretariat
>>> 
>>> _______________________________________________
>>> sipcore mailing list
>>> sipcore@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sipcore
>> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore