Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-02.txt

["Ram Mohan R (rmohanr)" <[e-mail]>]

Found this mail thread in the archives where this issue was discussed but
we have not reached to any conclusion -
https://www.ietf.org/mail-archive/web/rtcweb/current/msg04887.html

With ICE-lite mode since the ICE-lite endpoint does not typically generate
any binding requests, it may not generate STUN consent as well. This would
means a malicious application (running on a ICE-lite endpoint) can use it
for sending unwanted traffic.

Should we mandate an ICE-lite implementation to generate a STUN consent
request to its peer before it can send media ?

Regards,
Ram

-----Original Message-----
From: Ram Mohan Ravindranath <[e-mail]>
Date: Friday, 11 April 2014 12:23 pm
To: Christer Holmberg <[e-mail]>, "[e-mail]"
<[e-mail]>
Subject: Re: [rtcweb] I-D Action:
draft-ietf-rtcweb-stun-consent-freshness-02.txt

>Sure. We will add text for these two in the next revision.
>
>Thanks,
>Ram
>
>-----Original Message-----
>From: Christer Holmberg <[e-mail]>
>Date: Friday, 11 April 2014 12:22 pm
>To: Ram Mohan Ravindranath <[e-mail]>, "[e-mail]"
><[e-mail]>
>Subject: RE: [rtcweb] I-D Action:
>draft-ietf-rtcweb-stun-consent-freshness-02.txt
>
>>Hi,
>>
>>I think it would be good to have some text about usage of consent
>>freshness when one entity is ICE lite.
>>
>>And, I think it would be good to make it more clear that the usage of
>>consent is always negotiated per direction.
>>
>>Thanks!
>>
>>Regards,
>>
>>Christer
>>
>>
>>-----Original Message-----
>>From: rtcweb [mailto:[e-mail]] On Behalf Of Ram Mohan R
>>(rmohanr)
>>Sent: 11. huhtikuuta 2014 8:01
>>To: [e-mail]
>>Subject: Re: [rtcweb] I-D Action:
>>draft-ietf-rtcweb-stun-consent-freshness-02.txt
>>
>>Summary of changes in this revision
>>
>>Addressed the comments received from the WG.
>>Removed the timers definition from solution overview and made the text
>>more generic.
>>Incorporated text from draft-thomson-rtcweb-consent.
>>Most of the text of solution overview is re-written however the idea is
>>still kept intact
>>
>>
>>Comments are welcome.
>>
>>There is still some dangling reference (text) to SRTP/DTLS mechanism for
>>consent which we will modify in the next revision
>>
>>
>>Regards,
>>Authors
>>
>>-----Original Message-----
>>From: "[e-mail]" <[e-mail]>
>>Date: Friday, 11 April 2014 9:07 am
>>To: "[e-mail]" <[e-mail]>
>>Cc: "[e-mail]" <[e-mail]>
>>Subject: [rtcweb] I-D Action:
>>draft-ietf-rtcweb-stun-consent-freshness-02.txt
>>
>>>
>>>A New Internet-Draft is available from the on-line Internet-Drafts
>>>directories.
>>> This draft is a work item of the Real-Time Communication in
>>>WEB-browsers Working Group of the IETF.
>>>
>>>        Title           : STUN Usage for Consent Freshness
>>>        Authors         : Muthu Arul Mozhi Perumal
>>>                          Dan Wing
>>>                          Ram Mohan Ravindranath
>>>                          Tirumaleswar Reddy
>>>                          Martin Thomson
>>>	Filename        : draft-ietf-rtcweb-stun-consent-freshness-02.txt
>>>	Pages           : 8
>>>	Date            : 2014-04-10
>>>
>>>Abstract:
>>>   To prevent sending excessive traffic to an endpoint, periodic consent
>>>   needs to be obtained from that remote endpoint.
>>>
>>>   This document describes a consent mechanism using a new STUN usage.
>>>   This same mechanism can also determine connection loss ("liveness")
>>>   with a remote peer.
>>>
>>>
>>>The IETF datatracker status page for this draft is:
>>>https://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshne
>>>ss/
>>>
>>>There's also a htmlized version available at:
>>>http://tools.ietf.org/html/draft-ietf-rtcweb-stun-consent-freshness-02
>>>
>>>A diff from the previous version is available at:
>>>http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-stun-consent-freshne
>>>ss-
>>>02
>>>
>>>
>>>Please note that it may take a couple of minutes from the time of
>>>submission until the htmlized version and diff are available at
>>>tools.ietf.org.
>>>
>>>Internet-Drafts are also available by anonymous FTP at:
>>>ftp://ftp.ietf.org/internet-drafts/
>>>
>>>_______________________________________________
>>>rtcweb mailing list
>>>[e-mail]
>>>https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>_______________________________________________
>>rtcweb mailing list
>>[e-mail]
>>https://www.ietf.org/mailman/listinfo/rtcweb
>