IETF Logo Mail Archive

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

"Espen Berger (espeberg)" <espeberg@cisco.com> Fri, 14 September 2012 14:45 UTC

Return-Path: <espeberg@cisco.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 1581421F8514 for <clue@ietfa.amsl.com>; Fri, 14 Sep 2012 07:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 PZJXYvTtMfhU for <clue@ietfa.amsl.com>; Fri, 14 Sep 2012 07:45:53 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3C85721F850D for <clue@ietf.org>; Fri, 14 Sep 2012 07:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3245; q=dns/txt; s=iport; t=1347633953; x=1348843553; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=xVqzS44zQ4RmK2i+Zf7T79Z8nAk55vQ/luBCSRWcwvc=; b=SNueotaDcXW88aP3rENVo7f8QXuASt4gJnbjEhFjiErewV1q0qU848eZ MQq8j8yCDV4a3ubT4zJo5nnRGy1uGrbjQMlIoSEGnrO1e2+Zr3nSAzEBM 0LfIiSxuv/u7AbEhicDWlCYOg/0JU/pxN8gjMnP0XU/hZsfhBRpdAFSGU 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOpBU1CtJXG+/2dsb2JhbABFDrtvgQeCIAEBAQQBAQEPASc0CwwEAgEIEQQBAQEKFAkHJwsUCQgCBAENBQgah2sLmzSgHYsVJIVkYAOWdY0kgWmCLDqCFw
X-IronPort-AV: E=Sophos;i="4.80,423,1344211200"; d="scan'208";a="121651739"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 14 Sep 2012 14:45:52 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8EEjqlO002487 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Sep 2012 14:45:52 GMT
Received: from xmb-rcd-x11.cisco.com ([169.254.1.118]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0298.004; Fri, 14 Sep 2012 09:45:51 -0500
From: "Espen Berger (espeberg)" <espeberg@cisco.com>
To: Roni Even <roni.even@mail01.huawei.com>, 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: AQHNj4hEDH3Kh9UcMUyXPikWwz7jB5eEX3kAgAWPV/A=
Date: Fri, 14 Sep 2012 14:45:51 +0000
Message-ID: <E8F5F2C7B2623641BD9ABF0B622D726D0F4E26C6@xmb-rcd-x11.cisco.com>
References: <50477793.6050607@alum.mit.edu> <006f01cd8f7c$17c474c0$474d5e40$@gmail.com>, <504E3BA3.8000606@alum.mit.edu> <760B7D45D1EFF74988DBF5C2122830C205B442A1@szxpml504-mbx.exmail.huawei.com>
In-Reply-To: <760B7D45D1EFF74988DBF5C2122830C205B442A1@szxpml504-mbx.exmail.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.147.112.107]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19182.004
x-tm-as-result: No--43.876600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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: Fri, 14 Sep 2012 14:45:54 -0000

I like the srcname draft since its allow a producer to forward meta-information and attached it to an SSRC. The intent seems to be to be able to forward names like a capture name and a quality modifier. The example from the draft matched my suggestion to do a 'capture' .'encoding-quality' 

However I do not think its represent a name for the actual encoded stream, so I still like the capture encoding to represent a single media stream. 

Cheers 
 
-Espen 


-----Original Message-----
From: clue-bounces@ietf.org [mailto:clue-bounces@ietf.org] On Behalf Of Roni Even
Sent: 10. september 2012 22:47
To: Paul Kyzivat; Roni Even
Cc: 'CLUE'
Subject: Re: [clue] Ticket #16: Need a term for a particular encoding of a capture

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
_______________________________________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/listinfo/clue

v2.23.0 | Report a Bug | By Email