Re: [clue] Ticket #16: Need a term for a particular encoding of a capture

Roni Even <roni.even@mail01.huawei.com> Mon, 10 September 2012 20:46 UTC

Return-Path: <roni.even@mail01.huawei.com>
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 42ACA11E80BA for <clue@ietfa.amsl.com>; Mon, 10 Sep 2012 13:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcjFZOUHE4Se for <clue@ietfa.amsl.com>; Mon, 10 Sep 2012 13:46:37 -0700 (PDT)
Received: from hwsga01-in.huaweimarine.com (unknown [58.251.153.223]) by ietfa.amsl.com (Postfix) with ESMTP id E799E11E808A for <clue@ietf.org>; Mon, 10 Sep 2012 13:46:36 -0700 (PDT)
Received: from szxpml203-edg.exmail.huawei.com ([172.17.1.119]) by hwsga01-in.huaweimarine.com (MOS 4.1.3-GA) with ESMTP id ADL04285; Tue, 11 Sep 2012 04:46:33 +0800
X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com <roni.even@mail01.huawei.com> 5 none
X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com <roni.even@mail01.huawei.com> 5 none
X-Mirapoint-Received-SPF: 172.17.1.119 szxpml203-edg.exmail.huawei.com <roni.even@mail01.huawei.com> 5 none
Received: from SZXPML401-HUB.exmail.huawei.com (10.82.67.140) by szxpml203-edg.exmail.huawei.com (172.24.2.14) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 11 Sep 2012 04:46:16 +0800
Received: from SZXPML504-MBX.exmail.huawei.com ([169.254.3.38]) by szxpml401-hub.exmail.huawei.com ([10.82.67.140]) with mapi id 14.01.0323.003; Tue, 11 Sep 2012 04:46:32 +0800
From: Roni Even <roni.even@mail01.huawei.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roni Even <ron.even.tlv@gmail.com>
Thread-Topic: [clue] Ticket #16: Need a term for a particular encoding of a capture
Thread-Index: AQHNj4hBwXBRFE88qkqUZW6iQqu1IZeECoLH
Date: Mon, 10 Sep 2012 20:46:32 +0000
Message-ID: <760B7D45D1EFF74988DBF5C2122830C205B442A1@szxpml504-mbx.exmail.huawei.com>
References: <50477793.6050607@alum.mit.edu> <006f01cd8f7c$17c474c0$474d5e40$@gmail.com>, <504E3BA3.8000606@alum.mit.edu>
In-Reply-To: <504E3BA3.8000606@alum.mit.edu>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.1.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'CLUE' <clue@ietf.org>
Subject: Re: [clue] Ticket #16: Need a term for a particular encoding of a capture
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 10 Sep 2012 20:46:38 -0000

Paul,
srcname describes a specific encoding by using a hierarchy tree. I am not sure what byou mean by a source but it can be used to describe a specific enconding using the hierarchy. For example v1.hires and v1.lowres.
Roni

________________________________________
From: clue-bounces@ietf.org [clue-bounces@ietf.org] on behalf of Paul Kyzivat [pkyzivat@alum.mit.edu]
Sent: Monday, September 10, 2012 10:12 PM
To: Roni Even
Cc: 'CLUE'
Subject: Re: [clue] Ticket #16: Need a term for a particular encoding of a capture

On 9/10/12 1:45 PM, Roni Even wrote:
> Hi,
> Maybe we can use srcname as proposed in
> http://tools.ietf.org/id/draft-westerlund-avtext-rtcp-sdes-srcname-01.txt
> Roni

IIUC, SRCNAME would correspond to what Jonathan has been calling a
"source". But it wouldn't correspond to a Capture, or and Encoding, or
an RTP stream that is the result of applying a particular encoding to a
capture.

So, while I think SRCNAME is useful, I don't see its applicability to
ticket #16.

        Thanks,
        Paul

> -----Original Message-----
> From: clue-bounces@ietf.org [mailto:clue-bounces@ietf.org] On Behalf Of Paul
> Kyzivat
> Sent: 05 September, 2012 6:02 PM
> To: CLUE
> Subject: [clue] Ticket #16: Need a term for a particular encoding of a
> capture
>
> I am trying to kick off discussion to get this one resolved.
>
> Here is the description of the issue:
>
>> We keep encountering places where the term "capture" is used but where
>> what is meant is a specific encoding of a capture.
>> (It is possible to request/send multiple encodings of the same
>> capture.)
>>
>> We need a specific term, and definition, for this concept.
>> This should be in the framework, and it and other documents should be
>> fixed to use this new term where appropriate.
>
> A few things come to mind:
>
> - "capture encoding" - the obvious choice
> - "encoded capture"
> - "capture rendition"
>
> Or any of the above with a "-" instead of the space.
>
>       Thanks,
>       Paul
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
>

_______________________________________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/listinfo/clue