[Pidloc] New Non-WG Mailing List: PidLoc

IETF Secretariat <ietf-secretariat@ietf.org> Fri, 27 July 2018 20:32 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: PIdLoc@ietf.org
Delivered-To: pidloc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A26AC130DF5; Fri, 27 Jul 2018 13:32:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: PIdLoc@ietf.org, Dirk.von-Hugo@telekom.de, sarikaya2012@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153272356261.413.16107362846124064304.idtracker@ietfa.amsl.com>
Date: Fri, 27 Jul 2018 13:32:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/8VPRR88Hrf-YohuiD_LN5s11_6w>
X-Mailman-Approved-At: Mon, 30 Jul 2018 07:16:20 -0700
Subject: [Pidloc] New Non-WG Mailing List: PidLoc
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.27
List-Id: <pidloc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pidloc>, <mailto:pidloc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pidloc/>
List-Post: <mailto:pidloc@ietf.org>
List-Help: <mailto:pidloc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pidloc>, <mailto:pidloc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2018 20:32:43 -0000

A new IETF non-working group email list has been created.

List address: PIdLoc@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/pidloc/
To subscribe: https://www.ietf.org/mailman/listinfo/pidloc

Purpose:
 In IdLoc protocols like LISP, ILA, etc.  separation between (fixed)
Identifier and (dynamic) Location is proposed to find optimum path for data
packets to/from moving devices

The threats against privacy in IdLoc protocols include

location privacy where if a third party can at any time determine the IP
location of some identifier, then the device can at one point be IP
geolocated and

movement privacy where if a third party can determine that an identifier
has changed locator(s) at time T, then even without knowing the
particular locators
before and after, it can correlate this movement event with other
information to create a binding between the identifier and a person.

Privacy and security work is needed both in control and data plane

There is an existing draft https://www.ietf.org/id/
draft-nordmark-id-loc-privacy-00.txt that is expected to serve as a
starting point.

The work is expected to clear the way for a wider acceptance/deployment
of IdLoc protocol. This may open new application areas such as in future
mobile networks.

In future mobile networks more efficient differentiation of packet
handling according to specific service demands (QoS) are expected. Traditional
tunneling and encapsulation between IP addresses (= Id and/or Loc) have
disadvantages