The requirement of P2PSIP Peer protocol
draft-jiang-p2psip-peer-protocol-requirement-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | XingFeng Jiang | ||
| Last updated | 2007-07-10 | ||
| 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 this draft, we present what P2PSIP should achieve - a distributed location service. Then we compare the differences between C/S SIP and P2P SIP and point out that some features which are not standardized in C/S SIP should be addressed in the P2P SIP case. After analyzing some problems, some requirements of Peer protocol are proposed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)