Re: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Wed, 20 August 2014 04:09 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 AE7731A0B82 for <rtcweb@ietfa.amsl.com>; Tue, 19 Aug 2014 21:09:53 -0700 (PDT)
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 FkvADKVguuNq for <rtcweb@ietfa.amsl.com>; Tue, 19 Aug 2014 21:09:51 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 113E51A0174 for <rtcweb@ietf.org>; Tue, 19 Aug 2014 21:09:50 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so7216027wgh.23 for <rtcweb@ietf.org>; Tue, 19 Aug 2014 21:09:49 -0700 (PDT)
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=2WtU9ja1PJaporC/+m8CaxskGAQptNvhOs9bybQ42RE=; b=PC/UD/cH607vmTSuII0AjeJaGA92mXLssSbsZzzl1jIPOUCxp5aFIk6YQ0i5u5Jdql ktxR8XUOwLKOp9RN939ZW0Bb5dqpXyRk0qVCGLjtu9cQq7HA10jgqCK9qqwwOR4UncL6 y5r2KQvnxCKmhuxB8R4FCJIDivQdhBfBkqQuaVN7cWx/FfE+Ei8J1erWtYsFPNifxKNz Tn9lTMG/cSpIRdtYjd05UcyXuZOdcs2+kCcNunKi/gzMPTD9ZLkJU1xD4yjlBy/RF/mm kQI9CEbr9EOG3C3WUMh4zEKPdfF1zo5PCBUHgnOPBTvmeDgkVjfTSw62OUj4jT+vTk5c Z1hg==
MIME-Version: 1.0
X-Received: by 10.180.12.38 with SMTP id v6mr11574228wib.4.1408507789488; Tue, 19 Aug 2014 21:09:49 -0700 (PDT)
Received: by 10.180.211.102 with HTTP; Tue, 19 Aug 2014 21:09:49 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D41CDC3@ESESSMB209.ericsson.se>
References: <CA+9kkMCZT1XW4LLaJ4Nq2DbrxD59cYnjLo5JXn9fjEb8pyamaQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D41CDC3@ESESSMB209.ericsson.se>
Date: Wed, 20 Aug 2014 09:39:49 +0530
Message-ID: <CAKz0y8zycsyr9m4BA=-8xOaWkU+Sog5Mbz7K-oN3woqi++mVzg@mail.gmail.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a11c240ea74b7f5050107c67b"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/EqTIC8R43KiH7M_A8w_6WE72_sg
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness
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: Wed, 20 Aug 2014 04:09:53 -0000

I believe draft-ietf-rtcweb-stun-consent-freshness deals with the WebRTC
browser. A WebRTC device (eg. a mobile phone) on the other hand, could run
a WebRTC browser and a JS and perform consent. Similarly, a WebRTC endpoint
(whatever that gets defined as) might also perform consent, while a WebRTC
gateway might not, and how consent applies to those should get specified in
the document(s) that define those requirements (note: the gateway referred
to in draft-ietf-rtcweb-stun-consent-freshness is any SIP gateway).

So, draft-ietf-rtcweb-stun-consent-freshness should just replace WebRTC
endpoint and WebRTC implementation with WebRTC browser, IMHO.

Muthu

On Tue, Aug 19, 2014 at 7:36 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>
>
> The draft says:
>
>
>
> “WebRTC endpoints are required to support full ICE as specified in
>
>                 section 3.4 of [I-D.
> ​​
> ietf-rtcweb-transports].  However, when WebRTC
>
>                 endpoints interwork with other endpoints that support only
> ICE-lite
>
>                 (e.g., gateways) those endpoints will not generate consent
> checks,
>
>                 but just respond to consent checks they receive.”
>
>
>
> The draft also talks about “WebRTC implementations” and “WebRTC browsers”.
>
>
>
> We need to make sure that the terminology is aligned with
> draft-ietf-rtcweb-overview (for example,
> ​​
> draft-ietf-rtcweb-overview does not talk about “WebRTC endpoints”), which
> also may be impacted based on the outcome of the current
> terminology/gateway discussion.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
> *From:* rtcweb [mailto:rtcweb-bounces@ietf.org] *On Behalf Of *Ted Hardie
> *Sent:* 14. elokuuta 2014 18:10
> *To:* rtcweb@ietf.org; Sean Turner; Cullen Jennings
> *Subject:* [rtcweb] WG Last Call for
> draft-ietf-rtcweb-stun-consent-freshness
>
>
>
> This starts a WG Last Call for draft-ietf-rtcweb-stun-consent-freshness
> (available at
> http://datatracker.ietf.org/doc/draft-ietf-rtcweb-stun-consent-freshness/).
> Please review the document and send comments to the list by September 10,
> 2014.
>
> thanks,
>
> Ted Hardie
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>