IETF Logo Mail Archive

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

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Tue, 26 August 2014 04:14 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 0FF381A0709 for <rtcweb@ietfa.amsl.com>; Mon, 25 Aug 2014 21:14:55 -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 B_WZSrLQloe7 for <rtcweb@ietfa.amsl.com>; Mon, 25 Aug 2014 21:14:53 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 967A21A06D3 for <rtcweb@ietf.org>; Mon, 25 Aug 2014 21:14:52 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id k14so13843703wgh.8 for <rtcweb@ietf.org>; Mon, 25 Aug 2014 21:14:51 -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=44T+3hins2xEMXSoBZv8X8U+Y6mR03uCoCCJ4dYHWLI=; b=DwFgjiFQylxYWfnHk1j2I26dWCfsoWsNgaklkdZd60doPsuEAxi9OoJseDRx1yWB90 /89K+iWfmeCBrmBy3Ye+IHncDAdO9Dof2OaGJeFR4CEgZmNeXDoDucGABo4El6HVqudT +gXSwsS1sy5Et+AX63X+/KcEXrR6uhG9JTt7YjtOGR/r+WUquioMdYCi7ueu6qUWmxYV 85VY092Xn33SUbw+aia9SWU1IJbUlFJLiRr/qR7xkz3bgTqcsHehTXPW3a1O1QdcJsjL RJ8fwOhFgKuSvMBeHacuVavrAZypGi/yyyWurRFQPFzBpYcjJGI6I5DuIOcQ/T4YECUT STsg==
MIME-Version: 1.0
X-Received: by 10.180.184.20 with SMTP id eq20mr18873265wic.37.1409026491039; Mon, 25 Aug 2014 21:14:51 -0700 (PDT)
Received: by 10.180.197.168 with HTTP; Mon, 25 Aug 2014 21:14:50 -0700 (PDT)
In-Reply-To: <CABkgnnU6kv+=jQuxj4Ci-zYW9mHEfJ=6jqqrdqDTopPN06-kgw@mail.gmail.com>
References: <CA+9kkMCZT1XW4LLaJ4Nq2DbrxD59cYnjLo5JXn9fjEb8pyamaQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D41CDC3@ESESSMB209.ericsson.se> <CAKz0y8zycsyr9m4BA=-8xOaWkU+Sog5Mbz7K-oN3woqi++mVzg@mail.gmail.com> <53F451CF.10705@alvestrand.no> <001b01cfbc94$fccd5310$f667f930$@co.in> <CAKz0y8zNM3rc3XC6JqrK+d4hXiT5TomhNM+W2twg0+-83-pFow@mail.gmail.com> <CABkgnnUnfB5bskH4zWRfBMdHbSoqftV5Fo_GEXoLt9XCH9Tt_w@mail.gmail.com> <CAD5OKxsT9Vdm0=tjk9WsLAH4ekbAizgyjm--168TrOf8UAYGZw@mail.gmail.com> <CABkgnnXUpibu8kWYmbJJJT2J3RNGXFV8LbceLijgG0U-pGY2xQ@mail.gmail.com> <CAKz0y8z_oBf2efavfOLgzqE1R8sZstefZ1tvwwJLkhRskXZERQ@mail.gmail.com> <CAD5OKxsSqA=cki_fSaqAPP0GXCv_kHr6571C+K9ze4ceHCGYdQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D427B68@ESESSMB209.ericsson.se> <D01D6B42.104F8%rmohanr@cisco.com> <009001cfbe4f$6b92f280$42b8d780$@co.in> <CAKz0y8y3=0_-jwWiviR_Uj6tSq75NEq92Ocergc_NvFk2h_72Q@mail.gmail.com> <CAD5OKxugaPq=cLppPUqT8CUADV-E2zDMcz6m3sUgKOnK-TdQfQ@mail.gmail.com> <CABkgnnU6kv+=jQuxj4Ci-zYW9mHEfJ=6jqqrdqDTopPN06-kgw@mail.gmail.com>
Date: Tue, 26 Aug 2014 09:44:50 +0530
Message-ID: <CAKz0y8xv9WpVGohS++-S+hedcfO-Qq3SSz14A7h9O1iNPT3Qpg@mail.gmail.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c3536a7a46380501808b02"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/bcKWVg4Z9l2D3nRXH_T0HKLYOn0
Cc: "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: Tue, 26 Aug 2014 04:14:55 -0000

On Mon, Aug 25, 2014 at 10:45 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 25 August 2014 05:43, Roman Shpount <roman@telurix.com> wrote:
> > Any WebRTC entity implementing full ICE - MUST
> > Any WebRTC entity (such as WebRTC gateway) implementing ICE-lite -- MUST
> NOT
>
> Let's try this instead:
>
> Any WebRTC entity MUST implement full ICE
>

​The transport draft already has the following:

​   ICE [RFC5245] MUST be supported.  The implementation MUST be a full
   ICE implementation, not ICE-Lite.  A full ICE implementation allows
   interworking with both ICE and ICE-Lite implementations when they are
   deployed appropriately.

​It also says:

   This document focuses on the data transport protocols that are used
   by conforming implementations, including the protocols used for
   interaction with intermediate boxes such as firewalls, relays and NAT
   boxes.

"Conforming implementations" seem to mean any WebRTC entity. However, the
following limits it to only WebRTC devices (and leaves out WebRTC gateway,
in particular):

   This document describes requirements that apply to all WebRTC
   devices.​

We should probably sort this out the "full ICE" requirement in the
transport draft.


> Any entity performing full ICE MUST implement consent
>
>
I guess you mean any WebRTC entity (there may be other SIP entities doing
full ICE and nothing to do with WebRTC). If so, it works for me..

Muthu​



> Done.
>

v2.23.0 | Report a Bug | By Email