Requirements to Secure End to End Privacy in IdLoc Systems
draft-xyz-pidloc-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Luigi Iannone , Dirk Von Hugo , Behcet Sarikaya | ||
| Last updated | 2019-11-28 (Latest revision 2019-05-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Luigi Iannone
Dirk Von Hugo
Behcet Sarikaya
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)