The Evaluation of Different Network Address Translator (NAT) Traversal Techniques for Media Controlled by Real-time Streaming Protocol (RTSP)
draft-ietf-mmusic-rtsp-nat-evaluation-09

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16

Network Working Group                                      M. Westerlund
Internet-Draft                                                  Ericsson
Intended status: Informational                                   T. Zeng
Expires: November 30, 2013                                  May 29, 2013

 The Evaluation of Different Network Address Translator (NAT) Traversal
 Techniques for Media Controlled by Real-time Streaming Protocol (RTSP)
                draft-ietf-mmusic-rtsp-nat-evaluation-09

Abstract

   This document describes several Network Address Translator (NAT)
   traversal techniques that were considered to be used for establishing
   the RTP media flows controlled by the Real-time Streaming Protocol
   (RTSP).  Each technique includes a description on how it would be
   used, the security implications of using it and any other deployment
   considerations it has.  There are also discussions on how NAT
   traversal techniques relates to firewalls and how each technique can
   be applied in different use cases.  These findings where used when
   selecting the NAT traversal for RTSP 2.0.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 30, 2013.

Copyright Notice

   Copyright (c) 2013 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

Westerlund & Zeng      Expires November 30, 2013                [Page 1]
Internet-Draft    Evaluation of NAT Traversal for RTSP          May 2013

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Network Address Translators . . . . . . . . . . . . . . .   4
     1.2.  Firewalls . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   6
   2.  Detecting the loss of NAT mappings  . . . . . . . . . . . . .   7
   3.  Requirements on Solutions . . . . . . . . . . . . . . . . . .   8
   4.  NAT Traversal Techniques  . . . . . . . . . . . . . . . . . .   9
     4.1.  Stand-Alone STUN  . . . . . . . . . . . . . . . . . . . .  10
       4.1.1.  Introduction  . . . . . . . . . . . . . . . . . . . .  10
       4.1.2.  Using STUN to traverse NAT without server
               modifications . . . . . . . . . . . . . . . . . . . .  10
       4.1.3.  ALG considerations  . . . . . . . . . . . . . . . . .  12
       4.1.4.  Deployment Considerations . . . . . . . . . . . . . .  13
       4.1.5.  Security Considerations . . . . . . . . . . . . . . .  14
     4.2.  Server Embedded STUN  . . . . . . . . . . . . . . . . . .  14
       4.2.1.  Introduction  . . . . . . . . . . . . . . . . . . . .  14
       4.2.2.  Embedding STUN in RTSP  . . . . . . . . . . . . . . .  14
       4.2.3.  Discussion On Co-located STUN Server  . . . . . . . .  16
       4.2.4.  ALG considerations  . . . . . . . . . . . . . . . . .  16
       4.2.5.  Deployment Considerations . . . . . . . . . . . . . .  16
       4.2.6.  Security Considerations . . . . . . . . . . . . . . .  17