RE: Normatively referenced specifications

John C Klensin <john-ietf@jck.com> Wed, 18 December 2013 18:37 UTC

Return-Path: <john-ietf@jck.com>
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 DD0C01AE0B4 for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 10:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level:
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] 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 qkOyipwxrHhr for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 10:37:26 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CF07B1AE0A6 for <ipr-wg@ietf.org>; Wed, 18 Dec 2013 10:37:26 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VtLzm-000DW5-QK; Wed, 18 Dec 2013 13:37:22 -0500
Date: Wed, 18 Dec 2013 13:37:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: Michael Cameron <michael.cameron@ericsson.com>, dcrocker@bbiw.net, ipr-wg@ietf.org
Subject: RE: Normatively referenced specifications
Message-ID: <993E6E5E6EA5F13E50293C74@JcK-HP8200.jck.com>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A02B88190@eusaamb101.ericsson.se>
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> <52B1DE0C.8010201@dcrocker.net> <36BAA6A693139D4BBCB37CCCA660E08A02B87FCC@eusaamb101.ericsson.se> <52B1E830.30001@dcrocker.net> <36BAA6A693139D4BBCB37CCCA660E08A02B88190@eusaamb101.ericsson.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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 18:37:29 -0000

--On Wednesday, December 18, 2013 18:29 +0000 Michael Cameron
<michael.cameron@ericsson.com> wrote:

> We are discussing 2 different things--one thread of this
> conversation is what disclosure is required (your e-mail
> below), the other thread is what IPR Policy applies to a
> submission having a normative reference (my referenced
> e-mail). 

Much as some people persist in assuming otherwise, the IETF
doesn't have an IPR policy that would touch on what
non-copyright grants or rights to implement or use something are
required.  There is only a disclosure policy.  So Dave --and I
and others-- are talking about the disclosure policy.  As far as
what licensing terms are required in referenced documents, there
is no such requirement, not because the documents are
incorporated by reference but because there or no requirements
on the primary/ referencing document either.  Just a requirement
about disclosure by any who can reasonably be expected to know
about the IPR.

   john

> -----Original Message-----
> From: Dave Crocker [mailto:dhc@dcrocker.net] 
> Sent: Wednesday, December 18, 2013 10:24 AM
> To: Michael Cameron; ipr-wg@ietf.org
> Subject: Re: Normatively referenced specifications
> 
> On 12/18/2013 10:09 AM, Michael Cameron wrote:
>> But Dave may be right when the IPR is owned by one entity
> 
> 
> This is the sort of attempt at nuance that is impractical and,
> by my reading, does not apply to the IETF's disclosure
> requirement: