[rtcweb] Consent freshness - interaction with SDP direction attributes

"Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com> Tue, 08 May 2012 10:20 UTC

Return-Path: <mperumal@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EDDE021F8592 for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 03:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id hOJCgGPglFCt for <rtcweb@ietfa.amsl.com>; Tue, 8 May 2012 03:20:11 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 8DB0E21F855B for <rtcweb@ietf.org>; Tue, 8 May 2012 03:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=4659; q=dns/txt; s=iport; t=1336472410; x=1337682010; h=mime-version:subject:date:message-id:from:to; bh=QUiAc76EQIXNj9vC+nSZ2aTWjkDC3pvmr6KIE1ru5zY=; b=ZFQXoBEsTO4BqrkBTQOhvIJ1EEPSlJ2uhH6v1jVHt+nugwnTvwUg5foV wFBvNe0lLoXBe0bxQx4NRAFyW1v4MCO/7vBLBQ3KWdOo4R2sjl3gFA3er 7k1bbzG7FzYxFdCEbK38mWmUAdrs9zoQhooxgan62qJ/iVVoMYrnwbyYf 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAL7yqE9Io8UY/2dsb2JhbABEgkaxZoIOAQQSAQkRA1sBKgYYB1cBBAsQGodsmUKBKKA4jWaCQ2MEiGKbdYFpgnE
X-IronPort-AV: E=Sophos; i="4.75,549,1330905600"; d="scan'208,217"; a="11698294"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([]) by bgl-iport-2.cisco.com with ESMTP; 08 May 2012 10:20:07 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com []) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q48AK7VM001223 for <rtcweb@ietf.org>; Tue, 8 May 2012 10:20:07 GMT
Received: from xmb-bgl-414.cisco.com ([]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 May 2012 15:50:07 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD2D04.2432EA0C"
Date: Tue, 08 May 2012 15:50:06 +0530
Message-ID: <1D062974A4845E4D8A343C65380492020865B54D@XMB-BGL-414.cisco.com>
Thread-Topic: Consent freshness - interaction with SDP direction attributes
Thread-Index: Ac0tBCPSRkI2gF0yT9qNu1ywo1sR0w==
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: rtcweb@ietf.org
X-OriginalArrivalTime: 08 May 2012 10:20:07.0545 (UTC) FILETIME=[24484E90:01CD2D04]
Subject: [rtcweb] Consent freshness - interaction with SDP direction attributes
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 10:20:15 -0000

I was thinking what the interaction between the SDP direction attributes
and the generation of consent freshness (described in
draft-muthu-behave-consent-freshness-00) should be, in response to some
questions posted by Harald. My thought is that the direction attributes
in SDP should have no impact on the generation of consent freshness. As
far as the media connection address and port are valid, the browser
should continue to generate consent freshness requests, irrespective of
whether the stream is sendonly, recvonly, sendrecv or inactive,
analogous to RTCP.


This would:

- Eliminate the need for the browser to depend on the (untrusted) JS to
tell it when to stop/start generating consent requests.

- Keep the NAT bindings always alive.