IETF Logo Mail Archive

[rtcweb] Consent for fate-sharing connections (Do we need text in draft-ietf-rtcweb-stun-consent-freshness ?)

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Tue, 25 March 2014 15:17 UTC

Return-Path: <rmohanr@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 560081A016D for <rtcweb@ietfa.amsl.com>; Tue, 25 Mar 2014 08:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level:
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOTcb1wrbklN for <rtcweb@ietfa.amsl.com>; Tue, 25 Mar 2014 08:17:57 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id EF95B1A00D9 for <rtcweb@ietf.org>; Tue, 25 Mar 2014 08:17:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=532; q=dns/txt; s=iport; t=1395760676; x=1396970276; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=w9I6kCyZ//4Tec28k5YEi443pPFc2St4eGvQac/jilY=; b=VxTGFJ9jL/kmALcr9Cey2Nkd3pPXIyXwm6qOpZuEEllMjWGLGjeIFjMm +NkTRLgtAyaVVvl+kg0op0i4KFdWCWICM4tqKFbA7nIpPw6UCZPYakASx wEsHLOYjngUvQ0YvAJj+tyQpayu3z+Jk17h8l0Uj4wEuT/poI688Zwrp0 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFALqdMVOtJV2b/2dsb2JhbABZgwaBEsQHFnSCLDpRAT4FPScEiAydabFdF5MtBJhNkjKBcIE+gis
X-IronPort-AV: E=Sophos;i="4.97,728,1389744000"; d="scan'208";a="30209717"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP; 25 Mar 2014 15:17:55 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s2PFHtY4012484 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <rtcweb@ietf.org>; Tue, 25 Mar 2014 15:17:55 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.78]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Tue, 25 Mar 2014 10:17:55 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Consent for fate-sharing connections (Do we need text in draft-ietf-rtcweb-stun-consent-freshness ?)
Thread-Index: AQHPSD1l4RRh4jrUD02G0QWRQAr7eA==
Date: Tue, 25 Mar 2014 15:17:54 +0000
Message-ID: <CF579BF9.85AEA%rmohanr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.65.39.91]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <98EDFB73AFC93A428C5EB1324BEDA024@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/ESf2maPAAGAF15j5QvPCoFyEbgw
Subject: [rtcweb] Consent for fate-sharing connections (Do we need text in draft-ietf-rtcweb-stun-consent-freshness ?)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Mar 2014 15:17:58 -0000

Hi all,

Certain media streams(For example audio, video) may require multiple
components (RTP, RTCP) each of which has to work for the media stream as a
whole to work. If consent fails for one of the component then the
application(JS) may decide to cease transmission of that media stream.

Is there a need to describe some text (RECOMMENDATION) on how fate-sharing
connections need to be handled when consent fails for one of the
components in Consent draft ?
Or should this be left out of this draft ?

Regards,
Ram

v2.23.0 | Report a Bug | By Email