Problem Statement for SIP-signalled Peer-to-Peer Communication across Middleboxes
draft-quittek-p2p-sip-middlebox-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Juergen Quittek | ||
Last updated | 2006-03-01 | ||
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
Middleboxes, particularly firewalls and network address translators, are essential components of today's Internet infrastructure. They are designed to support client-server applications well, but very often they are obstacles for peer-to-peer communication. This memo discusses middlebox traversal issues of SIP-based peer-to-peer communication. Required communication steps are analyzed concerning their potential constraints caused by middleboxes. The requirements derived from this analysis are compared with the capabilites of currently available middlebox traversal methods and SIP signaling standards. The comparison identifies open issues that need to be considered when designing standards for a SIP-based peer-to-peer communication infrastructure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)