IETF Logo Mail Archive

Re: [rtcweb] Adopting draft-muthu-behave-consent-freshness?

"Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com> Wed, 11 September 2013 03:51 UTC

Return-Path: <mperumal@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D19D721F9027 for <rtcweb@ietfa.amsl.com>; Tue, 10 Sep 2013 20:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSIEsfUveClg for <rtcweb@ietfa.amsl.com>; Tue, 10 Sep 2013 20:51:29 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id A8FFF11E810D for <rtcweb@ietf.org>; Tue, 10 Sep 2013 20:51:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3222; q=dns/txt; s=iport; t=1378871489; x=1380081089; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AFeEZ8C5cbYk+xGr7guD81LrL9ejSd76RhWQIAWfR9I=; b=ZJ7VjNYcgA9xGx4pxP9WbRLwpWQpL1RFjx60LLL/a9f1zvVqC8n1ooIk gFnm3V15+UYhmASuh6sRRWBt8rTVtW1AQPFSA7l/C0S+F0CGzTxjGOzVF IevQs5ku+uh69USG8zH87XMtJVr+z56b5MwsS8pFecg8WDIt2esYdnAkV s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFAIXnL1KtJV2a/2dsb2JhbABbgwc4UcJmgR8WdIIlAQEBBAEBAQkRUQsMAgICAQgRBAEBCx0HGwwLFAkIAQEEAQ0FCIdoAw8MwnUEBIx0gj0xBwaDF4EAA4h+oGyDIIIq
X-IronPort-AV: E=Sophos;i="4.90,881,1371081600"; d="scan'208";a="257943822"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 11 Sep 2013 03:51:29 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r8B3pTvw022623 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Sep 2013 03:51:29 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.35]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Tue, 10 Sep 2013 22:51:28 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Mishra, Sanjay" <sanjay.mishra@verizon.com>, "Dan Wing (dwing)" <dwing@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Thread-Topic: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
Thread-Index: Ac6tN+qfR6vXQELAQEiGliH2MY4jagBGN0NQABQuU4A=
Date: Wed, 11 Sep 2013 03:51:28 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE224275BB8@xmb-rcd-x02.cisco.com>
References: <522D88A8.3010209@ericsson.com> <900A1E2059ADB149B905E3C8FA0046A62C79869199@FHDP1LUMXC7V23.us.one.verizon.com>
In-Reply-To: <900A1E2059ADB149B905E3C8FA0046A62C79869199@FHDP1LUMXC7V23.us.one.verizon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [72.163.208.201]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
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: Wed, 11 Sep 2013 03:51:34 -0000

|In the abstract, second paragraph, the text states "how" a WebRTC 
|browser can verify peer consent and as I read through the rest of 
|the document I also understood "why" this is needed. So, just a knit
|pick, it may be clear to the reader if the statement also includes 
|why within the body of the Abstract.

The "why" part is mentioned in the first paragraph of the abstract:
   Verification of peer consent before sending traffic is necessary in
   WebRTC deployments to ensure that a malicious JavaScript cannot use
   the browser as a platform for launching attacks.

Are you suggesting expanding this? The abstract needs to be concise, however.

|One minor typo in section 7. Please change "in-intended" to "un-intended".

Will fix it.

Thanks for the review..

Muthu 

|-----Original Message-----
|From: Mishra, Sanjay [mailto:sanjay.mishra@verizon.com]
|Sent: Wednesday, September 11, 2013 12:38 AM
|To: Muthu Arul Mozhi Perumal (mperumal); Dan Wing (dwing); Ram Mohan R (rmohanr); Tirumaleswar Reddy
|(tireddy)
|Cc: rtcweb@ietf.org
|Subject: RE: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
|
|Muthu et al --
|
|
|In the abstract, second paragraph, the text states "how" a WebRTC browser can verify peer consent and
|as I read through the rest of the document I also understood "why" this is needed. So, just a knit
|pick, it may be clear to the reader if the statement also includes why within the body of the
|Abstract.
|
|One minor typo in section 7. Please change "in-intended" to "un-intended".
|
|Thanks
|Sanjay
|
|-----Original Message-----
|From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus Westerlund
|Sent: Monday, September 09, 2013 4:37 AM
|To: rtcweb@ietf.org
|Subject: [rtcweb] Adopting draft-muthu-behave-consent-freshness?
|
|WG,
|
|This is a call for WG adoption of STUN Usage for Consent Freshness (draft-muthu-behave-consent-
|freshness-04). This document defines a STUN usage for consent freshness. As this requires no protocol
|extensions we as intended users can define this usage in our WG. Such work also matches our charter.
|The draft-ietf-rtcweb-security-arch-07 is normatively dependent on this STUN usage.
|
|Document:
|https://datatracker.ietf.org/doc/draft-muthu-behave-consent-freshness/
|
|WG, please indicate your support or issues with adopting this document as WG item with a proposed
|milestone:
|
|Mar 2014 Send STUN Usage for Consent Freshness to IESG for publication as proposed standard.
|
|Cheers
|
|Magnus Westerlund
|
|----------------------------------------------------------------------
|Multimedia Technologies, Ericsson Research EAB/TVM
|----------------------------------------------------------------------
|Ericsson AB                | Phone  +46 10 7148287
|Färögatan 6                | Mobile +46 73 0949079
|SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
|----------------------------------------------------------------------
|
|_______________________________________________
|rtcweb mailing list
|rtcweb@ietf.org
|https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email