Re: Proposed Update to Note Well

"Eggert, Lars" <lars@netapp.com> Sat, 23 June 2012 08:06 UTC

Return-Path: <lars@netapp.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 8C55B21F854B for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 01:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.346
X-Spam-Level:
X-Spam-Status: No, score=-10.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ge27ssdXbKBm for <ietf@ietfa.amsl.com>; Sat, 23 Jun 2012 01:06:41 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0F30B21F854D for <ietf@ietf.org>; Sat, 23 Jun 2012 01:06:40 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.77,462,1336374000"; d="p7s'?scan'208"; a="657404088"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 23 Jun 2012 01:06:34 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q5N86Yjn012117 for <ietf@ietf.org>; Sat, 23 Jun 2012 01:06:34 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.193]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0298.004; Sat, 23 Jun 2012 01:06:34 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF <ietf@ietf.org>
Subject: Re: Proposed Update to Note Well
Thread-Topic: Proposed Update to Note Well
Thread-Index: AQHNT/qkH0OL2Ixd6069A7hzCMzAQZcHGuuAgADoqIA=
Date: Sat, 23 Jun 2012 08:06:32 +0000
Message-ID: <BC155647-7F8A-4053-9B69-760114E85988@netapp.com>
References: <4FCF5B92.3070703@qualcomm.com> <4FCF5F99.3060807@cisco.com> <4FCF6BD5.7080503@qualcomm.com> <4FCF8471.2050701@cisco.com> <AEF1278E-68D1-47D3-932A-8B4940E864A0@harvard.edu> <4FD0679D.60304@cisco.com> <4FD068BC.5050405@cs.tcd.ie> <CAP0PwYZb87zRv0HpTES1twLnnTWUk9ft80bupUoB5f62P3eL=A@mail.gmail.com> <4FD0A53A.6010406@innovationslab.net> <4FD0AAA5.3060400@cisco.com> <C07B527F-37D1-4340-BF7D-F1B6BD263726@gmail.com> <4FD0B3A1.7090001@qualcomm.com> <4FD0B3FA.90704@qualcomm.com> <CAP0PwYYjbaHqkk7z5dXBB4kcH=NhT5_MofHFpwpgXnXvBG_tKQ@mail.gmail.com> <4FD0B86E.8020008@qualcomm.com> <CALaySJKSzsgpmxaiTsHMAEBJNTyPGScMnsfTM=rbMiMEUREb6w@mail.gmail.com> <BD3F594E-0ED1-4079-836F-5D7F5D63AD91@harvard.edu> <CAP0PwYam-arXn1vYebn16d7b_paD7P9ZwKhG1aYgCo2yxuUWaQ@mail.gmail.com> <4FD0F8C5.8000100@qualcomm.com> <4FD10927.8020906@qualcomm.com> <CALaySJ+cMTbcsQQXTa4xhxS+0jBHah4XBXuHEeo4+i2iv1cRVg@mail.gmail.com> <F1B6C50A-C9D2-46F6-B068-EBED878CC0AD@vigilsec.com> <8B7419F5-0C5C-473A-8EC0-1B 8A483171D8@ietf.org> <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
In-Reply-To: <C248F169-CCB5-4B88-9950-02714CCC89AE@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_B08244D9-3CA1-4723-8FB2-B5C848BA760B"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 23 Jun 2012 08:06:41 -0000

Hi,

having just gone through a similar exercise over on the IRTF side of things (see http://irtf.org/ipr), I wonder if what we came up with as a text couldn't be adapted to also work for the IETF:

> The IRTF follows the IETF Intellectual Property Rights (IPR) disclosure rules. This is a summary of these rules as they relate to IRTF research group discussions, mailing lists and Internet Drafts:
> 
> 	• If you include your own or your employer’s IPR in a contribution to an IRTF research group, then you must file an IPR disclosure with the IETF.
> 	• If you recognize your own or your employer’s IPR in someone else’s contribution and you are participating in the discussions in the research group relating to that contribution, then you must file an IPR disclosure with the IETF. Even if you are not participating in the discussion, the IRTFstill requests that you file an IPR disclosure with the IETF.
> 	• Finally, the IRTF requests that you file an IPR disclosure with the IETF if you recognize IPR owned by others in any IRTF contribution.
> You may file an IPR disclosure here: http://www.ietf.org/ipr/file-disclosure
> 
> See RFC 3979 (BCP 79) for definitions of “IPR” and “contribution” and for the detailed rules (substituting “IRTF” for “IETF”).


Lars