[rtcweb] Kathleen Moriarty's No Objection on draft-ietf-rtcweb-jsep-24: (with COMMENT)

Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com> Tue, 12 December 2017 21:53 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-rtcweb-jsep@ietf.org, Ted Hardie <ted.ietf@gmail.com>, rtcweb-chairs@ietf.org, ted.ietf@gmail.com, rtcweb@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151311562760.14100.8542671795905150712.idtracker@ietfa.amsl.com>
Date: Tue, 12 Dec 2017 13:53:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/LENAOocjBkRzrhouJrSERukg1d8>
Subject: [rtcweb] Kathleen Moriarty's No Objection on draft-ietf-rtcweb-jsep-24: (with COMMENT)

Kathleen Moriarty has entered the following ballot position for
draft-ietf-rtcweb-jsep-24: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-jsep/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm sure the RFC editor would have caught this nit:

2nd paragraph of security considerations section:
While formally the JSEP interface is an API, it is better to think of
   it is an Internet protocol
s/is an Internet/as an Internet/

[rtcweb] Kathleen Moriarty's No Objection on draf… Kathleen Moriarty
Re: [rtcweb] Kathleen Moriarty's No Objection on … Justin Uberti
Re: [rtcweb] Kathleen Moriarty's No Objection on … Kathleen Moriarty