P2PSIP Protocol Framework and Requirements
draft-bryan-p2psip-requirements-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | David A. Bryan | ||
Last updated | 2007-07-03 | ||
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
Though both SIP and various peer-to-peer (p2p) protocols have been widely deployed, there is no operational experience with SIP using overlay networks. Also, most p2p networks developed in the research community do not deal with NAT traversal. This document attempts to list the design requirements for a P2PSIP protocol taking into account the experience gained from both the p2p and the SIP communities. Special emphasis has been put on the SIP-DHT interface, on the overlay performance, on NAT traversal and on security.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)