[rtcweb] Opsdir last call review of draft-ietf-rtcweb-jsep-21

Carlos Martinez <carlosm3011@gmail.com> Thu, 17 August 2017 01:21 UTC

Return-Path: <carlosm3011@gmail.com>
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 05C1313239D; Wed, 16 Aug 2017 18:21:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Martinez <carlosm3011@gmail.com>
To: ops-dir@ietf.org
Cc: draft-ietf-rtcweb-jsep.all@ietf.org, rtcweb@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150293290297.12432.15822575176336895893@ietfa.amsl.com>
Date: Wed, 16 Aug 2017 18:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/b0sC1CMPg6nYJcOTApk2BCYlzmc>
Subject: [rtcweb] Opsdir last call review of draft-ietf-rtcweb-jsep-21
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: Thu, 17 Aug 2017 01:21:43 -0000

Reviewer: Carlos Martinez
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.

Noting that I'm certainly not an expert on the subject matter, I've found this
document to be READY. I found it well-written, it contains plenty of detailed
examples (which I believe are really important for API and programming-heavy
documents), and includes plenty of references as well.

Please do not forget to remove "Appendix B.  Change log".

A minor observation, not even a nit, is that the text in the Security
Considerations "While formally the JSEP interface is an API, it is better to
think of it is an Internet protocol, with the JS being untrustworthy from the
perspective of the endpoint. " could be more clear.

thanks!

/Carlos