IETF Logo Mail Archive

Re: [rtcweb] What is consent?

"Dan Wing" <dwing@cisco.com> Tue, 11 September 2012 23:39 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 02A9221E8040 for <rtcweb@ietfa.amsl.com>; Tue, 11 Sep 2012 16:39:08 -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 pEFAjwcpT0Gg for <rtcweb@ietfa.amsl.com>; Tue, 11 Sep 2012 16:39:07 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 5305421E8037 for <rtcweb@ietf.org>; Tue, 11 Sep 2012 16:39:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2077; q=dns/txt; s=iport; t=1347406747; x=1348616347; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=+m2Bb16L+IVBA/q9Avi1hIbMWmn0zpDXpCIHeyVUNp4=; b=eXuNSuBL9f/dvdwCBeqwQVqsrnSmYs3nRweK0ToqnJOJGnMuZPgaf0eF fAgoawoGi62/We8Q5VKL7jZzudkj4f7bphGj5PnddGr8TP9brfrQQUvg+ z8t4nIX1HxiGmcEQALRZXhNG9dqNwzRMfWlGIWpC4INSvfdCRJzLERexa s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjIFAKrKT1CrRDoI/2dsb2JhbABFq12PeoEHgiABAQEECAoBFxA/DAEDAgkPAgQBASgHGSMKCQgCBAESCxeHbZtToF+LEIYmA4hVhQ6WMoFngwY
X-IronPort-AV: E=Sophos;i="4.80,407,1344211200"; d="scan'208";a="54858856"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 11 Sep 2012 23:39:07 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8BNd6lr017953; Tue, 11 Sep 2012 23:39:06 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Bernard Aboba' <bernard_aboba@hotmail.com>, 'Eric Rescorla' <ekr@rtfm.com>
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> <BLU169-DS48211D4056CB291285DD4393930@phx.gbl>
In-Reply-To: <BLU169-DS48211D4056CB291285DD4393930@phx.gbl>
Date: Tue, 11 Sep 2012 16:39:06 -0700
Message-ID: <08c301cd9076$a2405c40$e6c114c0$@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: AQHuiFtacnnBjuI6raWX6lmK+8wORAGUpRMPAmkYFagCGeLX4JcS17FQgABGtXA=
Content-Language: en-us
Cc: rtcweb@ietf.org
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 23:39:08 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Bernard Aboba
> Sent: Tuesday, September 11, 2012 12:29 PM
> To: 'Eric Rescorla'
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] What is consent?
> 
> Eric Rescorla said:
> 
> "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."
> 
> [BA] While the presence of the MESSAGE-INTEGRITY field is a necessary
> condition, is it sufficient to demonstrate consent? For example, does
> the
> nominated flag need to be set to true?  RFC 5245 Section 7.1.3.2.4
> says:
> 
> 7.1.3.2.4.  Updating the Nominated Flag
> 
>    If the agent was a controlling agent, and it had included a USE-
>    CANDIDATE attribute in the Binding request, the valid pair generated
>    from that check has its nominated flag set to true.  This flag
>    indicates that this valid pair should be used for media if it is the
>    highest-priority one amongst those whose nominated flag is set.
> This
>    may conclude ICE processing for this media stream or all media
>    streams; see Section 8.
> 
>    If the agent is the controlled agent, the response may be the result
>    of a triggered check that was sent in response to a request that
>    itself had the USE-CANDIDATE attribute.  This case is described in
>    Section 7.2.1.5, and may now result in setting the nominated flag
> for
>    the pair learned from the original request.

For ICE Mobility (draft-wing-mmusic-ice-mobility), we might want to 
keep other candidates available, but inactive.  Over those other
candidates we would not signal USE-CANDIDATE, but we would want to
be able to switch to the other candidate as quickly as possible
(ideally, switch over immediately).  Similar considerations might 
apply to multipath RTP (draft-singh-avtcore-mprtp), too.
 
-d

v2.23.0 | Report a Bug | By Email