TURN extension to convey flow characteristics
draft-wing-tsvwg-turn-flowdata-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-06-04
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TSVWG                                                            D. Wing
Internet-Draft                                                  T. Reddy
Intended status: Standards Track                           Cisco Systems
Expires: December 6, 2014                                    B. Williams
                                                            Akamai, Inc.
                                                         R. Ravindranath
                                                           Cisco Systems
                                                            June 4, 2014

             TURN extension to convey flow characteristics
                   draft-wing-tsvwg-turn-flowdata-00

Abstract

   TURN server and the network in which it is hosted due to load could
   adversely impact the traffic relayed through it.  During such high
   load event, it is desirable to shed some traffic but TURN server lack
   requirements about the flows to prioritize them.  This document
   defines such a mechanism to communicate flow characteristics from the
   TURN client to its TURN server.

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 December 6, 2014.

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

Wing, et al.            Expires December 6, 2014                [Page 1]
Internet-Draft                TURN flowdata                    June 2014

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Design considerations . . . . . . . . . . . . . . . . . . . .   3
   4.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Sending a ChannelBind Request . . . . . . . . . . . . . .   4
     4.2.  Receiving a ChannelBind Request . . . . . . . . . . . . .   5
       4.2.1.  Conflict Resolution . . . . . . . . . . . . . . . . .   5
     4.3.  Receiving a ChannelBind Response  . . . . . . . . . . . .   6
   5.  FLOWDATA format . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Traversal Using Relay NAT (TURN) [RFC5766] is a protocol that is
   often used to improve the connectivity of P2P applications.  TURN
   ensures that a connection can be established even when one or both
   sides is incapable of a direct P2P connection.  A TURN server could
   be provided by an enterprise network, an access network, an
   application service provider or a third party provider.  A TURN
   server could be used to relay media streams, WebRTC data channels
   [I-D.ietf-rtcweb-overview] , gaming, file transfer etc.  A TURN
   server and the network in which it is hosted could have insufficient
   bandwidth or other characteristics that could adversely impact the
   traffic relayed through it and need a mechanism to identify and
   provide differentiated service to flows relayed through the TURN
   server.

   This specification provides a mechanism for the client to signal the
   flow characteristics of a relay channel to the TURN server, so that
   certain relay channels can receive service that is differentiated
   from others.  The TURN server authorizes the request and signals back
   to the client that it can (fully or partially) accommodate the flow.
Show full document text