IETF Logo Mail Archive

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

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Mon, 15 December 2014 14:52 UTC

Return-Path: <muthu.arul@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CD01A1B64 for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 06:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HjP7BNW9adUL for <rtcweb@ietfa.amsl.com>; Mon, 15 Dec 2014 06:52:07 -0800 (PST)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7201A6FE7 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 06:52:07 -0800 (PST)
Received: by mail-wg0-f53.google.com with SMTP id l18so14556702wgh.26 for <rtcweb@ietf.org>; Mon, 15 Dec 2014 06:52:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3UTExqgkhQ1u3bzXO6sxA80wmsyzpy/eB/7CFivWRT4=; b=0v94XSM7CXi3HQ5UvYhgqTEPXIXWuPra5Z6kHg180k7MhrOBAnMR6Xu/FML3WtJaJX peZMAcDHrK9cpHJJz+vEGNGQr+EPJKIOvEvf/W8xEwVux4niNVv2ed1gacPWiDLRESiP fT9qpoqQ/oun4F1qaow12QljV6f88Uuph9ONoTT5/5LLtTauCnrB3ISiysVgDJkzQvto KWs6In2cJbjdH9xMUZ3ZRHQsXjqVD5L+nFmZZerOYQJFiJLM2IXtd0OK3W/hcSCkm9Rh T7fWV8Nyd0flNoOhItlHfynrr2LxELi0b2eAV3N9KEjBDiXigmqA4+B028+MvQ0cAwJP MKTw==
MIME-Version: 1.0
X-Received: by 10.180.211.201 with SMTP id ne9mr31500900wic.30.1418655126184; Mon, 15 Dec 2014 06:52:06 -0800 (PST)
Received: by 10.180.76.242 with HTTP; Mon, 15 Dec 2014 06:52:06 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5CACA0@ESESSMB208.ericsson.se>
References: <20141215034305.14105.51004.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B1D5C7B1D@ESESSMB208.ericsson.se> <CANO7kWATP0_DcvNkMgRE_ddmcPa9DTdNSkRjY2WYFwGVkyCvfg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5CACA0@ESESSMB208.ericsson.se>
Date: Mon, 15 Dec 2014 20:22:06 +0530
Message-ID: <CAKz0y8zU9B=xN0bzQrEf8BuHOGBXkHEGJc3Q6sNtdyh9hJXJ0A@mail.gmail.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c266d6dae884050a4262df"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/nD05z_IXIKR-OGzUAzMdU7uWBco
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-stun-consent-freshness-10.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Dec 2014 14:52:09 -0000

We discussed this earlier in the WG:
http://www.ietf.org/mail-archive/web/rtcweb/current/msg13020.html

In fact, -08 had the following non-normative text:
   A WebRTC implementation [I-D.ietf-rtcweb-overview], which implements
   full ICE, performs consent freshness test using STUN request/response
   as described below:

I think the text in -10 can be replaced with:
   A full ICE implementation performs consent freshness test using STUN
   request/response as described below:

And the security-arch / overview documents can specify how it applies to
WebRTC.

Muthu

On Mon, Dec 15, 2014 at 7:19 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:
>
> Hi,
>
> >I suggest to simply remove the whole paragraph and the reference.
>
> That is my suggestion also :)
>
> As Harald indicated he will add text to the overview document about the
> usage, nothing is "lost".
>
> Regards,
>
> Christer
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email