Re: Proposed New Note Well

Pete Resnick <presnick@qti.qualcomm.com> Thu, 07 April 2016 03:27 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76FCD12D0DE for <ietf@ietfa.amsl.com>; Wed, 6 Apr 2016 20:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
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 9-Z9ibSCE1wd for <ietf@ietfa.amsl.com>; Wed, 6 Apr 2016 20:27:25 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4578012D0B3 for <ietf@ietf.org>; Wed, 6 Apr 2016 20:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1459999645; x=1491535645; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=CgKNMQT85/kxxk5ZH6YtFxZY8AfN6hClID9nuiPtYaA=; b=VzkdqepsugNruBbcJS/c2u184FtYXgHrkdZqpLhoY/zO9jVtO20IS4v8 d87CwVHR4rdKtjVp8VlJaP6bnA9Yl/QqVZPiuiWKrlv+9w8iyt+fdZNLC sg5uA+x7CS+ZIZUD4KV5VYjAsyBm645fY5wu/sQw/2J7EI0zRrbicri1o w=;
X-IronPort-AV: E=Sophos;i="5.24,448,1455004800"; d="scan'208,217";a="277903469"
Received: from ironmsg04-r-new.qualcomm.com (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Apr 2016 20:27:24 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8127"; a="1170796855"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Apr 2016 20:27:24 -0700
Received: from [10.64.173.153] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 6 Apr 2016 20:27:23 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Scott Bradner <sob@sobco.com>
Subject: Re: Proposed New Note Well
Date: Thu, 07 Apr 2016 00:27:20 -0300
Message-ID: <A3FBD041-3BC9-442C-B581-F874B4359FE1@qti.qualcomm.com>
In-Reply-To: <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com> <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com> <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0A13FA2C-4533-41CA-AC08-B156249E08CD_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5239)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/V6Muzh0H7vEr8CSiRZPwz-zoa5I>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 07 Apr 2016 03:27:29 -0000

How about if we changed the description of BCP 79:

BCP 79 (Patent Policy, definitions of "Participation" and 
"Contribution")

?

pr

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
>
> Scott
>
>> On Apr 6, 2016, at 6:33 PM, Pete Resnick <presnick@qti.qualcomm.com> 
>> 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 https://www.ietf.org/ombudsteam 
>> <https://www.ietf.org/ombudsteam> placed next to the line regarding 
>> anti-harassment procedures. That'll let people also find the IESG 
>> Statement and other info.
>>
>> 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 <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478