[rtcweb] Genart last call review of draft-uberti-rtcweb-rfc8829bis-02

Joel Halpern via Datatracker <noreply@ietf.org> Sun, 27 March 2022 17:49 UTC

Return-Path: <noreply@ietf.org>
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 AA97C3A087B; Sun, 27 Mar 2022 10:49:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-uberti-rtcweb-rfc8829bis.all@ietf.org, last-call@ietf.org, rtcweb@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164840334560.25727.8727238035250838155@ietfa.amsl.com>
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Date: Sun, 27 Mar 2022 10:49:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/vq-RWZElZ01sODyGWtRMVMxLq0c>
Subject: [rtcweb] Genart last call review of draft-uberti-rtcweb-rfc8829bis-02
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 27 Mar 2022 17:49:06 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-uberti-rtcweb-rfc8829bis-02
Reviewer: Joel Halpern
Review Date: 2022-03-27
IETF LC End Date: 2022-04-05
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard. 
However, there are some issues that should be considered before final approval.

Major issues: None

Minor issues:
    I found myself confused as a reader about one aspect of this document  The
    document seems to describe both the Interface to the JSEP and the details
    of what the underlying system must do in response to JSEP operations.  The
    later is described very well and clearly.  The former is described quite
    vaguely.  I suspect that the assumption is that the required parameters are
    described in the W3C documents.  But it is hard to tell, and the only
    formal reference is a vague citation in the introduction to an outdated W3C
    specification.  A little more clarity on how an implementor is supposed to
    know what actual interface objects, methods, and parameters they need to
    provide would be helpful.  Also, the reference should be updated to
    whatever is the current W3C specification.
Nits/editorial comments: