Re: [Pidloc] draft-kjsun-ipwave-id-loc-separation

"KJ SUN" <> Fri, 05 April 2019 06:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2012712036D for <>; Thu, 4 Apr 2019 23:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XgO9G4ZYLRPZ for <>; Thu, 4 Apr 2019 23:01:06 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::641]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BACC612035B for <>; Thu, 4 Apr 2019 23:01:06 -0700 (PDT)
Received: by with SMTP id t16so2449564plo.0 for <>; Thu, 04 Apr 2019 23:01:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:date:message-id:subject:from:to:cc:in-reply-to :references:user-agent; bh=AsS8Z5jfzAOIekNvpojd096f4lE55Z576NtgEYbashg=; b=a6pysslPdn25kjD1iBHTi25iRq4sBSkoJ/EPzzEiPp51Odfm8K/SfoQXFQZfYG8A/j ii6ZpCG+LHYgYreadThYDT4pvIXoIWPhX2quG9FH2wglQMtWenhyXQL2G2QCGO4lYfJw VOCqOPlJxKzkmi1Bd+4capRjkHIc7m4R88ioeYaO3SCmb0CopHQ8/blgPntKNEpt4oSt jbI8Ka/pZBE+xBUCPOdpuKJJCM1HRFQm/N4KwQX/TbJNXgheBaMLXMMFf4pXuwWST1Pa ZexrL/ZE9HgAa7ExDRarCfFlI0KuQCVO9xsL2dhIcmC3CE6pdQIpYmdz3fSATdeO/fh3 GO/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to:cc :in-reply-to:references:user-agent; bh=AsS8Z5jfzAOIekNvpojd096f4lE55Z576NtgEYbashg=; b=YfxKFKSiOVrFE+Sc4CE8peeazvF3UXJvOZxfBwvelI3E/PGHT1G9heFMZfW1uZrvDj 9FFGBah1FYjxqFvbwgq3UaAbolfbZB6OnQYSH37m+HRlmvwOGjLtPwO1xKZjcN9V7BEb IduTj3MMozykad9+oDSEIQdDdwEZkeySZ1PUJysP5ygptUL9ahwo49jLQfqrur6X/pLN WyqpKYlmH3HcvYEUGY3CgabO56ELueKBCQv13Ex1L4R7LG+kUVAhhOSliNlXML+9sBk5 os3WsYuDzpjRBE1izZzgS5MIEuOGmWhT+mjtys/BRh9HWgkupGlMXkjfczEWEnc4CM3q Ey/A==
X-Gm-Message-State: APjAAAW++XLwCQksrO3THgfQv19uwHPXsdT52o8oEDlAmC3QD1RPykdx PQuJVr68hXzD/HmhqIdziiscSQ==
X-Google-Smtp-Source: APXvYqyAOguQyhyPb5oRC0MqMK3Z7dU4fCIYLXrUIZTKg71ZC5h0TrzeD9SLGHsyvmAyDeLgWbJ5PQ==
X-Received: by 2002:a17:902:1486:: with SMTP id k6mr10971990pla.3.1554444065538; Thu, 04 Apr 2019 23:01:05 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id i15sm27466837pfd.162.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 23:01:04 -0700 (PDT)
Content-Type: multipart/alternative; boundary="----=_NextPart_14365204.822345660406"
MIME-Version: 1.0
Date: Fri, 05 Apr 2019 15:01:00 +0900
Message-ID: <>
From: "KJ SUN" <>
To: "" <>, "" <>
Cc: "" <>
In-Reply-To: <>
References: <>
User-Agent: Mailbird/
X-Antivirus: Avast (VPS 190404-10, 2019-04-05), Outbound message
X-Antivirus-Status: Clean
Archived-At: <>
Subject: Re: [Pidloc] draft-kjsun-ipwave-id-loc-separation
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Apr 2019 06:01:10 -0000

Hello Behcet, 

Thanks for giving me opportunity to introduce my draft "Considerations for ID/Location Separation Protocols in IP-based Vehicular Networks"

Purpose of this draft is to analyze applicability of ID/LOC protocols into vehicular network discussed in IPWAVE WG.

I considered LISP and ILNP as candidates protocols, and make use case based on vehicular network architecture described in IPWAVE PS doc (draft-ietf-ipwave-vehicular-networking)

In the Gap Analysis, I tried to follow issues described in PS doc, for each issue I referred d related ietf docs as possible solution.

Privacy issues in IPWAVE environment are well-described in PS doc. In that draft, they mentioned that tracking prevention should be supported with not only E2E continuity but also confidentiality. In my opinion, ID/LOC protocol may solve this problem easier since that ID information is not strongly bound to its location. 

Honestly, I still have no idea for that and privacy issues were out of my interests. So, pidloc work could be helpful to analyze privacy issue and make solution for that.

I will more read related privacy documents and try to figure out for vehicular network use case. All comments and co-operations are welcome.



Kyoungjae Sun / K. J. SUN (Ph. D. Student)
Distributed Computing Network laboratory (DCN Lab)
School of Electronic Engineering, Soongsil Univ.
369 Sangdo-ro, Dongjak-gu, Seoul.
Tel. +82-2-814-0151
Mobile +82-10-3643-5627
On 2019-04-04 오전 12:56:50, Behcet Sarikaya <> wrote:
Hello Gomjae,

Today, we had a Webex session with Dirk and discussed about your draft

in this draft you introduced architectures for the use of IDLOC protocols in 
vehicular networks. 
We consider this one of the significant use cases in our pidloc activity. 
We know you attended pidloc side meeting in Prague last week, thanks for that.

We would appreciate if you could introduce your draft to the list shortly in 
your reply?

Also any ideas on the privacy issues that arise in the vehicular networking 
from the use IDLOC protocols?


Behcet & Dirk

이 이메일은 Avast 안티바이러스 소프트웨어로 바이러스 검사를 완료했습니다.