draft-ietf-rtcweb-stun-consent-freshness-10.txt   draft-ietf-rtcweb-stun-consent-freshness-11.txt 
RTCWEB M. Perumal RTCWEB M. Perumal
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track D. Wing Intended status: Standards Track D. Wing
Expires: June 17, 2015 R. Ravindranath Expires: June 20, 2015 R. Ravindranath
T. Reddy T. Reddy
Cisco Systems Cisco Systems
M. Thomson M. Thomson
Mozilla Mozilla
December 14, 2014 December 17, 2014
STUN Usage for Consent Freshness STUN Usage for Consent Freshness
draft-ietf-rtcweb-stun-consent-freshness-10 draft-ietf-rtcweb-stun-consent-freshness-11
Abstract Abstract
To prevent sending excessive traffic to an endpoint, periodic consent To prevent sending excessive traffic to an endpoint, periodic consent
needs to be obtained from that remote endpoint. needs to be obtained from that remote endpoint.
This document describes a consent mechanism using a new Session This document describes a consent mechanism using a new Session
Traversal Utilities for NAT (STUN) usage. Traversal Utilities for NAT (STUN) usage.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 17, 2015. This Internet-Draft will expire on June 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 45 skipping to change at page 3, line 45
performed then there is no need to send keepalive messages. performed then there is no need to send keepalive messages.
4. Solution 4. Solution
There are two ways consent to send traffic is revoked: expiration of There are two ways consent to send traffic is revoked: expiration of
consent and immediate revocation of consent, which are discussed in consent and immediate revocation of consent, which are discussed in
the following sections. the following sections.
4.1. Expiration of Consent 4.1. Expiration of Consent
A WebRTC implementation [I-D.ietf-rtcweb-overview], which implements A full ICE implementation performs consent freshness test using STUN
full ICE, MUST perform consent freshness test using STUN request/ request/response as described below:
response as described below:
An endpoint MUST NOT send data other than paced STUN connectivity An endpoint MUST NOT send data other than paced STUN connectivity
checks or responses toward any transport address unless the receiving checks or responses toward any transport address unless the receiving
endpoint consents to receive data. That is, no application data endpoint consents to receive data. That is, no application data
(e.g., RTP or DTLS) can be sent until consent is obtained. After a (e.g., RTP or DTLS) can be sent until consent is obtained. After a
successful ICE connectivity check on a particular transport address, successful ICE connectivity check on a particular transport address,
consent MUST be maintained following the procedure described in this consent MUST be maintained following the procedure described in this
document. document.
Explicit consent to send is obtained and maintained by sending an Explicit consent to send is obtained and maintained by sending an
 End of changes. 5 change blocks. 
7 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/