Problems with STUN long-term Authentication for TURN
draft-ietf-tram-auth-problems-02

The information below is for an old version of the document
Document Type Active Internet-Draft (tram WG)
Last updated 2014-07-18 (latest revision 2014-07-03)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Gonzalo Camarillo
Shepherd write-up Show (last changed 2014-07-05)
IESG IESG state In Last Call (ends 2014-08-08)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to tram-chairs@tools.ietf.org, draft-ietf-tram-auth-problems@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
TRAM                                                            T. Reddy
Internet-Draft                                           R. Ravindranath
Intended status: Informational                            Muthu. Perumal
Expires: January 4, 2015                                           Cisco
                                                                A. Yegin
                                                                 Samsung
                                                            July 3, 2014

          Problems with STUN long-term Authentication for TURN
                    draft-ietf-tram-auth-problems-02

Abstract

   This document discusses some of the issues with STUN authentication
   for TURN messages.

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 January 4, 2015.

Copyright Notice

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

Reddy, et al.            Expires January 4, 2015                [Page 1]
Internet-Draft Problems with STUN Authentication for TURN      July 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   3
   3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Problems with STUN long-term Authentication for TURN  . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Traversal Using Relay NAT (TURN) [RFC5766] is a protocol that is
   often used to improve the connectivity of P2P applications (as
   defined in section 2.7 of [RFC5128]).  TURN ensures that a connection
   can be established even when one or both sides is incapable of a
   direct P2P connection.  The TURN server is also a a building block to
   support interactive, real-time communication using audio, video,
   collaboration, games, etc., between two peer web browsers using the
   Web Real-Time communication (WebRTC) [I-D.ietf-rtcweb-overview]
   framework.

   TURN server is also used in the following scenarios:

   o  Users of RTCWEB based web application may use TURN server to hide
      host candidate addresses from the remote peer for privacy.

   o  Enterprise networks deploy firewalls which typically block UDP
      traffic.  When SIP user agents or WebRTC endpoints are deployed
      behind such firewalls, media cannot be sent over UDP across the
      firewall, but must be sent using TCP (which causes a different
      user experience).  In such cases a TURN server deployed in the
      DeMilitarized Zone (DMZ) MAY be used to traverse firewalls.

   o  The use-case explained in "Simple Video Communication Service,
      enterprise aspects" (Section 3.2.5 of
      [I-D.ietf-rtcweb-use-cases-and-requirements]) refers to deploying
      a TURN server in the DMZ to audit all media sessions from inside
      an Enterprise premises to any external peer.

   o  TURN server could also be deployed for RTP Mobility
      [I-D.wing-tram-turn-mobility] etc.

Reddy, et al.            Expires January 4, 2015                [Page 2]
Internet-Draft Problems with STUN Authentication for TURN      July 2014

   o  TURN Server may be used for IPv4-to-IPv6, IPv6-to-IPv6, and IPv6 -
      to-IPv4 relaying [RFC6156].

   o  ICE connectivity checks using server reflexive candidates could
Show full document text