IETF Logo Mail Archive

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

Mary Barnes <mary.ietf.barnes@gmail.com> Thu, 05 December 2013 16:15 UTC

Return-Path: <mary.ietf.barnes@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 0A7A31AE0C5 for <clue@ietfa.amsl.com>; Thu, 5 Dec 2013 08:15:47 -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 kharZ7-8mDdj for <clue@ietfa.amsl.com>; Thu, 5 Dec 2013 08:15:44 -0800 (PST)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7B12C1AE028 for <clue@ietf.org>; Thu, 5 Dec 2013 08:15:44 -0800 (PST)
Received: by mail-wi0-f170.google.com with SMTP id hq4so1107961wib.5 for <clue@ietf.org>; Thu, 05 Dec 2013 08:15:40 -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=/LrwrEx41B1HtH/oDCX0flvzPGoVFHGGxdE6movgWXQ=; b=lfkPDeJdT7MdlMnzZnX+nkIImcwrxlb7KlSFufdCSsDDfURZG13MG+WOBD7+bgQJyK Q3/JOazfQkS3pqOJKxAtd3kz5qg4GKd8GaXzB3IJBNkFop94AWiqvqviXIJkKlKmc3tM 6/zSakhqvGVgJFerVO85BNP5+8AUE9pUY57+6BQzWfPRX4RqOLTN4CIQxOT6nCMBphUL AB4hEU6ZatpAn1IDN1Eo/UeeSCjXwzfEajHzMm5UREtqBMPD657tMnVdrj/p3tGpTvHH Q6T5S276AZbo/wZSdcOC69IPp5XCyElvFB3kFTHbxWGUlTntlx7bAmPMk4jiwxAn7EIV /iLA==
MIME-Version: 1.0
X-Received: by 10.194.202.230 with SMTP id kl6mr70806689wjc.9.1386260140646; Thu, 05 Dec 2013 08:15:40 -0800 (PST)
Received: by 10.216.172.9 with HTTP; Thu, 5 Dec 2013 08:15:40 -0800 (PST)
In-Reply-To: <CAMC7SJ4z=TQ=a4UVwxkWc1qnZhMmMNXexZv=qSxTVdA_M-ePPA@mail.gmail.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> <CAMC7SJ4z=TQ=a4UVwxkWc1qnZhMmMNXexZv=qSxTVdA_M-ePPA@mail.gmail.com>
Date: Thu, 05 Dec 2013 10:15:40 -0600
Message-ID: <CAHBDyN6__-604S65UeTCQhXHUb=RU_+=y5sbYFevjF7z=qSFUA@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Stephen Botzko <stephen.botzko@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b873a103fe48404eccbd7b2"
Cc: "clue@ietf.org" <clue@ietf.org>, "draft-ietf-clue-telepresence-requirements.all@tools.ietf.org" <draft-ietf-clue-telepresence-requirements.all@tools.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 16:15:47 -0000

We can expand CLUE on first usage and then qualify that the use of the term
CLUE in this document is referring to the solutions developed to enable
support for CLUE.

It may be most appropriate actually to introduce the term CLUE in the
abstract. Perhaps something like:
OLD
    This memo discusses the requirements for specifications that enable

   telepresence interoperability, by describing the relationship between
   multiple RTP streams.  In addition, the problem statement and related
   definitions are also covered herein.

NEW

   This memo discusses the requirements for specifications, that enable

   telepresence interoperability by describing behaviors and protocols
    for Controlling Multiple Streams for Telepresence (CLUE).

   In addition, the problem statement and related

   definitions are also covered herein.


Mary

On Thu, Dec 5, 2013 at 8:53 AM, Stephen Botzko <stephen.botzko@gmail.com>wrote:

> >>>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