Re: [sipcore] AD Review: draft-ietf-sipcore-locparam

<R.Jesske@telekom.de> Wed, 22 January 2020 06:58 UTC

Return-Path: <R.Jesske@telekom.de>
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 2EBED120013; Tue, 21 Jan 2020 22:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 1MK6FlJa7GxF; Tue, 21 Jan 2020 22:58:12 -0800 (PST)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 4CFBE120048; Tue, 21 Jan 2020 22:58:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1579676291; x=1611212291; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=M4JPj/ng86FPREfBfrn2YrnLGzmAJOS7XYMPHGSAZC4=; b=afCHlcvM7uKxFZga0DpqSNZHBjHTb0gUhmwUo0AuzGr4GT9mOd0JVxW+ mp21zkAfWsLlBV+WdIoJ3g4iMIdt6IIjPxT3caQ8KFPEtKfnj5ZnghI8U Rye7vh++zz+mu1hgzq6AmBsaM9oBUSPw2UH6lXDHcpc/TdiMCQ+tN/zl6 7nWuISUPtraszTt29KoUsQnAywolb8zDGKfzqG++1C0U6RCKQoZT5nQes /OpfR/9NVkAsvD9N6VAPhSXpk+5KkcsI6Rq7u+QKhjfIJ++QIsqf8YDwV FdGipGHxFlbPIPOgrJ+S7qrPJO5UlGH2/hlVyuk6wf+8rHTZhDLJZZXG4 Q==;
IronPort-SDR: cVGGEf4jEKDaHaAFVKzhSpW4vB+Mnw4kegtqS0FGp4+dt/K6vLriVU8tafuVft6zLwXq3s5G+8 OhCaWj4M3Ccg==
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jan 2020 07:58:08 +0100
IronPort-SDR: 3Ttxk+5X1NYPnBeQVIJNjyKRsz2FjiCdHeQ7x46K9sGdT2wlkOuLfRUc6x0omT9yKFijBiZQZe zYvLGQ4IjcvtuFIsof7BJi7mOnJt5dwwY=
X-IronPort-AV: E=Sophos;i="5.70,348,1574118000"; d="scan'208";a="31432228"
X-MGA-submission: MDGA/e9uCRPmhW84TsVie3B4fC/djhfJUJskkLugPKkDnIfgFVS+blrANBi3FWaozeehJM8+HzUuLcuiWAxEgtrFHQ6X8wNjL2I8Xg/Y/cxhDe2j8QPLpGKR8mb6TOwhHZWitGul+g8O+a8weayxWGmYrhUvj3eyD2lidMXb+XiSyw==
Received: from he105716.emea1.cds.t-internal.com ([10.169.118.52]) by QDEC97.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 22 Jan 2020 07:58:09 +0100
Received: from HE105715.EMEA1.cds.t-internal.com (10.169.118.51) by HE105716.emea1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 22 Jan 2020 07:58:08 +0100
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105715.EMEA1.cds.t-internal.com (10.169.118.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 22 Jan 2020 07:58:08 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.23) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 22 Jan 2020 07:58:05 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aLrQkWArJGxK9YH3wXO7GeLcTtuk3blDH7IxVt9V8AbIiiH0eNXO71hS1LZ9VIBJeH6BhAFHRTJh3XQHasGm4mwHrynTqvOW3P4SpN4Ml8LkNUvuXnlkeQt0YAro0ciyB7FAokoA66lsI15BUIwCKdzRwpuAh1ZH91m4lAzlrwndN7lfH4ngRKNIRntF0fpA967z/EBQ1vkO2PSLXUNLe7cJoVrqkXiu50B5QGKNohGt7SW6ymtEPtYHTkw9wuI2oo8SrzeeQLJ0WghGV1qDuw9X20lIuZOG2VctImCSZdZSoWBq4RBQsTN8juKfJpmMJRovTtbDrRGgbXgv6Gyn3w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=M4JPj/ng86FPREfBfrn2YrnLGzmAJOS7XYMPHGSAZC4=; b=il+4PJwZh+1kAkJzTQATRjsp4hP+rpqdPOjvBQgPuxExOHOAOfIP2mIIz8ZEYb4HOUGrdxcPFZgJ3PLPJEaj8wU7hG0Y1DVTz3Ztg5sEBX+LVuzGOyuyiSH3DD2wNbD0aRwNOPtvzpvx+Ri9RQin2mkJItaOWUnInQTbbjeloQGK9Sel3cH4rRwV4z5xeZOeFnAunv50RAKE3aRmJ6LK06G6JyL/PttR4gLm+qE/FDiieBfGAcLUUfqwwxptb95sJWKkqKa/MuMe6z7s8tMAJ7c7MUfjGnti+mSmpbegQ4OVgcIQ2s7IJGc56f/3Ob56KyfiHVR4rcTKXVb8fLu44g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEXPR01MB0045.DEUPRD01.PROD.OUTLOOK.DE (10.158.162.143) by LEXPR01MB1248.DEUPRD01.PROD.OUTLOOK.DE (10.158.164.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.25; Wed, 22 Jan 2020 06:58:08 +0000
Received: from LEXPR01MB0045.DEUPRD01.PROD.OUTLOOK.DE ([fe80::c111:a5e1:795:5c35]) by LEXPR01MB0045.DEUPRD01.PROD.OUTLOOK.DE ([fe80::c111:a5e1:795:5c35%6]) with mapi id 15.20.2644.027; Wed, 22 Jan 2020 06:58:07 +0000
From: R.Jesske@telekom.de
To: adam@nostrum.com, draft-ietf-sipcore-locparam.all@ietf.org
CC: sipcore@ietf.org
Thread-Topic: AD Review: draft-ietf-sipcore-locparam
Thread-Index: AQHVymmmVAWzl4+Fp06gO6Pi0dJ70Kf02Pcw
Date: Wed, 22 Jan 2020 06:58:07 +0000
Message-ID: <LEXPR01MB0045B239469FDD604493C0EDF90C0@LEXPR01MB0045.DEUPRD01.PROD.OUTLOOK.DE>
References: <fa9fde28-8366-3b05-cbf7-69623b2f8b08@nostrum.com>
In-Reply-To: <fa9fde28-8366-3b05-cbf7-69623b2f8b08@nostrum.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de;
x-originating-ip: [164.19.4.101]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0bc435b9-01d8-45e0-6f9d-08d79f086fc0
x-ms-traffictypediagnostic: LEXPR01MB1248:
x-microsoft-antispam-prvs: <LEXPR01MB1248AB7726F60B34D7B260E1F90C0@LEXPR01MB1248.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 029097202E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(376002)(136003)(39860400002)(346002)(199004)(189003)(66574012)(26005)(66946007)(4326008)(5660300002)(55016002)(71200400001)(86362001)(66476007)(478600001)(110136005)(76116006)(7696005)(66446008)(186003)(81166006)(33656002)(9686003)(2906002)(316002)(66556008)(81156014)(8936002)(64756008)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:LEXPR01MB1248; H:LEXPR01MB0045.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: D0AlHFpzWt4ZKUPdZQiUFvRRuFa/ylXJDm/zm/SzA4Zwz+8MJkW95ANJCnwYg1Bitph3bGz7N+yPY0XoqogQ3n0mATK3OvBKSADK8IQMZJKA3HnizZeuOud52w58kfg+E8mhIbUDPXbuoYSTn6YjyU/dg+r/L3d97LXDO/D62iFcUwrpjBNKfRcTqFvMNuX4r5NymeY9jV7jK1Vcii+ypk+75cs5ZP2y076BobdYL1ltQGOqhXSJyJVWlZwXDkUxzSCO6LRoC96plfQ9U1iu+m6ZwVO0bYK1dCNhsfaXh7y6BIDOhFNW1Mk2CPG8cMBk9tkkozqPSzrQNwozX6ZejywZDZ9C7Ea+QUWjURpX8Sl9nIJBDsCfOy7cllci3bIroslY1isuNVypQFnEYRcglAQgrlfA/l7nz6V0MG19YumnW30cQozQOgRL6DaTOxWc
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0bc435b9-01d8-45e0-6f9d-08d79f086fc0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2020 06:58:07.8322 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: gSBCQ29ZtkLoIZ44etFSeyLP5UCJfj1fTdJnaP07pS269KDFgGdxsWk7Zb9bBapjj7mRn5NogKWyuHAyqpOP+Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB1248
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/WDfA7NYWSgEFOaPWxJkqqBdM7n8>
Subject: Re: [sipcore] AD Review: draft-ietf-sipcore-locparam
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Jan 2020 06:58:15 -0000

Hi Adam,
Thank you for your review.
I have incoperated your proposed changes in the draft and wait for possible further comments.

I have changed the sentence along your proposal.

>    The "loc-src" parameter adds the location source generating the
>    locationValue to allow recipients to make informed decisions about which of multiple values to use.

Thank you and Best Regards

Roland
-----Ursprüngliche Nachricht-----
Von: Adam Roach <adam@nostrum.com> 
Gesendet: Dienstag, 14. Januar 2020 00:32
An: draft-ietf-sipcore-locparam.all@ietf.org
Cc: 'SIPCORE' <sipcore@ietf.org>
Betreff: AD Review: draft-ietf-sipcore-locparam

This is my AD review of draft-ietf-sipcore-locparam. Thanks for the work that went into creating this document. I find no serious issues, and will be requesting IETF last call momentarily.

I have included a small number of editorial suggestions below. Please treat them the same as you would any other IETF last call comments.


---------------------------------------------------------------------------

§1:

>    These solutions don't preclude the use of UE provided location but

Nit: "UE-provided"

>    "loc-src"."How the entity adding the locationValue to the header

Nit: extra quotation mark before "How"

---------------------------------------------------------------------------

§3:

>     All of them allow the UE to provide location information, however,

Nit: "...information; however..."

---------------------------------------------------------------------------

§3:

>    The "loc-src" parameter adds the location source generating the
>    locationValue to increase the trustworthiness of the location
>    information.

Given that this mechanism doesn't add any authentication mechanisms, I expect that this assertion will raise some eyebrows with the security folks. From a security perspective, the information appears to be exactly as trustworthy as it is without this mechanism.

I recommend that this sentence be struck, or changed to something more along the lines of: "...to allow recipients to make informed decisions about which of multiple values to use."

---------------------------------------------------------------------------

§7:

>    As already stated in [RFC6442] securing the location hop- by-hop,

Nit: "stated in [RFC6442], securing..."

Nit: "...hop-by-hop..."

>     between the domains.  If such trust domain is not given it is

Nit: "...is not given, it is..."

---------------------------------------------------------------------------