P2PSIP Bootstrap Status Maintenance
draft-song-p2psip-bootstrap-status-maintenance-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Song Yongchao | ||
| Last updated | 2010-02-28 | ||
| 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
In order to join the overlay, a joining peer/client has to find the enrollment server first, and then acquire the configuration file from the enrollment server where it can find the bootstrap peers' information, and after that it contact a bootstrap node to route the join request message to join the overlay. However, nodes in P2PSIP overlay network are dynamic. They can leave gracefully or abruptly at any time. This document focuses on the bootstrap server mechanism and proposes a mechanism to select proper bootstrap peers and improve the availability of bootstrap nodes through bootstrap peer status maintenance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)