[CCAMP] Reminder: IETF Disclosure Requirements & Process

Lou Berger <lberger@labn.net> Fri, 10 February 2012 16:44 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 026ED21F8657 for <ccamp@ietfa.amsl.com>; Fri, 10 Feb 2012 08:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.757
X-Spam-Status: No, score=-97.757 tagged_above=-999 required=5 tests=[AWL=0.545, BAYES_20=-0.74, 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 TQ7ZSFojNcZX for <ccamp@ietfa.amsl.com>; Fri, 10 Feb 2012 08:44:51 -0800 (PST)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id D645F21F8636 for <ccamp@ietf.org>; Fri, 10 Feb 2012 08:44:50 -0800 (PST)
Received: (qmail 8607 invoked by uid 0); 10 Feb 2012 16:44:49 -0000
Received: from unknown (HELO box313.bluehost.com) ( by oproxy9.bluehost.com with SMTP; 10 Feb 2012 16:44:49 -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=pyo/Cn/dGEbwTnLuP4Hd3A6Y2nOC2u6hixthCHD6UYY=; b=UUuObs9lh+cRglD94tk0tH9F7x3mtNieADG1FHWtqlxsN9xEblYW5CKCC7kWDYu+/b5abw19QA+pLIa3lBigAG1x0bevn/3lrq/3s4As4/mQSvYawBPJUijxSsHKSRo7;
Received: from box313.bluehost.com ([] helo=[]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1Rvtab-0005H0-8O; Fri, 10 Feb 2012 09:44:49 -0700
Message-ID: <4F35497E.5050000@labn.net>
Date: Fri, 10 Feb 2012 11:44:46 -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@tools.ietf.org" <ccamp-ads@tools.ietf.org>
Subject: [CCAMP] Reminder: IETF Disclosure Requirements & Process
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:44:52 -0000


We wanted to send out a reminder of the IETF's IPR disclosure
requirements.  To paraphrase, it says that if you have IPR in IETF work
you are to either:
(a) disclose it (or have your company disclose it), or
(b) not participate in discussions or I-Ds which may be encumbered by
the IPR.

Please take the time to read the rules about disclosing intellectual
property as expressed in RFC 3979 and at

Some key excerpts are:
[from the url]
    (c) in order for the working group and the rest of the IETF
    to have the information needed to make an informed decision
    about the use of a particular technology, all those
    contributing to the working group's discussions must disclose
    the existence of any IPR the Contributor or other IETF
    participant believes Covers or may ultimately Cover the
    technology under discussion. This applies to both
    Contributors and other participants, and applies whether they
    contribute in person, via email or by other means. The
    requirement applies to all IPR of the participant, the
    participant's employer, sponsor, or others represented by the
    participants, that is reasonably and personally known to the
    participant. No patent search is required.

[from the RFC]

   6.1.1.  A Contributor's IPR in his or her Contribution

   Any Contributor who reasonably and personally knows of IPR meeting
   the conditions of Section 6.6 which the Contributor believes Covers
   or may ultimately Cover his or her Contribution, or which the
   Contributor reasonably and personally knows his or her employer or
   sponsor may assert against Implementing Technologies based on such
   Contribution, must make a disclosure in accordance with this Section

   Contributors must disclose IPR meeting the description in this
   section; there are no exceptions to this rule.

   7.  Failure to Disclose

   There are cases where individuals are not permitted by their
   employers or by other factors to disclose the existence or substance
   of patent applications or other IPR.  Since disclosure is required
   for anyone submitting documents or participating in IETF discussions,
   a person who does not disclose IPR for this reason, or any other
   reason, must not contribute to or participate in IETF activities with
   respect to technologies that he or she reasonably and personally
   knows to be Covered by IPR which he or she will not disclose.
   Contributing to or participating in IETF discussions about a
   technology without making required IPR disclosures is a violation of
   IETF process.

Lou and Deborah