[clue] Alexey Melnikov's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Tue, 20 November 2018 16:49 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: clue@ietf.org
Delivered-To: clue@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 592C0130DD6; Tue, 20 Nov 2018 08:49:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-clue-protocol@ietf.org, "Daniel C. Burnett" <danielcburnett@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, clue-chairs@ietf.org, pkyzivat@alum.mit.edu, clue@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.88.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154273258728.18467.13818258072714840442.idtracker@ietfa.amsl.com>
Date: Tue, 20 Nov 2018 08:49:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/UUuUhggRTs8pSpGYaY8c9HFCStM>
Subject: [clue] Alexey Melnikov's No Objection on draft-ietf-clue-protocol-17: (with COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Nov 2018 16:49:48 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-clue-protocol-17: 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-clue-protocol/



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

I support Ben's DISCUSS.

A couple of extra nits, which I think need addressing:

XML and XML Schema need to be a Normative References.

12.4.1.  CLUE Message Types

   +-------------------+-----------------------------------+-----------+
   | Message           | Description                       | Reference |
   +-------------------+-----------------------------------+-----------+
   | options           | Sent by the CI to the CR  in the  | RFCXXXX   |
   |                   | initiation phase to specify the   |           |
   |                   | roles played by the CI, the       |           |
   |                   | supported versions and the        |           |
   |                   | supported extensions.             |           |
   | optionsResponse   | Sent by the CI to the CR in reply | RFCXXXX   |

Should the above be: "Sent by the CR to the CI ..."

   |                   | to an 'options' message to        |           |
   |                   | finally estabilsh the version and |           |

Typo: establish

   |                   | the extensions to be used in the  |           |
   |                   | following CLUE messages exchange. |           |

Examples in Section 10 contain URI
"http://wpage.unina.it/spromano/clue-protocol-17-schema-file.xsd". Maybe they
shouldn't.