CCNx Key Exchange Protocol Version 1.0
draft-wood-icnrg-ccnxkeyexchange-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Marc Mosko , Ersin Uzun , Christopher Wood | ||
| Last updated | 2018-01-07 (latest revision 2017-07-06) | ||
| 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-wood-icnrg-ccnxkeyexchange-02.txt
Abstract
This document specifies Version 1.0 of the CCNx Key Exchange (CCNxKE) protocol. The CCNxKE protocol allows two peers to establish a shared, forward-secure key for secure and confidential communication. The protocol is designed to prevent eavesdropping, tampering, and message forgery between two peers. It is also designed to minimize the number of rounds required to establish a shared key. In the worst case, it requires two RTTs between a consumer and producer to establish a shared key. In the best case, one RTT is required before sending any application data. This document outlines how to derive the keys used to encrypt traffic for a session and shows how session information is exchanged between a consumer and producer using message encapsulation.
Authors
Marc Mosko
(marc.mosko@parc.com)
Ersin Uzun
(ersin.uzun@parc.com)
Christopher Wood
(woodc1@uci.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)