Re: [rtcweb] Updated -gateways draft

Ted Hardie <ted.ietf@gmail.com> Mon, 06 July 2015 22:35 UTC

Return-Path: <ted.ietf@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 5FF641A1B4C for <rtcweb@ietfa.amsl.com>; Mon, 6 Jul 2015 15:35:25 -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 SKwhWSG-nRlV for <rtcweb@ietfa.amsl.com>; Mon, 6 Jul 2015 15:35:23 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66D871A1AE1 for <rtcweb@ietf.org>; Mon, 6 Jul 2015 15:35:23 -0700 (PDT)
Received: by wgqq4 with SMTP id q4so152633911wgq.1 for <rtcweb@ietf.org>; Mon, 06 Jul 2015 15:35:22 -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=Mc3kE/0cTeBcHzNzS76II/Zgxd/UYBMZpWoApWxrYgQ=; b=G1gcTPLOV8bW4CSC9UXWNrTGlOFVpfdre6YX7tA1HXKGhR0/fbz7O7zNEdAYK89Gt9 pYRsX+4tMhBUj88o1rhNb8Rma/XR72e3BzPd+HkTH0uiZ9ZOf0vxasLHk5QGDVEAL4t/ xlKPkKQ8oVILpvjZoKFs7i7QapHc6g9DEnJj8hnamQi3u6uwMXN7WARVpZJJGrZiAaKH ScJ9vCfHoxH405UlS5zZkTxRSJS2dxwB/Zs6ySnhaXsVorWrWlsOmm14MYAfiJo3QuTZ mZeOpqcpJ5NVjFRTHsDbFx8tCwjFzwpRW5PCx+g5tryGNQWlZ8CXYSfIfxfp4yomndSF 62Hg==
MIME-Version: 1.0
X-Received: by 10.194.189.80 with SMTP id gg16mr2152286wjc.9.1436222122161; Mon, 06 Jul 2015 15:35:22 -0700 (PDT)
Received: by 10.194.25.74 with HTTP; Mon, 6 Jul 2015 15:35:22 -0700 (PDT)
In-Reply-To: <559AFEDB.4070205@alvestrand.no>
References: <559AFEDB.4070205@alvestrand.no>
Date: Mon, 06 Jul 2015 15:35:22 -0700
Message-ID: <CA+9kkMCd0udsYrKAdAxt1zhb+=Gb9dy4rG=x5RWcxFBTx+tNOw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="047d7bb03f9c68fdaa051a3c8552"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/G4psEuDPmaUlWIAXWsM3MUZp5Kg>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Updated -gateways draft
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Jul 2015 22:35:25 -0000

On Mon, Jul 6, 2015 at 3:19 PM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> Uwe and I have prepared a new -gateways draft (version -01).
>
> I don't think there's much controversial in it, and there's only one
> issue that I think needs WG time at this time:
>
> Should it be Informational or Standards-track?
>
> An informational document defines guidance for how gateways should
> behave, but nobody needs to pay attention if they don't want to.
>
> A standards-track document (which no other RTCWEB document should be
> dependent on) defines requirements for how things that call themselves
> "WebRTC gateways" should behave, but nobody needs to call their gateways
> that, and anyway, there's no protocol police, so the difference isn't
> all that much in practice.
>
> More important: What do people want it to be?
>
>
​I think we adopted it in part because 3GPP had a dependency on it.  Does
it need to be standards track for them to reference it?

Ted​




> Harald
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>