Re: [OPSEC] Reminder about IPR relating to draft-gont-opsec-ipv6-nd-security-01
Warren Kumari <warren@kumari.net> Wed, 11 September 2013 17:20 UTC
Return-Path: <warren@kumari.net>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98ED911E8215 for <opsec@ietfa.amsl.com>; Wed, 11 Sep 2013 10:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.27
X-Spam-Level:
X-Spam-Status: No, score=-102.27 tagged_above=-999 required=5 tests=[AWL=0.329, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Gp9F1qLbgfwv for <opsec@ietfa.amsl.com>; Wed, 11 Sep 2013 10:20:54 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5CF11E80D2 for <OpSec@ietf.org>; Wed, 11 Sep 2013 10:20:42 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.103]) by vimes.kumari.net (Postfix) with ESMTPSA id 2488C1B400DE; Wed, 11 Sep 2013 13:20:41 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <97DF5BF5-F528-4049-A19F-8DAFBA2235B3@kumari.net>
Date: Wed, 11 Sep 2013 13:20:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <72A228D6-AA0A-4A50-A26B-6304352F7ABD@kumari.net>
References: <BE05D627-FF00-415A-9CC3-A46729226611@kumari.net> <5230841E.8070001@si6networks.com> <97DF5BF5-F528-4049-A19F-8DAFBA2235B3@kumari.net>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-gont-opsec-ipv6-nd-security-01@tools.ietf.org" <draft-gont-opsec-ipv6-nd-security-01@tools.ietf.org>, "OpSec@ietf.org" <OpSec@ietf.org>, Warren Kumari <warren@kumari.net>
Subject: Re: [OPSEC] Reminder about IPR relating to draft-gont-opsec-ipv6-nd-security-01
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 17:20:59 -0000
On Sep 11, 2013, at 11:45 AM, Warren Kumari <warren@kumari.net> wrote: > > On Sep 11, 2013, at 10:54 AM, Fernando Gont <fgont@si6networks.com> wrote: > >> On 09/11/2013 11:18 AM, Warren Kumari wrote: >>> The authors of draft-gont-opsec-ipv6-nd-security-01 have asked for it >>> to be adopted as a OpSec document -- we would like to check whether >>> any claims of Intellectual Property Rights (IPR) on the document have >>> not yet been disclosed. >>> >>> Are you personally aware of any IPR that applies to >>> draft-gont-opsec-ipv6-nd-security-01? If so, has this IPR been >>> disclosed in compliance with IETF IPR rules? (See RFCs 3979, 4879, >>> 3669, and 5378 for more details.) >> >> I know of no IPR claims on the aforementioned document (and would be >> disappointed if there were any, I should say :-) ). > > Fair 'nuff. > > I assumed that, but it doesn't hurt to ask (especially because I have a script to do so :-)) -- having this info available allows the WG to make a decision if they want to adopt or not[0]. It also makes it harder for folk to later claim that they didn't know about the IPR requirements. > > W > … and it wasn't clear to at least one participant that I was speaking as an individual (I didn't explicitly state so). <no hats> > [0]: Many folk (myself included) would prefer not to adopt an IPR encumbered draft if at all possible. This was a flippant statement. IPR stuff is complex and subtle. Personally if I was choosing between two drafts, one with (disclosed) IPR and one without, I would probably choose the draft with no IPR (assuming all else is equal). Of course, there is a chance that there is undisclosed IPR on both -- so perhaps the one with the disclosed IPR is actually better (it shows that someone IPR-aware has considered the issue)! Then there all all the considerations about licensing, FRAND, etc. As I said, complex and subtle…. </no hats> As a chair I will (of course) adopt, progress, etc drafts with IPR. 'tis the WGs decision… W > > >> >> Thanks, >> -- >> Fernando Gont >> SI6 Networks >> e-mail: fgont@si6networks.com >> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492 >> >> >> >> >> _______________________________________________ >> OPSEC mailing list >> OPSEC@ietf.org >> https://www.ietf.org/mailman/listinfo/opsec >> > > -- > My memory is failing, so I changed my password to "incorrect". > That way, when I login with the wrong password the computer tells me… "Your password is incorrect". > > > > _______________________________________________ > OPSEC mailing list > OPSEC@ietf.org > https://www.ietf.org/mailman/listinfo/opsec > -- Curse the dark, or light a match. You decide, it's your dark. -- Valdis Kletnieks
- [OPSEC] Reminder about IPR relating to draft-gont… Warren Kumari
- Re: [OPSEC] Reminder about IPR relating to draft-… Fernando Gont
- Re: [OPSEC] Reminder about IPR relating to draft-… Warren Kumari
- Re: [OPSEC] Reminder about IPR relating to draft-… Warren Kumari