IETF Logo Mail Archive

Re: [video-codec] Charter issues from BoF - strategy

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Tue, 15 January 2013 04:28 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 777D711E80A6 for <video-codec@ietfa.amsl.com>; Mon, 14 Jan 2013 20:28:49 -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 WeFMMsgvhGYw for <video-codec@ietfa.amsl.com>; Mon, 14 Jan 2013 20:28:49 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id EF02B11E809C for <video-codec@ietf.org>; Mon, 14 Jan 2013 20:28:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=417; q=dns/txt; s=iport; t=1358224129; x=1359433729; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=J11k68W9dqnBI3jjr3D3MU6nVm/M/VUcQ/83UBRAcO0=; b=VfufAm3sYB9K6U2muesOpEqPAsmvw0Ci/if/sOqbdFu6R84EFB3OZ+HK 1qjsNa9ADc2iyQyTo3912jTH64oEhvhT0bwQ4GAlD/Mw76AgkgKe7IcyO iMTx6Evn0xZIscp3Bc3aJbPtmrlepBtKmYRaUJ9NoPK+DuZ0LX2LFF6OJ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AogGAL/Z9FCtJXHB/2dsb2JhbABEhXO0SIM4FnOCHwEBBDo/EAIBCCIUEDIlAgQOBQiIEagHjiaMawuDV2EDplSCaA2BbzU
X-IronPort-AV: E=Sophos;i="4.84,469,1355097600"; d="scan'208";a="162463060"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-4.cisco.com with ESMTP; 15 Jan 2013 04:28:48 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r0F4Smwm009902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Jan 2013 04:28:48 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.197]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Mon, 14 Jan 2013 22:28:48 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Timothy B. Terriberry" <tterribe@xiph.org>
Thread-Topic: [video-codec] Charter issues from BoF - strategy
Thread-Index: AQHN8tjP7JJiza8OOkabmGUBTNEeKA==
Date: Tue, 15 Jan 2013 04:28:47 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11337D2C7@xmb-aln-x02.cisco.com>
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
In-Reply-To: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6CD3906FA43CD040AB1A389F1F9861E5@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<video-codec@ietf.org>" <video-codec@ietf.org>
Subject: Re: [video-codec] Charter issues from BoF - strategy
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: Tue, 15 Jan 2013 04:28:49 -0000

On Nov 6, 2012, at 9:26 AM, Timothy B. Terriberry <tterribe@xiph.org> wrote:

>> 
>> 7. Have a strategy for achieving RF.
> 
> The most important part of this strategy is already specified in the charter, namely that the codec be developed "Under the IPR rules of the IETF." I discussed that in a little bit more detail at the BoF.

Send a separate email along lines of what I meant on this

v2.23.0 | Report a Bug | By Email