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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 25 September 2017 13:05 UTC

Return-Path: <christer.holmberg@ericsson.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 32C4B1342F8 for <sipcore@ietfa.amsl.com>; Mon, 25 Sep 2017 06:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aCVtPuM24Fiz for <sipcore@ietfa.amsl.com>; Mon, 25 Sep 2017 06:05:00 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E805B1342E8 for <sipcore@ietf.org>; Mon, 25 Sep 2017 06:04:59 -0700 (PDT)
X-AuditID: c1b4fb25-967ff70000005333-ea-59c8fefa52e2
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 62.66.21299.AFEF8C95; Mon, 25 Sep 2017 15:04:58 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.6]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0352.000; Mon, 25 Sep 2017 15:04:57 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Dale R. Worley" <worley@ariadne.com>
CC: "R.Jesske@telekom.de" <R.Jesske@telekom.de>, "tasveren@sonusnet.com" <tasveren@sonusnet.com>, "sipcore@ietf.org" <sipcore@ietf.org>, "a.james.winterbottom@gmail.com" <a.james.winterbottom@gmail.com>
Thread-Topic: [sipcore] draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter
Thread-Index: AQHTNaXWGGJ4RYVmTLCLOQ8COa0QNqLFcBCAgAA0q4A=
Date: Mon, 25 Sep 2017 13:04:57 +0000
Message-ID: <D5EEDA7E.22697%christer.holmberg@ericsson.com>
References: <87377bbjho.fsf@hobgoblin.ariadne.com> <ca5a66bc-c238-335f-a78d-1596a08e189a@alum.mit.edu>
In-Reply-To: <ca5a66bc-c238-335f-a78d-1596a08e189a@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E25C84D0003CBE4388DD6ABE3B50E4AF@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCIsWRmVeSWpSXmKPExsUyM2K7k+6vfyciDc6eELK4t+kni8WKDQdY LZrudLFZfP2xic1idud7JouXJ8oc2Dz+vv/A5DF5/1dmj52z7rJ7LFnyk8nj0uf/7B5tLxUC 2KK4bFJSczLLUov07RK4Mg6cus9acI+9YlfXJdYGxolsXYycHBICJhK/rk1h72Lk4hASOMIo Me3VVhaQhJDAIkaJ6481uxg5ONgELCS6/2mDhEUEAiW6dh5jAqlnFjjHKPG1ay9YvbBAncT+ vkXMEEX1Eh+WbWcB6RURsJJYvdEGJMwioCqxv6cbrIRXwFri2fadzBCrMiT2nd7NBlLOKeAg 0bhOACTMKCAm8f3UGiYQm1lAXOLWk/lMECcLSCzZc54ZwhaVePn4HyuILSqgJ7HhxG12iLii RPvTBkaIXj2JG1OnsEHY1hIrl71hgbC1JZYtfA11jqDEyZlPWCYwis9Csm4WkvZZSNpnIWmf haR9ASPrKkbR4tTipNx0I2O91KLM5OLi/Dy9vNSSTYzAuD245bfqDsbLbxwPMQpwMCrx8N59 cSJSiDWxrLgy9xCjBAezkggv83egEG9KYmVValF+fFFpTmrxIUZpDhYlcV7HfRcihATSE0tS s1NTC1KLYLJMHJxSDYzxNw59ChQOf8Xx/OSHrKcrJX9wfRM0PtlgxSdpJrql3ydUk6HZtGjT gVMbvjE9P7Pp/aOU3zVcO/YIlQoJGcXGmL07WF0g7HcwasrC6YrqmQJit7jWfn8Yt1r20YbW ZwWMaQdaPReJzjKvtgoV1mLOMZCZHD/XqHRLDLtlvMO2UxFSyzoF1yuxFGckGmoxFxUnAgBh 4zUw1wIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/NPPrcOfS89K_eaBQLUQ4vqItYFo>
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:05:01 -0000

Hi,

>>>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.

I don¹t think I said ³IMS² :)

But, the draft DOES say that the identifier must only be used within a
trusted domain.

Regards,

Christer