A Distributed Resource Directory (DRD)
draft-jimenez-distributed-resource-directory-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jaime Jimenez , Meirong Liu, Erkki Harjula | ||
| Last updated | 2014-01-16 (Latest revision 2013-07-15) | ||
| Replaced by | draft-jimenez-t2trg-drd | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-jimenez-t2trg-drd | |
| 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
In some M2M scenarios, it is convenient to offer non-centralized alternatives for discovery and rendezvous. This document defines a Distributed Resource Directory (DRD) for Constrained Application Protocol (CoAP). Distribution is achieved by means of a structured Peer-to-Peer (P2P) overlay. The DHT-based P2P overlay provides discovery, rendezvous and caching services for CoAP End-points as well as HTTP proxy service for Web clients.
Authors
Jaime Jimenez
Meirong Liu
Erkki Harjula
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)