[rtcweb] Review of draft-ietf-rtcweb-overview-18

Jon Mitchell <jrmitche@puck.nether.net> Fri, 17 March 2017 18:18 UTC

Return-Path: <jrmitche@puck.nether.net>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D207A129524; Fri, 17 Mar 2017 11:18:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jrmitche@puck.nether.net>
To: ops-dir@ietf.org
Cc: draft-ietf-rtcweb-overview.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148977468781.13113.11027871370786405378@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 11:18:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/40ulwq3JQk2Y9n8p3YgrkV6NYAM>
Subject: [rtcweb] Review of draft-ietf-rtcweb-overview-18
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Mar 2017 18:18:08 -0000

Reviewer: Jon Mitchell
Review result: Ready

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments. 

This document is an overall of the WebRTC protocols that are
considered a "minimum" set to claim compliance with the standard the
draft sets forth.  As far as I can tell, no new protocols or
implementation details are contained in the draft and operational
concerns largely are covered (or not) by the many referenced protocol
specifications within it.  Therefore, I believe this draft is Ready,
although there is some question in my mind of whether this is actually
a standards track versus best current practice document as
interoperability from the standpoint of this document seems to not
require any new on the wire negotiation (outside of each individual's
protocols negotiations).