[CCAMP] Planned CCAMP WG process change

Lou Berger <lberger@labn.net> Fri, 10 February 2012 16:49 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 78AD121F86FC for <ccamp@ietfa.amsl.com>; Fri, 10 Feb 2012 08:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.709
X-Spam-Status: No, score=-98.709 tagged_above=-999 required=5 tests=[AWL=1.452, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id HyyGS2B5I0o6 for <ccamp@ietfa.amsl.com>; Fri, 10 Feb 2012 08:49:47 -0800 (PST)
Received: from oproxy3-pub.bluehost.com (oproxy3.bluehost.com [IPv6:2605:dc00:100:2::a3]) by ietfa.amsl.com (Postfix) with SMTP id 7975821F85AE for <ccamp@ietf.org>; Fri, 10 Feb 2012 08:49:44 -0800 (PST)
Received: (qmail 29496 invoked by uid 0); 10 Feb 2012 16:49:43 -0000
Received: from unknown (HELO box313.bluehost.com) ( by oproxy3.bluehost.com with SMTP; 10 Feb 2012 16:49:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=PxdxFn3cxdCJJYOljGvM/wkZXu/IcNJCGIk0Nr49kKg=; b=wALJd1Hru1JmJhWJ+nxvOYZdIuJIt9RY9nQVL/Vmnsww94q5AQEwr46IpHsLIojdIgVIxQoK7gZAiN2HQAEHa2WdGT1EE/4MS7b0m9f5ffAs8HMmHz6aI0A4xuFJwbBs;
Received: from box313.bluehost.com ([] helo=[]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1RvtfL-0007H7-HS; Fri, 10 Feb 2012 09:49:43 -0700
Message-ID: <4F354AA4.7050701@labn.net>
Date: Fri, 10 Feb 2012 11:49:40 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: CCAMP <ccamp@ietf.org>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth authed with lberger@labn.net}
Cc: CCAMP ADs <ccamp-ads@tools.ietf.org>
Subject: [CCAMP] Planned CCAMP WG process change
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2012 16:49:48 -0000


In order to avoid possible future issues, we plan to make a slight
change in how the WG processes documents.  In particular, we plan to
poll authors on their compliance with IETF IPR rules prior to moving a
document to the next step in the WG process, e.g., before an individual
draft becomes a WG document or a WG document goes to last call.

It is likely that you will see similar plans in other WGs in the near

Please let us know if you have any comments on this plan.

Deborah and Lou


To: <list all authors and contributors>

Subject: Regarding IPR on <insert document name>

Are you aware of any IPR that applies to <insert document name>? If so,
has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
3979, 4879, 3669 and 5378 for more details)?

If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR.  This document will not advance to the next
stage until a response has been received from each author and listed

If you are on the CCAMP WG email list but are not listed as an author or
contributor, we remind you of your obligations under the IETF IPR rules
which encourages you to notify the IETF if you are aware of IPR of
others on an IETF contribution, or to refrain from participating in any
contribution or discussion related to your undisclosed IPR.  For more
information, please see the RFCs listed above and