IETF Logo Mail Archive

Re: [sipcore] draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 25 September 2017 13:01 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 2651C1342F8 for <sipcore@ietfa.amsl.com>; Mon, 25 Sep 2017 06:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 kdykzhaGl3zN for <sipcore@ietfa.amsl.com>; Mon, 25 Sep 2017 06:01:50 -0700 (PDT)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id DFC221342E8 for <sipcore@ietf.org>; Mon, 25 Sep 2017 06:01:49 -0700 (PDT)
X-AuditID: 1207440d-86bff70000000f42-b1-59c8fe3c4807
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id E4.3B.03906.C3EF8C95; Mon, 25 Sep 2017 09:01:49 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id v8PD1lU4008619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 25 Sep 2017 09:01:47 -0400
To: "Dale R. Worley" <worley@ariadne.com>
Cc: christer.holmberg@ericsson.com, R.Jesske@telekom.de, tasveren@sonusnet.com, sipcore@ietf.org, a.james.winterbottom@gmail.com
References: <87377bbjho.fsf@hobgoblin.ariadne.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ca5a66bc-c238-335f-a78d-1596a08e189a@alum.mit.edu>
Date: Mon, 25 Sep 2017 09:01:47 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <87377bbjho.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCKsWRmVeSWpSXmKPExsUixO6iqGv770SkwftOfot7m36yWFyYeZjR oulOF5vF1x+b2Cxmd75nsnh5osyBzWPy/q/MHr++XmXz2DnrLrvHkiU/mTwuff7P7tH2UiGA LYrLJiU1J7MstUjfLoEr493VdWwFc9gr1vz1aGC8x9rFyMEhIWAisWY1YxcjF4eQwA4miaaz q5ghnIdMEm9/7wdyODmEBeokJr84ywbSICKgKdGxIAekhlmgk1Hi0acnjCBxIQEjie3nq0HK 2QS0JOYc+s8CYvMK2Esc/T+DDcRmEVCVWHCgnxHEFhVIk/i3+ywjRI2gxMmZT8DqOQWMJa4t eghWzyxgJjFv80NmCFtc4taT+UwQtrzE9rdzmCcwCsxC0j4LScssJC2zkLQsYGRZxSiXmFOa q5ubmJlTnJqsW5ycmJeXWqRrpJebWaKXmlK6iRESCbw7GP+vkznEKMDBqMTDG/HveKQQa2JZ cWXuIUZJDiYlUd67fCcihfiS8lMqMxKLM+KLSnNSiw8xSnAwK4nwMn8HyvGmJFZWpRblw6Sk OViUxHnVlqj7CQmkJ5akZqemFqQWwWRlODiUJHh9/gI1ChalpqdWpGXmlCCkmTg4QYbzAA1X A6nhLS5IzC3OTIfIn2K05Ljx8PofJo6enhtA8tLD23+YhFjy8vNSpcR5//8BahAAacgozYOb CUtsrxjFgV4U5g0HGcsDTIpwU18BLWQCWtg7FWxhSSJCSqqBUXrzlobvp55JH1yao8s4efqV CRO+MB76ErPoQ9OUih9Mu2+Kaae72HS9eCex/86d3v1H9P8Kyk1+6sWm1lfK965xQ0PAG7/f uY++H1v75uCmlUekVLaKS07MZp89oUXXIVpoHWOd/qIn7ZVbntsbrD7bF3Cv8UAp58uF67Xl Mz43XjZZNSe2uUGJpTgj0VCLuag4EQCPfeUxRwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/BsS2luGjAoW78M-m3Kz_x4ck5Os>
Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter
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: Mon, 25 Sep 2017 13:01:51 -0000

On 9/24/17 10:27 PM, Dale R. Worley wrote:
> Paul Kyzivat <pkyzivat@alum.mit.edu> writes:
>> Surely there ought to be some semantics to this. I presume it is to be
>> an identifier of something, and presumably there then need to be rules
>> for resolution/comparison/etc.
>>
>> Otherwise I could just enter XYZZY.
> 
> If usage is confined to a single administrative domain (which is what I
> think Christer is saying), there don't need to be general semantic
> rules.  There don't even need to be general syntactic rules.

The usage isn't *restricted* to IMS. It is simply defined with the 
expectation that they are the ones who need it. If others are allowed to 
use it then there need to be some rules to ensure mutual understanding. 
Otherwise this is just using sip to tunnel another protocol.

The advantage of using FQDNs is that there are clear rules for 
assignment of those.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email