Re: Proposed New Note Well

Dave Cridland <> Mon, 04 January 2016 21:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B4CDD1ABD3D for <>; Mon, 4 Jan 2016 13:11:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4FUBJKyT_dF1 for <>; Mon, 4 Jan 2016 13:11:46 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B88081ABD3B for <>; Mon, 4 Jan 2016 13:11:45 -0800 (PST)
Received: by with SMTP id b14so1029475wmb.1 for <>; Mon, 04 Jan 2016 13:11:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TbHyXijsnf1m4lGWzsHau07fMPVAo4soUvK3a71YY6E=; b=Twtg++DWSyT7ecs2z1oUKlb0wQPkX2aJQviEm8cdHprNPCBp5n53Y/Dy+xU0thHV9h cOMJrJ/pjy8bU/kJGTTTjKz+bVKNcaippFn2CEZQuG5p16z+/RXlSsGjLfxx4wQRNRhZ pixqap5spvUuSTm15nCpjVHFzSQXWB6s3iuGw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TbHyXijsnf1m4lGWzsHau07fMPVAo4soUvK3a71YY6E=; b=mGt/cQ9MBBl7l/SEB0LKwmsfigdzSTbxBkCC34DGwq0P1b3dm6b8RbFcATD2gIVczP 3QLAu0/8M04M0+6svYERIznQW0vAQIv+Sx2xgejWm1MnKFTypSyBrPOr2XdQE3sTsxOE a/WUh17TI0RcTtJZgrubzNsbgJ4E7i0+NlwwzQiwSQL19z7GZV2MekOjyNJ8f9XoCiNX 787KcYsoVbXxD3wouAXEW0v61tx5+AGbSyPuqZ6/iDGhy/hyg2ivClSpdu/M+qcvT70x 7OCIZ7ptpr8PDPzkFbnEkI4jTIyrLIffgYD7vlOxnLa6LhnboH6lW0wHBbC6LCjNUDTg ov4A==
X-Gm-Message-State: ALoCoQkgrV2ftsgKmkrJlyFmkB6h9gFlMOzBl25hlaZuxD2l7PC8NMaLRu9y5B1IGmjOWnEX4ZnE+ICb/9MHcmfec2rXOoT55TU5m15Su4jpHfI0h8+3fEE=
MIME-Version: 1.0
X-Received: by with SMTP id bg2mr97170954wjb.162.1451941904250; Mon, 04 Jan 2016 13:11:44 -0800 (PST)
Received: by with HTTP; Mon, 4 Jan 2016 13:11:44 -0800 (PST)
In-Reply-To: <>
References: <>
Date: Mon, 04 Jan 2016 21:11:44 +0000
Message-ID: <>
Subject: Re: Proposed New Note Well
From: Dave Cridland <>
To: " Discussion" <>
Content-Type: multipart/alternative; boundary="089e010d826a70198a0528889127"
Archived-At: <>
Cc: The IESG <>, IETF Announcement List <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jan 2016 21:11:47 -0000

On 4 January 2016 at 15:41, 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
> and the proposed new one is
> below.
> The IESG will make a decision about this matter shortly. Please provide
> comments, if any, to or to the IESG at 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:
No, this is not a summary; these are "some key points".

> • 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:

I don't think that's an "or". I think:

The definitive policies are covered in the following documents which you
should read. If you are unsure, please contact a Working Group Chair or an
Area Director prior to participating.

> ​
> 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)
It's essential that these are provided as URLs as well as simple
references. Newcomers to the IETF may have heard of an RFC and be
comfortable with locating them; but not a BCP.