STUN Usage for Consent Freshness
draft-muthu-behave-consent-freshness-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-01-17
Replaced by draft-ietf-rtcweb-stun-consent-freshness, rfc7675
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Behave                                                Muthu A M. Perumal
Internet-Draft                                                   D. Wing
Intended status: Standards Track                 Ram Mohan. Ravindranath
Expires: July 21, 2013                                     Cisco Systems
                                                               H. Kaplan
                                                             Acme Packet
                                                        January 17, 2013

                    STUN Usage for Consent Freshness
                draft-muthu-behave-consent-freshness-02

Abstract

   Verification of peer consent is necessary in WebRTC deployments to
   ensure that a malicious JavaScript cannot use the browser as a
   platform for launching attacks.  A related problem is session
   liveness.  WebRTC applications may want to detect connection failure
   and take appropriate actions.  This document describes a STUN usage
   that enables a WebRTC browser to perform the following on a candidate
   pair ICE is using for a media component after session establishment:

   1.  Verify the peer consent for continuing to receive traffic.
   2.  Dectect connection failure.

Status of this Memo

   This Internet-Draft is submitted to IETF 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 July 21, 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

Perumal, et al.           Expires July 21, 2013                 [Page 1]
Internet-Draft      STUN Usage for Consent Freshness        January 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Design Considerations . . . . . . . . . . . . . . . . . . . . . 4
   5.  Solution Overview . . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Interaction with Keepalives used for Refreshing NAT
       Bindings  . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   9.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 6
   10. Normative References  . . . . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Perumal, et al.           Expires July 21, 2013                 [Page 2]
Internet-Draft      STUN Usage for Consent Freshness        January 2013

1.  Introduction

   Consent verification is the mechanism using which WebRTC
   implementations can verify the peer consent for receiving traffic on
   candidate media transport addresses.  This has two parts

   1.  Verifying peer consent for receiving traffic on candidate media
       transport addresses at session establishment.
   2.  Verifying peer consent for continuing to receive traffic on
       candidate media transport addresses after session establishment.

   WebRTC implements are required to perform STUN connectivity checks at
   session establishment as part of ICE procedures [RFC5245].  This
   takes care of the first part of the consent verification described
   above.

   After session establishment ICE requires STUN Binding indications to
   be used for refreshing NAT bindings for a candidate pair ICE is using
   for a media component.  Since a STUN Binding indication does not
   evoke a response, it cannot be used for the second part of the
   consent verification describes above.
Show full document text