IETF Logo Mail Archive

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

Stephen Botzko <stephen.botzko@gmail.com> Thu, 05 December 2013 14:53 UTC

Return-Path: <stephen.botzko@gmail.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 30FF21AE007 for <clue@ietfa.amsl.com>; Thu, 5 Dec 2013 06:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-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 wsu_cYDU4uSf for <clue@ietfa.amsl.com>; Thu, 5 Dec 2013 06:53:07 -0800 (PST)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 24EEB1ADF9C for <clue@ietf.org>; Thu, 5 Dec 2013 06:53:07 -0800 (PST)
Received: by mail-ve0-f181.google.com with SMTP id oy12so13637906veb.40 for <clue@ietf.org>; Thu, 05 Dec 2013 06:53:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7VIAUJkRYoG2VT0UokM1VLrEa5uC+2scuyvZsGEqMA8=; b=SchS3N8rsuiuL7c6Wrs+4B9dp8nZjtEife5ZW0P+Clm1wAgA/OoOtIhtVAWfsaZTH4 DInZYDnFXUJCN+ULpyY7zRbLsw6lPhJZqMIIVVnjR/INtKOVeKdk1ENMz1+63Wk2WPLu 7EPCmc3JO/LjPoZpFPAB8aM2PP2utcDqI+HayrWtlx3McDDN11AwXEu002XL4JZRl/8r zsfjH634lCRFjevPMS6bXoTJ4mfx/f9kitxcWLtKwWcbpcsa+VmQxITAalU0uJA+oeQx 66FmYRDTnjtJW2v9jcUtoGO2gGd83/SF/1by635OwVK4Hg5Zx0KDqgpa9zhxt8ckyuj6 PsBg==
MIME-Version: 1.0
X-Received: by 10.52.230.102 with SMTP id sx6mr53518017vdc.15.1386255183613; Thu, 05 Dec 2013 06:53:03 -0800 (PST)
Received: by 10.220.187.68 with HTTP; Thu, 5 Dec 2013 06:53:03 -0800 (PST)
In-Reply-To: <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> <9904FB1B0159DA42B0B887B7FA8119CA1294E040@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 05 Dec 2013 09:53:03 -0500
Message-ID: <CAMC7SJ4z=TQ=a4UVwxkWc1qnZhMmMNXexZv=qSxTVdA_M-ePPA@mail.gmail.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary="089e0111ae34c9d04604eccaaf60"
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: Thu, 05 Dec 2013 14:53:09 -0000

>>>The document talks about ‘CLUE will not dictate’, ‘architecture for
CLUE’, ‘CLUE enables’, etc., but what is CLUE? (someone may wonder)
I imagine other WGs have run into this with their requirements.  How is it
normally handled?

Stephen


On Tue, Dec 3, 2013 at 6:37 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>wrote:

>  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