Re: Proposed New Note Well

John C Klensin <> Thu, 07 April 2016 12:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7BD3312D8E6 for <>; Thu, 7 Apr 2016 05:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
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 autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NjBtvWDqQ-UQ for <>; Thu, 7 Apr 2016 05:50:40 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2661012D8F7 for <>; Thu, 7 Apr 2016 05:50:32 -0700 (PDT)
Received: from [] ( by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1ao9OH-0006cr-En; Thu, 07 Apr 2016 08:50:29 -0400
Date: Thu, 07 Apr 2016 08:50:24 -0400
From: John C Klensin <>
To: Pete Resnick <>, Scott Bradner <>
Subject: Re: Proposed New Note Well
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Apr 2016 12:50:42 -0000


I think that would be an improvement, but I see a slightly
different tension that we probably need to deal with explicitly.
If we really want "short", e.g., fitting on one slide in big
letters, then the Note Well can be reduced to something like...

	"The IETF has a collection of policies.   As with a
	shrink-wrap license, you are responsible for all of them
	the moment you start participating or contributing, or
	interacting with other participants, in any way and can
	get yourself and your organization into big trouble for
	violating them.  An introduction to those policies and
	links to the details can be found at <link>."

If it seems to be useful, one more sentence to the effect that,
if one has questions after reading through the policies,
contact... could be added, but that might (should) be in
whatever is at the end of the link anyway.

IIR, a very brief statement of that sort is where this "Note
Well" stuff started.  It has gotten bloated as its mission has
crept toward explaining or enumerating the policies and the IETF
has become more policy-laden.

If we actually care about an on-screen version, a list of a
half-dozen or more links just isn't going to do it anyway.  It
won't be displayed long enough to copy it down.  That is
actually a reasonable guideline -- anything that requires
someone to look at material later, rather than being
read/listened to and absorbed, needs to be reduced to NTE one
link or reference or it won't be written down/ remembered.

In a way, we are going to end up with two Note Wells, one for
slide display and quick reminders (like registration forms) and
something else for posting, circulation in writing, and the
target of the reference/link in the first.  I fear that is
inevitable and that we should be adapting to it rather than
pretending we can create a one-screen document that covers


--On Thursday, April 07, 2016 00:27 -0300 Pete Resnick
<> wrote:

> How about if we changed the description of BCP 79:
> BCP 79 (Patent Policy, definitions of "Participation" and
> "Contribution")

> On 6 Apr 2016, at 19:37, Scott Bradner wrote:
>> imo - the 2nd pp is not duplicative - consider that the whole
>> current  note we'll is just covering "what is a
>> contribution" and the question of what
>> "participating"" is has been a  contentious issue for a
>> long time