[TLS] New Non-WG Mailing List: PidLoc

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 10 August 2018 14:08 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A08F130DF7 for <tls@ietfa.amsl.com>; Fri, 10 Aug 2018 07:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gtorLLSTLj8M for <tls@ietfa.amsl.com>; Fri, 10 Aug 2018 07:08:21 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CDB2129C6A for <tls@ietf.org>; Fri, 10 Aug 2018 07:08:21 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id o11-v6so2040913wmh.2 for <tls@ietf.org>; Fri, 10 Aug 2018 07:08:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to:cc; bh=DNUaCB8r1WmkI6Vej4KGjf2Efj0Bbdy8Q3fVr3L6BtE=; b=Yh+1mjwAZ7hbCZmFM0q0wTJ/z5zSolAl96tUu2nQvD/z34HYF0d8zfXVSXR9d7YGJJ JbMkdU8kbjeoahZ29WiXKbXm+8cAjRsxyUuZEPgakG5SW0y9Rahey/Vslelc+k31j9nC u40Dlx5eP/taCuvaSD212Si1O+B6hhfJupXOqnqQoIrMViJsig26GgP2d6FhWCtN/H7q nv4yGAhufVnyj6Oag0vuAGlZ7VhYDZp6twS7Z8G4sFFvVjzN5Rq7GBspzZdzi+7/aGUm 28AGIU8XCjtXRdcoKT8h7XpITSQAdGRneD/aF6qIaer91vUgHhsOSsFM/t3I0WnjOOSt KDAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to:cc; bh=DNUaCB8r1WmkI6Vej4KGjf2Efj0Bbdy8Q3fVr3L6BtE=; b=hIVsOa1jLCkirUqJpAWaVGHFomdXeJv7KqkJlPf5uooOIztsw0NyUcd2nnvOakxWPS Q8zR+w7OVzxH9YWcgx5mYjreElvfZtkw8ftk/B/i6ZlGb0+yBUp434skGMv408evmo4O aQaTZ14GKL47k2lgAO2S3oqOFLQijF4HR9Ohi2zXZPHpguDdOPHvg1+xOiqNX3U2FGou kdtfNekMDwHOle2spftI8XVD68bT65XruLb5g2OP7+6gaUgWJVgSl7JCviWkhR0GglJV YqAktofOUQSFZ1JPQNCLH1PxovgB1nsKVWogIIvcUibFDDocwtckusqtfZD8ths4ecZk zaSA==
X-Gm-Message-State: AOUpUlE2+b3SElrzgTIWANVvA9xP30vxxxbQBv8YZIbVTiiejIj4Gv9L cg2MMlB7KZ9O2RG+HaC7MJxuMSivj0HWt9x2YHaNkw==
X-Google-Smtp-Source: AA+uWPz2bL3yWFTYohhhaSg2AFgHd63Vs4ffh3RgSDFVAOaL0CY5rGAfNB0a+7+1xCunJ1qrXvTq/onol8OSD95dj9A=
X-Received: by 2002:a1c:1a02:: with SMTP id a2-v6mr1773859wma.52.1533910099478; Fri, 10 Aug 2018 07:08:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:adf:ef8f:0:0:0:0:0 with HTTP; Fri, 10 Aug 2018 07:08:19 -0700 (PDT)
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 10 Aug 2018 09:08:19 -0500
Message-ID: <CAC8QAccagFK9BQ8renCaysihskCyMxAhN83UxHL-+fxwMb9+0Q@mail.gmail.com>
To: tls@ietf.org
Cc: Dirk.von-Hugo@telekom.de
Content-Type: multipart/alternative; boundary="00000000000098cc7e05731546e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/dnBFiVtycUwWSo9J9U-_0H0JfB4>
Subject: [TLS] New Non-WG Mailing List: PidLoc
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2018 14:08:22 -0000

TLS chairs, please approve this non-member post.


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