Why SIP should be used for encoding the P2PSIP Peer Protocol.
draft-zangrilli-p2psip-whysip-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marcia Zangrilli , Bruce Lowekamp | ||
| Last updated | 2007-03-19 | ||
| 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
The P2PSIP working group's charter charges the group to define a P2PSIP peer protocol that defines how peers "collectively provide for user and resource location in a SIP environment with no or minimal centralized servers." The charter also states that the group may define a peer protocol that is syntactically based on SIP. This document outlines the motivation and merits of using conventional SIP messages as the syntax to encode the P2PSIP peer protocol and discusses arguments made against this design decision.
Authors
Marcia Zangrilli
Bruce Lowekamp
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)