Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows (RFC6263)

IP.com Disclosure Number: IPCOM000207847D
Original Publication Date: 2011-Jun-01
Included in the Prior Art Database: 2011-Nov-30
Document File: 24 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

X. Marjou: AUTHOR [+2]

Abstract

[RFC4787] and [RFC5382] describe Network Address Translator (NAT) behaviors and point out that two key aspects of NAT are mappings (a.k.a. bindings) and keeping them refreshed. This introduces a derived requirement for applications engaged in a multimedia session involving NAT traversal: they need to generate a minimum of flow activity in order to create NAT mappings and maintain them.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                         X. Marjou Request for Comments: 6263                                    A. Sollaud Category: Standards Track                          France Telecom Orange ISSN: 2070-1721                                                June 2011

         Application Mechanism for Keeping Alive the NAT Mappings         Associated with RTP / RTP Control Protocol (RTCP) Flows

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6263.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Marjou & Sollaud             Standards Track                    [Page 1]
 RFC 6263                      RTP Keepalive                    June 2011

 Table of Contents

   1. Introduction ....................................................2

   2. Terminology .....................................................4

   3. Requirements ....................................................4

   4. List of Alternatives for Performing RTP Keepalive ...............4

      4.1. Empty (0-Byte) Transport Packet ............................4

      4.2. RTP Packet with Comfort Noise Payload ...............