Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu-behave-consent-freshness-04.txt
Eric Rescorla <ekr@rtfm.com> Wed, 17 July 2013 22:00 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 7228321F9E26 for <rtcweb@ietfa.amsl.com>; Wed, 17 Jul 2013 15:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 B25dvCT5pxjm for <rtcweb@ietfa.amsl.com>; Wed, 17 Jul 2013 15:00:21 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDA821F9DFA for <rtcweb@ietf.org>; Wed, 17 Jul 2013 15:00:21 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id j10so1400864qcx.3 for <rtcweb@ietf.org>; Wed, 17 Jul 2013 15:00:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=1kl0FiMgbzIOlmmkviZphtkH32h7K+ZXj5O3h1Rmku4=; b=DkRqf3+5qec73pjsf994MPJ7BgVT35r+BKDJkafC/ZxfvLZNlBKrcr43OKMcX4LSe2 2G9fmxnam30VVDR67qF5co8jON9PbU523TsBBr8c9YTyjlDimCWBKBul6AysmaRHe/iN sPqij0QdguF5naqhmyhil3hSSsGAo8FWBrrXs/mgtqXdG5fwd651ai1ywULzOvpfSYyR x29cPE8P1OI7BbuN8I+WtLyMOkPNSJn6vt5coHc+voUCvlpp1LJU/3r8v7GrApBEnu8k DBUpZdW689THbRFat86aBImPcGq+vLf/qdO+Aq2WlI2ej+er3B6xrgafKaHvx3NrjUIT SZaw==
X-Received: by 10.49.85.4 with SMTP id d4mr10169429qez.10.1374098420747; Wed, 17 Jul 2013 15:00:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.48.234 with HTTP; Wed, 17 Jul 2013 14:59:40 -0700 (PDT)
X-Originating-IP: [203.69.99.16]
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE22419C35D@xmb-rcd-x02.cisco.com>
References: <20130715173816.18605.12504.idtracker@ietfa.amsl.com> <E721D8C6A2E1544DB2DEBC313AF54DE224198182@xmb-rcd-x02.cisco.com> <51E513BF.2040405@viagenie.ca> <E721D8C6A2E1544DB2DEBC313AF54DE224199A15@xmb-rcd-x02.cisco.com> <CABcZeBOchbtu8exo93QS5rri2Bvfa5z=2ty7a3dGr-pExY8hyQ@mail.gmail.com> <E721D8C6A2E1544DB2DEBC313AF54DE22419C35D@xmb-rcd-x02.cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 18 Jul 2013 05:59:40 +0800
Message-ID: <CABcZeBN4i=Nbiybksg8QrOeH+GYwNKeqUqQuxM-O40dtPkqx4A@mail.gmail.com>
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
Content-Type: multipart/alternative; boundary="047d7bb03e6a41619d04e1bc38e6"
X-Gm-Message-State: ALoCoQm/BqeeFQGO/IvO6qZOvu4aLNMn1+KJFW+MWqK0fstybeY/j8pDwRm/afTA6XnIdS1H1N/U
Cc: "behave@ietf.org" <behave@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu-behave-consent-freshness-04.txt
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: Wed, 17 Jul 2013 22:00:27 -0000
On Wed, Jul 17, 2013 at 8:47 PM, Muthu Arul Mozhi Perumal (mperumal) < mperumal@cisco.com> wrote: > |Uh, then how would they be sent to the other side?**** > > ** ** > > Ah, the browser would have to modify the SDP when it is sent on the wire.. > I don't really see how this helps since the server is going to see it and call tell the JS (remember, that's where the JS came from). -Ekr > > |As far as I can tell, with any plausible API SDES requires exposing the > keys to JS.**** > > ** ** > > That helps..thanks.**** > > ** ** > > Muthu**** > > ** ** > > *From:* Eric Rescorla [mailto:ekr@rtfm.com] > *Sent:* Wednesday, July 17, 2013 2:32 PM > *To:* Muthu Arul Mozhi Perumal (mperumal) > *Cc:* Simon Perreault; behave@ietf.org; rtcweb@ietf.org > *Subject:* Re: [rtcweb] [BEHAVE] FW: I-D Action: > draft-muthu-behave-consent-freshness-04.txt**** > > ** ** > > ** ** > > ** ** > > On Tue, Jul 16, 2013 at 6:49 PM, Muthu Arul Mozhi Perumal (mperumal) < > mperumal@cisco.com> wrote:**** > > [Added rtcweb since I am not sure if everyone involved there are following > this discussion in behave] > > Thanks for the review. See inline.. > > |-----Original Message----- > |From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf > Of Simon Perreault > |Sent: Tuesday, July 16, 2013 3:05 PM > |To: behave@ietf.org > |Subject: Re: [BEHAVE] FW: I-D Action: > draft-muthu-behave-consent-freshness-04.txt > | > |Le 2013-07-15 20:42, Muthu Arul Mozhi Perumal (mperumal) a écrit :**** > > |> The text and the algorithm in the draft are significantly simplified in > this updated version. > |> > |> Comments welcome.. > |**** > > |MUCH better introduction. Now I feel like I understand the need exactly. > | > |The "Design Considerations" section is still very confusing to me. > | > |> Though ICE specifies STUN Binding indications to be used for > |> keepalives, it requires that an agent be prepared to receive > |> connectivity check as well. If a connectivity check is received, a > |> response is generated, but there is no impact on ICE processing, as > |> described in section 10 of [RFC5245]. > | > |...so? Why is "an impact on ICE processing" necessary? > > Meant to stress these Binding request/response doesn't trigger an ICE > restart.. > > | > |> While a WebRTC browser could verify whether the peer continues to > |> send SRTCP reports before sending traffic to the peer, the usage of > |> SRTCP together with Security Descriptions [RFC4568] requires exposing > |> the media keys to the JavaScript and renders SRTCP unsuitable for > |> consent freshness. > | > |Why does it "require exposing the media keys to the JavaScript"? Is this > |because of a law of nature, or is it because of the way the JavaScript > |API is being designed? Could the JS API be changed to accommodate > |SRTCP+SDES? > > That's how the API construct looks like today -- the JavaScript would get > an SDP blob from the browser containing the crypto keys used for SDES-SRTP. > Of course, the browser could hide those keys by putting a "****" in SDP -:). > **** > > ** ** > > ** ** > > Uh, then how would they be sent to the other side?**** > > ** ** > > As far as I can tell, with any plausible API SDES requires exposing the > keys to JS.**** > > ** ** > > -Ekr**** > > ** ** >
- [rtcweb] FW: I-D Action: draft-muthu-behave-conse… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Simon Perreault
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Simon Perreault
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Avasarala, Ranjit (NSN - IN/Bangalore)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Avasarala, Ranjit (NSN - IN/Bangalore)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Eric Rescorla
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Avasarala, Ranjit (NSN - IN/Bangalore)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Simon Perreault
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Eric Rescorla
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Avasarala, Ranjit (NSN - IN/Bangalore)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Muthu Arul Mozhi Perumal (mperumal)
- Re: [rtcweb] [BEHAVE] FW: I-D Action: draft-muthu… Avasarala, Ranjit (NSN - IN/Bangalore)