Service Discovery Usage for REsource LOcation And Discovery (RELOAD)
draft-maenpaa-p2psip-service-discovery-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jouni Maenpaa , Gonzalo Camarillo | ||
| Last updated | 2009-10-18 | ||
| Replaced by | RFC 7374 | ||
| 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-ietf-p2psip-service-discovery | |
| 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
REsource LOcation and Discovery (RELOAD) does not define a generic service discovery mechanism as part of the base protocol. This document defines how the Recursive Distributed Rendezvous (ReDiR) service discovery mechanism used in OpenDHT can be applied to RELOAD overlays to provide a generic service discovery mechanism.
Authors
Jouni Maenpaa
Gonzalo Camarillo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)