Re: Normatively referenced specifications
Dave Crocker <dhc@dcrocker.net> Wed, 18 December 2013 17:41 UTC
Return-Path: <dhc@dcrocker.net>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBF441AE005 for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 09:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 PJtfQltbyZj1 for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 09:41:55 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 770211AC448 for <ipr-wg@ietf.org>; Wed, 18 Dec 2013 09:41:55 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rBIHfg0q013968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 18 Dec 2013 09:41:45 -0800
Message-ID: <52B1DE0C.8010201@dcrocker.net>
Date: Wed, 18 Dec 2013 09:40:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "Dale Mohlenhoff (dmohlenh)" <dmohlenh@cisco.com>, SM <sm@resistor.net>, "Black, David" <david.black@emc.com>
Subject: Re: Normatively referenced specifications
References: <CED46C85.AC4EC%stewe@stewe.org> <6.2.5.6.2.20131217001052.0c5bff98@resistor.net> <8D3D17ACE214DC429325B2B98F3AE712026ECD3A9B@MX15A.corp.emc.com> <6.2.5.6.2.20131218001051.0c266ed0@resistor.net> <CED70C71.119D0%dmohlenh@cisco.com> <52B1CF27.3010905@joelhalpern.com>
In-Reply-To: <52B1CF27.3010905@joelhalpern.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 18 Dec 2013 09:41:47 -0800 (PST)
Cc: "ipr-wg@ietf.org" <ipr-wg@ietf.org>
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipr-wg/>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 17:41:57 -0000
On 12/18/2013 8:36 AM, Joel M. Halpern wrote: > Dale, your interpretation is exactly the opposite of what I thought > Dave was saying. Referencing a spec normally does not and ought not > mean that the referencers IPR rules apply to the referenced > specification. They can't, since in the abstract the referencer has > no control over the IPR grants of the referenced document. > > And IETF IPR grants apply when implementing IETF RFCs, even when > those RFCs are implemented in conjunction with some other > specification. The IPR grants don't apply (as I understand it all > bets are off) if you modify the spec. > > Equally, the IETF can not insist that our IPR rules apply to a spec > we reference. I think this confuses the nature of what our disclosure rules mean. For example, they don't mean that we are affecting some other standards group. Rather they affect decision-making within the IETF. So, absent a clear consensus from legal experts who are familiar with the IETF's IPR rules, I disagree with Joel's assessment. As I just posted on rtcweb: > Normative language in a specification defines the syntax and > semantics of the thing being specified. > > It does not make much sense to handle IPR differently for normative > text that includes details by reference (citation) rather than by > inline explication. In terms of the syntax and semantics, the > specification is an integrated whole. > > If there is an legal distinction between inline normative reference, > versus citation-based inclusion, which is relevant to the > interpretation of IETF IPR rules, then some lawyers should provide > the community with expert opinions on the matter. > > Absent a clear and compelling presentation from legal experts, common > sense needs to prevail in the IETF's interpretation of its rules. > > Our rule is quite simple: participation obligates disclosure. Here's a simple example: Assume I own a patent on a component technology that has been published somewhere other than the IETF. The organization publishing that specification did not require me to divulge my intellectual property claims. I now participate in an important IETF effort that considers including the component technology, by citing it normatively. I of course, work vigorously to get the IETF to adopt the technology, but no one know that I stand to make serious money if the technology is included. Given the intent behind the IETF's IPR rules, it makes no sense to allow me to participate without divulging my IPR interest in the topic. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net -- Dave Crocker Brandenburg InternetWorking bbiw.net
- Normatively referenced specifications SM
- RE: Normatively referenced specifications Black, David
- RE: Normatively referenced specifications SM
- Re: Normatively referenced specifications Dale Mohlenhoff (dmohlenh)
- Re: Normatively referenced specifications Joel M. Halpern
- Re: Normatively referenced specifications Dale Mohlenhoff (dmohlenh)
- RE: Normatively referenced specifications Lawrence Rosen
- Re: Normatively referenced specifications Dave Crocker
- RE: Normatively referenced specifications Michael Cameron
- RE: Normatively referenced specifications Michael Cameron
- Re: Normatively referenced specifications John C Klensin
- Re: Normatively referenced specifications Joel M. Halpern
- Re: Normatively referenced specifications Dave Crocker
- Re: Normatively referenced specifications Dave Crocker
- RE: Normatively referenced specifications Michael Cameron
- RE: Normatively referenced specifications Michael Cameron
- Re: Normatively referenced specifications Dale Mohlenhoff (dmohlenh)
- Re: Normatively referenced specifications Joel M. Halpern
- RE: Normatively referenced specifications John C Klensin
- Re: Normatively referenced specifications Joel M. Halpern
- Re: Normatively referenced specifications Joel M. Halpern
- Re: Normatively referenced specifications Dale Mohlenhoff (dmohlenh)
- RE: Normatively referenced specifications Michael Cameron
- Re: Normatively referenced specifications todd glassey
- Re: Normatively referenced specifications John C Klensin
- RE: Normatively referenced specifications Black, David
- RE: Normatively referenced specifications SM
- Re: Normatively referenced specifications SM