Contributions (Re: Proposed New Note Well)

Harald Alvestrand <harald@alvestrand.no> Tue, 05 January 2016 10:00 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A131B2A59 for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2016 02:00:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6VS1p_ONB63C for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2016 02:00:38 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 046B91B2A51 for <ietf@ietf.org>; Tue, 5 Jan 2016 02:00:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 3683C7C6607 for <ietf@ietf.org>; Tue, 5 Jan 2016 11:00:37 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BiqHh1ZXBlYw for <ietf@ietf.org>; Tue, 5 Jan 2016 11:00:36 +0100 (CET)
Received: from [IPv6:2001:470:de0a:1:30ac:3259:1d2a:d494] (unknown [IPv6:2001:470:de0a:1:30ac:3259:1d2a:d494]) by mork.alvestrand.no (Postfix) with ESMTPSA id F353A7C63AC for <ietf@ietf.org>; Tue, 5 Jan 2016 11:00:35 +0100 (CET)
Subject: Contributions (Re: Proposed New Note Well)
To: ietf@ietf.org
References: <20160104154102.1127.50621.idtracker@ietfa.amsl.com>
From: Harald Alvestrand <harald@alvestrand.no>
X-Enigmail-Draft-Status: N1110
Message-ID: <568B9443.8080708@alvestrand.no>
Date: Tue, 5 Jan 2016 11:00:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20160104154102.1127.50621.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jhpcVpUuVKyOQ-MEXh6CmCrWems>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 10:00:40 -0000

A subject that was heavily promoted in the old Note Well and not at all
covered in the new one is the nature of "contribution".

RFC 3979 section 1 has this text, which I believe actually came from
earlier "note well" versions:

   c. "IETF Contribution": any submission to the IETF intended by the
      Contributor for publication as all or part of an Internet-Draft or
      RFC (except for RFC Editor Contributions described below) and any
      statement made within the context of an IETF activity.  Such
      statements include oral statements in IETF sessions, as well as
      written and electronic communications made at any time or place,
      which are addressed to:

      o  the IETF plenary session,
      o  any IETF working group or portion thereof,
      o  the IESG, or any member thereof on behalf of the IESG,
      o  any IETF mailing list, including the IETF list itself, any
         working group or design team list, or any other list
         functioning under IETF auspices,
      o  the RFC Editor or the Internet-Drafts function (except for RFC
         Editor Contributions described below).

      Statements made outside of an IETF session, mailing list or other
      function, that are clearly not intended to be input to an IETF
      activity, group or function, are not IETF Contributions in the
      context of this document.

People keep being surprised by this - they imagine that they don't have
disclosure obligations in stuff they mentioned on the mike or in a
presentation but wasn't in their draft (they have), or think that
something someone else said at the bar is public information just
because the bar was at an IETF venue (it isn't), or that they can keep
something from triggering licensing obligations by buttonholing the AD
after the meeting (they can't).

Given that this is such a source of misunderstandings, going from laying
out the details to not mentioning the dividing line at all seems like a
larger leap than we should do.



On 01/04/2016 04:41 PM, IESG Secretary wrote:
> The IESG and the IAOC legal team have worked together to propose a new version for the note well that is used in various IETF activities. The intent is to make the note well shorter and more readable, and point more clearly to the full documentation of the various rules.
>
> The current note well is available at https://www.ietf.org/about/note-well.html and the proposed new one is below.
>
> The IESG will make a decision about this matter shortly. Please provide comments, if any, to ietf@ietf.org or to the IESG at iesg@ietf.org before January 30, 2016.
>
> ———
>
> Note Well
>
> This summary does not contain all the details and is only meant to point you in the right direction. Exceptions may apply. The IETF's patent policy and the definition of an IETF "contribution" are set forth in BCP 79; please read it carefully.
>
> The brief summary:
>
> • By participating with the IETF, you agree to follow IETF processes and policies.
> • If you are aware that any contribution to the IETF is covered by patents or patent applications that are owned by, controlled by, or would benefit you or your sponsor, you must disclose that fact, or not participate in the discussion.
> • As a participant in any IETF activity you acknowledge that written, audio and video records of meetings may be made and may be available to the public, and that recordings of you or your likeness, voice and conduct at the recorded event may be displayed, transmitted, copied, used and promoted in electronic and physical media accessible throughout the world.
> • Personal information that you provide to IETF will be handled in accordance with the IETF Privacy Statement set.
>
> For further information, talk to a chair, ask an Area Director, or review the following:
> ​
> BCP 9 (on the Internet Standards Process)
> ​BCP 25 (on the Working Group processes)
> ​BCP 78 (on copyright in IETF documents)
> ​BCP 79 (on patents covering IETF documents)
> TBD (on IETF Privacy Statement)
>


-- 
Surveillance is pervasive. Go Dark.