IETF Logo Mail Archive

Re: [clue] Gen-ART review of draft-ietf-clue-telepresence-requirements-06.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 03 December 2013 11:37 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1133F1AE118 for <clue@ietfa.amsl.com>; Tue, 3 Dec 2013 03:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 xwSj_PNl5nCS for <clue@ietfa.amsl.com>; Tue, 3 Dec 2013 03:37:25 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 87C461AE116 for <clue@ietf.org>; Tue, 3 Dec 2013 03:37:25 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFANnBnVKHCzI1/2dsb2JhbABagkMjIThTuGeBHBZ0giYBAQEDEhtMEAIBCA0FECQyFw4CBAENDRqHXwGmKJsGF45NMQeDIIETA5Qxik+LJ4Mpgio
X-IronPort-AV: E=Sophos; i="4.93,817,1378872000"; d="scan'208,217"; a="39672298"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 03 Dec 2013 06:37:22 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 03 Dec 2013 06:26:28 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0146.000; Tue, 3 Dec 2013 06:37:20 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Stephen Botzko <stephen.botzko@gmail.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [clue] Gen-ART review of draft-ietf-clue-telepresence-requirements-06.txt
Thread-Index: AQHO67/3lpfRdohfAEekr7wrGB/gDJpCXzpQ
Date: Tue, 03 Dec 2013 11:37:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1294E040@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA12943EA9@AZ-FFEXMB04.global.avaya.com> <528E3706.1000102@alum.mit.edu> <CAHBDyN7TEMfqZPrpgOeGDrWa-=9NDEeeZp9PQhoLXc0sawT4wA@mail.gmail.com> <CAMC7SJ5Tq9XoDt=U2AWOQsQ6mB-fcP9BeXDmzA8KurC8e2zkZQ@mail.gmail.com>
In-Reply-To: <CAMC7SJ5Tq9XoDt=U2AWOQsQ6mB-fcP9BeXDmzA8KurC8e2zkZQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA1294E040AZFFEXMB04globa_"
MIME-Version: 1.0
Cc: "draft-ietf-clue-telepresence-requirements.all@tools.ietf.org" <draft-ietf-clue-telepresence-requirements.all@tools.ietf.org>, "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] Gen-ART review of draft-ietf-clue-telepresence-requirements-06.txt
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 03 Dec 2013 11:37:28 -0000

Minor clarification of my comment on a minor issue. What needs definition here is the term CLUE itself. The document talks about 'CLUE will not dictate', 'architecture for CLUE', 'CLUE enables', etc., but what is CLUE? (someone may wonder)

Regards,

Dan





Minor issues:

1. If this is the first and basic document to be read by somebody who starts to browse through the CLUE specifications, it would be good to define or expand some place in the introduction what CLUE is.
[SB] I am not sure if the CLUE WG has a recommended order for reading the various documents.  Personally I would recommend that people start with the use cases.  In any event, I think the document purpose is properly captured in the abstract - it is not intended to be an introduction to telepresence generally or as an orientation to CLUE specifications.
[/SB]

v2.23.0 | Report a Bug | By Email