IETF Logo Mail Archive

Re: [rtcweb] What is consent?

"Dan Wing" <dwing@cisco.com> Tue, 11 September 2012 18:29 UTC

Return-Path: <dwing@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 EF30521F862A for <rtcweb@ietfa.amsl.com>; Tue, 11 Sep 2012 11:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9ehNzXK3m4e for <rtcweb@ietfa.amsl.com>; Tue, 11 Sep 2012 11:29:29 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBF521F8608 for <rtcweb@ietf.org>; Tue, 11 Sep 2012 11:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1635; q=dns/txt; s=iport; t=1347388169; x=1348597769; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=80FIFgil0NexWyXvoA0RPgGjnx6XHf/Hb/6O82UC1XI=; b=eGvBNfJW1eeg2yA0ClA9SchGLg/5lrLaD4RQT0nDvZfAnGniJfER9SaE G1+x/PjEeBxb+avPgvepklEiCxEVgYEI7w1iJKl6RkAOZ9vem2GSkZV8a SO8A4VSeOkGaBKBbHcXTS9VWTji4XzXi5yhfSyUp55UtaNAgEF+7PVtlD 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFAEWCT1CrRDoI/2dsb2JhbAA7Cqtcj3mBB4IgAQEBBAgKARcQPwwBAwIJDwIEAQEBGA8HGSMKCQgBAQQBEgsXh22bKqBTixAQgnmDHQOIVYUOljKBZ4MG
X-IronPort-AV: E=Sophos;i="4.80,406,1344211200"; d="scan'208";a="55362958"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 11 Sep 2012 18:29:28 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8BITSmA004277; Tue, 11 Sep 2012 18:29:28 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Harald Alvestrand' <harald@alvestrand.no>, rtcweb@ietf.org
References: <CABkgnnXAPZ5BN=CUwYdEpHKbCLBxctqpONL==QWf_WwgrNEK_A@mail.gmail.com> <CABcZeBNnoQwJu1MYSW=6q6pkrgXSPSUtVyOsngrPP6b8GaegdQ@mail.gmail.com> <CABkgnnUNhka8OJsiNCV5iOvU_cGyvt_y8=DN6qnud3Xr-dy1iQ@mail.gmail.com> <CABcZeBNddHgHnkZ5b2N4i-np3WuY51f6WHkBdT5mHBsieLMDow@mail.gmail.com> <CABkgnnVcf06uXPznn38VGGSi6u6brH_4j30cZjbF_YYj7zg9zA@mail.gmail.com> <504F6BB6.9050301@alvestrand.no>
In-Reply-To: <504F6BB6.9050301@alvestrand.no>
Date: Tue, 11 Sep 2012 11:29:28 -0700
Message-ID: <07c101cd904b$60bd2d50$223787f0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac2QPXaN9yJ05vyTRsGuoTSwXrvMaQADUE7A
Content-Language: en-us
Subject: Re: [rtcweb] What is consent?
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: Tue, 11 Sep 2012 18:29:30 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Harald Alvestrand
> Sent: Tuesday, September 11, 2012 9:50 AM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] What is consent?
> 
> On 09/11/2012 06:34 PM, Martin Thomson wrote:
> > On 11 September 2012 09:22, Eric Rescorla <ekr@rtfm.com> wrote:
> >> I'm really not following this.
> >>
> >> Responses from the server need to *contain* the MESSAGE-INTEGRITY
> >> field and otherwise are not taken as evidence of consent. This field
> can
> >> only be generated by a server that has the ICE credentials. So,
> obviously,
> >> a legacy STUN server won't generate that.
> > It's clear that I'm just being thick.
> >
> > The STUN server (legacy or otherwise) won't have a password and wont
> > generate MESSAGE-INTEGRITY.
> >
> > I apologise for wasting your (and everyone else's) time.
> The terms might have gotten confused, since STUN is used in two modes:
> 
> - With a STUN server, to identify reflexive addresses
> - With a peer, to verify ability to communicate, and to verify
> continued
> consent.
> 
> We don't want to mandate credentials for the first one.
> We do want to mandate credentials for the second.

Right.  The confusion is that ICE uses the STUN protocol for
two purposes:  to collect reflexive addresses, and to
perform connectivity checks with peers.  In RTCWEB, we plan
to additionally use connectivity checks for "consent", so
the STUN protocol will be used for three different purposes.

(And four if we count TURN, which also uses the STUN packet
format.)

-d

v2.23.0 | Report a Bug | By Email