Re: [clue] Alexey Melnikov's Discuss on draft-ietf-clue-data-model-schema-15: (with DISCUSS and COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Fri, 03 June 2016 14:02 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16FD312D191; Fri, 3 Jun 2016 07:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=NSEWkGQ7; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=AKnuFmV4
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMS-f4pwWrNa; Fri, 3 Jun 2016 07:02:42 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52D6E12D10F; Fri, 3 Jun 2016 07:02:42 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B2F0C20F27; Fri, 3 Jun 2016 10:02:41 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Fri, 03 Jun 2016 10:02:41 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=H+QRXYqRysJeVCUhJMuf0KBZcDo=; b=NSEWkG Q7AI+UofatGwHBRrOweJDsaCAEgcO46gdYFvzbuTuG2OTcPMGUJg+9J0FvSWkDro DhWqVKktFPlto7mjiAjDrI3yYMVDxrDX65uPAjuuiuWIY0TZqUe5yU9I74KWZvQP BekPV3SmTxOOlwIj0J2t2UNIIh07Q8W7z6//o=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=H+QRXYqRysJeVCU hJMuf0KBZcDo=; b=AKnuFmV4l8Hlo8RkrQX8C7ny46eySXSforbBr2lDPklJtN6 /G0lxF0OtS4cHW7OdqsHOt3D0Bxo2uUsXNp6Y6x6nSJpwCCAR9Gi3aFSvFIKjEEj 2VwPTUMhcWyABsAumJI6aujF1FEgaDOa+x4OdnRCPuHoM3Ie9QcL7BZ5G2eI=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 789B5A87E7; Fri, 3 Jun 2016 10:02:41 -0400 (EDT)
Message-Id: <1464962561.2590545.627005033.085F0AF6@webmail.messagingengine.com>
X-Sasl-Enc: rLgmeF/rVxMEfDQrleOYHahM8lRbR73Gz2D3/tmPfMEQ 1464962561
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Simon Pietro Romano <spromano@unina.it>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-38f217ef
In-Reply-To: <3568EEC4-B24B-4E8F-91EC-528D7489977E@unina.it>
References: <20160601074658.16192.65128.idtracker@ietfa.amsl.com> <3568EEC4-B24B-4E8F-91EC-528D7489977E@unina.it>
Date: Fri, 03 Jun 2016 15:02:41 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/clue/hCSF4qtuI7fdnL-YSxP5s8ERwJE>
Cc: clue-chairs@ietf.org, clue@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-clue-data-model-schema@ietf.org
Subject: Re: [clue] Alexey Melnikov's Discuss on draft-ietf-clue-data-model-schema-15: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Fri, 03 Jun 2016 14:02:44 -0000

Hi Simon,

On Fri, Jun 3, 2016, at 02:11 PM, Simon Pietro Romano wrote:
> Hello Alexey,
> 
> please find in-line our answers to your comments (preceded by
> [spromano]).
> 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > This is generally a well written document, but I have a couple of very
> > small points that need to be fixed:
> > 
> > Abstract: I have no CLUE what you are talking about. Abstracts should be
> > self contained, i.e. being understandable on its own. The Introduction
> > section has more relevant text which you might want to copy here.
> 
> [spromano] Got it. What about the following amended abstract?
>
> *****************************************************************************
> This document provides an XML schema file 
> for the definition of CLUE data model types. the term 'CLUE' stands for 
> "ControLling mUltiple streams for tElepresence" and is the name of 
> the IETF working group in which this document, as well as other 
> companion documents, has been developed. The document defines a coherent
> structure for information associated with the description of a 
> telepresence session. 
> *****************************************************************************

This is much better. I am not convinced that the acronym CLUE is going
to have much relevance after the WG is closed, but this is not a reason
to block publication of this document.
 
> > In 11.13: you need to have a Normative Reference to the language tag
> > document here (RFC 5646) when you describe the "lang" attribute.
> 
> [spromano] Done.
> 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > In 11.24.1: A reference to xCard would be good to have here.
> 
> [spromano] Done (the mentioned text is now in Section 16.1, btw).
> 
> > In 16.30:
> > 
> > MIME type name typo on the Subject line.
> 
> [spromano] Typo corrected.

Thank you for fixing these.

> > "Application that use this media type: none ?"
> > 
> > I don't think this is correct. Please provide some examples of
> > applications that would be using this media type. If no applications are
> > going to be using this media type, there is no need to register it ;-).
> 
> [spromano] Corrected. We put "CLUE-capable telepresence systems” there.
> Does this work for you?

Yes.

Best Regards,
Alexey