Requirements to Secure End to End Privacy in IdLoc Systems
draft-xyz-pidloc-reqs-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-11-28 (latest revision 2019-05-27) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-xyz-pidloc-reqs-00.txt
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
(ggx@gigix.net)
Dirk Hugo
(dirk.von-hugo@telekom.de)
Behcet Sarikaya
(sarikaya@ieee.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)