Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol Flows
RFC 6263, “Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol Flows”, is a Proposed Standard document published in June 2011 by X. Marjou, A. Sollaud. The canonical text is published by the RFC Editor.
Abstract
This document lists the different mechanisms that enable applications using the Real-time Transport Protocol (RTP) and the RTP Control Protocol (RTCP) to keep their RTP Network Address Translator (NAT) mappings alive. It also makes a recommendation for a preferred mechanism. This document is not applicable to Interactive Connectivity Establishment (ICE) agents. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6263 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6262 RTP Payload Format for IP-MR Speech Codec
- RFC 6264 An Incremental Carrier-Grade NAT for IPv6 Transition
- RFC 6261 Encrypted Signaling Transport Modes for the Host Identity Protocol
- RFC 6265 HTTP State Management Mechanism
- RFC 6260 Compressed Bundle Header Encoding
- RFC 6266 Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol
- RFC 6259 Delay-Tolerant Networking Previous-Hop Insertion Block
- RFC 6267 MIKEY-IBAKE: Identity-Based Authenticated Key Exchange Mode of Key Distribution in Multimedia Internet KEYing