Transport Options for Clue
draft-wenger-clue-transport-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Stephan Wenger , Marshall Eubanks , Roni Even , Gonzalo Camarillo | ||
Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
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 memo describes the assumption and the proposed options for the coding and transport of CLUE messages as outlined in version 01 of the framework draft.
Authors
Stephan Wenger
Marshall Eubanks
Roni Even
Gonzalo Camarillo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)