
From nobody Tue May 14 08:22:26 2019
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C241200E5 for <pidloc@ietfa.amsl.com>; Tue, 14 May 2019 08:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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, URIBL_BLOCKED=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 8HZqfwkG6x-n for <pidloc@ietfa.amsl.com>; Tue, 14 May 2019 08:22:23 -0700 (PDT)
Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 9FF5112015A for <pidloc@ietf.org>; Tue, 14 May 2019 08:22:23 -0700 (PDT)
Received: by mail-yw1-xc33.google.com with SMTP id 18so14278606ywe.7 for <pidloc@ietf.org>; Tue, 14 May 2019 08:22:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=TeKSZFKR1H7414aW/X8QCFzQyLjk9eDEFwkCnRL9TvU=; b=lW/ekTV2ot/UKUBcBUbN3lA4ccKjt5uPE0lrMolXxNb6LJdVMMhMQnUf2lUk1Sm1U6 VUBl0PO6QByJedYbu2gxvYotz04z71rAVT2JSIUJHnGXRovP3+cEuO0lwa/ydiQpIFea p+gR8dfhrOpYy+wqdqBPMXo6wbuTDJnA1mEMUFhVhu3M4tCJMceCDVPjQ+TFZvbR95Nf wXpnUS2CCwR9xBdtWF/EXvGCDKIvnP7HebtTX81CnpVo+lhSe8ZPHHYtsOCB/uyvAd3u 2lFzqelccIf3fVx37P5/v6SOBC7HIv+/0GwBDtCCxvG9r/gW9T4OTgy/PMMeVVI12wJy U1Lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=TeKSZFKR1H7414aW/X8QCFzQyLjk9eDEFwkCnRL9TvU=; b=ckd7vREa2d1d+Jf1y0wi8Qs2iNc7zXNZl6c4DjQ3HfJ3+nyajiaPiqAatpfl9jRcA2 jSkuTSoJzFABc7iqUaRPWARDs46FkJry0iE3INAN2cENJMBCg6FIv0MTHMm/cuEilhKU AgFgUC24cSjPcQq28Eq+EhvcOLLzM6+etyfNzL/RVeJu4iDdCk9Aqq9uK7rcUVPW2KHX 9lXrpSanWqOF6E5Hb+L3CEXFftbacvW3G46Sbf9MnMM//0S1Y9P4Wl7MVgSFPvLdQkPk ru9Xm+AZ/zlqXbeCHzYtHOmA48X2rxqSEpI7XxepKLdyGlqUuViYL8wxfZeI1+oybCDi 42JA==
X-Gm-Message-State: APjAAAXGU3Jb777wsb9+mVGhc+eLjt7E4NVCPWZ3qN4yjKIDqvfdM0sW d2heOgoxdNHiHZNhvu2eV5S9yvUvjy3zN1CHXSszVpQd
X-Google-Smtp-Source: APXvYqwJO+X7l/rCIdukmg6KI+TXuqPPY6FZIE1JBE68ArNUHQV2Jd4r0UQFQc5HHGpT76Cxrb40SN1Wv0eUoBVeFl0=
X-Received: by 2002:a81:351:: with SMTP id 78mr17443372ywd.323.1557847342644;  Tue, 14 May 2019 08:22:22 -0700 (PDT)
MIME-Version: 1.0
References: <155784681012.30242.12515312586897152818.idtracker@ietfa.amsl.com>
In-Reply-To: <155784681012.30242.12515312586897152818.idtracker@ietfa.amsl.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 14 May 2019 10:22:11 -0500
Message-ID: <CAC8QAcdY+GPY-YuNNDo8YdRzn4uSy+duAt_dLgvSaMA4Q0x1BQ@mail.gmail.com>
To: pidloc@ietf.org
Cc: "<Dirk.von-Hugo@telekom.de>" <Dirk.von-Hugo@telekom.de>
Content-Type: multipart/alternative; boundary="0000000000007904670588da9990"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/ZvHOeRDunQe1ciKSR6UlKrH4Qd4>
Subject: [Pidloc] Problem Statement for Secure End to End Privacy in IdLoc Systems
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 14 May 2019 15:22:25 -0000

--0000000000007904670588da9990
Content-Type: text/plain; charset="UTF-8"

Hello all,

We submitted Rev. 00 of Pidloc PS draft as follows.
Note that the draft author names are provisional and could change in future
versions.

To the list: please read the draft and send your comments to the list. Any
ideas, new use cases, improvements are very welcome.

Also we need to  develop a set of requirements which could be published as
a separate draft, please feel free to initiate it.

We hope to keep updating the draft for several weeks down the road. Expect
some new authors in already pretty crowded author list.

Regards,
Behcet & Dirk

A new version of I-D, draft-xyz-pidloc-ps-00.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>
> Name:           draft-xyz-pidloc-ps
> Revision:       00
> Title:          Problem Statement for Secure End to End Privacy in IdLoc
> Systems
> Document date:  2019-05-14
> Group:          Individual Submission
> Pages:          8
> URL:
> https://www.ietf.org/internet-drafts/draft-xyz-pidloc-ps-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-xyz-pidloc-ps/
> Htmlized:       https://tools.ietf.org/html/draft-xyz-pidloc-ps-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-xyz-pidloc-ps
>
>
> Abstract:
>    Efficient and service aware flexible end-to-end routing in future
>    communication networks is achieved by routing protocol approaches
>    making use of Identifier Locator separation systems.  Since these
>    systems require a correlation between identifiers and location which
>    might allow tracking and misusage of individuals' identities and
>    locations such operation demands for highly secure measures to
>    preserve privacy of users and devices.  This document tries to
>    identify and describe typical use cases and derive thereof
>    requirements to be fulfilled by privacy preserving Identifier-Locator
>    split (PidLoc) approaches.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>

--0000000000007904670588da9990
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div>Hello all,<div><br></div><div>W=
e submitted Rev. 00 of Pidloc PS draft as follows.</div><div>Note that the =
draft author names are provisional and could change in future versions.</di=
v><div><br></div><div>To the list: please read the draft and send your comm=
ents to the list. Any ideas, new use cases, improvements are very welcome.=
=C2=A0</div><div><br></div><div>Also we need to =C2=A0develop a set of requ=
irements which could be published as a separate draft, please feel free to =
initiate it.</div><div><br></div><div>We hope to keep updating the draft fo=
r several weeks down the road. Expect some new authors in already pretty cr=
owded author list.</div><div><br></div><div>Regards,</div><div>Behcet &amp;=
 Dirk<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"><=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,2=
04,204);padding-left:1ex">A new version of I-D, draft-xyz-pidloc-ps-00.txt<=
br>
has been successfully submitted by Behcet Sarikaya and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-xyz-pidloc-ps<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Problem Statement for Secure End t=
o End Privacy in IdLoc Systems<br>
Document date:=C2=A0 2019-05-14<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-xyz-pidloc-ps-00.txt" rel=3D"noreferrer" target=3D=
"_blank">https://www.ietf.org/internet-drafts/draft-xyz-pidloc-ps-00.txt</a=
><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-xyz-pidloc-ps/" rel=3D"noreferrer" target=3D"_blank">https:=
//datatracker.ietf.org/doc/draft-xyz-pidloc-ps/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-xyz-pidloc-ps-00" rel=3D"noreferrer" target=3D"_blank">https://tools.=
ietf.org/html/draft-xyz-pidloc-ps-00</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-xyz-pidloc-ps" rel=3D"noreferrer" target=3D"_blank">https:/=
/datatracker.ietf.org/doc/html/draft-xyz-pidloc-ps</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Efficient and service aware flexible end-to-end routing in fut=
ure<br>
=C2=A0 =C2=A0communication networks is achieved by routing protocol approac=
hes<br>
=C2=A0 =C2=A0making use of Identifier Locator separation systems.=C2=A0 Sin=
ce these<br>
=C2=A0 =C2=A0systems require a correlation between identifiers and location=
 which<br>
=C2=A0 =C2=A0might allow tracking and misusage of individuals&#39; identiti=
es and<br>
=C2=A0 =C2=A0locations such operation demands for highly secure measures to=
<br>
=C2=A0 =C2=A0preserve privacy of users and devices.=C2=A0 This document tri=
es to<br>
=C2=A0 =C2=A0identify and describe typical use cases and derive thereof<br>
=C2=A0 =C2=A0requirements to be fulfilled by privacy preserving Identifier-=
Locator<br>
=C2=A0 =C2=A0split (PidLoc) approaches.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</blockquote></div></div></div>

--0000000000007904670588da9990--


From nobody Mon May 27 08:15:34 2019
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD408120132 for <pidloc@ietfa.amsl.com>; Mon, 27 May 2019 08:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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_HELO_NONE=0.001, 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 8YqvSaeRTiGQ for <pidloc@ietfa.amsl.com>; Mon, 27 May 2019 08:15:31 -0700 (PDT)
Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 01F671201B5 for <pidloc@ietf.org>; Mon, 27 May 2019 08:15:30 -0700 (PDT)
Received: by mail-yw1-xc32.google.com with SMTP id 186so6756154ywo.4 for <pidloc@ietf.org>; Mon, 27 May 2019 08:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=+loR/vYzZwBnhum+Onf8cOLW4x8axn0xGJkMGChofbo=; b=m5WXWnuaH7PdonOkJEhOsdOVXnq4I2Q10lcUqmhYQvuZI0qslaZ3VTIUROSmB3wM7O 2fYooggZLQxIION56CRnoejcePo6FsTdUmk4pofmr7i2hABo4cUgGG0AgunKEQaYGqKp RmQyse5Rag7/qKII/DDigPqlN/KEn/1AfwFDPmaTvPytiVnKEEqO9QP3N2A/J8YDOqAh w/oyYL6s4EjzgELHI4Q8A34LUqaWKfPqGujetpcn/1oKD4Mv1ldkR2JiZ0rkp1vqu5Jl yPGj9lwv34Ini6MRbd9/x1DD4BsBfoqycwPw05fmLMPs8EhW3EoFtM2lGixBXwFSbPBD cb7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=+loR/vYzZwBnhum+Onf8cOLW4x8axn0xGJkMGChofbo=; b=E7FhrxW/VPdfFlnsE+Uzq7DEOcX4UGMvREsxXVFw67NlOOS77f63IDAxGXUmQhV3HV o1TA4FFuH6/lSG6NDOue7tkV52qqT3c/w/2+8xmPMsBRAbHLYJPhrgFKAzCeK7QpaYwN 4/CLEouTDyDvQ7o+8JY7EKjP6PH99HOTQ159na5pfUCPRR39YEHbkFphHrECHLwq+HHG LvoRlQEgbht7UcaARHotKfU2N/XAtZhhDUSPTLAyMWD/gmEHVoJyYJdCooAbuTzBu3XQ HjGzh/DNDQNBX3fp1RmVLV3kBCsQSo9G/o+iVmGc17np/mpEo+qHqVA+4vXmwVVqckMk 5Q2Q==
X-Gm-Message-State: APjAAAXvB9sZPYyCORgobiIu4vDwsOdbxMhWrd03SxuI8iw1u/8G5GSs EOp2mxJkye+3x79kY7r3nEuK5oiOvs/XgVy1l2JcenGV
X-Google-Smtp-Source: APXvYqxkHhOhVyhz43/q3/UrWvC5h0Q8AcEyYpd7fCJsQXc19V5r5R4PPsWBT/vEcVIhGrSmcXA6wQFl/wuNgE3tPkM=
X-Received: by 2002:a0d:eb8c:: with SMTP id u134mr17949267ywe.390.1558970129938;  Mon, 27 May 2019 08:15:29 -0700 (PDT)
MIME-Version: 1.0
References: <155896990052.658.14784539114024737548.idtracker@ietfa.amsl.com>
In-Reply-To: <155896990052.658.14784539114024737548.idtracker@ietfa.amsl.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 27 May 2019 10:15:19 -0500
Message-ID: <CAC8QAcefYgx2nQmRWg9c0hzG6X-Bn2=7gomhOfh2v83_qQq5gA@mail.gmail.com>
To: pidloc@ietf.org
Cc: "<Dirk.von-Hugo@telekom.de>" <Dirk.von-Hugo@telekom.de>, Padma Pillay-Esnault <padma.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000cf7f240589e004c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/K1nvs6BNajvsX45Hoxs14fq_n_I>
Subject: [Pidloc] REQUIREMENT DRAFT draft-xyz-pidloc-reqs-00 SUBMISSION
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 27 May 2019 15:15:33 -0000

--000000000000cf7f240589e004c2
Content-Type: text/plain; charset="UTF-8"

Folks,

Just now, we submitted the requirement draft Rev. 00.
Please read it, it is very short.
Send your comments, text contributions to the list.
Have a nice Memorial Day.

Regards,
Behcet


A new version of I-D, draft-xyz-pidloc-reqs-00.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-xyz-pidloc-reqs
Revision:       00
Title:          Requirements to Secure End to End Privacy in IdLoc Systems
Document date:  2019-05-27
Group:          Individual Submission
Pages:          6
URL:
https://www.ietf.org/internet-drafts/draft-xyz-pidloc-reqs-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xyz-pidloc-reqs/
Htmlized:       https://tools.ietf.org/html/draft-xyz-pidloc-reqs-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xyz-pidloc-reqs


Abstract:
   Use of Identifier Locator separation systems is proposed for various
   use cases to allow for efficient and service aware flexible end-to-
   end routing.  A statement on the issue of privacy preservation of
   both users and devices identity and location describes major
   challenges identified for this problem.  This document attempts to
   derive requirements towards a potential solution space of approaches
   to preserve privacy in Identifier-Locator split (PidLoc) protocols.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--000000000000cf7f240589e004c2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Folks,<div><br>Just now, we submitted the requirement draf=
t Rev. 00.</div><div>Please read it, it is very short.</div><div>Send your =
comments, text contributions to the list.</div><div>Have a nice Memorial Da=
y.</div><div><br></div><div>Regards,</div><div>Behcet<br><div class=3D"gmai=
l_quote"><br><br>
A new version of I-D, draft-xyz-pidloc-reqs-00.txt<br>
has been successfully submitted by Behcet Sarikaya and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-xyz-pidloc-reqs<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Requirements to Secure End to End =
Privacy in IdLoc Systems<br>
Document date:=C2=A0 2019-05-27<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 6<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-xyz-pidloc-reqs-00.txt" rel=3D"noreferrer" target=
=3D"_blank">https://www.ietf.org/internet-drafts/draft-xyz-pidloc-reqs-00.t=
xt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-xyz-pidloc-reqs/" rel=3D"noreferrer" target=3D"_blank">http=
s://datatracker.ietf.org/doc/draft-xyz-pidloc-reqs/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-xyz-pidloc-reqs-00" rel=3D"noreferrer" target=3D"_blank">https://tool=
s.ietf.org/html/draft-xyz-pidloc-reqs-00</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-xyz-pidloc-reqs" rel=3D"noreferrer" target=3D"_blank">https=
://datatracker.ietf.org/doc/html/draft-xyz-pidloc-reqs</a><br>
<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Use of Identifier Locator separation systems is proposed for v=
arious<br>
=C2=A0 =C2=A0use cases to allow for efficient and service aware flexible en=
d-to-<br>
=C2=A0 =C2=A0end routing.=C2=A0 A statement on the issue of privacy preserv=
ation of<br>
=C2=A0 =C2=A0both users and devices identity and location describes major<b=
r>
=C2=A0 =C2=A0challenges identified for this problem.=C2=A0 This document at=
tempts to<br>
=C2=A0 =C2=A0derive requirements towards a potential solution space of appr=
oaches<br>
=C2=A0 =C2=A0to preserve privacy in Identifier-Locator split (PidLoc) proto=
cols.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div></div></div>

--000000000000cf7f240589e004c2--


From nobody Mon May 27 08:26:47 2019
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3951200C4 for <pidloc@ietfa.amsl.com>; Mon, 27 May 2019 08:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 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_HELO_NONE=0.001, 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 3NyFWcGNL-bd for <pidloc@ietfa.amsl.com>; Mon, 27 May 2019 08:26:44 -0700 (PDT)
Received: from mail-yw1-xc2d.google.com (mail-yw1-xc2d.google.com [IPv6:2607:f8b0:4864:20::c2d]) (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 8A75D120074 for <pidloc@ietf.org>; Mon, 27 May 2019 08:26:44 -0700 (PDT)
Received: by mail-yw1-xc2d.google.com with SMTP id e74so6759752ywe.11 for <pidloc@ietf.org>; Mon, 27 May 2019 08:26:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=Mbfc+Wz+mM7A5ZhBfihsfRyGuZFKwC/XrbffY/qtHAg=; b=Rsr7zerFztCmLTLHUdeSd63shNq25T984DeRpJpZ0Pur/NObFPaoUXeEwmtGuKF5gr U8xj+Hk/DlrLHHSBNY01mFzSI0CF3FhNuku92zft1dVKeo35h6Q0PJdaIgwd1aBacuFh IkuQzKrcTNGstR+IDE5NPASOqLNDHcgJsAVZMULa9KQ2LgKJEC9YylsOgOPirk6jtO5Q WKD/JoAYAhdDifLrPiQdTQLLp6wJTwdSLvpcn9WzZXyedMRQFMVYk9w2qXtR7351w4/S Pr1pzroCDkt8ddxZuQSQ72WyAnBZT4SRRQUgWACueWwPyHPoEzDp0IZNiYLs5eZA6+9Q GbcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=Mbfc+Wz+mM7A5ZhBfihsfRyGuZFKwC/XrbffY/qtHAg=; b=BxZoe1eMoBC/+MIYVM8jE/aUKPdZ0BLGIPwJ2NZcsMwsC972eb2mCDyFyIaQLXWq99 JVQ748RgZ3SzO2GI5n0qLuFowkmzzZak7lcar3jxngQkZ5lIs114bcMCerlwOmY+CvH3 Tu7E6EQmrYQkeUxk1f+psIplu5L/OBAqtFrKSOUojgpmBCXvYH2mVHcTPmXWQ1nmgbFe tTQCm3OamS50dElYTM/FQro1r6doAtJjSAgVmRWf0Bj0FIb+3hCypM7WSMTEov/Qomdm X1vUfQBKPEzShMx05OtDLbETm0Mv4COIY1Rpo+hzZMc2x8enMa8efmCwL5V0n5eoCqB2 E9Pw==
X-Gm-Message-State: APjAAAV55tCUyWczgIb5zMeY33+WF5dkoXwAPtjSlMqX533OAHrM0MM/ SjjcZh/tNvqK4GQ79mrS7mJqRSje/KQrq5564iD0Q3+/
X-Google-Smtp-Source: APXvYqwCENi8+UwqQ6kIiUPHwXwJGLrYurK3j4fJ8+KuzqYhFGGigKRGAPMHFjdZCQhZ2ob0HenABJTEvXf0lU9fuAg=
X-Received: by 2002:a81:3641:: with SMTP id d62mr57490951ywa.509.1558970803699;  Mon, 27 May 2019 08:26:43 -0700 (PDT)
MIME-Version: 1.0
References: <155897060646.684.11390181345078229051.idtracker@ietfa.amsl.com>
In-Reply-To: <155897060646.684.11390181345078229051.idtracker@ietfa.amsl.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 27 May 2019 10:26:32 -0500
Message-ID: <CAC8QAcfU4BOfnxKyDPAoE-U9P_iXD8P=E+6b1LgddJpgdocMXg@mail.gmail.com>
To: pidloc@ietf.org
Cc: "<Dirk.von-Hugo@telekom.de>" <Dirk.von-Hugo@telekom.de>
Content-Type: multipart/alternative; boundary="000000000000f844ea0589e02cd2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/fWV876oCCFtUKutXoUgctjrQ8mQ>
Subject: [Pidloc] Fwd: New Version Notification for draft-xyz-pidloc-ps-01.txt
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 27 May 2019 15:26:46 -0000

--000000000000f844ea0589e02cd2
Content-Type: text/plain; charset="UTF-8"

Hi all,

PIdLoc Problem Statement draft Rev. 01 has just been submitted.
We expect to have more revisions in the coming days, so please contribute
text, send your comments to the list.
Regards,
Behcet & Dirk

A new version of I-D, draft-xyz-pidloc-ps-01.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-xyz-pidloc-ps
Revision:       01
Title:          Problem Statement for Secure End to End Privacy in IdLoc
Systems
Document date:  2019-05-27
Group:          Individual Submission
Pages:          10
URL:
https://www.ietf.org/internet-drafts/draft-xyz-pidloc-ps-01.txt
Status:         https://datatracker.ietf.org/doc/draft-xyz-pidloc-ps/
Htmlized:       https://tools.ietf.org/html/draft-xyz-pidloc-ps-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-xyz-pidloc-ps
Diff:           https://www.ietf.org/rfcdiff?url2=draft-xyz-pidloc-ps-01

Abstract:
   Efficient and service aware flexible end-to-end routing in future
   communication networks is achieved by routing protocol approaches
   making use of Identifier Locator separation systems.  Since these
   systems require a correlation between identifiers and location which
   might allow tracking and misusage of individuals' identities and
   locations such operation demands for highly secure measures to
   preserve privacy of users and devices.  This document tries to
   identify and describe typical use cases and derive thereof a problem
   statement describing issues and challenges for application of privacy
   preserving Identifier-Locator split (PidLoc) approaches.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--000000000000f844ea0589e02cd2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>PIdLoc Problem Statement draft =
Rev. 01 has just been submitted.</div><div>We expect to have more revisions=
 in the coming days, so please contribute text, send your comments to the l=
ist.</div><div>Regards,</div><div>Behcet &amp; Dirk<br><div class=3D"gmail_=
quote"><br>
A new version of I-D, draft-xyz-pidloc-ps-01.txt<br>
has been successfully submitted by Behcet Sarikaya and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-xyz-pidloc-ps<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Problem Statement for Secure End t=
o End Privacy in IdLoc Systems<br>
Document date:=C2=A0 2019-05-27<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 10<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-xyz-pidloc-ps-01.txt" rel=3D"noreferrer" target=3D=
"_blank">https://www.ietf.org/internet-drafts/draft-xyz-pidloc-ps-01.txt</a=
><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-xyz-pidloc-ps/" rel=3D"noreferrer" target=3D"_blank">https:=
//datatracker.ietf.org/doc/draft-xyz-pidloc-ps/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-xyz-pidloc-ps-01" rel=3D"noreferrer" target=3D"_blank">https://tools.=
ietf.org/html/draft-xyz-pidloc-ps-01</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-xyz-pidloc-ps" rel=3D"noreferrer" target=3D"_blank">https:/=
/datatracker.ietf.org/doc/html/draft-xyz-pidloc-ps</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-xyz-pidloc-ps-01" rel=3D"noreferrer" target=3D"_bla=
nk">https://www.ietf.org/rfcdiff?url2=3Ddraft-xyz-pidloc-ps-01</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Efficient and service aware flexible end-to-end routing in fut=
ure<br>
=C2=A0 =C2=A0communication networks is achieved by routing protocol approac=
hes<br>
=C2=A0 =C2=A0making use of Identifier Locator separation systems.=C2=A0 Sin=
ce these<br>
=C2=A0 =C2=A0systems require a correlation between identifiers and location=
 which<br>
=C2=A0 =C2=A0might allow tracking and misusage of individuals&#39; identiti=
es and<br>
=C2=A0 =C2=A0locations such operation demands for highly secure measures to=
<br>
=C2=A0 =C2=A0preserve privacy of users and devices.=C2=A0 This document tri=
es to<br>
=C2=A0 =C2=A0identify and describe typical use cases and derive thereof a p=
roblem<br>
=C2=A0 =C2=A0statement describing issues and challenges for application of =
privacy<br>
=C2=A0 =C2=A0preserving Identifier-Locator split (PidLoc) approaches.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div></div></div>

--000000000000f844ea0589e02cd2--

