Requirements for Key Management Schemes in Content-Centric Networking/ Named Data Networking
draft-li-icnrg-km-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ruidong Li , Hitoshi Asaeda | ||
| Last updated | 2018-09-06 (Latest revision 2018-03-05) | ||
| 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
Signature is adopted as the fundamental function in Content-Centric Networking (CCN) / Named Data Networking (NDN). Its service and performance rely heavily on the key management (KM) schemes, which are the processes to generate, deliver, store, protect, update, and revoke cryptographic keys. This document describes the use scenarios and further requirements for KM schemes in CCN/NDN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)