Identifying Intra-realm Calls using STUN
draft-sen-sipping-intrarealm-stun-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Francois Audet , Frank Meijer , Cedric Aoun | ||
| Last updated | 2002-09-05 | ||
| 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
This draft proposes the use of STUN to determine whether two communicating endpoints are in the same realm. This draft describes the use of STUN in a peer-to-peer fashion between endpoints during call set-up. The call set-up may proceed in parallel with the STUN messaging, allowing the peers to initially exchange media using their public IP addresses. If the peers are in the same realm, then the media is switched to the private IP addresses using a SIP UPDATE or a SIP reINVITE SDP offer-answer exchange. With this proposal, media flows are kept within the same addressing realm whenever possible, thus avoiding certain network intermediaries and reducing bandwidth requirements on external links into the realm.
Authors
Francois Audet
Frank Meijer
Cedric Aoun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)