[Last-Call] Opsdir last call review of draft-ietf-mmusic-msrp-usage-data-channel-22

Al Morton via Datatracker <noreply@ietf.org> Sat, 18 July 2020 23:21 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90ED83A0E59; Sat, 18 Jul 2020 16:21:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, draft-ietf-mmusic-msrp-usage-data-channel.all@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159511450354.23221.6528626623548419509@ietfa.amsl.com>
Reply-To: Al Morton <acmorton@att.com>
Date: Sat, 18 Jul 2020 16:21:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/I5M4_gqqMeqZoRci91Lg323ye60>
Subject: [Last-Call] Opsdir last call review of draft-ietf-mmusic-msrp-usage-data-channel-22
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2020 23:21:44 -0000

Reviewer: Al Morton
Review result: Has Nits

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/