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

["Mishra, Sanjay" <[e-mail]>]

On Tuesday, September 10, 2013 11:51 PM Muthu Arul Mozhi Perumal <[e-mail]> wrote:
>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.

I agree the first paragraph states the premise and that is good, however, the second paragraph which lays out the purpose of this document, and since the purpose is both how and why, the second paragraph could state something like this:

"This document describes both how and why a webRTC browser can and must verify peer consent to continue sending traffic and detect connection failure."

Thanks
Sanjay

-----Original Message-----
From: Muthu Arul Mozhi Perumal (mperumal) [mailto:[e-mail]] 
Sent: Tuesday, September 10, 2013 11:51 PM
To: Mishra, Sanjay; Dan Wing (dwing); Ram Mohan R (rmohanr); Tirumaleswar Reddy (tireddy)
Cc: [e-mail]
Subject: RE: [rtcweb] Adopting draft-muthu-behave-consent-freshness?

|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:[e-mail]]
|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: [e-mail]
|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: [e-mail] [mailto:[e-mail]] On 
|Behalf Of Magnus Westerlund
|Sent: Monday, September 09, 2013 4:37 AM
|To: [e-mail]
|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  [phone]
|Färögatan 6                | Mobile [phone]
|SE-164 80 Stockholm, Sweden| mailto: [e-mail]
|----------------------------------------------------------------------
|
|_______________________________________________
|rtcweb mailing list
|[e-mail]
|https://www.ietf.org/mailman/listinfo/rtcweb