[codec] Summary of codec specification

Cullen Jennings <fluffy@cisco.com> Fri, 01 October 2010 17:26 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A90473A6C09 for <codec@core3.amsl.com>; Fri, 1 Oct 2010 10:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.409
X-Spam-Level:
X-Spam-Status: No, score=-110.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2J9dZnq4c3ZS for <codec@core3.amsl.com>; Fri, 1 Oct 2010 10:26:27 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C78313A6918 for <codec@ietf.org>; Fri, 1 Oct 2010 10:26:27 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkGAEu2pUyrRN+J/2dsb2JhbACUMI4HcatdnD2FRASEUYVrgwI
X-IronPort-AV: E=Sophos;i="4.57,267,1283731200"; d="scan'208";a="263420413"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 01 Oct 2010 17:27:08 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o91HR7fR005320; Fri, 1 Oct 2010 17:27:07 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 01 Oct 2010 11:27:06 -0600
Message-Id: <1E7430DC-ED0D-44A3-826B-B1F344CB918E@cisco.com>
To: codec@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>
Subject: [codec] Summary of codec specification
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 17:26:28 -0000

With my chair hat on, here are thing thing I believe we have consensus on to move forward on.

1) The code will be in the appendix of the draft base64 encoded. We can sort out later if it is gziped tar file of whatever but it will be some easy to extract format. This has been done on other documents. I have talked to the AD about this before. I have not talked to RFC Ed but do not foresee any issues there. 

2) The code will be under the simplified BSD license as specified by current IETF process documents and most importantly the IETF Trust Licensee Policy. (As a side note, this is not a topic that is debatable in this WG - if you want to change IETF process, go somewhere else)

3) We have rough consensus that where the code and the text version description of the algorithm disagree, the code version is the one that is "correct"

4) The chairs have not yet made any decision about if we have consensus on bit-exactness. I'm not 100% sure where we stand on this but given we are in doubt on this, there is no consensus yet. 

5) The chairs have not made any decisions about if we have consensus on characterization gating. See logic around #4. 

Once we have a WG guidelines document, we as a WG can make sure it represents what is and is not consensus - something we can't do for an individual draft. Given the discussion over the last week, we are probably going to  adopt draft-valin-codec-guidelines as the basis for the WG document  some time real soon now. The chairs need to have a few more conversations about this first. It's would be fine at this point in time for a WG draft on guidelines to have proposed text in it that did not yet have consensus but it should clearly state they did not have consensus and was simply proposed text. 

Cullen <CODEC Co-Chair> - That's a lot of "C"s