Hi Paull, pidloc is a new non-WG list, we are looking for mainly privacy and also security experts to join the list. Whether or not IKE/ipsec related we will see, right now we just have sort-of Problem Statement document and we will go from there.
We encourage all interested parties to subscribe. Behcet On Fri, Aug 10, 2018 at 10:09 AM, Paul Wouters <[email protected]> wrote: > None of this seems related to ipsec and things should be discussed > elsewhere. > > If there is a component related to IKE or IPsec, please clarify as your > list archive or the draft you link to provide information showing this to > be on topic here. > > Paul > > Sent from my phone > > On Aug 10, 2018, at 10:18, Behcet Sarikaya <[email protected]> wrote: > > IPSEC chairs: please approve this non-member post. > > > A new IETF non-working group email list has been created. > > List address: [email protected] > 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 > > _______________________________________________ > IPsec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ipsec > >
_______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
