Re: Proposed New Note Well

Tim Chown <> Wed, 06 April 2016 23:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AF2B812D7C9 for <>; Wed, 6 Apr 2016 16:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.53
X-Spam-Status: No, score=-3.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yrEqhJhRSwO1 for <>; Wed, 6 Apr 2016 16:02:29 -0700 (PDT)
Received: from ( [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5308112D635 for <>; Wed, 6 Apr 2016 16:02:28 -0700 (PDT)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id u36N2Mss021996; Thu, 7 Apr 2016 00:02:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 u36N2Mss021996
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1459983742; bh=Y4yiQfpMpKhJS6GkIG8dUJwF84w=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=0KdcO3gIE8dSkfRSFXuiweETOP0TJWfQ8BXlnxCkjZIMLR2coGJeJja2lLzIwucT6 5blI7jexcC2Jdrjw2VqOCFJAHWYlbdyqGALFfJcCYdeFYyTm1v6xRm3Rr3Wsq7k8zN hKbOlSjEJB51BPLA854mFEqcx3YMS34JX+qT7GL0=
Received: from ([2001:630:d0:f102:250:56ff:fea0:401]) by ( [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <> with ESMTP (valid=N/A) id s3602M30539121461A ret-id none; Thu, 07 Apr 2016 00:02:22 +0100
Received: from [IPv6:2001:67c:370:152:706f:f3be:f1f3:4fd0] ([IPv6:2001:67c:370:152:706f:f3be:f1f3:4fd0]) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id u36N2CEi007223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 00:02:15 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_639196CB-FC6B-43F2-8882-ADAE338894AD"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Proposed New Note Well
From: Tim Chown <>
In-Reply-To: <>
Date: Thu, 07 Apr 2016 00:02:12 +0100
Message-ID: <EMEW3|3d155810c4ad7ef897f82a141d170921s3602M03tjc||>
References: <> <> <>
To: Pete Resnick <>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3602M305391214600; tid=s3602M30539121461A; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u36N2Mss021996
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: Wed, 06 Apr 2016 23:02:31 -0000

On 6 Apr 2016, at 23:33, Pete Resnick <> wrote:
> Two things, neither earth-shattering:
> Jari did say he thought it was still too long. The second paragraph (mentioning the patent policy) seems duplicative with what's in the second bullet and the list at the bottom. And of course the top-level message should be that first bullet: You have to follow all of the rules. Let's just strike the second paragraph.
> In addition to the pointer to the documents at the bottom (which I presume will be links when this thing appears in HTML), it would be great to have a link to <> placed next to the line regarding anti-harassment procedures. That'll let people also find the IESG Statement and other info.
I agree. And it would be good if it could fit legibly on a single slide, for use in the WG chair slide decks, even if it’s something that in reality gets all the attention of a pre-flight safety video.

As a slight aside, I noticed this week that at least one WG used the proposed template rather than the (I think!) current one. While the direction of the new text  looks fine, we should probably be careful about what we’re using if it’s not yet official.

> pr
> On 21 Mar 2016, at 13:51, IESG Secretary wrote:
> Note Well
> This is a reminder of IETF policies in effect on various topics such as
> patents or code of conduct. It 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"
> and "participation" are set forth in BCP 79; please read it carefully.
> As a reminder:
> • By participating in the IETF, you agree to follow IETF processes and
> policies.
> • If you are aware that any IETF contribution is covered by patents or
> patent applications that are owned or controlled by 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 public.
> • Personal information that you provide to IETF will be handled in
> accordance with the IETF Privacy Statement.
> Definitive information is in the documents listed below and other IETF
> BCPs. For advice, please talk to WG chairs or ADs:
> ​
> BCP 9 (Internet Standards Process)
> ​BCP 25 (Working Group processes)
> BCP 25 (Anti-Harassment Procedures)
> BCP 54 (Code of Conduct)
> ​BCP 78 (Copyright)
> ​BCP 79 (Patents, Participation)
> TBD (Privacy)
> -- 
> Pete Resnick <>
> Qualcomm Technologies, Inc. - +1 (858)651-4478