Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows.
draft-marjou-behave-app-rtp-keepalive-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Xavier Marjou | ||
| Last updated | 2009-02-24 (Latest revision 2007-02-02) | ||
| Replaced by | RFC 6263 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avt-app-rtp-keepalive | |
| 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 document defines a mechanism that enables applications using Real Time Protocol (RTP) to maintain their RTP Network Address Translator (NAT) mappings alive.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)