datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows
draft-ietf-avt-app-rtp-keepalive-10

RFC
Document Stream: IETF
Last updated: 2011-03-04
Replaces: draft-marjou-behave-app-rtp-keepalive
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (avtcore)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6263
IANA Action State: No IC 
Responsible AD: Robert Sparks
Send notices to: avtcore-chairs@tools.ietf.org, draft-ietf-avt-app-rtp-keepalive@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-avt-app-rtp-keepalive.

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]

Authors:
Aurelien Sollaud <aurelien.sollaud@orange-ftgroup.com>
Xavier Marjou <xavier.marjou@orange-ftgroup.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)