A P2PSIP Client Routing for Reload
draft-xiao-p2psip-client-routing-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lin Xiao , Yunfei Zhang | ||
| Last updated | 2009-05-13 | ||
| 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 analyses the routing requirements of different types of clients, and then proposes a P2P client routing mechanism for REsource LOcation And Discovery (RELOAD). This mechanism is designed to solve the issues in one of the client routing options described in the RELOAD Base protocol [I-D.ietf-p2psip-base], where clients are allowed to connect with arbitrary peers. The solution is to store the information of a client's Attached Peer in the overlay together with the registration data of the client. The extension could be deployed on SIP usage of RELOAD easily [I-D.draft-ietf-p2psip-sip].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)