Usage of CLUE with PERC
draft-groves-perc-clue-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Christian Groves , Weiwei Yang , Roni Even | ||
| Last updated | 2016-04-18 (Latest revision 2015-10-16) | ||
| 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
This document provides an initial discussion of the relationship between PERC and CLUE. It seeks to identify any potential impacts or/and enhancement to the way that CLUE is used in the PERC architecture.
Authors
Christian Groves
Weiwei Yang
Roni Even
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)