Re: [Pidloc] Pidloc in IETF Prague #104

Marco Liebsch <> Tue, 16 April 2019 16:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4531112047E for <>; Tue, 16 Apr 2019 09:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OGFTfFi-4gAw for <>; Tue, 16 Apr 2019 09:08:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0A5931204AD for <>; Tue, 16 Apr 2019 08:46:14 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 982E5F200F; Tue, 16 Apr 2019 17:46:11 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aR6QZ5jVVNNN; Tue, 16 Apr 2019 17:46:11 +0200 (CEST)
Received: by (Postfix, from userid 1001) id 46D10F202A; Tue, 16 Apr 2019 17:46:11 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D7392F200F; Tue, 16 Apr 2019 17:46:01 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0319.002; Tue, 16 Apr 2019 17:46:01 +0200
From: Marco Liebsch <>
To: "" <>, "" <>
CC: "" <>, "" <>, Umberto Fattore <>
Thread-Topic: [Pidloc] Pidloc in IETF Prague #104
Thread-Index: AdTmQ1mz3M0UO0PHTCCpL9dcG6vIRwABpJ6AA4QP3kAABB9d4A==
Date: Tue, 16 Apr 2019 15:46:00 +0000
Message-ID: <>
References: <LEXPR01MB06697AD320805F58B004443FD15A0@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE> <> <FRXPR01MB066429AC69CED822C889A1ADD1240@FRXPR01MB0664.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <FRXPR01MB066429AC69CED822C889A1ADD1240@FRXPR01MB0664.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: de-DE, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_69756203DDDDE64E987BC4F70B71A26DE5AABBDDHydraofficehd_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Approved-At: Tue, 16 Apr 2019 11:39:46 -0700
Subject: Re: [Pidloc] Pidloc in IETF Prague #104
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Apr 2019 16:08:42 -0000

Hi Dirk,

Traffic Identifier can be also something broader and more aggregate, e.g. all data traffic associated with a single user
or a group of users. Depends on how fine granular treatment policies should apply. This can be for example a PDU session
identifier or the associated UE IP address. UPF/DPN as N6 endpoint, yes, that is the data plane anchor where downlink
traffic should be transported to. Dependent on its deployment, it can reveal more or less accurate location information.

Best regards,

From: []
Sent: Dienstag, 16. April 2019 15:53
Cc:;; Umberto Fattore
Subject: RE: [Pidloc] Pidloc in IETF Prague #104

Dear all,
sorry for delayed reply:
I agree that data plane will also be in scope of privacy issues for Id-Loc protocols – if I understood correctly the use case on ‘Location exposure of nearest User Plane Function to local (non-3GPP) Data Networks’ described by Marco and Umberto in addresses data plane issues.
@Marco and Umberto: ‘Traffic Identifier’ and ‘UPF/DPN N6 endpoint’ here serve as Id and Loc, right?
Kind regards

From: Behcet Sarikaya <>
Sent: Freitag, 29. März 2019 17:10
To: von Hugo, Dirk <>
Subject: Re: [Pidloc] Pidloc in IETF Prague #104

Hi Dirk,

Thanks for the minutes.

Let me add that there was some discussion on whether we should concentrate the privacy work on the control or data plane.
I thought the conclusion was control plane. However, thinking a little bit more on this, I came to the conclusion that we also need to work on the data plane.
The reason being as some previous work has shown, changing identifiers/locators that the UE uses from one session to another  improves a lot the privacy issues.

What do you think?


On Fri, Mar 29, 2019 at 10:52 AM <<>> wrote:
Dear all,
as announced before we actually had our side meeting here in Prague and some fruitful discussions.
I’d like to share with you some notes of the 1-hour session where seven people attended on site and about four more on the phone/webex. Sorry for the inconvenience of a sub-optimum audio connection.
I will also attach the slides shown and the link provided by Marco.

Dirk presented chairs slides - focus was more on the open questions (gaps and problems) to be solved than on solutions.
Erik commented on use cases as edge computing in IoT (location is an issue here) and consumers sharing voluntarily Id and Location on application layer – which of course also should not be leaked beyond intended recipients.
VPN like closed groups pose less problem than rather consumer scale device numbers (walled garden or separate domains).

Shunsuke presented 5G use case attempting to include Id-Loc compatible with 3GPP architecture.
Location exposure of nearest UPF to local (non-3GPP) Data Networks (maybe untrusted) may raise privacy issues on related location information (from UPF to derive that of UE).

Next steps might be a more complete collection and classification of use cases and thereof identification of a requirements set to be demanded from potential solutions.

Marco and Umberto promised and meanwhile did to provide a link to related slides in DMM (draft at pointing to the LDN problem:

ID-LOC applies to the data network’s DPN and the user’s current (edge) UPF (serving as session anchor).

A question was whether slicing shall be provided via Id-Loc? Rather than that a low latency service on DP/UP would be the goal.
Somebody mentioned that also tunneling between two endpoints could be seen as Id-Loc approach.
Thanks for comments and updates/corrections by all participants.
Let’s continue discussion on the list.

Kind regards

Pidloc mailing list<>