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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 20 September 2017 20:45 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 26D121320D8 for <sipcore@ietfa.amsl.com>; Wed, 20 Sep 2017 13:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 g66ygFteU3Th for <sipcore@ietfa.amsl.com>; Wed, 20 Sep 2017 13:45:07 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 B40771320B5 for <sipcore@ietf.org>; Wed, 20 Sep 2017 13:45:06 -0700 (PDT)
X-AuditID: c1b4fb3a-617ff700000051a3-00-59c2d3502467
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A6.8B.20899.053D2C95; Wed, 20 Sep 2017 22:45:04 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.6]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0352.000; Wed, 20 Sep 2017 22:45:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Jesske, Roland" <R.Jesske@telekom.de>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter
Thread-Index: AdMgpPpaGGJ4RYVmTLCLOQ8COa0QNgRKYIsgACAyS3A=
Date: Wed, 20 Sep 2017 20:45:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B562E74F9@ESESSMB109.ericsson.se>
References: <87cf2edcef014e268e000ef358cc3c2c@HE105828.emea1.cds.t-internal.com> <FRAPR01MB04835E32A47072E2DFD00673F9610@FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <FRAPR01MB04835E32A47072E2DFD00673F9610@FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B562E74F9ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbE9XDfg8qFIgyk7JC2a7nSxWXz9sYnN gcljyZKfTB5tLxUCmKK4bFJSczLLUov07RK4Mra+28pc8LqyYsX/VtYGxl/ZXYwcHBICJhK3 5qZ2MXJxCAkcYZSY92MGUxcjJ5CziFFixgxJkBo2AQuJ7n/aIGERgWCJz9N3sYPYwgIlEvs/ LWKGiJdK3H51iB3CtpJYufIs2BgWAVWJczdOgsV5BXwlPp37zASxC2j81O9/wZo5BWIkLv+Z D9bAKCAm8f3UGjCbWUBc4tYTiLiEgIDEkj3nmSFsUYmXj/+xQthKEiu2X2KEqM+XaLs3iQli maDEyZlPWCYwCs9CMmoWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkbR4tTi 4tx0IyO91KLM5OLi/Dy9vNSSTYzA2Dm45bfVDsaDzx0PMQpwMCrx8L6MPRgpxJpYVlyZe4hR goNZSYR3wrlDkUK8KYmVValF+fFFpTmpxYcYpTlYlMR5HfZdiBASSE8sSc1OTS1ILYLJMnFw SjUwsq2LVtxwUJ55wtY7DyvbWzkqbrQ8Zv3Wfds29PPBTxnz/7469Ddlaf4Dh1XXi1y/GFb7 ZHgbKpoIMOcv4a2O+uMhcdVKIC6pJOfPF8OVqSKPtPW/3UxeEKsV0XpxBteVm5/9Zbg2/XJW fP7t79pna184JUwy/VpVL2wrUvr/yaoooQP23wW9lFiKMxINtZiLihMBc7abDpkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/iYehxkSkmmq3k9xMz9QPheMA8Mw>
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: Wed, 20 Sep 2017 20:45:09 -0000

Hi,

I am ok with the draft as such, but I have a few comments, in addition to those given by Paul.

First, there are some MUSTs and MUST NOTs, without any clear justification.

For example:

"Only a fully qualified host name is valid, an IP address MUST NOT be added by an entity conforming with this specification."

"A UE MUST NOT provide a loc-src parameter value."

Second, "UE" is not an IETF term. You should use "UA". But still, I think you need to be a little more clear what exactly you mean. Because, a B2BUA also implements a "UA", but I assume you don't want to prevent it from using the mechanism?

Third, related to the first, why do you mandate the value to be a FQDN?

Fourth, I am pretty sure the security folks are going to request more text on the fact that you don't know whether the receiver of the parameter supports it or not, which means it might not be removed (and, thus, forwarded e.g., to a non-trusted network).

Regards,

Christer




From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Jesske, Roland
Sent: 20 September 2017 07:10
To: sipcore@ietf.org
Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter

Dear all,
since I did not get any comments on our draft it look for me that people are happy with the content.

So I would like to ask the group for adoption of this draft.

Best Regards

Roland

Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von Jesske, Roland
Gesendet: Dienstag, 29. August 2017 10:59
An: sipcore@ietf.org<mailto:sipcore@ietf.org>
Betreff: [sipcore] draft-winterbottom-sipcore-locparam-01.txt and Liaison Statement to IETF on location source parameter

Dear all,
since I have uploaded the latest draft on draft-winterbottom-sipcore-locparam-01.txt and the last clarification on questions were given on 23. May I did not get any further comment.



With a reference to this draft a Liaison from ETSI ( https://datatracker.ietf.org/liaison/1527/ ) is waiting for action.



The liaison from ETSI is asking on the progress of the draft for their solution on Emergency Call due to the Project of  the European Union Mandate: M493.

My question is, since we have no open questions, if we can now progress the draft.



Thank you for consideration.



Best Regards



Roland