Re: [video-codec] Proposed charter

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Sun, 04 November 2012 23:47 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94AC221F8807 for <video-codec@ietfa.amsl.com>; Sun, 4 Nov 2012 15:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 KUQ-akXAGXWy for <video-codec@ietfa.amsl.com>; Sun, 4 Nov 2012 15:47:42 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 0D95521F8806 for <video-codec@ietf.org>; Sun, 4 Nov 2012 15:47:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=662; q=dns/txt; s=iport; t=1352072862; x=1353282462; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=C1t3RG8kPejCyzVTzIm13mmAAP0wFTPtZLlAzH3TNs8=; b=KnB6s+KinSoq+2POX5m6Z3iKMzBSS22YireOKhSura7HyUPMyD9cIyqZ +7wf7KqYYy0vwAMv3TM4qHqRSUa/ZeyvHuMri/GUh29frZESAIMWxX6Ze 24GikLJ9td00+cw9zyjrY6SHt3Z97+FEHzh+JUsGClTu3anGRuo4S1clx M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMFAHr9llCtJXG9/2dsb2JhbABDhVC9aoEIgh4BAQEDARIBJ0QLAgEIIhQQMiUCBAoJCBqHYgaZUJ8JjAEghTthA6RUgWuCb4FcPQ
X-IronPort-AV: E=Sophos;i="4.80,712,1344211200"; d="scan'208";a="138718101"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 04 Nov 2012 23:47:41 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id qA4Nlfst015543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <video-codec@ietf.org>; Sun, 4 Nov 2012 23:47:41 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.001; Sun, 4 Nov 2012 17:47:41 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "<video-codec@ietf.org>" <video-codec@ietf.org>
Thread-Topic: [video-codec] Proposed charter
Thread-Index: AQHNuubHGywIucR2FESNOo0Is1Bzbg==
Date: Sun, 04 Nov 2012 23:47:41 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
References: <5032B6F5.7030402@xiph.org>
In-Reply-To: <5032B6F5.7030402@xiph.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.91.211]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19338.004
x-tm-as-result: No--32.324400-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-ID: <06961F8C2D276D4CBD63C6B53FA67FCA@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [video-codec] Proposed charter
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 23:47:42 -0000

On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org> wrote:

> 4. Specification of a storage format for non-interactive (HTTP)
> streaming or file transfer of the codec. It is envisioned that this
> document shall be a Proposed Standard document.

I think I would prefer to see this say something a little more specific like do a storage format appropriate for use with DASH. If folks want to propose something other than DASH, sure, replace DASH with whatever, but my point is, I don't want this WG to be charter to do a DASH equivalent just as one of the sides topics. That is enough work it would need it's own WG.