Last Call Review of draft-ietf-mmusic-msrp-usage-data-channel-22
review-ietf-mmusic-msrp-usage-data-channel-22-opsdir-lc-morton-2020-07-18-00

Request Review of draft-ietf-mmusic-msrp-usage-data-channel
Requested rev. no specific revision (document currently at 24)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2020-07-21
Requested 2020-07-07
Authors Jose Recio, Christer Holmberg
Draft last updated 2020-07-18
Completed reviews Genart Last Call review of -21 by Brian Carpenter (diff)
Secdir Last Call review of -22 by Alexey Melnikov (diff)
Tsvart Last Call review of -23 by Yoshifumi Nishida (diff)
Opsdir Last Call review of -22 by Al Morton (diff)
Assignment Reviewer Al Morton 
State Completed
Review review-ietf-mmusic-msrp-usage-data-channel-22-opsdir-lc-morton-2020-07-18
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/_ieKFtzSnIV8IzzUs4i6pHN9uYU
Reviewed rev. 22 (document currently at 24)
Review result Has Nits
Review completed: 2020-07-18

Review
review-ietf-mmusic-msrp-usage-data-channel-22-opsdir-lc-morton-2020-07-18

OPS-DIR review of MSRP over Data Channels
draft-ietf-mmusic-msrp-usage-data-channel-21

   This document specifies how the Message Session Relay Protocol (MSRP)
   can be transported as a WebRTC data channel sub-protocol, using the
   SDP offer/answer generic data channel negotiation framework to
   establish such a channel.
   
Summary: Operational impact of this protocol appears to be minimal, if any.

Gen-ART review has found some Nits that must be resolved.

Key Notes from the Doc Shepherd's write-up [0]: 
   It seems that this document was revived after being abandoned, when 3GPP noticed the change in status and recognized use of the draft as a normative reference in 3GPP Specifications.

   There are no known implementations of the protocol, and thus no operational issues at this time. However, some vendors (of???) have indicated plans to implement.

   Further investigation indicates that there are Normative References 
   to drafts that are more than a year old. For example, the 2 refs below:
   ...the channel is
   negotiated using the SDP-based external negotiation method defined in
      [I-D.ietf-mmusic-data-channel-sdpneg].

   The following WebRTC data channel property values
   [I-D.ietf-rtcweb-data-channel] apply to an MSRP data channel:

Also, from the Normative References section:
   
   [I-D.ietf-rtcweb-data-protocol]
              Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Channel
              Establishment Protocol", draft-ietf-rtcweb-data-
              protocol-09 (work in progress), January *2015*.

   [I-D.ietf-rtcweb-data-channel]
              Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
              Channels", draft-ietf-rtcweb-data-channel-13 (work in
              progress), January *2015*. 

Nits:

2.  Conventions
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALLNOT",
s/"SHALLNOT"/"SHALL NOT"/



[0] https://datatracker.ietf.org/doc/draft-ietf-mmusic-msrp-usage-data-channel/shepherdwriteup/