Re: [rtcweb] consent freshness [was RE: STUN for keep-alive]

Eric Rescorla <ekr@rtfm.com> Mon, 19 September 2011 16:15 UTC

Return-Path: <ekr@rtfm.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 B533E21F8CBE for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 09:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.901
X-Spam-Level:
X-Spam-Status: No, score=-102.901 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2HhoPqpUno9d for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 09:15:15 -0700 (PDT)
Received: from mail-wy0-f170.google.com (mail-wy0-f170.google.com [74.125.82.170]) by ietfa.amsl.com (Postfix) with ESMTP id EF4C621F8CBD for <rtcweb@ietf.org>; Mon, 19 Sep 2011 09:15:14 -0700 (PDT)
Received: by wyg8 with SMTP id 8so6591982wyg.15 for <rtcweb@ietf.org>; Mon, 19 Sep 2011 09:17:37 -0700 (PDT)
Received: by 10.227.28.17 with SMTP id k17mr3065397wbc.3.1316448998062; Mon, 19 Sep 2011 09:16:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.55.82 with HTTP; Mon, 19 Sep 2011 09:16:18 -0700 (PDT)
In-Reply-To: <0d4101cc76e5$2333d6d0$699b8470$@com>
References: <7F2072F1E0DE894DA4B517B93C6A05852233EDB21D@ESESSCMS0356.eemea.ericsson.se> <1D062974A4845E4D8A343C653804920206648CB0@XMB-BGL-414.cisco.com> <7F2072F1E0DE894DA4B517B93C6A05852233EDB264@ESESSCMS0356.eemea.ericsson.se> <1D062974A4845E4D8A343C653804920206648CEB@XMB-BGL-414.cisco.com> <7F2072F1E0DE894DA4B517B93C6A05852233EDB2F0@ESESSCMS0356.eemea.ericsson.se> <1D062974A4845E4D8A343C653804920206648D0F@XMB-BGL-414.cisco.com> <7F2072F1E0DE894DA4B517B93C6A05852233EDB3E5@ESESSCMS0356.eemea.ericsson.se> <4E70D2E6.1000809@alvestrand.no> <CABcZeBORi5NLSsztnMfkwL43p9oKG9mi6e1WWOaiafAO_DpTVg@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852233D45FA3@ESESSCMS0356.eemea.ericsson.se> <CABcZeBO9hUSYZhLrcfbaK9HLGXq-q1EvqWOy6-gAN5xom6Z2-A@mail.gmail.com> <092401cc749b$8fd64940$af82dbc0$@com> <CABcZeBPgRD6kb2gg=m9NckSa1wrzwzJS6527nYqFG34b0cjfgQ@mail.gmail.com> <4E765E4A.3050801@alvestrand.no> <0ced01cc76de$28731630$79594290$@com> <4E77613B.4020805@ericsson.com> <0d4101cc76e5$2333d6d0$699b8470$@com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 19 Sep 2011 09:16:18 -0700
Message-ID: <CABcZeBO5KZhiPKOAFFPkX8NofKmDY12MA2z1LaqwStx1hxBnmQ@mail.gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] consent freshness [was RE: STUN for keep-alive]
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: Mon, 19 Sep 2011 16:15:15 -0000

On Mon, Sep 19, 2011 at 8:59 AM, Dan Wing <dwing@cisco.com> wrote:
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> When Eric mentioned 'consent freshness', it was the first time I
> had seen him use that term.  (No, I didn't search the archives.)

Yeah, I just made it up. Maybe not the best term....


> My interpretation 'consent freshness' is that, after a call had been
> up and running the RTP receiver might die or disconnect from the
> network, and a new host or restarted application might take over
> that IP address and possibly also start listening on that same
> UDP port.  By 'consent freshness', he wants a valid listener to
> occasionally say "yes, I still like receiving this flow"
> and he wants other listeners to not send that message -- causing
> the sender to eventually give up.

Yep. I'm certainly open to arguments that this isn't important... :)

-Ekr